Study guide

4.4 Globalized Call Routing & Local Route Group (LRG)

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.4 Globalized Call Routing & Local Route Group (LRG)

Key Takeaways Explain This Topic AI

Globalized Call Routing normalizes all internal and external telephone numbers into the international +E.164 format (+[Country Code][Subscriber Number]), establishing a singular, scalable call routing core.

The Standard Local Route Group (SLRG) decouples Route Lists from physical hardware gateways by dynamically resolving the egress trunk based on the calling device's Device Pool.

Inbound globalization transforms national, local, and abbreviated caller IDs into +E.164 at ingress, enabling direct one-touch callback from missed call logs without dial prefix manipulation.

Egress localization uses Called Party Transformation Patterns applied through the egress gateway's Called Party Transformation CSS to strip +E.164 prefixes and match carrier-specific digit requirements.

By combining SLRG with globalized route patterns (such as +!), enterprise dial plans scale from tens of thousands of site-specific patterns down to a single unified routing configuration.

Last updated: October 2026

4.4 Globalized Call Routing & Local Route Group (LRG)

In traditional, localized enterprise dial plans, call routing logic is deeply intertwined with physical site geography. Every branch office required dedicated Route Patterns (such as 9.1[2-9]XX[2-9]XXXXXX ), custom Route Lists, and unique Partitions to ensure outbound calls egressed that specific site's local gateway. For multi-site enterprises with dozens or hundreds of locations, this model caused an exponential explosion of dial plan objects, fractured Call Detail Records (CDR), and prevented users from redialing missed external numbers from their phone history.

Cisco Globalized Call Routing resolves these scaling challenges by establishing a unified, location-independent dial plan based on the international +E.164 standard, powered by the Standard Local Route Group (SLRG) feature.

1. The +E.164 Standardization Framework

ITU-T Recommendation E.164 defines an international public telecommunication numbering plan. In Cisco Globalized Call Routing, every internal Directory Number and external PSTN destination is normalized to full E.164 format with a leading plus sign ( + ):

E.164 Format = + + [ Country Code ] + [ National Destination Code / Area Code ] + [ Subscriber Number ] \text{E.164 Format} = \mathbf{+} + [\text{Country Code}] + [\text{National Destination Code / Area Code}] + [\text{Subscriber Number}] E.164 Format = + + [ Country Code ] + [ National Destination Code / Area Code ] + [ Subscriber Number ]

  • Examples of Globalized Numbers
  • United States (San Jose) : +14085550100 ( + , Country Code 1 , Area Code 408 , Local Number 5550100 )
  • United Kingdom (London) : +442079460123 ( + , Country Code 44 , Area Code 20 , Local Number 79460123 )
  • Germany (Frankfurt) : +49691234567 ( + , Country Code 49 , Area Code 69 , Local Number 1234567 )
  • Australia (Sydney) : +61299990123 ( + , Country Code 61 , Area Code 2 , Local Number 99990123 )
  • Core Benefits of Globalized Routing

Unified Core Dial Plan : CUCM maintains a single, globalized routing table across all geographic locations, eliminating redundant site-specific patterns.

Consistent Call Detail Records (CDR) : Billing and reporting systems track uniform +E.164 numbers regardless of which branch placed or received the call.

One-Touch Redial / Callback : When an external call arrives, the caller ID is normalized to +E.164 before appearing on the phone screen. When the recipient views missed calls and presses "Call", the phone dials +14085550100 directly, which matches the global routing core without requiring manual digit editing or steering digit prefixes.

Linear Multi-Site Scalability : Adding a new remote site requires zero changes to the core route patterns or route lists.

2. Standard Local Route Group (SLRG)

In a legacy architecture, if an enterprise operated 50 branch offices, routing outbound PSTN calls required 50 distinct Route Lists (e.g., RL_Site1_PSTN , RL_Site2_PSTN , ..., RL_Site50_PSTN ) and 50 distinct Route Patterns in separate site partitions.

Decoupling Patterns from Hardware

The Standard Local Route Group (SLRG) completely decouples dial patterns from physical gateways by introducing a dynamic placeholder into Route Lists: [Route Pattern: \+!] ---> [Route List: RL_Global_PSTN]

  • |
  • v
  • [Standard Local Route Group (Virtual)]
  • |
  • +------------------+------------------+
  • | |
  • (Caller in San Jose DP) (Caller in London DP)
  • | |
  • v v
  • [Resolved Gateway: CUBE_SJ] [Resolved Gateway: CUBE_LDN]
  • How SLRG Works at Runtime

An administrator creates a single global Route Pattern (e.g., \+! or 9.\+! ) pointing to a global Route List named RL_Global_PSTN .

Inside RL_Global_PSTN , instead of selecting a specific physical Route Group, the administrator selects the built-in virtual entity: Standard Local Route Group .

On each branch's Device Pool (e.g., DP_SanJose , DP_London ), the administrator maps the virtual SLRG to that site's actual physical Route Group under the Local Route Group drop-down menu:

  • DP_SanJose : Local Route Group = RG_SanJose_Gateways
  • DP_London : Local Route Group = RG_London_Gateways

