Work doesn’t end just because your meeting did. Included in every Webex plan is the ultimate team collaboration platform for messaging, file-sharing, whiteboarding, and getting stuff done. Webex Teams requires a few items to be configured in CUCM for Endusers in order to be ‘Webex Teams’ compliant and allow the Webex Teams ‘Control Hub’ to automatically create Webex Remote Destinations or CTI Endpoints essentially. Required Items - Enduser must control atleast one device or device profile. Must have Mobility Enabled.
We endeavor to make our Cisco TelePresence products interoperable with all relevant standards-based equipment. Although it is not possible to test all scenarios, the testing on which this data is based covers most common functions of the listed endpoints and infrastructure.
The following pages describe the software releases that were tested for interoperability with Cisco TelePresence products. The results are grouped by product range. It is not possible to guarantee that all the models listed in the Product(s) column have been tested with the specified software release, although to the best of our knowledge we believe that all such models are interoperable with the associated software release. The absence of a device or release does not imply a lack of interoperability.
Cisco Meeting Server software version 3.0
Webex Teams Softphone Cucm
Show data for version: 3.23.13.02.92.8
Interoperability testing often requires interworking from one signaling/call control protocol to another. The following table lists phrases that are used to briefly describe the call paths that were tested for each interoperability scenario. The explicit call paths in the table place the endpoint first and the Cisco Meeting Server last as a general convention.
Note: We recommend using the most up-to-date software on all devices and Endpoints.
Call Path Phrase
Explicit call path description
Endpoint < SIP > Cisco Meeting Server
Cisco Unified Communication Manager (CUCM) to Cisco Expressway
Endpoint < SIP > Cisco Unified CM < SIP > Cisco Expressway < SIP > Cisco Meeting Server
Endpoint < SIP > Cisco Unified CM < SIP > Cisco Expressway < SIP > Cisco Meeting Server TIP enabled (requires TIP-compatible endpoint)
|Cisco Meeting Management||3.0|
Meeting Server 3.0 introduces a mandatory requirement to have Cisco Meeting Management 3.0. Refer to Cisco Meeting Management Release Notes for latest information.
|Cisco TelePresence Management Suite (TMS)||15.12|
If you use TMS versions earlier than 15.12.0 for scheduled meetings — CUCM ad hoc conferencing calls — do not set a security profile at the system or tenant level.
|Cisco TelePresence SX10||CE9.13|
|Cisco TelePresence SX20||CE9.13|
|Cisco TelePresence SX80 Codec||CE9.13|
|Cisco Webex Desk Pro||CE9.13|
|Cisco Webex DX70||CE9.13|
|Cisco Webex DX80||CE9.13|
|Cisco Webex Room 55 dual||CE9.13|
|Cisco Webex Room 55 Single||CE9.13|
|Cisco Webex Room Kit||CE9.13|
|Cisco Webex Room Kit Mini||CE9.13|
|Cisco Webex Room Kit Plus||CE9.13|
|Cisco Webex Room Kit Pro||CE9.13|
|Cisco Webex Room Panorama||CE9.13|
Cisco Infrastructure Platforms
Only Expressway version X12.6 or later are supported.
Note: Refer to the Release Notes for Cisco Meeting Server for more information about call capacities for both clients.
|Cisco Unified Communication Manager (CUCM)||12.5(1)SU2|
Meeting Server is supported with CUCM 11.5(SU1) or later for ad hoc call escalation. Version 10.5(SU1) is not supported.
Cisco Software Based Apps
Webex Teams Cucm
Supported for Jabber on Mac, Windows, iPhone, iPad and Apple Watch, Android and Android Wearable. Minimum recommended version is 12.5.
Note: Version 12.5 supports Active Control which provides roster list and meeting controls. For more information, see Release Notes for Cisco Jabber.
|Cisco Meeting Server web app||3.0|
Cisco Meeting App for WebRTC is now removed in Cisco Meeting Server version 3.0. You will now need to use Cisco Meeting Server web app instead of Cisco Meeting App for WebRTC.
For more information, see Cisco Meeting Server web app important information document.
|Cisco Webex Teams||N/A|
Use latest version of Cisco Webex Teams. Available on mobile (iOS or android), desktop (macOS or Windows) and a Web version which works on any browser. Click here for more information regarding Cisco Webex teams.
|Microsoft Active Directory||Windows Server 2008 and later|
No issues found
No issues found
|Oracle Internet Directory||LDAP version 3|
No issues found
|Cisco UCS Manager||4.0, 4.1|
Newer versions of Cisco UCS Manager maybe available. Please contact Cisco support for if you wish to upgrade to a newer version.
|VMWare ESXi||7.0, 6.7, 6.5 Update 2, 6.0 Update 3|
Meeting Server Version 2.8 and later supports ESXi 6.7, ESXi 6.5 Update 2, ESXi 6.0 Update 3. However the audio capacity has been reduced. For more information, refer to Release Notes.
|Vbrick||Rev API v1|
Supported. Vbrick is planning to deprecate 'Rev API v1' in April 2021.
Strategic Alliances and Integrations Enable Comprehensive Calling, Meetings, and Messaging Capabilities
In my role as a product manager here at Cisco, I regularly talk to customers about their collaboration environments. One question I get asked is what they can do to bring together collaboration tools from different vendors…
The Webex unified app is providing our customers with comprehensive calling, meetings, and messaging capabilities that integrate with our award-winning video devices and IP phones. The result is seamless and consistent workflows.
But we are also aware that many customers have existing investments in place with collaboration tools from other vendors, and we are committed to making sure that Webex is an open platform, that integrates with 3rd party applications to ensure our mutual customers have a solution that delivers the best possible outcomes.
Earlier this year one of my colleagues talked about how we are enabling organizations with Microsoft Teams and Slack messaging users to start Webex Meetings from these applications.
Now, new Cisco calling integrations allow you to use all your enterprise-grade voice and video calling features in combination with these messaging platforms.
Cisco Calling Integrations
Calling integrations allow you to expose Cisco calling buttons directly in other vendors messaging apps. We’ve built the Cisco calling integrations to provide you with flexible solutions plus we’ve made them very easy to deploy. We started with Microsoft Teams and Slack messaging apps. To deploy a Cisco calling integration you simply select the Cisco client you are using for calling and the calling platform you want to use.
When you have added the Cisco calling integration, you can launch a Webex Teams or Cisco Jabber call directly from your messaging app. When you click the call button, the integrations identify who you’re chatting with, resolves their calling address, and passes this information to your installed Cisco client which starts a Cisco voice or video call. The integrations support all Cisco calling platforms including Cisco Unified Communication Manager (UCM) based on-premises and hosted deployments, and Webex Calling for cloud.
There are no complex back end changes to make as these are client integrations. There are no call routing policies or dial plan changes to make, no additional licenses required, and no new hardware to manage. You can even use the calling integrations with desk phone control, which means your users don’t have to replace their handsets.
Cisco Calling from Slack
Slack has made its messaging platform very open to integrating calling providers like Cisco. Adding the Cisco calling integration to Slack means you use the native Slack call button to start a Cisco call directly from Slack.
This could be using Webex Teams or Cisco Jabber as your softphone or controlling your desk phone. If your Cisco client is controlling your Cisco desk phone clicking the call button in Slack causes your Cisco desk phone to go off-hook and call your colleague.
Slack is popular with developers where users tend to like keyboard commands to take actions like making calls. Talking to Slack users it becomes clear this is a requirement for Slack users so we implement “/jabber” and “/webexteams” slash command allowing you to make calls at the command line.
We are continuing to work in partnership with Slack and plan to implement Slack’s new shortcut controls shortly. This will give you more calling destination selectable directly in Slack.
Cisco Calling from Microsoft Teams
The Cisco calling integration for Microsoft Teams has been available from the Microsoft Teams app store for just over a month now. This month we have extended it with new features and functionality. In addition to supporting Microsoft Teams desktop and web users, this month we added support for mobile and tablet devices. We also added new contact search capabilities, you can now search your Microsoft 365 Outlook contacts and call them using your Cisco calling platform via the integration.
Webex Teams Cucm Calling
Building Bridges with Webex
These two new calling integrations are just examples of the many integrations that the Webex platform supports, enabling people to enhance their communication and collaboration within their everyday workflows. For example, we’ve also worked with Microsoft to integrate Microsoft SharePoint and OneDrive Enterprise Content Management (ECM) solutions into Webex team messaging services to streamline collaboration on documents.
If you’re interested in learning more about Cisco calling integration contact your Cisco account team to discuss how to build on your current Cisco UC investments with Webex to enhance the collaboration experience for your users and/or integrate with 3rd party collaboration tools.