Study guide

4.3 Translation Patterns, Transformation Patterns & Digit Manipulation

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.3 Translation Patterns, Transformation Patterns & Digit Manipulation

Key Takeaways Explain This Topic AI

Translation Patterns execute prior to call routing, altering dialed or calling party digits and feeding the translated result back into digit analysis using the Translation Pattern's own CSS.

Transformation Patterns execute at the egress or ingress boundary after routing decisions are finalized, reformatting calling or called numbers without re-triggering digit analysis.

Translation pattern masking uses the Called Party Transform Mask to overwrite specific digit positions while preserving unchanged digits denoted by the wildcard X.

Transformation CSS applied to gateways, trunks, or device pools localizes calling party numbers to conform with regulatory caller ID mandates and carrier presentation standards.

SIP URI dialing routes calls based on alphanumeric domain addresses (user@domain) using Directory URIs, SIP Route Patterns, and Blended Addressing alongside traditional numeric dialing.

Last updated: October 2026

4.3 Translation Patterns, Transformation Patterns & Digit Manipulation

Digit manipulation is a central capability of Cisco Unified Communications Manager (CUCM), allowing collaboration engineers to adapt numbers between internal enterprise representations and external carrier formats. CUCM provides two distinct tools for digit manipulation: Translation Patterns and Transformation Patterns . Although their names sound similar, their underlying architecture, execution points in the call processing pipeline, and operational scopes are fundamentally different.

1. Translation Patterns vs. Transformation Patterns: Architectural Comparison

The fundamental distinction between Translation Patterns and Transformation Patterns lies in where and when they execute in the call routing pipeline:

Translation Patterns execute BEFORE the call routing decision is made . They intercept dialed digits, transform the called and/or calling numbers, and feed the result back into the Digit Analysis engine from the beginning , using the Translation Pattern's assigned Calling Search Space.

Transformation Patterns execute AFTER the call routing decision is finalized . They operate at the egress or ingress interface (gateways, trunks, or endpoints) to modify number presentation (caller ID or dialed digits) for external carrier compliance or localized screen display without re-entering digit analysis or altering the selected routing path .

Comprehensive Comparison Matrix

Feature / Attribute Translation Patterns Transformation Patterns

Execution Point Pre-routing (at initial digit analysis ingress) Post-routing (at trunk/gateway egress or ingress handoff)

Re-enters Digit Analysis? Yes : The rewritten string is analyzed anew from the top No : Digits are modified purely for wire presentation

Next Hop Destination Does not route calls directly; feeds back into DA engine Direct egress to SIP trunk, voice gateway, or IP phone display

Search Space Utilized Uses the Translation Pattern's own Calling Search Space Evaluated via Transformation CSS on Trunk, Gateway, or Device Pool

Modifies Routing Path? Yes : By rewriting the called number, it alters routing No : The physical egress route path remains unchanged

Primary Enterprise Use Cases Abbreviated inter-site dialing, dialing normalization (stripping 9), speed dial mapping, number blocking Caller ID presentation (E.164 normalization), carrier digit requirements (stripping +1 for local 10D), emergency ANI formatting

2. Translation Patterns in the Call Routing Pipeline

When a Translation Pattern is matched, CUCM applies configured manipulation rules (called party masks, prefixes, discard digits instructions) and restarts digit analysis.

The Translation Pattern CSS Hand-Off

A critical exam concept is how Calling Search Spaces transition during translation:

A phone initiates a call using its Effective CSS (Line CSS + Device CSS).

CUCM matches a Translation Pattern residing in one of the partitions within the phone's CSS.

The Translation Pattern transforms the dialed number (and optionally the calling number).

CUCM re-enters Digit Analysis using the Translation Pattern's Calling Search Space , discarding the originating phone's CSS for subsequent routing. If the translation pattern's Use Originator's Calling Search Space checkbox is selected, CUCM reuses the caller's own CSS for the second lookup instead; Cisco's +E.164 normalization designs use this to keep each user's class of service. [Phone (CSS: User_CSS)] dials '8201'

  • |
  • v
  • [Translation Pattern: 8XXX in Partition Abbrev_PT]
  • Called Party Transform Mask: 5551XXX
  • Prefix: 91408
  • Translation Pattern CSS: Gateway_CSS
  • |
  • v
  • [Rewritten Number: 914085551201]
  • |
  • v
  • [CUCM Restarts Digit Analysis using Gateway_CSS]
  • Matches Route Pattern: 9.1[2-9]XX[2-9]XXXXXX
  • Routes out PSTN via Route List
  • Common Enterprise Translation Pattern Use Cases

Abbreviated Inter-Site Dialing : Users dial an internal site code plus extension (e.g., 8 + 4-digit extension 2XXX ). The Translation Pattern 82XXX rewrites the digits to the full E.164 DID ( +14085552XXX ) and evaluates internal directory numbers across the WAN.

