Design a collision-free Webex Calling dial plan: internal extensions, ESN site codes, outbound access, emergency dialing, international restrictions, and short codes for paging/intercom. Emits Control Hub-ready config.
Webex Calling lets each location have its own extension range, but users expect to dial the same number of digits regardless of where they're calling. ESN (Enterprise Significant Number) with site codes gives you that: a 7-digit internal number that works from any phone, any location. This tool designs the ESN plan, outbound routing, emergency, and international controls in one pass.
Set inputs, click Generate Dial Plan.
Extensions + ESN site codes.
Access code, LD, emergency.
Paging, intercom, pickup.
User-dialed → E.164.
In a single-site deployment, 4-digit extensions are easy: dial 1042 and you reach Mary. In a multi-site deployment with overlapping extensions (both HQ and Branch have 1042), you need Enterprise Significant Number (ESN) patterns. The common convention is site code + extension: dial 81-1042 to reach Mary at HQ (site 81), dial 82-1042 to reach a different Mary at Branch (site 82). Webex Calling implements this via Location Routing Prefix in Control Hub — assign each location a prefix, users dial prefix + extension.
Emergency dialing is non-negotiable. US users will dial 911 by reflex, even if your trained pattern is 9.911. Always configure both 911 and 9.911 as emergency route patterns — Webex Calling handles this automatically for CER-integrated sites, but you must verify in Control Hub Calling Settings. 988 (suicide and crisis lifeline) was added in 2022 and should route with the same urgency as 911 to local PSAPs.
International dialing is where fraud happens. Most toll fraud comes from compromised voicemail calling +234 (Nigeria) or +27 (South Africa) overnight. Unless your business needs global dialing, restrict to the countries you actually call. Webex Calling lets you build an allowed-country list — maintain it as a named policy and apply to user groups. Use a separate PIN-protected class of service for the few users who need everywhere.
No — direct E.164 works natively. Access code 9 is for migration from legacy PBX users who won't change habits.
Technically yes, but confusing. Standardize on one length org-wide unless you have a strong reason.
Webex Calling routes to the emergency address configured for that user in Control Hub. Keep this updated via HELD or manual per E911.
Yes — add explicit deny rules for 1-900, 1-976 before the general LD allow.
One location, direct E.164 outbound.
HQ + 2 branches, ESN routing.
US + UK + AU, mixed emergency.
Our UC Modernization Sprint reverse-engineers your legacy PBX dial plan and rebuilds it cleanly in Webex Calling — no surprise call failures.