Study guide

9.3 Webex Calling Call Routing Process & Translation Patterns

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

9.3 Webex Calling Call Routing Process & Translation Patterns

Key Takeaways Explain This Topic AI

Webex Calling routes every call in three phases: source classification (user, premises, or external), destination selection, and screening and routing against the caller's permissions.

Destination selection checks emergency numbers first, then translation patterns, the outside dial digit, feature access codes, internal numbers (extension before ESN before telephone number), virtual extensions, and dial plans.

National number analysis classifies the call type, converts the number to +E.164 when needed, and loops back so that +E.164 patterns can match before unknown numbers go to the premises or the PSTN.

Translation patterns exist at the organization and location levels, with location patterns taking precedence; there can be up to 500 per location and 1,000 per organization.

A translation that changes the dialed string restarts the lookup, with at most 10 translations per call leg, and the Control Hub call routing tool shows which patterns applied.

Last updated: October 2026

9.3 Webex Calling Call Routing Process & Translation Patterns

Blueprint objective 5.2 asks you to describe the call routing process in Webex Calling , and objective 5.4.d covers translation patterns . Unlike Unified CM, Webex Calling has no partitions or calling search spaces that an administrator arranges. Instead, the cloud applies a fixed decision sequence to every call, and administrators influence it through numbers, dial plans, translation patterns, permissions, and PSTN settings. Cisco's Webex Calling design sessions describe that sequence in three phases.

1. Phase One: Source Classification

Webex Calling first decides what kind of caller it is dealing with, because later rules depend on it:

  • Call arrives from Classified as
  • Webex Calling devices (MPP phones, Room devices) and the Webex App User
  • Cloud PSTN (Cisco Calling Plan or Cloud Connected PSTN) External
  • A Local Gateway trunk Premises or External , depending on the calling number

For trunk calls, the calling number (or the number in the SIP Diversion header, if present) is compared with the organization's configuration: a match on a dial plan pattern marks the call as coming from the premises PBX, and the location's settings for unknown extensions can also mark short numbers as premises calls. Anything else from the trunk is treated as an external PSTN call.

2. Phase Two: Destination Selection

Webex Calling then works out where the dialed string should go, in this order:

Emergency numbers : A match on the location's emergency number is routed to the PSTN for emergency handling immediately.

Translation patterns : If the dialed string matches a translation pattern, it is rewritten and the lookup starts again. A pattern that does not actually change the string (for example, 6XXX rewritten to the same digits) does not loop, and Webex Calling allows at most 10 translations per call leg .

Outside dial digit : If the location uses an outside dial digit (such as 9) for external calls, it is removed once.

Feature access codes : Codes such as call park or call forwarding activation are recognized after translation patterns.

Internal matches , in priority order: a user's extension , then the user's enterprise significant number (routing prefix plus extension), then a telephone number in the organization. An extension wins over an overlapping ESN or telephone number, which is why Cisco advises against overlapping extensions with other number types.

Virtual extensions map an extension to an external number and send the call straight to the PSTN.

Dial plans : A match on a dial plan's enterprise or +E.164 pattern sends the call to that dial plan's trunk or route group (Section 9.2).

National number analysis : Using the national dialing plan of the caller's location, Webex Calling classifies the number (national, international, toll-free, and so on), converts it to +E.164 when needed, and loops back so that +E.164 translation patterns, telephone numbers, and dial plans can match.

Unknown numbers : Short strings that match nothing can be sent to the premises as unknown extensions (per-location setting, 2 to 10 digits), and the organization's unknown-number handling decides whether other unmatched strings go to a premises trunk or to the location's PSTN connection.

3. Phase Three: Screening and Routing

Finally, Webex Calling checks whether the call is allowed and sends it:

The call type found during number analysis is checked against the caller's outgoing call permissions (Section 9.4). A blocked type is rejected or sent to an authorization-code prompt or an auto-transfer number.

Calls to a Webex meeting dial-in number are recognized and routed straight to the meeting service instead of across the PSTN.

Allowed calls go to a user, to a trunk or route group, or to the location's PSTN connection: Cisco Calling Plan, Cloud Connected PSTN, or premises-based PSTN through a Local Gateway.

4. Translation Patterns

Translation patterns let administrators rewrite dialed strings before routing, which Webex Calling dial plans cannot do (Section 9.2).

  • Property Detail
  • Levels Organization level and location level

Precedence A location-level pattern wins; organization-level patterns are checked only when no location-level pattern matches

  • Scale Up to 500 translation patterns per location and 1,000 at the organization level
  • Scope Outbound calls from users and features, including redirected (forwarded) calls
  • Parts A matching pattern and a replacement pattern
  • Verification The call routing test tool in Control Hub shows which translation patterns applied

Typical uses:

Abbreviated dialing : 88 translated to the IT help desk's full +E.164 number.

Preserving dialing habits : Cisco's example translates the 10-digit Bangalore pattern 80[2-9]XXXXXXX by putting 91 , India's country code, in front of the original digits.

Migrations : Old site codes or short codes translated to +E.164 numbers so that users keep dialing the way they did on the previous PBX.

Because the lookup restarts after a translation, the rewritten number can then match a user, a dial plan, or the PSTN exactly as if the user had dialed it.

5. Worked Example

A user in the London location dials 88 :

88 is not an emergency number.

A location-level translation pattern matches 88 and rewrites it to +442079460100 ; the lookup restarts.

+442079460100 matches a telephone number owned by a Webex Calling user in the organization, so the call stays on-net and rings that user.

If instead the user dials 02079460777 , a London number that is not in the organization, national number analysis tags it as a national call for the United Kingdom location, converts it to +442079460777 , finds no dial plan match, checks that national calls are allowed for the user, and sends it out through the London location's PSTN connection.

Loading diagram... Webex Calling Call Routing Phases