Why Number Management Deserves Its Own Guide
Number management is one of those topics that looks simple until something goes wrong. Porting a number that doesn’t complete on time delays a go-live. A number assigned to the wrong location routes emergency calls to the wrong PSAP. An unassigned number sitting in inventory runs up billing without serving anyone.
This guide covers the full number management lifecycle in Webex Calling — ordering new numbers, porting existing numbers from another carrier, assigning numbers to users and services, and the operational practices that keep number management clean over time.
Before working through number management, your PSTN option should already be selected and configured. The decision framework for Cisco Calling Plans, Operator Connect, and Local Gateway is covered in PSTN Options in Webex Calling. Location setup, which determines where numbers land in your inventory, is covered in Control Hub Deep Dive — Configuring Users, Locations, and Calling Features.
How Numbers Work in Webex Calling
Every phone number in Webex Calling lives in one of two states: inventory or assigned. Inventory numbers are provisioned to your organization but not yet assigned to a user, workspace, or service. Assigned numbers are actively routing calls to a destination.
Numbers are always tied to a location. When you order or port a number, it lands in the inventory of a specific location. When you assign it, it routes calls based on the PSTN provider and calling policies of that location. A number cannot be assigned to a user at a different location without first being moved — this matters for multi-site deployments where numbers and users need to be at the same location for emergency calling to work correctly.
Number management in Control Hub lives under Calling > Numbers. From this view you can see all numbers across all locations, filter by assignment status, and initiate number orders and ports.
Adding New Numbers
Cisco Calling Plans
If your PSTN option is Cisco Calling Plans, new numbers are ordered directly through Control Hub. Navigate to Calling > Numbers > Add Numbers and select Get New Numbers.
Choose the location the numbers should be assigned to, select the country, and search by area code or city. Control Hub returns available numbers in the requested area code. Select the numbers you want and confirm the order. Numbers typically appear in your inventory within minutes for standard DID orders.
A few things to keep in mind when ordering:
Order more than you need. Order 10–20% more numbers than your immediate requirement. Numbers in a specific area code are not always available when you need them, and having inventory on hand avoids delays when you need to assign a number quickly for a new hire or a new service.
Toll-free numbers are ordered separately. Navigate to Calling > Numbers > Add Numbers and select Get Toll-Free Numbers. Toll-free number availability is separate from geographic DID availability and the ordering process is slightly different — you select a toll-free prefix (800, 888, 877, etc.) and search for available numbers.
Number types matter for assignment. Standard DIDs can be assigned to users, workspaces, call queues, and auto attendants. Toll-free numbers are typically assigned to call queues, auto attendants, or hunt groups that handle inbound calls — assigning a toll-free number directly to a user extension is unusual and usually intentional.
Cloud Connected PSTN (Operator Connect)
For Operator Connect deployments, number ordering happens through your carrier’s provisioning portal, not through Control Hub. The carrier provisions the numbers on their side and they appear in your Control Hub inventory once the carrier completes provisioning.
The Control Hub side of the process is assignment only — you cannot initiate a new number order from Control Hub for Operator Connect numbers. Work with your carrier’s account team for number orders and coordinate the timing so numbers appear in inventory before you need to assign them.
Local Gateway
For Local Gateway deployments, numbers are provisioned by your SIP carrier outside of Webex Calling entirely. Numbers appear in Webex Calling only after they have been manually added to Control Hub and associated with the Local Gateway trunk.
Navigate to Calling > Numbers > Add Numbers > Add Numbers Manually to add numbers from a Local Gateway carrier. Enter the number in E.164 format and select the location and trunk the number should be associated with. This is a manual process — there is no automatic synchronization between your carrier’s number inventory and Control Hub for Local Gateway deployments.
For deployments with large number ranges, the manual add process is impractical for individual numbers. Use the CSV import option under Calling > Numbers to bulk-add a range of numbers in a single operation. Format the CSV with one number per row in E.164 format, specify the location and trunk, and import.
Porting Existing Numbers
What Number Porting Actually Involves
Porting transfers a phone number from one carrier (the losing carrier) to another (the gaining carrier). In a Webex Calling deployment, Cisco or your Operator Connect carrier is the gaining carrier. The losing carrier is whoever currently holds the number.
The process requires a Letter of Authorization — a document signed by an authorized representative of the account that currently holds the number, authorizing the transfer. The LOA must match exactly what the losing carrier has on file for the account. Mismatches between the LOA and the carrier’s account records are the most common cause of port rejections.
What Can and Cannot Be Ported
Most geographic DIDs can be ported. Numbers that frequently encounter porting complications:
- Numbers with active contracts — if the losing carrier has the number locked under an early termination clause, porting may trigger a contract penalty. Verify contract status before initiating a port
- Toll-free numbers — toll-free numbers can be ported but the process and timeline are different from geographic DIDs. Some toll-free numbers are subject to Responsible Organization (RespOrg) restrictions that complicate porting
- Numbers associated with DSL or bundled services — some carriers bundle phone numbers with internet service. Porting the number may affect the associated services. Confirm with the losing carrier before initiating
- Foreign numbers — numbers in countries where the gaining carrier doesn’t support porting cannot be ported. Verify porting availability for every country in a multi-country deployment before committing to a porting timeline
Initiating a Port in Control Hub
For Cisco Calling Plans, porting is initiated through Control Hub. Navigate to Calling > Numbers > Add Numbers > Port Numbers. The process:
- Enter the numbers to be ported — one per line in the format the carrier uses
- Provide the account information that matches the losing carrier’s records exactly — account number, billing address, authorized contact name
- Upload the signed Letter of Authorization
- Select the target location and the requested port date
Control Hub submits the port request to Cisco, who coordinates with the losing carrier. You’ll receive status updates as the port progresses through the standard porting stages: submitted, accepted, scheduled, and completed.
For Operator Connect, porting is initiated through your carrier’s portal. The process varies by carrier but the information required is the same — account details, LOA, requested port date. Coordinate with your carrier’s porting team rather than through Control Hub.
LOA Requirements — Where Ports Go Wrong
The LOA is the document the losing carrier uses to verify that the account holder has authorized the transfer. Carriers reject ports when the LOA information doesn’t match their records exactly. Common rejection reasons:
Name mismatch — the authorized contact name on the LOA doesn’t match the name on the losing carrier’s account. Use the exact legal name associated with the account, not a common name or nickname.
Address mismatch — the billing address on the LOA doesn’t match the carrier’s records. Use the address the carrier has on file, not the current physical address if the account was set up at a previous address.
Account number error — wrong account number on the LOA. Get the account number directly from the carrier’s billing portal or a recent invoice, not from memory.
Partial number lists — some carriers require that all numbers on an account are either ported together or that the account holder explicitly authorizes a partial port. Submitting a partial port without that authorization gets rejected.
Rejected ports restart the clock. A port that gets rejected and resubmitted adds one to two weeks to the porting timeline. Get the LOA right the first time.
Porting Timelines
Standard geographic DID porting in North America typically takes 5–10 business days from LOA submission to completion, assuming no rejection. Plan for two to four weeks of total elapsed time from initiating the port to having numbers available to assign — this accounts for LOA preparation, carrier processing, potential rejection and resubmission, and the scheduled port date.
Do not schedule a go-live date around a port completion date you don’t control. Port dates slip. Build a buffer into the project timeline and have a contingency plan — temporary numbers or call forwarding from the old carrier — that covers the gap if the port runs late.
The Actual Port Event
On the scheduled port date, the number transfers at a specific time — typically during a maintenance window in the early morning hours. During the port, the number is briefly unavailable on both the old and new carrier. This unavailability window is typically seconds to minutes but can be longer if the losing carrier’s systems are slow to release.
For business-critical numbers, schedule ports during off-hours or on weekends when call volume is lowest. A support line that ports at 2am on a Sunday affects fewer callers than one that ports at 10am on a Tuesday.
After the port completes, verify the number is in your Control Hub inventory and test inbound and outbound calls before considering the port successful.
Assigning Numbers
Assigning to Users
Navigate to Management > Users > select user > Calling. Under the calling configuration, assign a primary phone number and optionally one or more extension numbers. The primary number must be from the inventory of the same location the user is assigned to.
A user can have one primary number and multiple extensions. Extensions are for internal dialing only — they don’t consume a DID from your inventory. If a user needs to be reachable from outside the organization, they need a DID assigned as their primary number.
For bulk number assignment during initial deployment, the CSV import process under Management > Users supports number assignment as part of the user import. Include the number column in the CSV template and assign numbers during the initial user creation rather than as a separate step.
Assigning to Workspaces
Workspace numbers are assigned when the workspace is created or from the workspace configuration in Control Hub under Workspaces > select workspace > Calling. The same rule applies — the number must be from the inventory of the location the workspace is assigned to.
Workspaces typically represent shared phones: lobby phones, conference rooms, common area devices. Each workspace needs a number if it needs to be reachable by external callers. Internal-only workspaces can operate with an extension only.
Assigning to Services
Call queues, auto attendants, and hunt groups each need a number or extension to be reachable. Numbers are assigned during service configuration under Calling > Features > select the service. Full configuration guidance for these services is covered in Webex Calling Hunt Groups, Auto Attendants, and Call Queues — Production Setup Guide.
A few assignment considerations for services:
Main company number — the primary inbound number for the organization typically points to the main auto attendant. This is the number that appears on business cards, the website, and in directory listings. Assign it to the auto attendant during initial configuration and don’t change it without planning for the downstream effects on all the places that number is published.
Direct numbers for queues — high-volume call queues sometimes benefit from a dedicated DID that bypasses the auto attendant. Customers who know the direct number for support or sales reach the queue without navigating the main menu.
Extension-only services — services that are only reachable internally (a back-office hunt group, an internal announcement service) can use an extension without a DID. This preserves DID inventory for services that need external reachability.
Number Inventory Management
Auditing Unassigned Numbers
Unassigned numbers in inventory still cost money on Cisco Calling Plans — you’re paying for capacity that isn’t being used. Run a number audit periodically to identify and release numbers that aren’t needed.
Navigate to Calling > Numbers and filter by Unassigned. Review the unassigned inventory against your current deployment and release numbers that have no planned use. For Cisco Calling Plans, releasing a number removes it from your inventory and stops the associated billing.
For Operator Connect and Local Gateway deployments, releasing a number from Control Hub may not automatically remove it from your carrier’s inventory — coordinate with your carrier to ensure released numbers are removed from billing.
Moving Numbers Between Locations
A number assigned to one location cannot be directly reassigned to a user at a different location. To move a number between locations:
- Unassign the number from its current user or service
- Navigate to the number in Calling > Numbers and change the location assignment
- Reassign the number to the user or service at the new location
For Local Gateway deployments, moving a number between locations may also require updating the trunk association if the two locations use different Local Gateway trunks.
E911 Address Verification
Every assigned number must have a valid emergency address. Run a periodic audit of number-to-address assignments to verify that emergency addresses are current — particularly after office moves, location changes, or user relocations.
Navigate to Calling > Numbers and review the emergency address column for each assigned number. Numbers with missing or outdated emergency addresses are a compliance risk under Ray Baum’s Act. Resolve them before they become a problem.
Common Number Management Mistakes
Porting on a tight timeline. Building a go-live date around a port completion date is a recurring source of project delays. Ports slip. Build two to four weeks of buffer and have a fallback plan.
LOA information that doesn’t match carrier records. Check the exact account name, billing address, and account number against the carrier’s records before submitting the LOA. One mismatched field restarts the clock.
Numbers assigned to the wrong location. A number at Location A assigned to a user at Location B routes emergency calls to the wrong PSAP. Verify number and user location assignments match before go-live.
Unmanaged number inventory. Unassigned numbers accumulate over time as users leave and services are retired. Quarterly audits prevent billing for unused capacity from becoming a line item nobody questions.
Not ordering spare inventory. Needing a specific area code number on short notice and finding none available is avoidable. Keep a small buffer of unassigned numbers in each area code where the organization operates.
Forgetting toll-free porting lead time. Toll-free number ports take longer than geographic DID ports and involve additional steps. If a toll-free number is part of the go-live scope, initiate the port earlier than you think you need to.
Final Thoughts
Number management is operational discipline more than technical complexity. The technical steps — ordering, porting, assigning — are straightforward once you understand how Control Hub organizes numbers by location and how porting works at the carrier level. What causes problems is the operational side: LOAs that don’t match, ports scheduled too close to go-live, inventories that drift out of alignment over time.
Build number management into your ongoing operational cadence — quarterly audits, proactive LOA preparation before ports, and spare inventory in active area codes — and it stays manageable. Let it slide and you end up with billing for numbers nobody uses and emergency addresses that haven’t been updated since the last office move.