Nano Cisco Unified Border Element Configuration Guide, Cisco IOS Release 15M&T

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents

Find Matches in This Book

Results

Updated:: August 1, 2013

Chapter: Hosted Scenarios Topology

Contents

Hosted Scenarios Topology
Using NanoCUBE in Hosted Scenarios (lineside)

Hosted Scenarios Topology

Using NanoCUBE in Hosted Scenarios (lineside)

Using NanoCUBE in Hosted Scenarios (lineside)

NanoCUBE supports Hosted or Centrex-based deployments, typically found in Small and Medium Enterprises and Businesses. In these deployments, the Call Control Agents are located in Service Provider network or the Cloud. FXS and SIP end-points are connected to NanoCUBE without any Call Control agent in between them. Hence, NanoCUBE performs lineside termination for endpoints in the enterprise and connects to the Service Provider network or cloud over a SIP trunk. This is achieved by supporting Centrex-certified call flows and passing through Registrations, 401/407, and SUBSCRIBE/NOTIFY type of messages.

Note

Some of the hosted deployments would need COR-related (Class of Restrictions) configurations for routing the calls from endpoint to service provider and vice-versa. Please refer to the following link: http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008019d649.shtml.

Figure 1. NanoCUBE in Hosted Call Control Scenario

Hosted Scenarios Topology

Contents
Hosted Scenarios Topology
Using NanoCUBE in Hosted Scenarios (lineside)
Hosted Scenarios Topology

Using NanoCUBE in Hosted Scenarios (lineside)

Using NanoCUBE in Hosted Scenarios (lineside)

NanoCUBE supports Hosted or Centrex-based deployments, typically found in Small and Medium Enterprises and Businesses. In these deployments, the Call Control Agents are located in Service Provider network or the Cloud. FXS and SIP end-points are connected to NanoCUBE without any Call Control agent in between them. Hence, NanoCUBE performs lineside termination for endpoints in the enterprise and connects to the Service Provider network or cloud over a SIP trunk. This is achieved by supporting Centrex-certified call flows and passing through Registrations, 401/407, and SUBSCRIBE/NOTIFY type of messages.

Note
Some of the hosted deployments would need COR-related (Class of Restrictions) configurations for routing the calls from endpoint to service provider and vice-versa. Please refer to the following link: http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008019d649.shtml.

Figure 1. NanoCUBE in Hosted Call Control Scenario

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)