4.3 Translation Patterns, Transformation Patterns & Digit Manipulation

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

---

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:

1. A phone initiates a call using its Effective CSS (Line CSS + Device CSS).
2. CUCM matches a Translation Pattern residing in one of the partitions within the phone's CSS.
3. The Translation Pattern transforms the dialed number (and optionally the calling number).
4. 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:

1. Calling Party Transformation Patterns (CPTP): Modify the calling number (Caller ID / ANI).
2. 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

---

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]