Source record · tier 2 current vendor documentation
Implement the migration from Unified CM to Webex Calling
- Publisher
- Cisco Systems, Inc. (Webex Help Center)
- URL
- https://help.webex.com/en-us/article/q0pgpb/Implement-the-migration-from-Unified-CM-to-Webex-Calling
- Published
- unknown
- Updated
- unknown
- Accessed
- 2026-09-16
- HTTP status
- 200
- License
- Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only
Source notes citing this source
- For dual call control, Cisco says to deploy one or more Local Gateways for on-premises PSTN to allow calling between Webex Calling and Unified CM endpoints. in context
- Cisco says to create a trunk and a route group for each Local Gateway and assign the route group as the location's PSTN choice, and recommends always choosing a route group so trunks can be added later for scale and redundancy. in context
- Cisco's implementation checklist says to disable or delete the user and device directory number and calling features on Unified CM after the user has transitioned to Webex Calling. in context
- When on-premises call control is integrated, Webex Calling enterprise dial plans should contain only the patterns needed to route calls to on-premises destinations. in context
- After migrating a group of users Cisco says to test a subset of them, including end-to-end inbound and outbound PSTN calls delivered to users, call queues, hunt groups and auto attendants. in context
- In the US and Canada the Webex Calling location address is validated and used to send PIDF-LO location information with emergency calls. in context
- The Webex Calling enterprise dial plans used for coexistence contain only the patterns needed to route calls to on-premises destinations. in context
- Cisco's implementation guidance says to enable dual-identity and P-Charge-Info support on every PSTN trunk. in context
- Numbers can be added to a Webex Calling location as inactive when they should not yet be included in call routing. in context
- Cisco recommends migrating whole physical sites or departments in the same batch, after verifying that the batch's users and telephone numbers are all in Control Hub. in context
- For on-premises PSTN and Cloud Connected PSTN, numbers are ordered and ported with the provider before they are configured in Control Hub; for Cisco Calling Plans, ordering and porting start in Control Hub once the location exists. in context
- Cisco strongly recommends always selecting a route group, not a single trunk, as a location's PSTN choice, and says a trunk and a route group must be created for each local gateway. in context
- Cisco's implementation sequence begins by setting up the trunks and local gateways that interconnect with the on-premises call control system, then creating enterprise dial plans that point to the appropriate route group. in context
- After a transition, Cisco says to disable or delete the user and device directory numbers and calling features on Unified CM. in context
- Each Webex Calling location needs its voicemail pilot number (voice portal number) set during location configuration. in context
- Acceptance testing includes confirming voicemail boxes are correctly assigned and accessible both from within the organization and remotely. in context
- The documented acceptance testing covers user provisioning against the source directory including extensions and DID assignments, inbound and outbound PSTN with caller ID, on-net calls with transfer, hold, forwarding and conferencing, call queue distribution logic, hunt group hunting algorithm, auto attendant greetings and menu trees, and voicemail retrieval. in context
- Users who must move in the same batch are identified by BLF monitoring relationships, membership of hunt pilots or call queues, shared lines, call pickup groups, intercom, and executive and administrative assistant pairings. in context
- When the integration involves multiple on-premises call control systems reached through different trunks, multiple Webex Calling dial plans are required. in context
- The documented implementation sequence runs network readiness, initial setup, Webex Calling service settings, procure PSTN, configure locations, integration with on-premises call control, migrate users in batches, provision devices, configure features, and acceptance testing. in context
- Before each batch is migrated the documented checks are that all users exist in Control Hub, that all their telephone numbers exist in Control Hub, that the directory holds the correct phone number format, and that licensing and settings templates are configured. in context
- The PSTN connectivity option is selected and phone numbers ordered before calling locations are configured, because a location is provisioned with its PSTN choice and its main and voicemail pilot numbers. in context
- Integrating Webex Calling with on-premises call control requires configuring trunks, route groups, enterprise dial plans and both location and global settings. in context
- Coexistence routing is enabled per location by turning on unknown extension routing and specifying the maximum unknown extension length in the Call Routing between Webex Calling and premises section. in context
- A calling location requires a valid street address, and in the United States and Canada that address is validated by the platform and used to send PIDF-LO location information for emergency calls. in context
- Since neither the data migration nor the firmware migration documents a reverse action, the practical safety net for a batch is keeping the Unified CM configuration and the Local Gateway interconnect in place so unmigrated and migrated users still reach each other, rather than an undo. inferred in context
- Cisco's migration implementation guidance says acceptance tests should verify that mailboxes are correctly assigned, accessible from inside the organisation and remotely, that messages can be recorded, retrieved and managed, and that notifications are delivered. in context
- To enable voicemail at a Webex Calling location, the administrator must set the voicemail pilot number, which Cisco also calls the voice portal number. in context
Cite this source record
APA
WarmTransfer. (2026, September 16). Implement the migration from Unified CM to Webex Calling. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-q0pgpb-implement-migrate-ucm-wxc
BibTeX
@misc{warmtransfer-cisco-help-q0pgpb-implement-migrate-ucm-wxc,
title = {Implement the migration from Unified CM to Webex Calling},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/cisco-help-q0pgpb-implement-migrate-ucm-wxc},
note = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-16}
}