Study guide
4.2 Route Patterns, Route Groups & Route Lists
Cisco 350-801 CLCOR CCNP/CCIE Collaboration Core v2.0
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Collaboration Architecture, Deployment Models, Sizing & Upgrades
1.1 Collaboration Architecture & Deployment Models 1.2 Capacity Planning, Sizing & Bandwidth Considerations 1.3 High Availability, Redundancy & Disaster Recovery 1.4 Cisco Unified CM Cluster Upgrade Process
2 Chapter 2: Edge Architecture, Security & Network Services
2.1 Collaboration Edge Architecture: CUBE & Expressway 2.2 Security Protocols & PKI: SSO, OAuth, TLS & SRTP 2.3 Network Infrastructure Services: DNS, NTP, DHCP & LDAP
3 Chapter 3: Protocols, Codecs & Endpoint Provisioning
3.1 SIP Signaling Architecture & Call Flows 3.2 Session Description Protocol (SDP) & Early Offer vs. Delayed Offer 3.3 Audio/Video Codecs & DTMF Relay 3.4 Endpoint Deployment, Onboarding & Troubleshooting
4 Chapter 4: CUCM Dial Plan Fundamentals & Digit Analysis
4.1 Partitions and Calling Search Spaces (CSS) 4.2 Route Patterns, Route Groups & Route Lists 4.3 Translation Patterns, Transformation Patterns & Digit Manipulation 4.4 Globalized Call Routing & Local Route Group (LRG)
5 Chapter 5: Advanced Call Control, Call Routing & User Management
5.1 Call Admission Control (CAC), Locations & AAR 5.2 Toll Fraud Prevention & Call Privileges 5.3 CUCM User Management, LDAP Integration & RBAC 5.4 Administrative XML (AXL) API & Dial-Plan Troubleshooting Tools
6 Chapter 6: Cisco Unity Connection & Voicemail Integration
6.1 Cisco Unity Connection Architecture & SIP Integration 6.2 Mailbox Provisioning, User Templates & Class of Service 6.3 Message Waiting Indication (MWI) & Troubleshooting 6.4 Call Handlers & Directory Handlers
7 Chapter 7: IOS XE Voice Gateways, CUBE & Media Resources
7.1 Cisco IOS XE Voice Gateways & Dial Peers 7.2 Voice Translation Rules and Translation Profiles 7.3 Cisco Unified Border Element (CUBE) Configuration & Redundancy 7.4 IOS XE Media Resources & DSP Management
8 Chapter 8: Webex Architecture, Control Hub, Meetings & Messaging
8.1 Webex Suite Overview & Control Hub Architecture 8.2 Cloud Identity Management, SCIM & Directory Connector 8.3 Webex Developer Platform & APIs 8.4 Configuring Webex Cloud Meetings 8.5 Configuring Webex Cloud Messaging
9 Chapter 9: Webex Calling Routing, Permissions & PSTN Connectivity
9.1 Webex Calling Architecture, Locations & Number Management 9.2 Webex Calling Routing, Trunks & Dial Plans 9.3 Webex Calling Call Routing Process & Translation Patterns 9.4 Webex Calling Toll Fraud Prevention, Call Permissions & Operating Modes 9.5 PSTN Connectivity: Cloud-Connected PSTN (CC-PSTN) & Cisco Calling Plans 9.6 Webex Calling Local Gateway (LGW) Architecture & Configuration
10 Chapter 10: Webex Hybrid Services & Cloud Connected UC
10.1 Cloud-Connected UC (CCUC) Architecture & Telemetry 10.2 Webex Hybrid Calendar & Hybrid Directory Services 10.3 Webex Video Mesh & Hybrid Data Security
11 Chapter 11: Media Quality, QoS Engineering & Troubleshooting
11.1 Real-Time Media Characteristics & Impairments 11.2 QoS Classification, Marking & Trust Boundaries 11.3 Low Latency Queuing (LLQ) Configuration on Cisco IOS XE 11.4 Troubleshooting Media Quality & Call Failures
4.2 Route Patterns, Route Groups & Route Lists
Key Takeaways Explain This Topic AI
Route Patterns define external dialed number strings using wildcards such as X, N, [0-9], !, and the NANP macro @, directing call traffic to Route Lists, Gateways, or Trunks.
Urgent Priority forces CUCM to terminate the interdigit timeout (T.302 timer, default 15,000 ms) immediately upon an exact pattern match, but will truncate dialing if applied to shorter overlapping patterns.
Discard Digits Instructions (DDIs) like PreDot strip prefix access codes and delimiters before delivering dialed digits to external PSTN circuits.
Route Groups organize voice gateways and trunks using Top Down (sequential failover) or Circular (load balancing) distribution algorithms.
Route Lists aggregate multiple Route Groups into an ordered hierarchy to enforce path failover and apply route-specific digit transformations.
Last updated: October 2026
4.2 Route Patterns, Route Groups & Route Lists
Outbound call routing in Cisco Unified Communications Manager (CUCM) directs dialed numbers from internal endpoints to external Public Switched Telephone Network (PSTN) gateways, Session Border Controllers (such as Cisco Unified Border Element, or CUBE), and inter-cluster SIP trunks. The routing hierarchy is structured into three tiered elements: Route Patterns , Route Lists , and Route Groups , complemented by Call Hunting mechanisms for incoming call distribution.
1. Route Patterns and Dial Plan Wildcards
A Route Pattern defines a string of digits and wildcards that match a dialed telephone number. Unlike Translation Patterns, which rewrite digits and restart digit analysis internally, a Route Pattern represents an egress routing decision, pointing directly to a Route List, a Gateway, or a SIP Trunk.
Wildcard Syntax Reference
CUCM digit analysis supports a comprehensive set of wildcards and special characters for constructing precise dial patterns:
Wildcard Character Range / Definition Example Pattern Matched String Example Common Architectural Use Case
X Any single digit from 0 to 9 9.[2-9]XXXXXX 95551234 North American 7-digit local dialing.
N Any single digit from 2 to 9 9.NXXXXXX 92551234 Excludes numbers starting with 0 (operator) or 1 (toll prefix).
[ ] Any single digit within the bracketed range or set [2-5]XXX 2100 , 3550 , 5999 4-digit internal extensions restricted to specific numerical blocks.
! Variable-length repeat wildcard; matches 1 or more digits 9.011! 9011442079460123 International dialing where digit lengths vary across global destinations.
? Matches zero or more occurrences of the preceding digit or wildcard 91X? 91 , 912 , 9123 , ... Variable-length matching; like ! , it makes CUCM wait for the interdigit timeout.
\+ A literal plus sign (escaped); an unescaped + means one or more occurrences of the preceding digit or wildcard \+1[2-9]XX[2-9]XXXXXX +14085550100 Globalized +E.164 dial plans
. Delimiter character for Discard Digits Instructions (DDI) 9.1[2-9]XX[2-9]XXXXXX 914085550100 Marks the boundary where leading access codes are stripped via PreDot .
@ North American Numbering Plan (NANP) macro 9.@ Any valid NANP number Built-in Cisco macro expanding to all North American dialed numbering rules.
^ Inside brackets, excludes the listed digits [^0-1]XXX 2345 Any 4-digit string whose first digit is not 0 or 1
# Ends digit collection when dialed; must be the last character of a pattern 9.011!# 9011442079460123# Lets international callers skip the interdigit timeout
2. Urgent Priority and Interdigit Timeout (T.302) Mechanics
When a user enters digits off-hook on a Cisco IP phone without pressing # or a "Call" softkey, CUCM receives digits one-by-one via Keypad Markup Language (KPML) or Skinny Station Protocol. As each digit arrives, CUCM determines whether the dialed string matches an active pattern.
The T.302 Interdigit Timer
If the entered string matches a pattern, but longer matching patterns exist in the dial plan, CUCM cannot immediately route the call. It starts the T.302 Interdigit Timeout timer (default: 15,000 milliseconds , or 15 seconds) to wait for subsequent digits:
If the user dials another digit before T.302 expires, the timer resets, and digit analysis continues.
If the user enters no further digits and T.302 expires, CUCM routes the call based on the best matching pattern accumulated so far.
If the user dials # , CUCM terminates dialing immediately without waiting for T.302.
Urgent Priority Behavior
The Urgent Priority setting is a checkbox available on Route Patterns, Translation Patterns, and Directory Numbers. When enabled, Urgent Priority instructs the Digit Analysis engine to halt the T.302 interdigit timer immediately upon reaching an exact match , routing the call without waiting for potential longer patterns. Scenario: Emergency Calling vs. Variable-Length International
- -----------------------------------------------------------------------
- Pattern A: 911 (Urgent Priority = ENABLED)
- Pattern B: 9.! (Variable-length international, e.g., 9011...)
- Caller Dials: 9 -> 1 -> 1
- Result: Because Urgent Priority is ENABLED on 911, CUCM terminates digit
analysis instantly and dispatches the call to the emergency gateway.
- If Urgent Priority were DISABLED, CUCM would pause for 15 seconds
- (T.302) after the second '1' to see if the caller intended to dial
a longer string matching 9.!
Architectural Pitfall: Premature Digit Truncation
Applying Urgent Priority incorrectly can severely disrupt internal dial plans. For example, consider an enterprise with both 4-digit extensions ( 3XXX ) and 5-digit extensions ( 3XXXX ). If an administrator enables Urgent Priority on the 3XXX pattern, callers can never dial 5-digit extensions starting with 3 . As soon as the fourth digit is entered, CUCM matches 3XXX , immediately terminates digit analysis, and routes the call to the 4-digit target, truncating the fifth digit.
3. Discard Digits Instructions (DDIs)
Public carriers expect standard numbers (such as 10-digit local or 11-digit national) without internal enterprise steering digits (such as an external access code 9 ). Discard Digits Instructions (DDIs) remove these steering digits at the egress boundary before the call is delivered to a Route Group or Gateway.
Standard Discard Digits Instructions
- DDI Name Action Performed Example Route Pattern Dialed Number Sent to PSTN / Gateway
- PreDot Strips all digits up to and including the dot ( . ) 9.1[2-9]XX[2-9]XXXXXX 914085550199 14085550199
- PreDot Strips access code and delimiter 9.[2-9]XXXXXX 95551234 5551234
- PreAt Strips access code preceding the @ macro 9.@ 912125550123 12125550123
- Trailing-# Removes the end-of-dialing # 9.@ 901181910555# 901181910555
- NoDigits Removes no digits 9.@ 919728135000 919728135000
- <None> Preserves the entire dialed string intact \+1[2-9]XX[2-9]XXXXXX +14085550100 +14085550100
In addition to DDIs, administrators can configure Prefix Digits (Outgoing Calls) to prepend digits (such as prepending an international carrier access code 011 ) after the DDI has stripped the designated prefix.
4. Route Groups and Distribution Algorithms
A Route Group is an ordered, logical aggregation of one or more physical voice gateways or trunks (such as Cisco Unified Border Elements, MGCP gateways, or SIP trunks). Route Groups do not contain dial patterns; they represent pools of egress hardware interfaces.
Distribution Algorithms
When multiple gateways or trunks are placed inside a Route Group, CUCM distributes outbound calls across those devices using one of two distribution algorithms:
Top Down :
CUCM always attempts to route calls out the first device listed at the top of the Route Group.
If the first device is busy (all DS0 channels or SIP call legs exhausted) or unreachable, CUCM rolls over to the second device, and so forth down the list.
Use Case : Preferred when one egress path has lower carrier costs or higher quality (e.g., primary fiber SIP trunk over an ISR 4451, failing over to a secondary T1/E1 PRI circuit).
Circular (Round-Robin) :
CUCM distributes calls evenly across all operational gateways in the Route Group by cycling through the list in a round-robin sequence.
Each new call setup request is offered to the gateway immediately following the device that received the preceding call.
Use Case : Preferred when distributing load across multiple equal-cost Session Border Controllers or parallel SIP trunks to maximize hardware utilization and prevent bottlenecking.
5. Route Lists and Path Failover Logic
A Route List is an ordered collection of Route Groups. While a Route Group selects the physical gateway, a Route List establishes the hierarchical failover strategy across different Route Groups and applies path-specific digit manipulations. [Route Pattern: 9.1[2-9]XX[2-9]XXXXXX]
- |
- v
- [Route List: RL_Outbound_WAN]
- |
- +---> Route Group 1: RG_HQ_CUBE_SIP (Primary path - SIP)
- | |---> CUBE-01 (HQ)
- | |---> CUBE-02 (HQ Backup)
- |
- +---> Route Group 2: RG_HQ_PRI_GATEWAY (Secondary path - T1 PRI)
- |---> ISR4331-MGCP-PRI
- Failover Conditions and PSTN Cause Codes
CUCM automatically advances to the next Route Group in a Route List under specific network and signaling conditions:
Circuit Congestion / Busy : The gateway returns ISDN Cause Code 34 ( Circuit/Channel Congestion ) or SIP 503 Service Unavailable .
Temporary Failure : The gateway returns ISDN cause 41 ( Temporary Failure ), which SIP devices typically signal as 503 Service Unavailable .
Unreachable Interface : Layer 3 connection failure or SIP OPTIONS keepalive failure on the trunk.
Critical Distinction : If a carrier rejects a call due to an invalid dialed number (e.g., ISDN Cause Code 1 Unallocated/Unassigned Number or SIP 404 Not Found ), CUCM does not fail over to the next Route Group (the Stop Routing on Unallocated Number Flag service parameter, True by default). An unallocated number indicates the destination does not exist; retrying the same invalid number across alternate carrier circuits would needlessly waste PSTN resources.
Path-Specific Digit Manipulation
Route Lists allow administrators to configure digit transformations on a per-Route Group member basis . For example, if Route Group 1 routes over a SIP trunk expecting standard 11-digit numbers ( 14085550100 ), while Route Group 2 routes over an older legacy PBX expecting 7 digits ( 5550100 ), the Route List can apply PreDot on Route Group 1 and a Called Party Transform Mask stripping the area code on Route Group 2.
6. Call Hunting Architecture
Call Hunting distributes incoming calls to a designated group of internal directory numbers when a single shared department number is dialed (such as Technical Support, IT Helpdesk, or Billing).
Hunting Component Hierarchy
Call hunting in CUCM is constructed using three layered objects:
Hunt Pilot : The virtual telephone number (with an assigned partition and CSS) dialed by callers (e.g., extension 4500 ). The Hunt Pilot points to a single Hunt List.
Hunt List : An ordered collection of one or more Line Groups. It defines the sequence in which different agent tiers are engaged.
Line Group : An ordered collection of individual Directory Numbers (endpoints) that ring according to a selected distribution algorithm.
Line Group Distribution Algorithms
Distribution Algorithm Hunting Mechanism Optimal Enterprise Use Case
Top Down Always begins with the first directory number listed in the Line Group. Moves down sequentially only if earlier members are busy or do not answer. Seniority-based routing or tiered dispatch desks where senior staff receive calls first.
Circular Remembers the last answered extension; offers the next incoming call to the member immediately following the last answering member. Equal distribution across shift workers when active idle time tracking is not required.
Longest Idle Time Dynamically tracks line state; routes incoming calls to the agent who has been off the phone (idle) for the longest elapsed duration. High-volume call centers and technical support desks to ensure fair, uniform workload distribution.
Broadcast Simultaneously rings every directory number in the Line Group at the same time. The first agent to answer claims the call. Emergency response teams, executive admin pools, and urgent dispatch centers.
Hunting Timers and Native Queuing
RNA Reversion Timeout : Configured on the Line Group, the time (default 10 seconds ) that CUCM rings a member before treating the attempt as Ring No Answer (RNA) and advancing to the next member.
RNA Reversion Destination : The fallback destination (such as a general voicemail box or external answering service) if all members across all Line Groups fail to answer.
Native Call Queuing : Built-in CUCM capability allowing callers to wait in queue when all Line Group members are busy. Features include maximum queue depth (e.g., 32 callers), periodic queue position and wait-time announcements, and Music on Hold (MoH) streaming.