Dialing Normalization : If users dial 7-digit local numbers ( 5551234 ), a Translation Pattern [2-9]XXXXXX prefixes the local area code ( 408 ) and access code 91 to construct standard 11-digit NANP strings.

Emergency Dialing Normalization : In many enterprises, users inadvertently dial 9911 instead of 911 . A Translation Pattern 9911 with Called Party Transform Mask 911 seamlessly redirects the call to the emergency route pattern.

Call Blocking : Setting a Translation Pattern with the Route Option set to Block this pattern enables administrators to reject specific numbers (e.g., high-cost 900-numbers or international toll destinations) with specific cause codes such as Unallocated Number or Call Rejected .

3. Transformation Patterns and Transformation CSS

Transformation Patterns format numbers without changing routing. They fall into two categories:

Calling Party Transformation Patterns (CPTP) : Modify the calling number (Caller ID / ANI).

Called Party Transformation Patterns (CDTP) : Modify the dialed number (DNIS) delivered to the carrier.

Transformation CSS Hierarchy

Transformation patterns are grouped into partitions and accessed via Transformation Calling Search Spaces . These are configured at three distinct hierarchical locations:

Gateway / Trunk Level : Directly on the SIP Trunk, MGCP port, or H.323 gateway configuration page under Calling Party Transformation CSS and Called Party Transformation CSS .

Device Pool Level : Configured on the Device Pool to provide default transformation rules for all gateways or phones belonging to that site.

Phone Configuration Level : Applied to IP phones under Calling Party Transformation CSS to localize incoming caller ID displayed on the screen (e.g., converting incoming +14085550100 to 7-digit 555-0100 for localized user display). Hierarchy Resolution Order:

If 'Use Device Pool Calling/Called Party Transformation CSS' is checked on the gateway or trunk -> the device pool's CSS is used.

If that box is unchecked -> the CSS set on the gateway or trunk itself is used, even if it is <None>.

4. Digit Masking and Manipulation Mechanics

CUCM provides flexible masking parameters across Translation Patterns, Route Patterns, Route Lists, and Transformation Patterns:

Masking Rules and Wildcard Behavior

The wildcard character X preserves the original dialed digit in that character position.

Any literal digit replaces the digit at that position.

Masks are aligned from the right. If the mask is shorter than the number, the leftmost digits are dropped (a mask of ten X characters keeps the last 10 digits).

If the mask is longer than the number, its extra leftmost literal digits are prepended.

Transformation Examples

Original Dialed Digits Called Party Transform Mask Prefix Digits Resulting Output String Mechanism Explanation

4123 555XXXX None 5554123 Prepends literal 555 while preserving 4123 via XXXX .

4123 5551XXX 91 915551123 Literal 5551 replaces 4 ; XXX retains 123 ; 91 prepends.

914085551234 XXXXXXXXXX (10 X's) None 4085551234 Strips leading 91 by matching the trailing 10 digits.

2001 +1408555XXXX None +14085552001 Normalizes 4-digit internal extension to global E.164.

5. SIP URI Dialing and Blended Addressing

Modern collaboration architectures increasingly use Session Initiation Protocol (SIP) Uniform Resource Identifiers (URIs) instead of traditional numeric telephone numbers. A SIP URI resembles an email address (e.g., alice@example.com or sales@company.com ), providing human-readable, domain-based routing across enterprise networks and the internet.

Architectural Components of SIP URI Dialing

Directory URIs : Configured directly on the Directory Number (DN) in CUCM. Each DN can hold up to 5 Directory URIs, commonly populated from Microsoft Active Directory through LDAP synchronization (for example, from the mail attribute).

SIP Route Patterns : Analogous to traditional Route Patterns, but match domain names rather than numbers. Examples include example.com , *.cisco.com , or an IPv4 address. SIP Route Patterns point directly to SIP Trunks (such as a trunk to Cisco Expressway-C for Business-to-Business calling).

Blended Addressing : Allows CUCM to associate a Directory Number and a Directory URI to the same endpoint simultaneously. When an internal user places a call, CUCM displays both the numeric extension and the alphanumeric URI on the receiving phone's screen. Similarly, Call Detail Records (CDR) capture both attributes.

URI Route Partitions : SIP Route Patterns and Directory URIs are assigned to partitions. A calling device must have the partition in its CSS to resolve and dial the URI destination. [Caller Dials: bob@partner.com]

  • |
  • v
  • [CUCM Digit Analysis]
  • |
  • v
  • [Matches SIP Route Pattern: partner.com]
  • |
  • v
  • [Routes to SIP Trunk -> Cisco Expressway-C]
  • |
  • v
  • [Expressway-E resolves DNS SRV _sips._tcp.partner.com -> B2B Call Setup]

Loading diagram... Complete CUCM Digit Processing Pipeline: Translation vs. Transformation