As of April 30, 2021, all Workspace devices were automatically migrated in the backend. You do not need to manually migrate your Workspaces. Use the Device Connector to resync configuration changes if needed.

If you're an existing Hybrid Calling for Webex Devices (Call Connector) customer, you can use the Webex Device Connector to migrate your organization to the Hybrid Calling for Webex Device (Device Connector) solution. You're presented with a migration button directly in the tool. The tool preserves your existing configuration in the cloud; when completed, you can connect to your Unified CM environment to complete synchronization between the premises and the cloud. The migration does not cause a disruption in service; the data is moved and continues to work as before.

Before you begin

Install the Webex Device Connector using the procedure in the Device Connector documentation.

1

From Webex Device Connector, click I want to add on-premises calling to my cloud registered devices.

2

Read the migration notice to make sure you understand, and then click Migrate Now when you're ready.

Your organization is migrated in the backend.

3

After you receive a message that the migration succeeded, click Connect to Unified CM to begin synchronizing your on-premises setting with the Webex Device Connector.

  1. When selecting the service card (to proceed with enabling Call Service Connect as required), you must enter a value for the Expressway (you can enter any address and it doesn't need to resolve to a real Expressway).

  2. Then, go to the Hybrid Call Settings to configure Hybrid Call Service Connect (the SIP Destination that resolves to the Expressway-E).

  3. When that is done, you can download and install the Device Connector to migrate your organization and provision the workspaces.

This experience will be consistent for all organizations when Hybrid Call Service (for users) goes into end of support status.

What to do next

Follow the deployment guide for the synchronization steps.

You can retain your existing Hybrid Calling configuration and use the new solution to make sure it works correctly. After you verify that the new solution works, you can read the deployment guide for considerations for cleaning up existing configuration (for example, Expressways that are hosting the Call Connector).

You must ensure that the following configuration remains for Webex devices in a Workspace that are enabled for Hybrid Calling before migrating to the new solution (Hybrid Calling with the Webex Device Connector architecture).

1

Do not remove configuration from the Expressway-C and Expressway-E traversal pair.

Enterprise calls to and from Webex devices in a Workspace are securely routed over the Expressway pair for Hybrid Calling.

2

Do not remove SIP Destinations.

The SIP destination address in Control Hub resolves to your Expressway-E in the call traversal pair for Hybrid Call Service. All the hybrid call traffic goes through this address. This entry is typically a DNS-SRV record which can resolve to multiple Expressway-Es.

3

Do not deactivate Hybrid Call Service Connect for your organization.

This setting resides in Control Hub and is organization-wide. When enabled, Hybrid Call Service is active and available and can then be assigned to Webex-registered devices.

4

Do not remove Cisco Spark-RD or end user accounts that are tied to Webex devices in a Workspace.

The Cisco Spark-RD is a virtual device that is attached to an end user account's work number and links the Cisco Webex account SIP identity to the enterprise SIP identity so that calls anchor on the Unified CM side or fork to the Cisco Webex cloud side. Behind the scenes, the Cisco Spark-RD ties together call activity in the cloud, the premises, and the end user account is associated with Webex devices in a Workspace.

5

Do not remove Cisco Unified Communications Manager Settings for Hybrid Call Service.

Cisco Unified Communications Manager receives calls from Expressway-C. This configuration enables URI routing between the cloud and the on-premises enterprise. The cluster FQDN specified in the enterprise parameter is used in SIP routing decisions, and that helps identify multiple clusters so that calls can occur between them.

6

Do not remove verified domains used for hybrid Webex devices or those who administer them.

Domain verification is essential to the security and integrity of your organization. The established verification proves to us that you own a particular domain and is required for this service to work. For Hybrid Call Service, the verified domains are the ones in on-premises directory URIs tied to Webex devices and anyone who administers the devices.

What to do next

Follow these tasks to access the Webex Device Connector, install the software, and use it to synchronize your configuration between Unified CM and Webex cloud-registered devices:

  1. Install Cisco Webex Device Connector

  2. Synchronize Configuration Changes With The Cisco Webex Device Connector

Move users to Calling in Webex (Unified CM) by using the steps in the deployment guide.

If you received the following notice in Webex Control Hub, you must take action immediately if you want your user's personal mode devices to continue to have PSTN access.

These steps help you reenable the devices for Hybrid Calling and synchronize the changes using the Webex Device Connector software.

Before you begin

  • Install the Webex Device Connector.

  • This task assumes that you've already registered devices to the Webex cloud.

  • If you don't reconfigure the devices for Hybrid Calling on the Device Connector architecture, the devices still work but won't have PSTN access.

1

Enable Hybrid Calling for Personal Mode Devices in Control Hub.

The linked document covers both Unified CM prerequisites and how to enable Hybrid Calling.

Personal mode devices are Webex Room, Desk, or Board devices that are registered to the cloud but also assigned to a user in Control Hub. These devices share the same line that is assigned to the end user account in Unified CM. Once the required Unified CM configuration is in place, you can add Unified CM calling functionality by enabling Hybrid Calling for these devices.

2

Synchronize configuration changes with Webex Device Connector.

Whenever you make changes to configuration on Unified CM (premises) or to devices in Control Hub (the cloud), you can run the Cisco Webex Device Connector to make sure the changes on both sides are synchronized and Webex devices continue to function properly with Hybrid Calling. The software synchronizes the SIP address, device name, and device information into the cloud.


This section is only relevant if you already deployed Hybrid Calling for Webex devices. If you haven't yet deployed the service, you can ignore this section and use the deployment guide to set up the service from scratch.

If you deployed Hybrid Call Service for both users and devices, you must migrate users to the Calling in Webex (Unified CM) solution.

You may have seen a notification in Control Hub that said your organization is being migrated to the new Hybrid Call Service for Webex devices solution.

The table summarizes the key points that you must consider when you receive a notice that your organization is migrating from the old Hybrid Call Service (Call Connector architecture) solution to the new Hybrid Call Service (Webex Device Connector architecture) solution for Webex devices. This table takes into account what is required to transition Webex devices over to the new solution and what needs to be preserved if you want to continue to use your cloud-registered video devices with Hybrid Call Service.

The new solution only changes the synchronization steps.

  • You remove Call Connector Expressways and replace them with the Webex Device Connector software (on a Windows or Mac device).

  • You run the Device Connector once to synchronize configuration between your calling environment and the cloud.

  • Your Unified CM and Expressway pair configuration does not require changes, and the call flows and how the feature works for the Webex device remains the same.

  • Also, the migration does not cause disruption in service; the data is moved and continues to work as before.

Before Migration After Migration Impact Recommendation
Cisco Spark Remote Devices (Cisco Spark-RD) for Webex cloud-registered video devices Cisco Spark-RD for Webex cloud-registered video devices (Workspaces and Personal Mode)

For new devices that you want to enable for Hybrid Calling or for removal of devices, you must manually create or delete a Cisco Spark-RD using Cisco Unified CM Administration.

See the deployment chapter for guidance.

Capacity Review Unified CM device capacity utilization; deploy additional capacity (larger OVAs or more servers) as necessary
Call Connector required for Hybrid Call Service for video devices Webex Device Connector required for video devices and Call Connector is no longer supported No Call Connector capacity required and Call Connector is no longer supported.

If you need to make changes to your existing Hybrid Calling for Webex devices, you must manually run the Webex Device Connector software to synchronize the configuration.

After migration, remove Expressway capacity for Call Connectors; reallocate capacity to other connectors (Calendar, Messaging, Serviceability)

Download and install the Webex Device Connector from Control Hub. See the deployment information in this guide for further help.

Call Connector created automatic Cisco Spark-RDs for existing video devices.

You as the administrator must manually create Cisco Spark-RDs for new video devices.

Removal of Call Connector Expressways does not affect automatically created Cisco Spark-RDs.

For new devices that you want to enable for Hybrid Call Service or for remove of devices, you must manually create or delete a Cisco Spark-RD using Cisco Unified CM Administration.

See the deployment chapter for guidance.

Call Connector synchronized Unified CM data to the cloud automatically

Webex Device Connector synchronizes Unified CM data to the cloud on demand (when you run the synchronization step from the software).

Call Connector is no longer needed for Hybrid Calling for Webex devices.

If you need to make changes to your existing Hybrid Call Service for Webex devices, you must run the Webex Device Connector software.

Remove Expressway capacity for Call Connectors; reallocate capacity to other connectors (Calendar, Messaging, Serviceability)

Download and install the Webex Device Connector from Control Hub. See the deployment information in this guide for further help.

Hybrid Calling is still required if you added the service to Room, Desk, or Board devices that are in a Workspace in Control Hub. You must not remove anything necessary for Room, Desk, and Board devices enabled with Hybrid Calling.

To migrate users to Calling in Webex (Unified CM), you must remove Hybrid Calling for just your users before you can deploy new solution. Use these steps to disable Hybrid Calling for your users, and remove any of the related configuration from Unified CM.


If any Hybrid Calling users have personal mode devices configured, these devices still support Hybrid Calling. However, the personal mode devices must be reenabled with Hybrid Calling after you migrate to the Webex Device Connector solution.

1

To remove Call Service Aware and Call Service Connect from user accounts in Cisco Webex Control Hub, sign in to the customer view in https://admin.webex.com. You can then use any of the following methods:

Table 1. Options to Remove the Service from Webex User Accounts in Control Hub

User Configuration Method

Steps to Disable Hybrid Call Service

Individual Users

Go to Management > Users, click a username in the list to open the overview pane, click Call Service, then Connect, and then toggle off the setting. Then return and toggle off the Aware setting.

Bulk users accounts using the CSV template

Go to Management > Users, click Manage Users > Export Users List, enter FALSE in the Call Service Aware and Call Service Connect columns, save the file, and then go back to https://admin.webex.com to click Import and then choose the file that you updated. Click Add and remove services and then click Submit.

Directory-synchronized user accounts (through the Cisco Directory Connector)

Go to Management > Users, click Manage Users, choose Modify all synchronized users, and then click Next. Click through the prompts to get to the Sync Status screen. Click the refresh arrow, click Next, and then remove Call Service Aware and Call Service Connect from users.

This step completely disables Hybrid Calling for your users only, but it remains configured at the organization level (Hybrid Calling is still necessary for Room, Desk, and Board devices in a Workspace that are registered to the cloud). Next, you must remove the Cisco Spark Remote Device (Cisco Spark-RD) for any users who used Hybrid Calling. Whether you chose the automatic creation option in the Call Connector or manually created them in Unified CM, you must manually remove them in the next step.

2

To remove any Cisco Spark-RD that was associated with a user, go to Cisco Unified CM Administration and follow these steps:

  1. Click Device > Phone.

  2. In the Find phone where drop-down, choose Device Type, and in the Select item or enter search text drop-down, choose Cisco Spark Remote Device. Click Find.

  3. Check any of the devices that you want to remove, and then click Delete selected. Read the prompt and when you're sure, click OK.

    This step removes all selected Cisco Spark-RD and corresponding remote destinations for users.


     

    If you have Hybrid Calling configured for Room, Board, and Desk devices in a Workspace, only remove Cisco Spark-RD that are associated with Webex users on Hybrid Calling in your organization. Do not proceed to the next steps.

  4. Return to Device > Phone and search for CTI-RDs that may've been used for Hybrid Calling: in the Find phone where drop-down, choose Device Type, and in the Select item or enter search text drop-down, choose CTI Remote Device. Click Find.


     

    CTI-RDs that were used for Hybrid Calling contain a remote destination with *.call.ciscospark.com or *.calls.webex.com as the address.

  5. Check any of the devices that you want to remove, and then click Delete selected. Read the prompt and when you're sure, click OK.

    This step removes all selected CTI-RDs and corresponding remote destinations for users.

What to do next

After you've migrated Workspaces to Hybrid Calling with Webex Device Connector and users to Calling in Webex (Unified CM), you can remove the service from Expressway resources registered to the cloud and unregister those resources by using these steps:

  1. Remove Cisco Webex Hybrid Services From a Resource

  2. Deregister a Cisco Webex Hybrid Services Resource from the Cloud