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.
Within a site, users can make calls to their neighbors by using only the extension part of their directory number. Although the lines are registered with SLC + extension number (or simply extension in case of flat dial plan), when the user dials only a subset of this length of digits (extension), the dial plan treats the call as an intrasite call, and prefixes the called number with the SLC to route the call. The calling party display is SLC+Extension or simply extension in the case of flat dial plan.
Intrasite calls are made by dialing only the extension of the other phone. For Intrasite call routing, the signaling stays within the Unified Communications Manager cluster. Media flows directly between the two Cisco Unified IP Phones.
Cisco HCS supports multiple sites with overlapping extensions and intersite calling by dialing the site location codes, and supports the following dialing capabilities:
Variable length extensions between sites with no postdialing delay (PDD) caused by timeout (that is, there should be a positive translation pattern match on a given extension length per site so that the call completes without delay).
Intersite dialing should be provided between Unified Communications Manager controlled Unified IP Phones, Cisco TDM PBX controlled phones, and Cisco Unified Communications Manager Enterprise (CME)/UC500 controlled phones.
Intersite calls are made by dialing <Site Location Code><Extension> or simply the extension in case of flat dial plan. When the user dials a directory number of another user, the leaf cluster first examines the site code, and determines if the site code is for a site on the same cluster or another cluster. If the site is on the same cluster, the call is routed to the correct location and delivered to the phone.
If the internal DN is for a site on a different cluster, the call is routed to the correct cluster over Intercluster Trunk (ICT).
When a user dials an Intrasite or an Intersite number in the same cluster, the dialed digits match the extension (same as internal DN) defined in the InterSiteRoutingPT. These extensions are added to the InterSiteRoutingPT when the extensions (phones) are registered.
Unified Communications Manager Data Element | Unified Communications Manager Data Element Value | Unified Communications Domain Manager Transaction | Description |
---|---|---|---|
Line CSS DN=2221111 Dials 3331234 |
Local24HrsEnh-CSS<site id> |
AddLocation |
CSS based on the Class of Service assigned to the Line/DN |
Partition |
InterSiteRoutingPT |
InitIPPBX |
Partition where DN and devices are associated |
For the Shared Instance (G3) Dial Plan, internal calls are routed based on the Line CSS which contains the customer-specific site partition. All the DNs for a customer reside in this partition.
Calling Search Space | Partition | Transaction | Description |
---|---|---|---|
Line CSS | Site | AddCustomer | Internal DNs for a customer are provisioned in the customer-specific “Site” partition. The Site partition is created by the “AddCustomer” transaction. Each line-specific CSS contains the customer-specific Site partition which allows for extension dialing within a customer. |
When an aggregation layer is used to route a call, it is also referred to as Central Breakout (CBO). CBO provides centralized trunks toward the aggregation device. In the following figure, the aggregation layer comprises only a Session Border Controller (SBC).
In the following figure, the aggregation layer comprises SBC and Cisco PGW or Cisco vPGW. The interconnection to PSTN can be a SIP trunk toward the PSTN or TDM trunks toward the PSTN.
In addition to centralized breakout using the aggregation layer, customers can also connect to PSTN through a local gateway. This local gateway is also referred to as Local Breakout (LBO). For LBO, each site or location requiring LBO is equipped with a local gateway. When a local gateway is added to a location, the administrator defines the call types that can be routed through the local gateway. For example, you can select national calls to be routed through the local gateway. By default if the call type is not selected to be routed by local gateway, the call is routed by CBO.
To understand the Cisco HCS Dial Plan Model, you must understand call routing in terms of the data flow within the Cisco Unified Communications Manager. Several call types are used as examples to understand the Cisco HCS call routing architecture.
Cisco Unified Communications Domain Manager architecture uses class of service to assign calling restrictions to an end user. The class of service is mapped by Cisco HCS Dial Plan Model to a calling search space and partitions that are understood by Cisco Unified Communications Manager. The following class of service/calling search spaces are supported by Cisco HCS:
The following table lists the partitions supported by the Cisco HCS Dial Plan Model:
Note | The following table is based on HCS Software Release 8.6(2) and may not include all partitions. Refer to the latest dial plan model for a complete list of available partitions. |
InterSiteRouting partition - For customer that owns the cluster
Partition for Handling National Dialing except for Emergency
Partition for Service Calls - for example 100 123 1471 except for Emergency
Partition for Handling National Dialing except for Emergency
Partition for Service Calls - for example 100 123 1471 except for Emergency
Emergency calls Partition for a route pattern to handle +02 calls
Site Partition where all the devices within a site are registered
Partition for Handling Short Code Routing - Customer Level (for example DP customization)
Partition for Handling Short Code Dialing - Customer Level (for example DP customization)
Partition for Handling Short Code Dialing - Location Level (for example DP customization)
Partition for Handling Short Code Dialing - Location Level (for example DP customization)
Partition for Handling Short Code Dialing - Location Level (for example DP customization)
BlockAllCF-CSS
AddLocation§
Call Forwarding CSS to disallow Call Forwarding
CPUG-CSS
AddLocation§
CSS used for Call Pickup Group feature
IMSClientDevRouting-CSS**
AddLocation§
CSS used to route PSTN calls received over inbound trunks from IMS networks
IMSClientDevice-CSS**
AddLocation§
CSS associated to the inbound trunk from IMS networks
** IMS is not available to Shared Instance Dial Plan (G3) subscribers.
§All partitions that are created using the AddLocation transaction are appended with the Location ID. Location ID is an internal number generated by Cisco Unified Communications Domain Manager.
When a user dials an extension within the site, the dialed digits match the intrasite translation pattern. Cisco Unified Communications Manager prefixes SLC to the dialed digits converting it to a DN and routes the call to IncomingToSite-CSS. The following calling search spaces and partitions are involved in the call:
Note | The following table applies to the Generic Dial Plan (G1) only. |
Unified CM Data Element |
|||
---|---|---|---|
SLC=822, DN=8221111 dials 1234 |
CSS based on the Class of Service assigned to the line or DN. <site id> is assigned by Unified Communications Domain Manager |
||
Partition that contains translation pattern to handle intrasite calls from the line |
|||
IntraSite<siteid>=[^#FIRSTSLCDIGIT##EX T#]#SITEMASKMINUSONE# TP=[^89]xxxpfx=822 SLC,after prefixing SLC, called # = 8221234 calling # = 8221111 |
Translation pattern for intrasite calls. Cisco Unified Communications Manager prefixes dialed number with SLC and re-routes the call to the IncomingToSite CSS |
||
CSS that contains the partition where all devices are configured |
|||
called # = 8221234 |
When a user dials an intersite number that is in the same cluster, the dialed digits match the intersite translation pattern. The call is then routed to IncomingToSite-CSS based on the dialed SLC. The following calling search spaces and partitions are involved in the call:
Note | The following table applies to the Generic Dial Plan (G1) only. |
SLC=822, DN=8221111 dials 8331234 |
|||
Intersite routing partition that contains translation patterns to route call to the correct IncomingToSite CSS for directory number that resides in the same cluster as in this example and route patterns to route call to other clusters if the directory number is not local |
|||
#SITECODE##SITEMASK# TP=822XXXX |
|||
CSS that contains the partition where all devices are configured |
|||
called # = 8221234 |
When an inbound PSTN call is received at the aggregation layer, the called number is converted to an E.164 format and sent to the Cisco Unified Communications Manager. Cisco Unified Communications Manager performs an E.164 to a DN lookup and converts the called number to an internal DN. The following calling search spaces and partitions are involved in the call:
Called # = +19722221111 |
|||
Partition containing all the DID to DN mapping translation patterns. |
|||
E.164= +19722221111 maps to DN=8221111 |
|||
Intersite routing partition that contains translation patterns to route call to the correct IncomingToSite CSS for directory number that resides in the same cluster as in this example and route patterns to route call to otherclusters if the directory number is not local |
|||
TP=822xxxx TP=833xxxx |
|||
CSS that contains the partition where all devices are configured |
|||
DN=8221111 DN=8221234 calling #=+12123455555 |
Unified CM Data Element |
Unified CM Data Element Value |
Unified Communications Domain Manager Transaction |
Description |
---|---|---|---|
Trunk |
IncomingFromAggreg |
InitIPPBX |
CSS associated with the aggregation layer trunk |
Partition |
E.164LookUp |
InitlPPBX |
All the +E.164 are provisioned in this global partition. This partition contains Translation Patterns that converts +E.164 numbers to internal DN. The Translation Pattern points to the per-customer InterSiteRoutingCSS. |
CSS |
InterSiteRoutingCSS |
AddCustomer |
Per-customer InterSiteRoutingCSS. The Translation Patterns in the e164Lookup partition points to this CSS as the next CSS. It contains the InterSiteRoutingPT partition which contains a wildcard (!) Translation Pattern pointing to IncomingToSite-CSS. |
CSS |
IncomingToSite-CSS |
AddCustomer |
Per-Customer IncomingToSite-CSS. Contains per-customer Site Partition. |
Partition |
Site |
AddCustomer |
The Site partition contains DN corresponding to the received +E.164 number. |
Outbound PSTN calls are converted to E.164 format before routing them toward the aggregation layer.
The following calling search spaces and partitions are involved in the call:
Note | The default transformation CSS when using the ToAggregation trunk model type is the CallingT2AggregCSS. |
SLC=822,CC=1, NATCODE=972, FN=2221111 dials 912123455555 |
CSS based on the Class of Service assigned to the Line or DN (see Note below) |
||
AllowNatl24Hr-1 |
|||
TP=9.1[2-9]XX[2-9]XXXXXX remove 9 and prefix +Called #=+12123455555 calling #=+19722221111 |
Translation pattern for a national call in US. The national number is converted to an E.164 number |
||
RouteSelCSS-1 |
|||
RouteSelPT-1 |
|||
NatlCall-#COUNTRY#=\+#COUNTRY#.! NatlCall-1RP: \+1.! |
Per-country route pattern for a national call. Example for a national call in United States |
||
PSTNNAT1 |
|||
Called #=+12123455555 calling #=+19722221111 |
Note | When all phones have DID numbers at a customer location, but you want only the main number for the location to show when an outbound call is made, you can map a DN to DID in one of two ways: 1) use the External Calling Phone Mask and ensure that the route pattern is provisioned through GSIP with Use External Phone Mask, or 2) configure the Calling Transformation CSS on the trunk. Make sure that you use either External Calling Phone Mask, or Calling Transformation CSS, but not both. If both are set, the Calling Transformation CSS takes precedence. Also, note that if you are using External Calling Phone Mask and it is not using Plus E.164 numbers, make sure the cluster is not supporting multicountry locations (in other words, all locations must be in the same country) or you will experience problems with Call Forward. |
Note | For customer-to-customer calls within the same cluster using the Shared Instance Dial Plan (G3): Even if two customers are on the same cluster, the routing requirements are that the calls from one customer should be routed to aggregation toward the PSTN, and then the calls should be routed back as inbound PSTN calls. |
Outbound service calls are prefixed with +01#COUNTRY# before routing it toward the aggregation layer. The prefix +01 identifies the call as a service call to the routing logic. The prefixed digits +01#COUNTRY# are removed at the aggregation layer and the call is routed toward PSTN as dialed. The following calling search spaces and partitions are involved in the call:
SLC=822, NATCODE=972 dials 9611 |
CSS containing intersite routing partition (see Note in Outbound PSTN Call Through Aggregation) |
||
AllowSVCstd-1 |
|||
Remove Predot and Prefix+011 TP=9.[2-8]11 Called #=+011611 |
Translation pattern for a service call in United States. The dialed number is prefixed with +011 |
||
RouteSelCSS-1 |
|||
RouteSelPT-1 |
|||
SERVICE1 |
|||
Called #=+011611 |
Trunk toward aggregation for a service call. +011 is stripped off at aggregation. |
The following call flow is to route an emergency call through aggregation. The table in this section is for the North American Dial Plan. Cisco Unified Communications Manager uses Device Calling Search Space instead of Line Calling Search Space to translate and route an emergency call. When the call matches the translation pattern for an emergency call, the routing logic prefixes the emergency number with +02#COUNTRY# digits. Prefix +02 identifies the call as an emergency call to the routing logic. Prefixed digits +02#COUNTRY# are removed at the aggregation layer.
The calling party number is prefixed with LRID. Before the call is routed, Cisco Unified Communications Manager checks if the calling party is within the home location or if the user is remotely logged in. If the caller dials an emergency call from the home location, then the caller's DID number is conveyed in the call. If the caller calls remotely, the site published number is conveyed in the call.
SLC=822, CC=1, NATCODE=972 FNN=2221111, dials 9911 |
Device CSS. For emergency calls, Cisco Unified Communications Manager uses Device CSS and not Line CSS |
||
US-Allow-EmerCalls911<site id> Remove 9 and prefix +021 Called #=+021911 Calling Party Prefix=*#LRID# |
Translation pattern for an emergency call. The called # is prefixed with +02 and country code |
||
EMERGENCY1 |
|||
Partition containing transformation pattern for an emergency call |
|||
Transformation pattern for an emergency call (see Note in Outbound PSTN Call Through Aggregation) |
When an inbound PSTN call is received at the local gateway, the called number is converted to an E.164 format and sent to the Cisco Unified Communications Manager. Cisco Unified Communications Manager performs an E.164 to DN lookup and converts the called number to an internal DN. The following calling search spaces and partitions are involved in the call:
Called # = +19722221111 |
When an inbound PSTN call is received at the local gateway, the called number is converted to E.164 and sent to the Cisco Unified Communications Manager. |
||
Partition |
AddPlus |
AddLocationLocalGateway |
Partition to convert called number to E.164 number |
Translation Pattern |
#EXT##NAT#.! |
AddLocationLocalGateway |
Removes PSTN prefix and National Prefix and adds +CC to the called number. The call is rerouted using IncomingFromLGW-CSS. |
Partition containing all the DID to DN mapping translation patterns. Another possibility is to have a per-country partition instead of a global partition |
|||
E.164= +19722221111 maps to DN=8221111 |
|||
Partition containing all the DID-to-DN mapping translation patterns. Another possibility is to have a per-country partition instead of a global partition |
|||
TP=822xxxx TP=833xxxx |
|||
DN=8221111 DN=8221234 calling #=+12123455555 |
Partition containing all the DID-to-DN mapping translation patterns. Another possibility is to have a per-country partition instead of a global partition. |
Call Forwarding is very similar to a line-originated call, except that the Call Forwarding-related CSS is used for Call routing. There are no Call Forwarding-specific CSSs, but any of the line CSSs can be assigned to Call Forwarding features. If the call is forwarded to PSTN, the call will be routed using Local Breakout or Central Breakout, depending on the Translation and Route Patterns provisioned in the Cisco Unified Communications Manager.
An outbound PSTN call is converted to E.164 format before routing it toward the local gateway. The following calling search spaces and partitions are involved in the call:
US-Allow-Natl24Hr<site id> =#EXT#.1[2-9]XX[2-9]XXXXXXTP =9.1[2-9]XX[2-9]XXXXXX remove 9 and prefix + Called #=+12123455555 Calling #=+19722221111 |
Translation pattern for a national call in United States. The national number is converted to an E.164 number |
||
NatlCall-#COUNTRY#<site id>=\+#COUNTRY#.! RP=\+1.! |
|||
Called #=+12123455555 Calling #=+19722221111 |
An Outbound Service call is prefixed with +01#COUNTRY# before routing it toward the local gateway. The prefix +01 identifies the call as a service call to the routing logic. The prefixed digits +01#COUNTRY# are removed at the local gateway and the call is routed toward PSTN as dialed. The following calling search spaces and partitions are involved in the call:
SLC=822, CC=1, NATCODE=972, FNN=2221111 dials 9611 |
|||
TP=9.[2-8]11 Called #=+011611 |
Translation pattern for a service call in the United States. The national number is converted to an E.164 number |
||
RP=\+011.! |
|||
Called #=+011611 |
The following call flow is to route an emergency call by Local Breakout (LBO). The table in this section is for the United States. The Cisco Unified Communications Manager uses Device Calling Search Space instead of Line Calling Search Space to translate and route an emergency call. When the call matches the translation pattern for an emergency call, the routing logic prefixes the emergency number with +02#COUNTRY# digits. Prefix +02 identifies the call as an emergency call to the routing logic. Prefixed digits +02#COUNTRY# are removed at the local gateway.
SLC=822, CC=1, NATCODE=972, FNN-2221111 dials 9911 |
Device CSS. For emergency call, Cisco Unified Communications Manager uses Device CSS and not Line CSS. |
||
US-Allow-EmerCalls911<site id> remove 9 and prefix +021 Called #=+021911 Calling Party Prefix=*#LRID# |
Translation pattern for an emergency call. The Called # is prefixed with +02 and country code. |
||
Partition containing Transformation pattern for an emergency call |
|||
The Cisco HCS Dial Plan supports Intercluster calls over SIP-based Intercluster Trunks (ICT). In addition, the Cisco HCS Dial Plan also supports provisioning toward unmanaged PBXs. The following protocols toward unmanaged PBXs are supported:
Intersite routing partition contains translation patterns to route the call to the correct IncomingToSite CSS if the call is intracluster and contains route patterns to route the call to the correct cluster if the call is intercluster. |
|||
Route patterns for Intercluster or intersite calls toward unmanaged PBX |
|||
Route list for Intercluster or intersite calls toward unmanaged PBX |
|||
Route group for Intercluster or Intersite calls toward unmanaged PBX |
|||
— | ||||
— | ||||
— | ||||
An unmanaged Location is a customer location that resides on a third-party PBX not directly managed by Cisco Unified Communications Domain Manager as part of the HCS solution design. Unmanaged locations provide the context to allow H323 and SIP trunks to be configured from a Unified CM cluster to these locations. SLCs can then be assigned to these locations for intersite routing and E164 numbers and internal extensions can be assigned. ENT translation patterns can also be configured to route calls to these Unmanaged locations. The Unmanaged-PBX location reference bulk loader provides a worked example for:
Note | Internal Extensions and PSTN Numbers can also be assigned to an Unmanaged location as for a Managed location. IOS Local Gateway ports can also be assigned to Unmanaged locations. |
The following calling search spaces and partitions are involved in a call to voicemail:
Unified CM Data Element | Unified CM Data Element Value | Unified Communications Domain Manager Transaction | Description |
---|---|---|---|
CSS
Local24HrsEnh-CSS822 |
Local24HrsEnh-CSS<site id> | AddLocation | Call Forwarding CSS based on the Call Forwarding Type assigned to the line or DN |
Partition | AllowVMCalls | AddLocation | Partition containing Route Pattern toward Cisco Unity |
Route Pattern | #VMSLC##CMEXTENSION# | AddLocationVM | Route Pattern toward Cisco Unity |
Route List | RL-UNITY#VMCPID# | Route List toward Cisco Unity | |
Route Group | RG-UNITY#VMCPID# | Route Group | |
Trunk | VMAIL-#VMCPID# | Trunk toward Cisco Unity |
The following calling search spaces and partitions are involved in a call from voicemail:
Unified CM Data Element | Unified CM Data Element Value | Unified Communications Domain Manager Transaction | Description |
---|---|---|---|
CSS | IncomingFromUnity | InitlPPBX | Call Forwarding CSS based on the Call Forwarding Type assigned to the line or DN |
Partition | InterSiteRoutingPT | InitIPPBX | Partition containing Route Pattern toward Cisco Unity |
Translation Pattern | InterSite<site id>#SITECODE##SITEMASK# | Translation patterns for Intersite calls | |
CSS | IncomingToSite-CSS<site id> | CSS that contains the partition where all devices are configured | |
Partition | Site<site id> | Site partition where DN and devices are associated |