Overview
Caution |
Starting December 30, 2020, Hybrid Call Service for end users will be End of Support (EoS) for all customers. See the EoS announcement for more information. Going forward, customers must configure the Webex Teams app to register directly to Cisco Unified Communications Manager (Unified CM) for enterprise calling capabilities for their users. Hybrid Call for devices will continue to work but must be migrated to the Device Connector solution. Calling in Webex Teams (Unified CM) for users closely follows familiar Jabber deployment models where Webex Teams registers directly to Unified CM as a soft phone. No extra Expressway connector infrastructure nor firewall traversal capacity is required beyond what is needed for remote access (MRA). |
This document describes only the changes you need to make to your existing Hybrid Calling deployment so that the SIP addresses migrate successfully to the Webex domain. The guide contains configuration steps that are required in your on-premises environment (Expressway pair, Unified CM) and required cloud or intermediary configuration (Control Hub, Expressway connector host) to complete the SIP address migration for Webex users and cloud-registered Webex video devices (Room, Desk, and Board devices) in a Workspace.
Note |
This guide is only for customers that have already deployed Hybrid Calling in their organization. If you're a new deployment, you can only do Hybrid Calling for devices in a Workspace; follow the deployment guide and ignore this document. The information here is only relevant while existing Hybrid Calling customers need to change from Spark-branded call routing to Webex-branded routing. The deployment guide is the more permanent and more frequently updated material, so cross-references from this document may become irrelevant. |