sbc trunking · stub

Enterprise dial plan design and normalization

Verified 2026-09-04 · 7 claims · sources tier 2

Stub. This topic has 7 verified claims and no published article. The claims below are exactly what the corpus holds today.

This topic covers enterprise dial plan design and normalization within Webex Calling, specifically focusing on how global dial plans apply to all users across an organisation. The provided claims detail that dial plan patterns must remain unique to ensure deterministic routing. Additionally, they outline the specific evaluation order for calls resolving to Webex Calling, starting with plus-prefixed E.164 patterns, followed by enterprise number patterns without prior normalization, and concluding with domain or URI patterns. Finally, the coverage notes how conflicts are resolved when multiple patterns match, prioritizing the most specific pattern and preferring range patterns using X over prefix patterns using the exclamation mark.

See also

Depends on

Referenced by

Claims

#ClaimStatusConfidenceVerified
1For calls resolving to Webex Calling, plus-prefixed E.164 patterns are evaluated first, then enterprise number patterns with no normalisation applied beforehand, and finally domain or URI patterns; where several patterns match, the most specific wins and range patterns using X are preferred over prefix patterns using the exclamation mark.fact0.902026-09-04
2Dial plan patterns must be unique across the organisation; the same pattern cannot exist in 2 different dial plans, which makes routing deterministic.fact0.902026-09-04
3Webex Calling dial plans are global to the enterprise and apply to all users regardless of location.fact0.902026-09-04
4A per-location setting for calls to on-premises extensions lets users keep abbreviated dialling, for example 4 digits, while a site is only partially migrated, by routing unmatched extensions of a configured length between 2 and 10 digits to a chosen route group or trunk.
Configure trunks, route groups, and dial plans for Webex Calling · Configure calls to on-premises extensions
fact0.902026-09-04
5A Webex Calling dial plan differentiates destinations bound for the on-premises Unified CM, which are sent as enterprise calls, from all other destinations, which are sent as PSTN calls, over the same trunk or route group.
Cisco Preferred Architecture for Webex Calling — Design Overview · Interconnect with On-Premises Call Control, page 31
fact0.902026-09-04
6A maximum of 10000 dial plans may be configured per customer, and each dial plan may hold up to 10000 dial patterns.fact0.902026-09-04
7A location routing prefix may be 1 to 7 digits, and internal extension length is configurable from 2 to 10 digits with a default of 4.
Configure Webex Calling for your organization · Dial plan configuration, internal dialing settings
fact0.602026-09-04

Sources

tier 2 current vendor documentation

Cisco Preferred Architecture for Webex Calling — Design Overview

Cisco Systems, Inc. (CTG TME) · 2025-08 · accessed 2026-09-04

tier 2 current vendor documentation

Configure trunks, route groups, and dial plans for Webex Calling

Cisco Systems, Inc. (Webex Help Center) · 2026-04-28 · accessed 2026-09-04

tier 2 current vendor documentation

Configure Webex Calling for your organization

Cisco Systems, Inc. (Webex Help Center) · 2026-08-05 · accessed 2026-09-04

Cite this page

APA

WarmTransfer. (2026, September 4). Enterprise dial plan design and normalization. WarmTransfer. https://warmtransfer.net/knowledge/dial-plan-design

BibTeX

@misc{warmtransfer-dial-plan-design,
  title  = {Enterprise dial plan design and normalization},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/dial-plan-design},
  note   = {Verified 2026-09-04}
}