Plan a Cisco Unified CM to Webex Calling Dedicated Instance migration
Dedicated Instance is Cisco Unified CM run for you in the Webex cloud. Users keep the features they know. The work is rebuilding your configuration on a new cluster and moving phones, trunks and voicemail to it without a gap.
What stays the same
The call control software, the dial plan model of partitions and calling search spaces, device pools, hunt lists, and the phones themselves. An administrator who runs your current cluster will recognize the new one.
What changes
- Where the cluster lives. Phones and gateways reach it over the connection you set up to the Webex cloud, so addressing, name resolution and firewall rules change.
- Trust. Phones trust the cluster they were registered to. Moving them to a new cluster means dealing with each phone's stored trust list.
- Who operates what. Cisco runs the infrastructure the cluster sits on. Your configuration remains yours.
- How calls reach the telephone network. Through a local gateway you keep, or a cloud-connected carrier.
Plan in this order
- Inventory the source cluster, including presence and voicemail. Clean out what is unused before you copy it.
- Agree the network path between your sites and the new cluster, and test it with one phone before anything else.
- Rebuild the foundation: partitions and calling search spaces, regions, locations, device pools, media resources.
- Rebuild routing: trunks, route groups and lists, route and translation patterns. Decide which gateways stay.
- Move users and services, including directory integration and sign-in.
- Move devices in groups. Start with a small group on one site. Plan the trust list step for each phone model.
- Move features: hunt groups, pickup, park, intercom, extension mobility.
- Move voicemail: mailboxes, call handlers and greetings.
- Verify each layer by reading it back from the new cluster and comparing it with the source.
Decisions to make early
- Whether numbers are ported or stay with the current carrier through a local gateway.
- Whether encrypted phone profiles move as they are or are re-secured after the move.
- How users on the old and new clusters call each other while both are live.
- What you will remove to roll a group back, and who decides to do it.
A layer that was not verified is a layer the next one is built on anyway.
Where Vector helps
Vector reads the source cluster through an on-site collector and rebuilds it on Dedicated Instance in ordered phases, from calling search spaces through devices to voicemail. Each phase is pushed, verified and can be rolled back before the next begins.