When an endpoint in San Jose initiates an outbound call to +12125550199 , CUCM matches \+! , routes to RL_Global_PSTN , inspects the calling phone's Device Pool, resolves SLRG to RG_SanJose_Gateways , and sends the call out the local San Jose gateway.

When an endpoint in London dials the exact same number, CUCM resolves SLRG to RG_London_Gateways and routes out the London gateway.

3. Egress Localization

While CUCM processes and routes calls internally using +E.164 , external PSTN carriers rarely accept a leading + sign or uniform international formatting for local calls. For example, a local carrier in Dallas may require 10 digits ( 2145551234 ), while long-distance requires 11 digits ( 12145551234 ), and international requires 011 prefixed before the country code.

Egress Localization transforms globalized +E.164 numbers into carrier-mandated formats at the egress gateway or trunk using Called Party Transformation Patterns .

Localization Configuration via Called Party Transformation CSS

Localization patterns are assigned to partitions and associated with the egress trunk/gateway via a Called Party Transformation CSS :

Carrier Destination Egress Pattern Discard Digits Prefix Dialed E.164 Sent to Carrier Description

US Local 10-Digit \+1.408[2-9]XXXXXX PreDot None +14085550199 4085550199 A closer match than the national pattern, so local calls use it; strips +1 .

US Long Distance \+1.[2-9]XX[2-9]XXXXXX PreDot 1 +12125550123 12125550123 Strips +1. and prepends 1 for national.

US International \+.! PreDot 011 +442079460123 011442079460123 Strips +. and prepends 011 exit code.

UK National \+44.[1-9]XXXXXXXXX PreDot 0 +442079460123 02079460123 Strips +44. and prepends national 0 .

UK International \+.! PreDot 00 +14085550100 0014085550100 Strips +. and prepends 00 exit code.

Because localization transformation patterns reside in site-specific partitions applied to each site's gateway, each branch formats digits to suit its local carrier without impacting other branches.

Emergency numbers are normally not globalized. A dedicated 911 (and 9.911 ) route pattern with Urgent Priority points to a route list containing the Standard Local Route Group, so the call leaves through the caller's local gateway with the local emergency number intact.

4. Inbound Globalization and One-Touch Redial

PSTN carriers deliver incoming calls with disparate number formats depending on circuit type (PRI, SIP, BRI) and the nature of the call (Subscriber, National, International, or Unknown).

Inbound Globalization Mechanics

To achieve true end-to-end globalization, numbers must be converted to +E.164 at the ingress boundary before entering CUCM Digit Analysis:

Gateway / Trunk Ingress Settings : On SIP trunks or MGCP/H.323 voice gateways, administrators configure prefix rules based on ISDN Numbering Plan Indicator (NPI) and Type of Number (TON) , or apply an Inbound Calling Party Transformation CSS .

Mapping Carrier TON to +E.164 :

If TON = National (e.g., delivered as 4085550100 in the US): Prefix +1 -> +14085550100 .

If TON = International (e.g., delivered as 442079460123 ): Prefix + -> +442079460123 .

If TON = Subscriber (e.g., delivered as 7-digit 5550100 ): Prefix +1408 -> +14085550100 .

The One-Touch Redial Lifecycle

Inbound globalization and outbound localization create a seamless user experience:

An external customer ( 4085550199 ) calls an enterprise employee.

The ingress gateway globalizes the caller ID to +14085550199 .

The employee misses the call; the Cisco IP phone Call History logs +14085550199 .

Later, the employee opens Call History and presses Call .

The phone dials +14085550199 .

CUCM digit analysis matches globalized Route Pattern \+! .

The Route Pattern directs the call to RL_Global_PSTN , which evaluates Standard Local Route Group .

The employee's Device Pool resolves SLRG to the local branch CUBE.

The branch gateway's Called Party Transformation Pattern strips +1 to present 4085550199 to the local carrier.

The call connects immediately—requiring zero digit editing by the user.

5. End-to-End Call Lifecycle Comparison

  • Call Stage Processing Node / Boundary Applied Mechanism Number Format Example
  • 1. Carrier Ingress Ingress Voice Gateway PSTN carrier delivers 10-digit ANI 4085550199
  • 2. Inbound Globalization Gateway / Ingress Transformation CSS Prefix +1 based on TON National +14085550199
  • 3. Ringing & History Cisco IP Phone Displays Caller ID & stores in Call History +14085550199
  • 4. User Redial Cisco IP Phone One-touch "Call" softkey pressed +14085550199

5. Core Digit Analysis CUCM Call Processing Engine Matches Route Pattern \+! in Partition Global_PSTN_PT +14085550199

6. Route List Evaluation RL_Global_PSTN Resolves virtual Standard Local Route Group N/A (Egress trunk chosen)

7. Device Pool Resolution Calling Device's Device Pool Maps SLRG to local branch CUBE Route Group Local Gateway Selected

  • 8. Egress Localization Egress Gateway Called Party CSS CDTP \+1.408[2-9]XXXXXX applies PreDot 4085550199
  • 9. Carrier Egress Local Branch PSTN Trunk 10-digit format delivered to local telco 4085550199

Loading diagram... Globalized Call Routing Architecture: Inbound Globalization, SLRG, and Egress Localization