# Unified CM translation and transformation patterns

Canonical: https://warmtransfer.net/knowledge/cucm-translation-patterns

Last verified: 2026-09-24

Unified CM uses translation patterns and transformation patterns to alter digits and caller identities during call processing[^44][^2]. Translation patterns match dialed digits and re-route the call, whereas transformation patterns adapt numbers on egress or ingress without performing call routing[^44][^56][^59].

## How translation patterns work

In Unified CM Release 15, translation patterns follow the same general rules and use the same wildcards as route patterns[^45]. When dialed digits match a translation pattern, Unified CM does not route the call to an outside entity such as a gateway; it applies the translation and then routes the call again using the calling search space (CSS) configured on the translation pattern[^44]. Directory numbers, route patterns, and translation patterns can each belong to a partition, and a CSS is an ordered list of partitions that a calling device searches when placing a call[^35]. If the called number matches a pattern in a partition within the caller's CSS, the call is placed or, if the match is a translation pattern, the translation pattern is executed[^5]. On an IP phone that has both a line CSS and a device CSS, Cisco states that the line CSS takes precedence over the device CSS[^17].

Each translation pattern must have a unique combination of partition, route filter, and numbering plan[^46]. A translation pattern is assigned to a partition from the Partition drop-down list in the Translation Pattern Configuration window[^43]. The Unified CM System Configuration Guide does not document translation pattern fields individually; it refers administrators to the system Online Help for the fields and their configuration options[^8].

In preferred architecture designs, dialing normalization translation patterns route in 2 steps: first the dialed string is normalized to +E.164 where possible, and then the result is matched against the +E.164 numbering plan[^30]. The Collaboration 14 preferred architecture sets Use Originator's Calling Search Space on dialing normalization translation patterns so the secondary lookup uses the same CSS as the primary lookup[^33]. WarmTransfer's reading of the sources is that with Use Originator's Calling Search Space enabled, 1 set of normalization translation patterns can serve every class of service, because the re-lookup is done with the caller's own CSS instead of a CSS fixed on the pattern[^21]. The preferred architecture defines class of service using only the line CSS and uses the device CSS for dialing habits everyone needs, such as emergency calling[^27].

## Pattern wildcards and digit manipulation

| Wildcard | Definition |
| --- | --- |
| X | Matches any single digit from 0 through 9[^55] |
|! | Matches 1 or more digits from 0 through 9[^52] |
|. | Delimiter separating an access code from the directory number; marks boundary used by pre-dot digit removal[^53] |
| @ | Matches all National Numbering Plan numbers[^51] |
| # | Generally identifies the end of the dialing sequence[^54] |

A plain + means 1 or more occurrences of the preceding digit or wildcard, while \+ makes the international escape character + a dialable digit rather than a wildcard[^7]. The Discard Digits option can strip pre-dot digits, such as the external access code 9 in a pattern like 9.@, so that the PSTN can route the remaining digits[^37]. The preferred architecture's US national dialing normalization pattern is 9.1[2-9]XX[2-9]XXXXXX with the transformation 'strip pre-dot, prefix +', turning 914085554001 into +14085554001[^32].

## Interdigit timing and urgent priority

The T302 interdigit timer defaults to 15 seconds and is a clusterwide service parameter under Device - General[^42]. When urgent priority is enabled on a directory number, Unified CM routes a call to that fully qualified DN immediately rather than waiting for the interdigit timeout, even when longer overlapping patterns exist[^48]. WarmTransfer's reading of the sources is that urgent priority on directory numbers became available with Unified CM 10; before that, calls to a DN that overlapped longer patterns waited for T302[^49].

The Collaboration 14 preferred architecture provisions all dialing normalization translation patterns as urgent patterns[^31]. It also sets Do Not Wait For Interdigit Timeout On Subsequent Hops on fixed-length dialing normalization translation patterns, meaning patterns that do not end in a variable-length wildcard[^22].

## Transformation patterns and normalization

