Hybrid Calling Deployment Task Flow
With Hybrid Calling deployed in your organization and enabled for your Webex users, you get the following feature set:
-
Hybrid Calling for Cisco Webex Devices (Further steps are required in Deploy Hybrid Call Service for Cisco Webex Devices)
Before you begin
Complete the Prerequisites for Hybrid Calling
![]() Note |
After you've verified the prerequisites are met, you must perform all of the required configuration in this chapter, including Aware and Connect activation for users. Connect is the required activation state and Aware no longer supports any user features. These features may still work between Connect and Aware users, but are not supported and may stop working without advanced notice. |
Procedure
Command or Action | Purpose | |
---|---|---|
Step 1 |
Domain verification is essential to the security and integrity of your organization. Verification proves to us that you own a particular domain and is required for this service to work. If your company has multiple domains, add each domain one at a time. For example, if you have users in sales.example.com and in support.example.com, you must add both domains. If your organization enforces email addresses, you are presented with warnings about possible user lockout. You are forced to verify and remove domains in a particular order to prevent administrator lockout. When adding domains, for example, you must add the administrator domain first, followed by all other domains. |
|
Step 2 |
Register Expressway-C Connector Hosts to the Cisco Webex Cloud |
Cisco Webex Hybrid Services use software connectors to securely connect the Cisco Webex service to your organization's environment. Use Cisco Webex Control Hub to register your Expressway-C to the cloud. After you complete the registration steps, the connector software is automatically deployed on your on-premises Expressway-C (the software connector host). |
Step 3 |
Configure an administrator account with the required AXL access permissions. Call Connector uses this account to communicate with Cisco Unified Communications Manager, monitor any user's phone, and validate user configuration. |
|
Step 4 |
Configure the Connection to Cisco Unified Communications Manager |
Before you can enable Hybrid Calling, you must link Call Connector to your Cisco Unified Communications Manager environment by entering server information for a single node. This step provides a secure bridge between Cisco Unified Communications Manager and the Cisco Webex cloud, with the connector acting as the broker between the two. |
Step 5 |
Manually enable the Call Connector after you register your Expressway-C for Cisco Webex Hybrid Services. |
|
Step 6 |
Ensure that you correctly installed the Call Connector by viewing the status on the Expressway. |
|
Step 7 |
Configure Cisco Unified Communications Manager Settings for Hybrid Calling |
Configure Cisco Unified Communications Manager to receive calls directly from Expressway-E. This configuration enables URI routing between the cloud and the on-premises enterprise. You'll create a cluster FQDN, which is the enterprise parameter that is used in SIP routing decisions and that helps identify multiple clusters so calls can occur between them. |
Step 8 |
Perform one of the following tasks:
|
Configure Unified CM users so that their corresponding Cisco Webex accounts in the cloud are activated with the correct call settings. Call Connector creates the remote destination on the user's Cisco Spark Remote Device after all the Unified CM settings are properly configured. |
Step 9 |
Perform one of the following tasks: |
Every Hybrid Calling user requires a virtual device called a Cisco Spark Remote Device (Cisco Spark-RD). This virtual device is attached to a user's work number and links the user's 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. From a technical standpoint, the Cisco Spark-RD masks outbound calls from Cisco Webex and displays the user's work number for calls from the Cisco Webex app. Incoming calls also ring both the user's Cisco Webex app and desk phone. To automate your configuration, on the Expressway-C connector host you can create Cisco Spark-RD for all your users in one step. The connector shows the remote device field values from your Cisco Unified Communications Manager, and then you can choose the values specific to your deployment. After the connector creates Cisco Spark-RDs, they are automatically moved to the users' control lists and their Cisco Webex SIP addresses are automatically created as remote destinations. |
Step 10 |
Use this procedure to begin the initial setup for Hybrid Call Service Connect in Cisco Webex Control Hub. These settings ensure that Hybrid Call Service Connect is first enabled for your organization before you do further configuration. You specify the desired subdomain for your company, and that setting creates Cisco Webex SIP addresses to identify users in the Cisco Webex cloud. Then, you toggle on Hybrid Call Service Connect for your organization. Last, you enter the SIP destination address which resolves to your Expressway-E in the call traversal pair. This entry is typically a DNS-SRV record which can resolve to multiple Expressway-Es. |
|
Step 11 |
After you add a default SIP destination for Hybrid Call Service Connect, you can add more SIP destinations to specific hybrid call resources in Cisco Webex Control Hub. A single SIP destination means that all of the hybrid call traffic goes through a single Expressway-E or DNS SRV entry. You may want to add more SIP destinations and override the default entry so that you have more control over where the hybrid call traffic is routed. |
|
Step 12 |
Configure the Expressway-E for Hybrid Calling by following these tasks:
|
Enterprise calls are securely routed over the Expressway pair. If you want to reuse an existing pair, some of the required traversal configuration for Hybrid Calling may already be in place. However, read the procedures that follow to ensure that Expressway-E and Expressway-C are correctly configured. |
Step 13 |
Configure the Expressway-C for Hybrid Calling by following these tasks: |
Enterprise calls are securely routed over the Expressway pair. If you want to reuse an existing pair, some of the required traversal configuration for Hybrid Calling may already be in place. However, read the procedures that follow to ensure that Expressway-E and Expressway-C are correctly configured. |
Step 14 |
Enable Hybrid Call Service Connect for your users in Cisco Webex Control Hub—you can enable the service for individual users or in bulk. |
|
Step 15 |
Disable and reenable the Call Connector, so that the connector captures Unified CM user and device configuration changes that you made while deploying Hybrid Call Service. During this restart cycle, the connector creates a remote destination with the Cisco Webex SIP address on the Cisco Spark Remote Device. This address is associated with end user accounts and the corresponding Webex accounts. Toggle this setting as a troubleshooting step if you experience any issues, too. |
|
Step 16 |
Use this procedure to test Hybrid Calling call scenarios. These steps verify whether you correctly configured Hybrid Calling and can help isolate any potential issues. |