Requirements for Hybrid Calling
Cisco Webex License Requirements
To deploy Hybrid Call Service and provide its features to your users:
-
You must have a Cisco Webex organization with a paid subscription.
-
Cisco Webex hybrid call users must be assigned a paid license that provides access to core Cisco Webex messaging and meeting services.
-
The paid user licenses must not provide Cisco Webex hybrid call users access to a non-Unified CM-based calling service, such as Cisco Webex Calling (Formerly Spark Call).
Unified CM Device Requirements
Hybrid Call Service is supported only with Cisco SIP phones and Cisco Jabber clients that are registered to Unified CM.
SCCP phones may encounter problems due to the 48-character limitation on the destination address. Third-party IP phones and clients registered to Unified CM are not supported, neither are IP phones and clients registered to other call control servers (such as Cisco VCS/Expressway, Cisco Meraki, Microsoft Lync/Skype for Business, BroadSoft/BroadWorks).
Cisco Call Control Solution Requirements
To enable Hybrid Calling, you must use one of the supported Unified CM-based Cisco call control solutions, and ensure that you're on the minimum supported version or later.
Unified-CM Based Call Control Solution | Version |
---|---|
Cisco Unified Communications Manager |
Supported Cisco Spark Remote Device (Cisco Spark-RD) releases are required for Hybrid Calling deployments.
|
Cisco Business Edition |
Check the software load summary documentation for BE6K and BE7K to ensure the solution is running a supported version of Unified CM. |
Cisco Hosted Collaboration Solution (check to see if your provider is offering Cisco Webex Hybrid Services) |
11.5 and later |
Cisco Expressway Requirements
You must deploy Expressway to host the connectors. Organizations using Cisco Hosted Collaboration Solution do not need Cisco Expressway on their premises. Instead, their Hosted Collaboration Solution partner will deploy it in the cloud as part of their Cisco Webex Hybrid Services offering.
Requirements | Version | ||
Cisco Expressway E and C Traversal Pair ( for hybrid call traffic) |
X8.11.4 or later is required for Hybrid Calling. See the "Important Information" section in the Expressway Release Notes for more information. This release provides added security and toll fraud mitigation. Hybrid Calling calls are classified the same as Mobile Remote Access (MRA) calls. Hybrid Calling traverses existing Expressway C and E pairs and don't consume licenses.
Hybrid Calling follows existing MRA and B2B preferred architecture planning recommendations.
|
||
Cisco Expressway Connector Host (for hosting software connectors) |
You can download the software image from software.cisco.com at no charge.
See Expressway Connector Host Support for Hybrid Services for more information about which versions are supported for new and existing registrations to the cloud. |
Cisco Webex App Requirements
Cisco Webex hybrid call users must download the Cisco Webex app for a supported platform from https://www.webex.com/downloads.html.
Hybrid Calling is supported on Cisco Webex for Windows, Mac, and mobile (Android and iOS). The web client is not supported.Network Requirements
-
Port access for HTTPS or secure web sockets outbound from Expressway to *.rackcdn.com, *.wbx2.com, *.webex.com, *.ciscospark.com, and *.clouddrive.com: TCP port 443 (secure)
-
For AXL queries from Call Connector to Unified CM, TCP port 8443.
-
Open the following ports for media traversal between phones, Expressways in the traversl pair, and the Cisco Webex cloud:
Table 3. Media Traversal Port Requirements for Hybrid Calling Client
Destination
Ports
Protocol
Function
Expressway traversal pair
Any
36000–59999
UDP
SIP media between phones and Expressways. Open these ports on the Expressways themselves.
Cisco Webex app
Any*
33434–33598
TCP/UDP
Cisco Webex Hybrid Services media.
* If you want to restrict by IP addresses, see the IP address ranges that are documented in Webex IP subnets for media.
Other Network Requirements
We recommend that you implement network requirements that are covered in the following documents: