Source record · tier 2 current vendor documentation
System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization
- Publisher
- Cisco
- URL
- 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
- Published
- 2026-09-22
- Updated
- unknown
- Accessed
- 2026-09-23
- HTTP status
- 200
- License
- Cisco documentation copyright; no-redistribution; short excerpts and locators only
Source notes citing this source
- With calling party normalization, the phone shows a localized calling party number on its screen and the globalized number in its call log directories. in context
- Unified CM Calling Party Normalization lets administrators globalize and localize calling party numbers so that the appropriate calling presentation is displayed on the phone. in context
- A Calling Party Transformation CSS can be assigned to phones, device pools, gateways and trunks. in context
- The Unified CM calling party normalization chapter states that Cisco Unity Connection does not support the international escape character (+), so calling numbers must be localized before they reach Unity Connection. in context
- When a device roams under Device Mobility, the Calling Party Transformation CSS of the roaming device pool overrides the device-level Calling Party Transformation CSS. in context
- Incoming calling party prefix and strip-digit settings exist per number type (National, International, Subscriber, Unknown) and can be set on gateways, trunks, device pools and as clusterwide service parameters. in context
- Because Unified CM SIP trunks honour only Unknown-type incoming settings, a SIP-attached gateway facing an ISDN carrier needs to turn the ISDN number type into an explicit + prefix before the call reaches Unified CM, or the type is lost. inferred in context
- H.323 gateways do not support the + character, so numbers sent to them must be localized (the + removed) before egress. in context
- Unified CM SIP trunks and MGCP gateways can send the international escape character (+) on calls. in context
- Unified CM does not attempt to send the + character over QSIG. in context
- The clusterwide incoming calling party prefix service parameters apply to a device only when the corresponding prefix is left at its default at both the device and the device pool level. in context
- Cisco advises configuring the same Calling Party Transformation CSS on all devices that share a line, to avoid inconsistent calling number display. in context
- Because SIP does not carry number type, calls through Unified CM SIP trunks support only the incoming calling party settings for number type Unknown. in context
- Calling Party Transformation CSS settings do not apply to T1-CAS and FXO ports on a gateway. in context
- Calling party normalization may not be supported in some transferred-call scenarios because transfer relies on midcall updates. in context
- A phone inherits the device pool's calling party transformation CSS when its 'Use Device Pool Calling Party Transformation CSS' check box is selected. in context
- Calling Party Transformation CSS settings do not apply to T1-CAS and FXO ports on a gateway. in context
- Calling party transformation works only on the original calling party; changes made for redirecting numbers affect only the diversion header. in context
- 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. in context
- 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. in context
- Incoming calling party prefix and strip-digit settings are defined separately for four calling party number types: National, International, Subscriber and Unknown. in context
- 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. in context
- Calling party normalization prefix and strip-digit rules can be applied on device pools, route patterns, translation patterns, hunt pilots, gateways and trunks. in context
- SIP trunks and MGCP gateways can send the international escape character + on calls, but H.323 gateways do not support +. in context
- 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. in context
- 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. in context
- 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. in context
- Calling Party Normalization can strip at most 24 digits. in context
- Cisco Unity Connection does not support the international escape character +, so numbers must be localized before they are delivered to it. in context
- Calling party transformation patterns must be placed in a non-null partition that is not used for routing. in context
- In CUCM calling party normalization, globalization converts a local calling number to international form by adding country and area codes, and localization strips those prefixes for regional display so a phone can return the call without editing the number. in context
- CUCM 15 supports sending the '+' international escape character on outgoing calls over SIP trunks and MGCP gateways; H.323 gateways do not support it and QSIG trunks do not attempt to send it. in context
- Because SIP has no number type, CUCM SIP trunks apply only the Incoming Number prefix settings configured for calling party number type Unknown. in context
Cite this source record
APA
WarmTransfer. (2026, September 22). System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cucm-sysconfig-15-calling-party-normalization
BibTeX
@misc{warmtransfer-cisco-cucm-sysconfig-15-calling-party-normalization,
title = {System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Calling Party Normalization},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/cisco-cucm-sysconfig-15-calling-party-normalization},
note = {Cisco, accessed 2026-09-23}
}