Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control

Publisher

Cisco

URL

https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/control.html

Published

2021-05-21

Updated

unknown

Accessed

2026-09-23

HTTP status

200

License

Cisco website terms of use; no-redistribution; short excerpts and locators only

Source notes citing this source

• The calling number a carrier receives from a globalized Unified CM dial plan can be shaped in two places, Unified CM calling party transformation CSSs and IOS voice translation rules on the gateway, so both must be checked when the carrier sees an unexpected caller ID. inferred in context
• Combining +E.164 route patterns with local route groups means one country-level set of PSTN route patterns can serve every site in that country, with site-specific differences carried by device pools rather than by patterns. inferred in context
• With +E.164 directory numbers, AAR needs no multiple AAR groups or AAR PSTN prefixes because the on-net destination number can be used directly as the alternate PSTN address. in context
• Cisco lists as benefits of +E.164 directory numbers that they are unique, simplify forced on-net routing, and give correct caller ID automatically across call flows. in context
• In Cisco's Collaboration 14 Preferred Architecture, every endpoint directory number that has a DID is provisioned as a +E.164 number. in context
• Provider-specific localization of calling and called numbers on outbound calls is done either on the gateway with Cisco IOS voice translation rules or on Unified CM with calling and called party transformation patterns. in context
• For endpoints without a DID, the Preferred Architecture uses an enterprise specific number made of an access code, a site code and an extension (example 8-140-4001). in context
• Cisco identifies the number of classes of service as a key driver of dial plan complexity and advises defining as few as possible. in context
• In multi-cluster deployments the Preferred Architecture uses Global Dial Plan Replication, which can advertise one +E.164 number, one enterprise significant number and up to five alphanumeric URIs per directory number. in context
• Because the Preferred Architecture routes everything on +E.164, the called party number of every inbound PSTN call must be globalized to +E.164 from the format the provider sends. in context
• The Preferred Architecture globalizes inbound numbers partly with Cisco IOS translations on the SIP gateway, which it says are required so that ISDN number type information is not lost when the call is sent to Unified CM over SIP. in context
• A route pattern pointing at a route list that contains a local route group resolves to the route group configured for that local route group in the calling party's device pool. in context
• On fixed-length dialing normalization translation patterns, the Preferred Architecture also sets Do Not Wait For Interdigit Timeout On Subsequent Hops. in context
• The Preferred Architecture sets Use Originator's Calling Search Space on dialing normalization translation patterns so that the secondary lookup uses the same CSS as the primary lookup. in context
• The Preferred Architecture provisions all dialing normalization translation patterns as urgent patterns. in context
• The Preferred Architecture uses calling party transformation patterns in dedicated partitions (for example SJCPhLocalize and USPhLocalize) to localize +E.164 calling numbers for abbreviated display on phones. in context
• Cisco's Collaboration 14 Preferred Architecture recommends connecting individual Unified CM clusters with a full mesh of SIP trunks. in context
• The Preferred Architecture says ILS is required between all Unified CM clusters in a multi-cluster deployment because GDPR uses it as transport. in context
• With more than four clusters, the Preferred Architecture suggests Session Management Edition to centralise the dial plan and trunking instead of a full mesh of SIP trunks. in context
• The Collaboration 14 enterprise CVD call control chapter states that it does not cover Unified CM SME. in context
• The Collaboration 14 Preferred Architecture recommends deploying SME with four or more Unified CM clusters, to centralize dial plan and trunking and avoid a full-mesh SIP trunk topology. in context
• Without SME, the Preferred Architecture interconnects Unified CM clusters with a full mesh of SIP trunks so calls do not traverse intermediate clusters. in context
• GDPR can advertise one +E.164 number, one enterprise significant number and up to five alphanumeric URIs for each directory number. in context
• GDPR uses ILS as its transport, so a multi-cluster deployment requires ILS between all Unified CM clusters. in context
• 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 in context
• 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. in context
• The Cisco Collaboration 14 preferred architecture provisions every directory number on endpoints that have a DID as a +E.164 number. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• Route patterns that point to a local route group select the egress gateway dynamically, based on the device that originated the call. in context
• 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. in context
• 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. in context
• The Collaboration 14 preferred architecture provisions all dialing normalization translation patterns as urgent patterns. in context
• 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. in context
• 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. in context
• 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). in context
• 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 in context
• The Collaboration 14 Preferred Architecture recommends enabling Use Originator's Calling Search Space on normalization translation patterns, so the secondary lookup uses the same CSS as the primary lookup. in context

Cite this source record

APA

WarmTransfer. (2021, May 21). Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cvd-pa-collab14-call-control

BibTeX

@misc{warmtransfer-cisco-cvd-pa-collab14-call-control,
  title  = {Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control},
  author = {{WarmTransfer}},
  year   = {2021},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cvd-pa-collab14-call-control},
  note   = {Cisco, accessed 2026-09-23}
}