Cloud Calling · Webex

Webex Calling Number Plan

Plan DID ranges, extension numbering, and reserved blocks for auto-attendants, hunt groups, and voicemail pilots. Emits a carrier-ready port request and Control Hub assignment list.

By Faz Karim · 30 yrs Cisco UCLast updated 2026-04-20
What this tool does

DID blocks + extensions without collisions

Every Webex Calling deployment needs a clean number plan: DIDs for users who need external reach, extensions for internal-only, plus reserved blocks for AAs, hunt groups, paging, and voicemail pilots. This tool takes your user count + DID block size and produces the full allocation — plus a carrier LOA / port request template if you're migrating numbers.

Build your number plan

Inputs

Your number plan

Enter counts, click Generate Number Plan.

How to read your result

Four number categories

1

User DIDs

One per user with external calling.

2

Extensions

Internal-only. Same plan for DID users too.

3

AA / Hunt

Reserved ext block for call routing objects.

4

Spares

10-20% growth headroom.

Deep dive

Extensions that match last-4 of DID

Best-practice numbering: extension = last 4 of DID. If user DID is +1 214 555 1042, their extension is 1042. This makes internal reach-me predictable and works with mobile soft clients that show extension vs external number. The downside: DID block must be contiguous. If your carrier can only give you fragmented blocks, fall back to a separate extension plan (e.g. 2000-3999 for HQ, 4000-5999 for Branch).

Reserve extensions for routing objects. Don't assign AAs and hunt groups random numbers — designate a block like 8000-8099 for AAs, 8100-8199 for hunt groups, 8200-8299 for voicemail pilots. This makes audit and troubleshooting much easier two years later when you've forgotten which object answered what.

Port windows are 10-14 business days on average. Submit your port request with the full LOA (Letter of Authorization), CSR (Customer Service Record), and authorized signature 3 weeks before cutover. Webex Calling coordinates the port date with you; numbers swing at a pre-announced minute.

FK
Faz Karim30 years Cisco Network · UC · Data Center · LinkedIn
FAQ

Common questions

Can I split a DID block across locations?

Yes, but Control Hub assigns numbers to locations, not ranges. Easier if contiguous.

What's the minimum DID block size?

Webex Calling sells in blocks of 10, 100, or 1000 depending on provider.

How long does porting take?

10-14 business days for the LOA submission + carrier coordination.

Can I keep toll-free numbers?

Yes — toll-free ports work the same way. Submit separate LOA to the TF carrier.

Worked examples

Three numbering scenarios

100 users, all DID

Clean block from single area code.

100 user DIDs + 20 spares + 20 routing ext = 140 DIDs purchased.
Simplest case. Extension = last 4.

Mixed: 80 DID + 40 internal-only

Warehouse has shared phones, office has DIDs.

80 DIDs + 60 extensions (40 shared + 20 routing). Extension 2000-2039 = internal.
Save money on DID costs for shared-phone workers.

Porting 300 numbers

Leaving legacy PBX.

LOA submitted, port date scheduled, parallel provisioning 2 weeks.
Test forwarded call path before port date.
Sources verified against current Cisco guidance

Citations

Related tools

You might also need

Planning a number port?

Our UC Modernization Sprint coordinates carrier, validates records, and manages the port window — no lost calls.

$25K–$75Kturnkey
Book a 30-min call →Or email info@famoustec.com