System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing

Publisher

Cisco

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html

Published

unknown

Updated

unknown

Accessed

2026-09-21

HTTP status

200

License

Cisco.com terms and conditions; no-redistribution; short excerpts and locators only

Source notes citing this source

• AAR is enabled cluster-wide by setting the Automated Alternate Routing Enable service parameter to True, under Clusterwide Parameters (System - CCM Automated Alternate Routing) for the Cisco CallManager service. in context
• An AAR group name can be up to 20 alphanumeric characters and may also contain spaces, periods, hyphens and underscores. in context
• For AAR to work with hunt pilots, additional configuration is needed in the hunt pilot task flow. in context
• In Release 15, AAR reroutes calls through the PSTN or other networks when the system blocks a call for insufficient location bandwidth, so the caller does not have to hang up and redial. in context
• Block patterns prevent calls that should not be routed; Cisco's example blocks 91900XXXXXXX to stop calls to 900 services and suggests blocking area codes to prevent toll fraud. in context
• When a translation pattern rewrites dialed numbers to +E.164 before route patterns are matched, block patterns have to be written against the rewritten string and placed in a partition that the translation pattern's CSS reaches. inferred in context
• A gateway or trunk that a route pattern points to directly is not available for association with a route group. in context
• Dialed Number Analyzer lets an administrator test a Unified CM dial plan configuration before deploying it. in context
• Local route group names are added at Call Routing > Route/Hunt > Local Route Group Names, and a device pool maps the Standard Local Route Group to a real route group at System > Device Pool. in context
• Classifying a route pattern as Off-Net lets users hear a secondary dial tone that tells them the call is leaving the organisation. in context
• For a pattern such as 9.@, where 9 is the external access code, the Discard Digits option strips the pre-dot digits so the PSTN can route the call. in context
• Cisco lists completing the partition configuration task flow as a prerequisite for call routing configuration. in context
• Cisco cautions against assigning a single route filter to too many route patterns. in context
• Route groups are configured at Call Routing > Route/Hunt > Route Group, and a route group sets the order in which the system selects gateways for outgoing calls. in context
• A route list can contain only route groups and local route groups, not individual gateways or trunks. in context
• Route lists are configured at Call Routing > Route/Hunt > Route List, where route groups are added with Add Route Group and the list is saved and then applied with Apply Config. in context
• Although a route pattern can point directly to a gateway, Cisco recommends configuring route lists and route groups for flexibility and scalability. in context
• Route patterns are configured at Call Routing > Route/Hunt > Route Pattern, where the Gateway/Route List drop-down selects where matching calls are sent. in context
• Unified CM searches for a route pattern that matches an external dial string and uses it to send the call to a gateway or route list. in context
• The Route Plan Report at Call Routing > Route Plan Report shows the detailed route plan and can be saved as a CSV file. in context
• Cisco's call routing task flow orders the work as translation patterns, transformation patterns, local route groups, route groups, route lists, route filters and then route patterns. in context
• Time-of-day routing is configured by creating a time period, then a time schedule, then choosing the schedule in the partition's Time Schedule drop-down at Call Routing > Class of Control > Partition and saving. in context
• The @ wildcard matches all National Numbering Plan numbers, and a route pattern can contain only one @. in context
• In a route pattern the ! wildcard matches one or more digits 0 through 9. in context
• The dot (.) in a route pattern separates the access code from the rest of the number. in context
• In a route pattern \+ is the international escape character, used to match a leading plus sign. in context
• Square brackets enclose a range of values in a route pattern, a hyphen inside them denotes a range, and # generally marks the end of the dialing sequence. in context
• In a route pattern the X wildcard matches any single digit 0 through 9. in context
• Translation patterns are configured at Call Routing > Translation Pattern, with a partition and a Calling Search Space field among the settings. in context
• Translation patterns use the same rules and wildcards as route patterns; on a match Unified CM applies the translation and then routes the call again using the translation pattern's calling search space. in context
• Each translation pattern's combination of partition, route filter and numbering plan must be unique. in context
• Route groups are configured under Call Routing > Route/Hunt > Route Group, with a Distribution Algorithm of Circular or Top Down, and trunks are added to them as devices. in context
• A route list, configured under Call Routing > Route/Hunt > Route List, holds route groups in priority order and is saved and then applied with Apply Config. in context
• A route pattern, configured under Call Routing > Route/Hunt > Route Pattern, selects a gateway or route list in its Gateway/Route List field and is assigned a partition. in context
• A device learns its local route group through the device pool: the local route group is associated in the Local Route Group Settings section of System > Device Pool. in context
• Cisco says the local route group approach, with a single set of route patterns and gateway selection by device pool, works only for centralised call-processing deployments. in context
• Local route groups let one set of route patterns serve multiple locations: Unified CM picks the gateway from the calling device's location instead of from the route pattern. in context
• Unified CM provides a default local route group named Standard Local Route Group, and administrators can configure more. in context
• The Unified CM device pool carries Calling Party Transformation CSS and Called Party Transformation CSS fields used for call-routing number transformations. in context
• In Unified CM route patterns the @ wildcard matches all numbers the national numbering plan recognizes. For example, 9.@ routes or blocks all such numbers. in context
• The Unified CM 15 call routing task flow configures translation patterns and calling and called party transformation patterns first, then optional local route groups, route groups, route lists and route filters, then route patterns, and then optional AAR and time-of-day routing. in context
• Called party transformation patterns adapt the global form of the called party number into the local form required by the off-cluster network behind the route group devices. in context
• Calling party transformation patterns adapt the global form of the calling party number into the local form required by the off-cluster network behind the route group devices. in context
• To match a literal international escape character in a Unified CM pattern, the + must be preceded by a backslash (\+), which makes it a dialable digit rather than a wildcard. in context
• The Release 15 call routing chapter states that the local route group approach works for centralized call-deployment scenarios only. in context
• Each local route group is bound to an actual route group in the device pool, and the binding used for a call comes from the device pool of the originating device. in context
• Local route groups let a single set of route patterns serve multiple locations, with Unified CM choosing the gateway from the calling device's location rather than from the route pattern. in context
• Unified CM provides a default local route group named Standard Local Route Group, and administrators can define additional named local route groups. in context
• In Unified CM patterns an unescaped + is a wildcard that matches one or more occurrences of the preceding digit or wildcard. in context
• A route list can include the Standard Local Route Group or a custom named local route group as a member. in context
• Transformation patterns take effect by placing their partitions in a CSS set in the Calling Party Transformation CSS or Called Party Transformation CSS field of a device, device pool, gateway or trunk. in context
• A translation pattern applies its digit manipulation first and then routes the call again using the calling search space configured on the translation pattern. in context
• Unified CM local route groups let off-net calls use the gateway set by the calling device's device pool instead of the one set in the route pattern. in context
• Unified CM route filters are mandatory when a route pattern is based on a numbering plan installed with a dial plan installer file. in context
• Unified CM routes off-net calls through route patterns, which point to route lists, which contain route groups, which distribute calls to gateways and trunks. in context
• In Unified CM 15 each route pattern must have a unique combination of partition, route filter and numbering plan. in context
• Unified CM transformation patterns are assigned to a partition, and so take effect through calling search spaces that contain that partition. in context
• When a Unified CM translation pattern matches, Unified CM applies the translation and routes the call again using the calling search space configured on the translation pattern. in context
• Cisco recommends pointing route patterns at route lists and route groups rather than directly at a gateway, for routing flexibility and scalability. in context
• In Unified CM, the system matches a dial string to a route pattern and uses it to send the call to a gateway, trunk or route list; route lists hold route groups in priority order, and route groups distribute calls to gateways and trunks. in context
• In Cisco Unified Communications Manager a route pattern directs a matching dial string to a gateway or to a route list, a route list is a prioritised list of the available paths for the call, and a route group distributes the call to gateways and trunks. in context
• A Cisco Unified Communications Manager translation pattern manipulates the dialled digits first and then reroutes the call using the calling search space configured within that pattern. in context
• Called party transformation patterns let Unified CM adapt the global form of the called party number into the local form required by off-cluster networks connected to route group devices. in context
• Calling party transformation patterns let Unified CM adapt the global form of the calling party number into the local form required by off-cluster networks connected to route group devices such as gateways or trunks. in context
• In Unified CM patterns, a plain + means one or more occurrences of the preceding digit or wildcard, while \+ makes the international escape character + a dialable digit rather than a wildcard. in context
• For outbound calls, Unified CM selects the calling party transformation mask using the pre-transform calling party number (the extension assigned to the IP phone), even if the number was transformed at route pattern or route group level. in context
• The Discard Digits option can strip the pre-dot digits, such as the external access code 9 in a pattern like 9.@, so that the PSTN can route the remaining digits. in context
• When dialed digits match a translation pattern, Unified CM does not route the call to an outside entity such as a gateway; it applies the translation and then routes the call again using the calling search space configured on the translation pattern. in context
• In Unified CM Release 15, translation patterns follow the same general rules and use the same wildcards as route patterns. in context
• Each translation pattern must have a unique combination of partition, route filter and numbering plan. in context
• In Unified CM patterns, the @ wildcard matches all National Numbering Plan numbers. in context
• In Unified CM patterns, the ! wildcard matches one or more digits from 0 through 9. in context
• In Unified CM patterns, the dot (.) is a delimiter that separates an access code from the directory number and marks the boundary used by pre-dot digit removal. in context
• In Unified CM patterns, # generally identifies the end of the dialing sequence. in context
• In Unified CM patterns, the X wildcard matches any single digit from 0 through 9. in context
• Transformation patterns are placed in route partitions and reach calls through calling search spaces assigned in the device, device pool, gateway or trunk configuration. in context
• Unified CM called party transformation patterns turn the global form of a called number into the local form an off-cluster gateway or trunk requires. in context
• In Unified CM a route list is a prioritised list of paths for a call, and a route group distributes the call to gateways and trunks. in context
• Unified CM matches an external dial string against configured route patterns and sends the call to the gateway or route list that the matching pattern names. in context
• The Unified CM call routing task flow runs translation patterns and transformation patterns, then optional route groups, route lists and route filters, then route patterns. in context
• A Unified CM user sends a caller into Five9 by transferring to a number that is assigned as DNIS on a running inbound campaign, reached through a Unified CM route pattern pointing at either the PSTN gateway or the SIP trunk toward the Five9-facing SBC. inferred in context
• The Unified CM Release 15 call routing chapter includes a Troubleshooting with Dialed Number Analyzer section for checking how dialed digits route. in context
• In Unified CM a route group prioritises the gateways used for outgoing calls, and a route list places route groups in priority order. in context
• A Unified CM route pattern sends matching calls to the destination selected in its Gateway/Route List drop-down. in context
• Unified CM route patterns send matching calls to a gateway, trunk or route list. Cisco recommends route lists and route groups over pointing a route pattern directly at a device. in context
• Cisco says a Unified CM route pattern can point directly to a gateway but recommends configuring route lists and route groups instead. in context
• In Unified CM a route group sets the selection order of devices, a route list orders one or more route groups and must contain at least one, and route patterns route or block calls. in context
• A Unified CM route list can contain only route groups and local route groups, and must contain at least one route group. in context
• Unified CM call routing is built as route groups (device selection order), then route lists (route group order), then route patterns that direct matching digit strings to a gateway, trunk or route list. in context
• When a Unified CM translation pattern matches, the call is not routed to an outside entity. Unified CM applies the translation and then routes the call again. in context

Cite this source record

APA

WarmTransfer. (2026, September 21). System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cucm-sysconfig-15-call-routing

BibTeX

@misc{warmtransfer-cisco-cucm-sysconfig-15-call-routing,
  title  = {System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cucm-sysconfig-15-call-routing},
  note   = {Cisco, accessed 2026-09-21}
}