Hybrid Call Service for end users will be going into End of Support (EoS) status for all customers. See the EoS announcement for more information.

Going forward, customers must configure the Webex 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 (Unified CM) for users closely follows familiar Jabber deployment models where Webex 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).

For Cisco Webex Hybrid Services, X12.5 is the minimum supported version of Expressway for new connector host registrations to the cloud. X8.11 is the minimum version for existing registrations to the cloud.

Expressway X12.6 does not work for hosting the Call Connector software that is required in a Hybrid Call Service deployment. You must use an earlier supported version for your Expressway connector host.


Decenber 3, 2020

  • Resolved Call Connector restarts by fixing the dependent library versions.


April 23, 2020

  • Fixed an intermittent issue where Call Connector failed to start.

  • Fixed CSCvq07214—"Apache Xerces-C XML Parser Library External DTD Paths Denial of Service Vulnerability"


April 8, 2019

  • Fixed an issue where a remote destination (Webex SIP address) wasn't updated if a Place with Webex devices was renamed in Control Hub.


March 21, 2019

  • Added enhancements to avoid consuming extra AXL sessions

  • Added the following error message:

    • Title—Failed to create the user's remote device

    • Message—Call Connector did not create a remote device for the user. Some required configuration is missing.

    • Resolution—Check the required user configuration on Unified CM as detailed in the Prepare and Deploy chapters in www.cisco.com/go/hybrid-services-call.

    Further troubleshooting details can be found in the deployment guide.


February 13, 2019

  • As part of the upcoming changes to improve the deployability and reliability of Hybrid Call Service (announced here), we've removed CTI monitoring from the Call Connector.

  • Note the following impacts to Hybrid Call Service:

    • Removal of support for the instantly available screen share feature for Call Service Aware users.

    • Call history in the Webex Teams app may be incomplete or incorrect for calls that are placed or answered on a Connect user's deskphone.

  • The deployment guide is updated to reflect these changes.


February 7, 2019

  • Enhanced an error message for when you enable Call Service Connect for Webex Devices in a place where the directory number in Unified CM has auto-answer enabled:

    • Title: Failed to Add Hybrid Call Service to Webex Devices in a Place

    • Description: Call Connector cannot create a Cisco Spark remote device in Unified CM because auto-answer is enabled on the directory number.

    • Solution: Disable auto-answer for the directory number in Unified CM. Then wait for the call connector to pick up changes or restart the connector.

  • Added an update so that Call Connector uses AXL to configure remote destinations on Unified CM.


January 24, 2019

  • Added a new error message that appears when there are 15 or more characters in a device name for a Place with Hybrid Call Service.


November 29, 2018

  • No release notes for this maintenance upgrade.


October 24, 2018

  • Logging improvements for CTI messages.

  • Fixed a bug where the calling party name and directory number were displayed in the Webex Teams app when the calling party display name and line ID were restricted on Unified CM. Now, the calling party name is shown as "Private" and the directory number is cleared in the app.

8.10-1.0.6548—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

Targeted for September 23, 2018

  • When a Call Connector receives a TLS error from the Webex cloud, the connector used to raise a certificate verification failed alarm and shut down. Now, the Call Connector continues to run and periodically attempts to reconnect to the Webex cloud.

    You must continue to verify that the correct certificates are installed on the Expressway-C and update them if necessary.


September 4, 2018

  • No release notes for this maintenance upgrade.


August 15, 2018

  • Fixed the case where the Unified CM cache error alarm remained when the cache rebuild timed out and then recovered. Now, the Unified CM cache error alarm completely goes away after the connector rebuilds the cache of all user and device information.

  • The minimum supported version of Expressway is now X8.11 for new registrations and X8.10 for existing registrations. If your connector hosts are on an earlier version, connector software upgrades will install and run, but you see an error-level alarm indicating that you must upgrade to a supported version. No technical support is provided until you upgrade your Expressway to an appropriate release. For more information, see Expressway Connector Host Support for Cisco Webex Hybrid Services.


July 26, 2018

  • Improved descriptions of alarms to aid administrators with troubleshooting.

    • Example Before—The user's Cisco Spark SIP address cannot be routed to Cisco Spark.

    • Example After—Updating Remote Destination failed as the user's Cisco Spark SIP address cannot be routed to Cisco Spark.

  • Distinct alarms for “Creating” versus “Updating” a Remote Device Destination with a SIP address that cannot be routed.

    • Alarms indicate Unified CM routing configuration errors.

    • “Updating” alarm supports future migration from “*.ciscospark.com” to “*.webex.com” SIP URIs.

    • Call Connector is exclusively responsible for creating or updating the Remote Destination as part of the user activation or brand migration process. Manual creation or update of Remote Destinations is not supported.


June 12, 2018

You may have been notified about a connector upgrade to version 6285. This version was removed for more quality control testing before release. We apologize for any inconvenience caused.

  • Improved reliability of user discovery.


June 1, 2018

  • Logging improvements to help with user activation tracing.


May 24, 2018

  • No release notes for this maintenance upgrade.


May 18, 2018

  • Enhanced the nightly process that discovers new users and places to be activated.

  • Cisco SparkRDs are now cleaned up when you use Control Hub to delete a Place with hybrid-enabled devices.


May 10, 2018

  • Enhanced CTI load balancing—now, connections to CTI Manager from call connectors are distributed across the Unified CM cluster rather than all connectors pointing to the same Unified CM node in a cluster.

  • Improved the efficiency of AXL connections to Unified CM.


March 23, 2018

  • No release notes for this maintenance upgrade.


March 8, 2018

  • Improved activation error messages.

  • Clarified the error message that involves users with mismatched primary directory numbers.

  • Updated the email template to include only the URL to release notes.

  • Enhanced logging for AXL errors.

  • Call Connector now periodically retries for authentication errors, instead of stopping.

  • This connector release is the candidate build for Hybrid Call Service for Cisco Spark Devices. See https://www.cisco.com/go/hybrid-services-call for more information about this feature.


February 15, 2018

  • Improved Cisco Spark Remote Device Conversion errors.

  • Improved various Expressway UI messages for better serviceability.

  • During user activation, primary extension verification now checks both number and partition.


January 15, 2018

  • Call Connector will now detect new users configured on Unified CM without having to wait overnight or restarting the connector.


December 1, 2017

  • Improved performance by decreasing database usage.

  • Automatically created Cisco Spark Remote Devices (SparkRDs) descriptions now contain a username.

  • Resolved the issue where Call Connector incorrectly reported alarms when connectivity to the Unified CM AXL service was lost, before attempting connection to other Unified CM nodes.

  • Optimized the reporting of registration status when a device unregisters and registers immediately.

  • Resolved the accidental removal of Unified CM configuration when you make updates in Hybrid Services Call Connector Administration after an expired session.

  • Optimized the keepalive notifications from Call Connector to the Cisco Collaboration Cloud.