Cisco Microsoft Teams Interop

Posted : admin On 1/3/2022

What You’ll Find in This Demo

The companies planned to release a Microsoft Cloud Video Interop (CVI) certified solution that would allow Cisco Webex Room and SIP video conferencing devices to join Microsoft Teams meetings. Additionally, they also proposed creating a direct guest join pathway connecting their respective video conferencing devices with their meeting web apps. Learn how Cisco Webex interoperates with Microsoft Teams and helps solve your realtime business communications challenges. See how Webex Meetings ties in ti.

The guide for this preconfigured demo includes two independent Cisco Calling and Meeting Integration demos: Microsoft Teams and Slack.

What’s New

The Microsoft Teams integration section has a new scenario: Cloud Video Interop (CVI) and WebRTC.

Overview

Microsoft Teams

Users demand interoperability with calendaring, ECM, workflow, telephony, meetings, video, devices, and more. Cisco meets this demand with client-based integration with Microsoft Teams.

The simple-to-deploy client/plug-in integration with Microsoft Teams works with your choice of Cisco clients — Cisco Jabber, Webex Calling, and Webex Meetings.

Calling

With RealConnect, it’s easy to connect your video conferencing systems to Microsoft Teams (or Skype for Business) meetings. Keep the workflow you’re used to, just add video interop so anyone can join the meeting from their personal clients, Microsoft Teams Rooms, as well as from videoconferencing systems. It’s simple, flexible and smart. 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.

  • Click to call with your existing phones from Microsoft Teams
  • No compromise on calling features
  • No dial plan and routing reconfiguration

Meetings

  • Simple-to-implement Webex Meetings Bot
  • Get your default website for Meetings
  • Set your default Meetings website

And all this is at no additional license costs because of the following:

  • Covered by your existing Cisco licenses/subscription
  • No (E5) Microsoft Cloud PBX Phone system license is required

Cloud Video Interop (CVI) and WebRTC

  • SIP-capable video endpoints can join Microsoft Teams meetings via CVI for a rich, seamless meeting experience, without requiring third-party interop using OBTP join with Calendar Service, direct dial in, or IVR join experience.
  • WebRTC supports the OBTP join with Calendar Service for B2B meetings from a Cisco video endpoint that has Media Engine running. These devices support WebRTC: Cisco Webex Board, Room Devices, and DeskPro.

Slack

Cisco Jabber, Webex Call, and Webex Meetings integrated with Slack lets you collaborate seamlessly – whoever, whenever, however.

Calling

Cisco Jabber and Cisco Webex are simple-to-deploy plug-ins that can be cross-launched from within Slack when you want to call someone internally or externally.

With Cisco Jabber and Cisco Webex plugins, Slack users can:

  • Call someone internal with their extension or SIP URI
  • Call someone over PSTN

The simple-to-deploy client/plug-in Webex Meetings integration with Slack lets Slack users to schedule, start, or join Cisco Webex Personal Room meetings, and Cisco Webex scheduled meetings directly from Slack.

Meetings

With Cisco Webex Meetings plug-in, Slack users can:

  • Start and join meetings directly in their channel
  • Schedule a meeting and the meeting info card will be added to the conversation.
  • Automatically get status alerts and, if your meeting has already started, see who has joined
  • Preview your upcoming meetings and join from the list
  • Edit a scheduled Webex meeting
  • Play recordings, which are posted in the channel when ready
  • See if other users are currently in a Webex meeting

Scenarios

The Microsoft Teams integration section has three independent scenarios:

  • Scenario 1: Cisco Jabber and Webex Meetings Integration with Microsoft Teams
  • Scenario 2: Cisco Calling and Webex Meetings Integration with Microsoft Teams
  • Scenario 3: Cloud Video Interop (CVI) and WebRTC

The Slack integration section has two independent scenarios:

  • Scenario 1: Cisco Jabber and Webex Meetings Integration with Slack
  • Scenario 2: Cisco Webex Calling and Webex Meetings Integration with Slack

Get Started & Resources

  • Schedule this demo and get the lab guide: Cisco Calling and Meeting Integration with Microsoft Teams and Slack v1
  • Visit the Cisco dCloud help page: https://dcloud-cms.cisco.com/help
  • Access all available Cisco dCloud content: https://dcloud.cisco.com
  • Contact Us: https://dcloud-cms.cisco.com/help/dcloud-collaboration-contacts
  • Talk about it on the dCloud Community

What is Microsoft Teams CVI ?

Microsoft Teams Cisco Video Interop

Cloud Video Interop (CVI) is a Microsoft Qualified third-party solution that enables third-party meeting rooms (telepresence) and personal video devices (VTCs) to join Microsoft Teams meetings.

With Microsoft Teams, you get rich online content collaboration in meetings that include audio, video, and content sharing. This can be enjoyed through the desktop and web client, as well as through many partner devices that integrate natively with Microsoft Teams. However, many customers have already invested in video teleconferencing and personal video communication devices, which can be expensive to upgrade. Cloud Video Interop provides an easy solution, allowing you to keep using your existing solutions until you are ready to upgrade.

With Cloud Video Interop, Microsoft Teams delivers a native meeting experience for all participants – in meeting rooms or inside of Teams clients.

Who are these Third-Party Solution Providers ?

Cisco

Is Cloud Video Interop for You?

Cloud Video Interop provides an intermediate service while you transition to a full native Microsoft Teams Solution, using Teams endpoints. The service provided should be part of your migration path.

Cloud Video Interop is intended for customers who meet the following criteria:

  • Have a large deployment of meeting room devices and personal video devices deployment (50+ devices) that are not qualified for direct integration with Microsoft Teams
  • Are supported by one of our Cloud Video Interop partners
  • Want to retain the value of their investment in their current meeting room devices and personal video devices during the migration to a native Microsoft Teams solution

Pre-Requisites :

  1. Office 365 Tenant
  2. License from CVI Vendor (ideally it will be concurrent call licenses)
  3. Network Requirements
    1. Poly RealConnect — https://rc-docs.plcm.vc/docs/prerequisites
    2. PexIP — https://docs.pexip.com/admin/teams_planning.htm
    3. BlueJeans – https://support.bluejeans.com/s/article/TCP-UDP-ports-used-by-BlueJeans-Network
    4. Cisco — https://help.webex.com/en-us/nffx8kj/Deploy-the-Cisco-Webex-Video-Integration-for-Microsoft-Teams

Codecs Supported :

Cisco interop with microsoft teams

Where are these CVI solution deployed ?

Microsoft Azure Data centers

How to Provision (Steps) ?

  • Poly RealConnect – https://rc-docs.plcm.vc/docs/teams/enroll
  • PexIP – https://www.pexip.com/blog1.0/pexip-cloud-video-interop-service-setup
  • BlueJeans – https://support.bluejeans.com/s/article/gateway-admin-guide
  • Cisco — https://help.webex.com/en-us/nffx8kj/Deploy-the-Cisco-Webex-Video-Integration-for-Microsoft-Teams

How does the Microsoft teams Calendar invite looks like ?

Poly RealConnect :

PexIP :

Cisco Microsoft Teams Interop

Bluejeans :

Cisco WebEx :

Calls Flows :

Assuming there is NO Video Infra like Poly or Cisco and taking an example of Signalling protocol SIP

  1. VTC Endpoint dial a dial string for example [email protected] / [email protected] over SIP (Manual Dial or through OTD/OBTP/OneClickToJoin)
  2. All standard video endpoints does know how to discover the destination IP address by querying the DNS record.
  3. The Endpoint does the DNS query to t.plcm.vc (for Poly) and establish the TCP and TLS connectivity to CVI Server hosted in Azure.
    1. For PexIP, it does DNS query for domain.onpexip.com in order to establish the connection to CVI server; where domain is your enterprise domain.
    2. For Bluejeans, it does DNS query for teams.bjn.com in order to establish the connection to CVI server
    3. For Cisco, it does DNS query for m.webex.com in order to establish the connection to CVI server
  4. Endpoint will be redirected to nearest Azure data center’s / Best available CVI Server based on the Azure Latency checks.
  5. Now the Endpoint and CVI server will exchange the candidates over SIP methods (INVITE) and negotiate to find the optimal path to establish the media.
  6. Typically, the media will flow between Endpoints and CVI server directly or through any firewall in place.

Assuming there is Video Infra like Poly or Cisco is in place and all the Endpoints are registered to gatekeeper (DMA/CUCM) and taking an example of Signalling protocol SIP

  1. VTC Endpoint dial a dial string for example [email protected] / [email protected] over SIP and send a request to registered Gatekeeper Server (DMA/CUCM) (Manual Dial or through OTD/OBTP/OneClickToJoin)
  2. The Gatekeeper will then validate the dial string and proxy it to next hop which will be Edge server (Media Traversal Server DMA Edge or VCS-E)
  3. The Media traversal will then discover the destination IP address by querying the DNS record t.plcm.vc (for Poly) and establish the TCP and TLS connectivity to CVI Server hosted in Azure.
    1. For PexIP, it does DNS query for domain.onpexip.com in order to establish the connection to CVI server; where domain is your enterprise domain.
    2. For Bluejeans, it does DNS query for teams.bjn.com in order to establish the connection to CVI server
    3. For Cisco, it does DNS query for m.webex.com in order to establish the connection to CVI server
  4. Media Traversal Server (DMA Edge/VCS-E) will be redirected to nearest Azure data center’s / Best available CVI Server based on the Azure Latency checks.
  5. Now the Endpoint and CVI server will exchange the candidates over SIP methods (INVITE) and negotiate to find the optimal path to establish the media through the Gatekeeper and Edge servers.
  6. The media will flow between Endpoints <>Edge/VCS-E <>Firewall <>CVI server <>Microsoft Teams

Example Call flow traces from Wire-shark tool :

SIP :

H.323 :

Since the CVI solution is deployed by respective vendor in specific Azure datacentres, it is advised to you optimize your network route accordingly.

For Example Poly RealConnect CVI is deployed in following Azure Data centers,

  1. South Central US
  2. West US 2
  3. East US 2
  4. West Europe
  5. Australia Southeast

And CiscoWebEx CVI have in the following Azure Data centers

  1. East US
  2. West Europe
  3. Southeast Asia
  4. Australia East

And Bluejeans CVI have in following Azure Data centers,

  1. West US 2
  2. West Europe
  3. Southeast Asia
  4. Australia East

Cisco Cloud Video Interop

It is highly recommended to disable the SIP and H.323 helper services for the port TCP 5060, 5061, 1720 & 1729 on your firewall, in order to have a seamless connectivity to CVI and enjoy the rich experience of Microsoft team meeting from your VTC rooms.

Microsoft Teams Skype Interop

If you are looking for the feature wise comparison, may refer to the blog written by Satish Upadhyaya here — https://networking-talks.blogspot.com/2020/09/feature-wise-comparison-between.html