Calling party transformation patterns let Unified CM adapt the global form of the calling party number into the local form required by off-cluster networks connected to route group devices such as gateways or trunks[^2]. Called party transformation patterns adapt the global form of the called party number into the local form required by off-cluster networks connected to route group devices[^1]. Transformation patterns are placed in route partitions and reach calls through calling search spaces assigned in the device, device pool, gateway, or trunk configuration[^56]. Calling party transformation patterns must be placed in a non-null partition that is not used for routing[^59]. Calling and called party transformation patterns are configured in Cisco Unified CM Administration under Call Routing > Transformation > Transformation Pattern > Calling Party Transformation Pattern and Called Party Transformation Pattern respectively[^58]. Transformation profiles (Call Routing > Transformation > Transformation Profile) are needed only when Cisco Intercompany Media Engine is used, to convert numbers to E.164 form[^60].

Transformation patterns can discard digits, prefix digits, apply a calling party transformation mask, and control calling party number presentation[^57]. For outbound calls, Unified CM selects the calling party transformation mask using the pre-transform calling party number (the extension assigned to the IP phone), even if the number was transformed at the route pattern or route group level[^19]. Calling party transformation works only on the original calling party; changes made for redirecting numbers affect only the diversion header[^4]. For a phone roaming within the same Device Mobility Group, the Calling Party Transformation CSS of the roaming device pool overrides the phone's device-level setting[^39]. Calling Party Transformation CSS settings do not apply to T1-CAS and FXO ports on a gateway[^3].

Cisco defines globalization of the calling party number as converting it to a form that includes the international escape and country code so it can be dialed back from anywhere[^9]. Cisco defines localization of the calling party number as removing the country code and access codes from a globalized number that are not needed for local display or callback[^18]. Unified CM uses number patterns such as route patterns or translation patterns, together with the Calling Party Number Type value, to globalize a calling party number[^10]. Calling party normalization prefix and strip-digit rules can be applied on device pools, route patterns, translation patterns, hunt pilots, gateways, and trunks[^20]. Incoming calling party prefix and strip-digit settings are defined separately for 4 calling party number types: National, International, Subscriber, and Unknown[^11]. Calling Party Normalization can strip at most 24 digits[^41]. Because SIP does not carry a number type, calls over SIP trunks use only the Incoming Number settings for the Unknown calling party number type[^40].

The Cisco Collaboration 14 preferred architecture provisions every directory number on endpoints that have a DID as a +E.164 number[^23]. For destinations without a DID, it recommends an enterprise specific numbering (ESN) scheme of access code, site code, and extension, such as 8-140-4XXX[^24]. Because all Unified CM call routing in the preferred architecture is based on +E.164, the called party number of every incoming call must be globalized to +E.164 from the format received, using a mix of Cisco IOS translations on the SIP gateways and prefixes or transformations on Unified CM[^26]. Route patterns that point to a local route group select the egress gateway dynamically, based on the device that originated the call[^28]. When route patterns use local route groups, service-provider-specific calling and called party localization cannot be done at route pattern or route list level; the preferred architecture does it with Cisco IOS voice translation rules on the gateway or with transformation patterns reached through transformation CSSs on the gateway or its device pool[^29].

Protocol support varies: SIP trunks and MGCP gateways can send the international escape character + on calls, but H.323 gateways do not support +[^36]. Cisco Unity Connection does not support the international escape character +, so numbers must be localized before they are delivered to it[^47].

## Historical Release 4.2(1) behavior

In Cisco Unified CallManager 4.2(1), every translation pattern carried urgent priority and administrators could not change it[^16]. WarmTransfer's reading of the sources is that in current Unified CM releases, urgent priority on a translation pattern appears to be a per-pattern setting rather than fixed, because Cisco design guidance tells administrators to provision normalization translation patterns as urgent[^50]. In Unified CallManager 4.2(1), a translation pattern's Route Option could block the pattern, which required a reason: No Error, Unallocated Number, Call Rejected, Number Changed, Invalid Number Format, or Precedence Level Exceeded[^13]. Which discard digits instructions a translation pattern offered depended on the numbering plan selected[^14]. A blank Called Party Transform Mask meant no transformation, sending the dialed digits exactly as dialed[^12]. The check box Use Calling Party's External Phone Number Mask made outgoing calls use the full external phone number for calling line identification[^15].

## See also

