Enterprise dial plan design and normalization
Verified 2026-09-04 · 7 claims · sources tier 2
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
- E.164 numbering and dial string normalizationstub — Pattern matching is defined over E.164 and enterprise formats
Referenced by
- Trunks route groups and dial plans in Control Hub — Dial plans select the trunk or route group for a pattern
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | For 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. Cisco Preferred Architecture for Webex Calling — Design Overview · Patterns and pattern matching, page 30 | fact | 0.90 | 2026-09-04 |
| 2 | Dial plan patterns must be unique across the organisation; the same pattern cannot exist in 2 different dial plans, which makes routing deterministic. Cisco Preferred Architecture for Webex Calling — Design Overview · Patterns and pattern matching, page 30 | fact | 0.90 | 2026-09-04 |
| 3 | Webex Calling dial plans are global to the enterprise and apply to all users regardless of location. Cisco Preferred Architecture for Webex Calling — Design Overview · Dial Plans, page 30 | fact | 0.90 | 2026-09-04 |
| 4 | A 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 | fact | 0.90 | 2026-09-04 |
| 5 | A 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 | fact | 0.90 | 2026-09-04 |
| 6 | A maximum of 10000 dial plans may be configured per customer, and each dial plan may hold up to 10000 dial patterns. Cisco Preferred Architecture for Webex Calling — Design Overview · Dial Plans, page 30 | fact | 0.90 | 2026-09-04 |
| 7 | A 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 | fact | 0.60 | 2026-09-04 |
Sources
Cisco Preferred Architecture for Webex Calling — Design Overview
Configure trunks, route groups, and dial plans for Webex Calling
Configure Webex Calling for your organization
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}
}