See also [Unified CM dial plan partitions and calling search spaces](https://warmtransfer.net/knowledge/cucm-dial-plan).
See also [Unified CM route patterns and partitions configuration](https://warmtransfer.net/knowledge/cucm-config-route-patterns-and-partitions).
See also [Unified CM device pools and device configuration model](https://warmtransfer.net/knowledge/cucm-device-pools).
See also [Unified CM SIP trunks and security profiles](https://warmtransfer.net/knowledge/cucm-sip-trunks).
See also [Unified CM hunt pilots and hunt lists and line groups](https://warmtransfer.net/knowledge/cucm-hunt-pilots).
See also [Cisco Unity Connection voicemail and migration](https://warmtransfer.net/knowledge/cucm-unity-connection).
See also [CUBE dial-peer matching and voice class URI and translation profiles](https://warmtransfer.net/knowledge/cube-dial-peers).

## Applicability

Applies to: Cisco Unified Communications Manager and Cisco Unified CallManager. Deployments: on-premises. Sources checked 2026-09-24. The dialing normalization pattern 9.1[2-9]XX[2-9]XXXXXX specifically applies to the US region[^32].

## What remains uncertain

Order and override rules when route pattern and route list details and egress-device transformation CSSs all manipulate the same number are not covered by the sources below. Incoming called party settings and incoming calling/called party transformation CSS on gateways, trunks, and device pools are not covered by the sources below. The closest-match rule and partition-order tie-breaking in digit analysis including translation pattern matches are not covered by the sources below. The use of translation patterns for emergency call normalization and ELIN or RedSky/Intrado handoff is not covered by the sources below. How Webex Calling Dedicated Instance and Webex Calling dial plans express translation and transformation is not covered by the sources below. Whether Unified CM limits chained translation patterns or detects translation loops is not covered by the sources below. Whether line and device CSS are concatenated (line partitions first) or one replaces the other is not covered by the sources below. Cisco IOS voice translation rules on CUBE as an alternative to CUCM transformation patterns are not covered by the sources below.

## Sources

[^1]: Called party transformation patterns let Unified CM adapt the global form of the called party number into the local form required by off-cluster networks connected to route group devices. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Configure Call Routing > Call Routing Overview > Transformation Patterns. Checked 2026-09-24.
[^2]: Calling party transformation patterns let Unified CM adapt the global form of the calling party number into the local form required by off-cluster networks connected to route group devices such as gateways or trunks. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Configure Call Routing > Call Routing Overview > Transformation Patterns. Checked 2026-09-24.
[^3]: Calling Party Transformation CSS settings do not apply to T1-CAS and FXO ports on a gateway. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Restrictions. Checked 2026-09-24.
[^4]: Calling party transformation works only on the original calling party; changes made for redirecting numbers affect only the diversion header. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Prerequisites. Checked 2026-09-24.
[^5]: If the called number matches a pattern in a partition within the caller's CSS, the call is placed or, if the match is a translation pattern, the translation pattern is executed. Source: [Configure Partition and Calling Search Space](https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/22325-part-css-tn.html), Background Information. Checked 2026-09-24.
[^6]: The 12.5(1) guide notes that Dialed Number Analyzer uses the transformed calling number to select the calling party transformation mask, which differs from actual call processing and is identified there as incorrect. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) - Configure Transformation Patterns](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1/systemConfig/cucm_b_system-configuration-guide-1251/cucm_b_system-configuration-guide-1251_chapter_010111.html), Configure Calling Party Transformation Patterns (note following the mask-selection note). Checked 2026-09-24.
[^7]: In Unified CM patterns, a plain + means one or more occurrences of the preceding digit or wildcard, while \+ makes the international escape character + a dialable digit rather than a wildcard. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Route Patterns Settings > wildcards and special characters table, rows + and \+. Checked 2026-09-24.
[^8]: The Unified CM System Configuration Guide does not document translation pattern fields individually; it refers administrators to the system Online Help for the fields and their configuration options. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) - Configure Translation Patterns](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1/systemConfig/cucm_b_system-configuration-guide-1251/cucm_b_system-configuration-guide-1251_chapter_010110.html), Configure Translation Patterns > procedure, final step note. Checked 2026-09-24.
[^9]: Cisco defines globalization of the calling party number as converting it to a form that includes the international escape and country code so it can be dialed back from anywhere. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Overview > Globalization of the Calling Party Number. Checked 2026-09-24.
[^10]: Unified CM uses number patterns such as route patterns or translation patterns, together with the Calling Party Number Type value, to globalize a calling party number. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Overview > Globalization of the Calling Party Number. Checked 2026-09-24.
[^11]: Incoming calling party prefix and strip-digit settings are defined separately for four calling party number types: National, International, Subscriber and Unknown. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Globalize Calling Party Numbers; Calling Party Normalization Service Parameter Examples. Checked 2026-09-24.
[^12]: In Unified CallManager 4.2(1), a blank Called Party Transform Mask on a translation pattern meant no transformation: the dialed digits were sent exactly as dialed. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Translation Pattern Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03txpat.html), Translation Pattern Configuration Settings table > Called Party Transform Mask. Checked 2026-09-24.
[^13]: In Unified CallManager 4.2(1), a translation pattern's Route Option could block the pattern, and blocking required a reason: No Error, Unallocated Number, Call Rejected, Number Changed, Invalid Number Format or Precedence Level Exceeded. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Translation Pattern Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03txpat.html), Translation Pattern Configuration Settings table > Route Option. Checked 2026-09-24.
[^14]: In Unified CallManager 4.2(1), which discard digits instructions a translation pattern offered depended on the numbering plan selected. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Translation Pattern Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03txpat.html), Translation Pattern Configuration Settings table > Discard Digits. Checked 2026-09-24.
[^15]: In Unified CallManager 4.2(1), the translation pattern check box Use Calling Party's External Phone Number Mask made outgoing calls use the full external phone number for calling line identification. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Translation Pattern Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03txpat.html), Translation Pattern Configuration Settings table > Use Calling Party's External Phone Number Mask. Checked 2026-09-24.
[^16]: In Cisco Unified CallManager 4.2(1), every translation pattern carried urgent priority and administrators could not change it. Source: [Cisco Unified CallManager Administration Guide, Release 4.2(1) - Translation Pattern Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmcfg/b03txpat.html), Translation Pattern Configuration Settings table > Urgent Priority. Checked 2026-09-24.
[^17]: On an IP phone that has both a line CSS and a device CSS, Cisco states that the line CSS takes precedence over the device CSS. Source: [Configure Partition and Calling Search Space](https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/22325-part-css-tn.html), Configure / line and device CSS note. Checked 2026-09-24.
[^18]: Cisco defines localization of the calling party number as removing the country code and access codes from a globalized number that are not needed for local display or callback. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Overview > Localization of the Calling Party Number. Checked 2026-09-24.
[^19]: For outbound calls, Unified CM selects the calling party transformation mask using the pre-transform calling party number (the extension assigned to the IP phone), even if the number was transformed at route pattern or route group level. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Configure Call Routing > Configure Calling Party Transformation Patterns (note). Checked 2026-09-24.
[^20]: Calling party normalization prefix and strip-digit rules can be applied on device pools, route patterns, translation patterns, hunt pilots, gateways and trunks. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Configuration Task Flow. Checked 2026-09-24.
[^21]: With Use Originator's Calling Search Space enabled, one set of normalization translation patterns can serve every class of service, because the re-lookup is done with the caller's own CSS instead of a CSS fixed on the pattern (inferred). Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Dialing Normalization Translation Patterns; Class of Service. Checked 2026-09-24.
[^22]: The Collaboration 14 preferred architecture also sets Do Not Wait For Interdigit Timeout On Subsequent Hops on fixed-length dialing normalization translation patterns, meaning patterns that do not end in a variable-length wildcard. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Dialing Normalization Translation Patterns. Checked 2026-09-24.
[^23]: The Cisco Collaboration 14 preferred architecture provisions every directory number on endpoints that have a DID as a +E.164 number. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Endpoint Addressing. Checked 2026-09-24.
[^24]: For destinations without a DID, the Collaboration 14 preferred architecture recommends an enterprise specific numbering (ESN) scheme of access code, site code and extension, for example 8-140-4XXX. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Enterprise Specific Numbering. Checked 2026-09-24.
[^25]: In the preferred architecture, an ESN translation pattern such as 81404XXX uses the called party transformation mask +14085554XXX to turn abbreviated inter-site dialing into the +E.164 number. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Table 2-14. Checked 2026-09-24.
[^26]: Because all Unified CM call routing in the preferred architecture is based on +E.164, the called party number of every incoming call must be globalized to +E.164 from the format received, using a mix of Cisco IOS translations on the SIP gateways and prefixes or transformations on Unified CM. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > inbound call globalization. Checked 2026-09-24.
[^27]: The preferred architecture defines class of service using only the line CSS and uses the device CSS for dialing habits everyone needs, such as emergency calling. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Partitions and Calling Search Spaces; Class of Service. Checked 2026-09-24.
[^28]: Route patterns that point to a local route group select the egress gateway dynamically, based on the device that originated the call. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Local Route Groups. Checked 2026-09-24.
[^29]: When route patterns use local route groups, service-provider-specific calling and called party localization cannot be done at route pattern or route list level; the preferred architecture does it with Cisco IOS voice translation rules on the gateway or with transformation patterns reached through transformation CSSs on the gateway or its device pool. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Local Route Groups; Called Party Transformations. Checked 2026-09-24.
[^30]: Dialing normalization translation patterns in the Collaboration 14 preferred architecture route in two steps: first the dialed string is normalized to +E.164 where possible, then the result is matched against the +E.164 numbering plan. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Dialing Normalization Translation Patterns. Checked 2026-09-24.
[^31]: The Collaboration 14 preferred architecture provisions all dialing normalization translation patterns as urgent patterns. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Dialing Normalization Translation Patterns. Checked 2026-09-24.
[^32]: The preferred architecture's US national dialing normalization pattern is 9.1[2-9]XX[2-9]XXXXXX with the transformation 'strip pre-dot, prefix +', turning 914085554001 into +14085554001. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > dialing normalization translation pattern table (US). Checked 2026-09-24.
[^33]: The Collaboration 14 preferred architecture sets Use Originator's Calling Search Space on dialing normalization translation patterns so the secondary lookup uses the same CSS as the primary lookup. Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Dialing Normalization Translation Patterns. Checked 2026-09-24.
[^34]: For variable-length international and Italian national dialing, the preferred architecture uses patterns ending in !# with 'strip pre-dot trailing #' plus a prefix, for example 000.!# with prefix + (Germany) and 0.[^0]!# with prefix +39 (Italy). Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > dialing normalization translation pattern tables (Germany, Italy). Checked 2026-09-24.
[^35]: Directory numbers, route patterns and translation patterns can each belong to a partition, and a calling search space is an ordered list of partitions that a calling device searches when placing a call. Source: [Configure Partition and Calling Search Space](https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/22325-part-css-tn.html), Background Information. Checked 2026-09-24.
[^36]: SIP trunks and MGCP gateways can send the international escape character + on calls, but H.323 gateways do not support +. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Interactions and Restrictions > Calling Party Normalization Restrictions. Checked 2026-09-24.
[^37]: The Discard Digits option can strip the pre-dot digits, such as the external access code 9 in a pattern like 9.@, so that the PSTN can route the remaining digits. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Route Patterns Settings > pre-dot digit removal text. Checked 2026-09-24.
[^38]: A device uses the clusterwide Calling Party Normalization service parameter only when its own incoming prefix is set to Default; device settings take precedence over device pool settings, which take precedence over the service parameters. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Service Parameter Examples. Checked 2026-09-24.
[^39]: For a phone roaming within the same Device Mobility Group, the Calling Party Transformation CSS of the roaming device pool overrides the phone's device-level setting. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Interactions. Checked 2026-09-24.
[^40]: Because SIP does not carry a number type, calls over SIP trunks use only the Incoming Number settings for the Unknown calling party number type. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Restrictions. Checked 2026-09-24.
[^41]: Calling Party Normalization can strip at most 24 digits. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Service Parameter Examples. Checked 2026-09-24.
[^42]: The T302 interdigit timer defaults to 15 seconds and is a clusterwide service parameter under Device - General. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Configure / T302 timer section. Checked 2026-09-24.
[^43]: A translation pattern is assigned to a partition from the Partition drop-down list in the Translation Pattern Configuration window. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) - Configure Translation Patterns](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1/systemConfig/cucm_b_system-configuration-guide-1251/cucm_b_system-configuration-guide-1251_chapter_010110.html), Configure Translation Patterns > procedure steps. Checked 2026-09-24.
[^44]: When dialed digits match a translation pattern, Unified CM does not route the call to an outside entity such as a gateway; it applies the translation and then routes the call again using the calling search space configured on the translation pattern. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Configure Call Routing > Call Routing Overview > Translation Patterns. Checked 2026-09-24.
[^45]: In Unified CM Release 15, translation patterns follow the same general rules and use the same wildcards as route patterns. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Configure Call Routing > Call Routing Overview > Translation Patterns. Checked 2026-09-24.
[^46]: Each translation pattern must have a unique combination of partition, route filter and numbering plan. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Configure Call Routing > Call Routing Configuration Task Flow > Configure Translation Patterns (note). Checked 2026-09-24.
[^47]: Cisco Unity Connection does not support the international escape character +, so numbers must be localized before they are delivered to it. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Restrictions. Checked 2026-09-24.
[^48]: When urgent priority is enabled on a directory number, Unified CM routes a call to that fully qualified DN immediately rather than waiting for the interdigit timeout, even when longer overlapping patterns exist. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Introduction / feature overview. Checked 2026-09-24.
[^49]: Urgent priority on directory numbers became available with Unified CM 10; before that, calls to a DN that overlapped longer patterns waited for T302 (inferred). Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Background / pre-10.0 behaviour statement. Checked 2026-09-24.
[^50]: In current Unified CM releases, urgent priority on a translation pattern appears to be a per-pattern setting rather than fixed, because Cisco design guidance tells administrators to provision normalization translation patterns as urgent (inferred). Source: [Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html), Dial Plan > Dialing Normalization Translation Patterns. Checked 2026-09-24.
[^51]: In Unified CM patterns, the @ wildcard matches all National Numbering Plan numbers. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Route Patterns Settings > wildcards and special characters table, row @. Checked 2026-09-24.
[^52]: In Unified CM patterns, the ! wildcard matches one or more digits from 0 through 9. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Route Patterns Settings > wildcards and special characters table, row !. Checked 2026-09-24.
[^53]: In Unified CM patterns, the dot (.) is a delimiter that separates an access code from the directory number and marks the boundary used by pre-dot digit removal. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Route Patterns Settings > wildcards and special characters table, row . and pre-dot digit removal text. Checked 2026-09-24.
[^54]: In Unified CM patterns, # generally identifies the end of the dialing sequence. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Route Patterns Settings > wildcards and special characters table, row #. Checked 2026-09-24.
[^55]: In Unified CM patterns, the X wildcard matches any single digit from 0 through 9. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Route Patterns Settings > wildcards and special characters table, row X. Checked 2026-09-24.
[^56]: Transformation patterns are placed in route partitions and reach calls through calling search spaces assigned in the device, device pool, gateway or trunk configuration. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Configure Call Routing > Call Routing Overview > Transformation Patterns. Checked 2026-09-24.
[^57]: Transformation patterns can discard digits, prefix digits, apply a calling party transformation mask and control calling party number presentation. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) - Configure Transformation Patterns](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1/systemConfig/cucm_b_system-configuration-guide-1251/cucm_b_system-configuration-guide-1251_chapter_010111.html), Transformation Pattern Overview. Checked 2026-09-24.
[^58]: Calling and called party transformation patterns are configured in Cisco Unified CM Administration under Call Routing > Transformation > Transformation Pattern > Calling Party Transformation Pattern and Called Party Transformation Pattern respectively. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) - Configure Transformation Patterns](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1/systemConfig/cucm_b_system-configuration-guide-1251/cucm_b_system-configuration-guide-1251_chapter_010111.html), Transformation Pattern Configuration Task Flow, steps 1 and 2. Checked 2026-09-24.
[^59]: Calling party transformation patterns must be placed in a non-null partition that is not used for routing. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010110.html), Calling Party Normalization Restrictions. Checked 2026-09-24.
[^60]: Transformation profiles (Call Routing > Transformation > Transformation Profile) are needed only when Cisco Intercompany Media Engine is used, to convert numbers to E.164 form. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) - Configure Transformation Patterns](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1/systemConfig/cucm_b_system-configuration-guide-1251/cucm_b_system-configuration-guide-1251_chapter_010111.html), Transformation Pattern Configuration Task Flow, step 3. Checked 2026-09-24.