Overview

Webex Video Integration with Microsoft Teams enables calling into Microsoft Teams meetings from Cisco and SIP-capable video devices registered either in the cloud or on-premises.

With this integration, you get this enhanced experience on supported devices when they join Microsoft Teams meetings hosted within your organization:

  • Cisco Webex experience—multi-screen with flexible layout options

  • Full roster list, with sharing and mute indicators

  • Bi-directional content sharing

  • Indicator if conference recording is in progress

Video Device Join Experience from the Meeting Invitation

A standard email invitation to a Microsoft Teams meeting has meeting join details that include a clickable link to join the meeting from the Microsoft Teams client. The section may also include audio dial-in information—an audio conference ID and phone numbers to join as an audio-only participant. When you enable the video integration, the invitation join details section expands to include a block of video conferencing device join details.

Figure 1. Video join details in Microsoft Teams meeting invitation

When it is time to join the meeting, video device users can call the SIP video address listed under the Join with a video conferencing device heading. The device calls the Cisco Webex interactive voice response (IVR) system, which asks the caller to provide the VTC conference ID. Note that the VTC Conference ID is specifically for video devices and is different from the audio conference ID, if one is included for the meeting.

The SIP IVR video address is specific to your organization and is formed from your organization's Cisco Webex SIP subdomain in the format <subdomain>@m.webex.com.

Below the SIP IVR video address and VTC Conference ID, the invitation links to a web page of alternate dialing instructions, which shows how to join the meeting by dialing directly.

Alternative Video Device Join Method—Direct Dial

Video callers can join the meeting directly, bypassing the IVR, by using a SIP address in the format <VTC Conference ID>.<subdomain>@m.webex.com. This method is listed at the top of the alternate VTC dialing instructions web page that the invitation links to. The web page also repeats the IVR prompt join details from the meeting invitation.

Figure 2. Alternate VTC dialing instructions (hyperlinked meeting-specific web page)

Alternative Video Device Join Method—Join Button

If you also enable the Cisco Webex Hybrid Calendar Service, devices can receive One Button to Push (OBTP) when schedulers invite them to Microsoft Teams meetings. An attendee using the device then simply presses the Join button when it's time to connect the device to the meeting.

When you're using a cloud-registered Cisco Webex device, the OBTP method includes the Microsoft Teams logo to let you know the type of meeing you're joining.

Requirements for Video Integration for Microsoft Teams

Requirement

Notes

An active Cisco Webex organization

If you do not yet have an active Webex organization, we will provision one for you when you purchase the Video Integration

A Microsoft 365 tenant with Microsoft Teams accounts for users in the organization

The setup process requires an account that can sign in as a Global administrator for the tenant to grant application permissions, and a Microsoft Teams administrator account for the tenant that can execute PowerShell commands.

Licenses (part number A-MST-WX-CVI-ROOMS) for the video devices that you plan to use with this integration.

Webex devices registered to your Webex organization, or other SIP video devices that can make internet calls.

Cisco Webex Hybrid Calendar Service (Optional, but highly recommended)

For the best experience using Hybrid Calendar, all meeting organizers and shared room mailboxes should be Hybrid Calendar enabled.

Required to provide One Button to Push (OBTP) to video devices.

Hybrid Calendar Service has additional requirements. For instructions, see https://www.cisco.com/go/hybrid-services-calendar.

Ports and Protocols for Video Integration Traffic

Signaling

Video devices connect to the Cisco Webex data centers for signaling.

Table 1. Signaling with Webex data centers

Video Device

Protocol

Port Number(s)

Comments

Webex device registered to your organization

TCP

443

For requirements, see Network Requirements for Webex Teams Services

Other SIP video device

TCP

5060/5061

For requirements, see How Do I Allow Webex Meetings Traffic On My Network?

Media

The media path for video integration calls differs from other Cisco Webex Meetings call flows because specialized media clusters handle this call type. These specialized media clusters aren’t part of the address ranges published for Webex Meetings, and deployments must ensure that traffic can reach these additional IP networks.

The specialized media clusters are not part of the reachability tests that Webex registered devices perform. Failure to open access to any of the media cluster IP ranges can lead to call failures. The integration attempts to use the optimal media cluster for each call based on where the caller originates. However, you must allow access to all media clusters because the media cluster used can vary based on run-time conditions.

Table 2. Media with specialized media clusters

Video Device

Protocol

Port Number(s)

Media Cluster Regions and IP Ranges

Webex device registered to your organization

TCP/UDP

5004

  • US EAST

    52.232.210.0/24

  • WEST EUROPE

    20.50.235.0/24

  • SOUTHEAST ASIA

    40.119.234.0/24

  • AUSTRALIA EAST

    20.53.87.0/24

UDP

33434

Other SIP video device

UDP

36000-59999

Set Up the Video Integration in Control Hub

Follow these steps to register Microsoft Teams to the Cisco Webex cloud, authorize service permissions with Microsoft, and enable Cisco video devices to join Microsoft Teams meetings. The setup wizard in https://admin.webex.com guides you through the process.

The Microsoft user has to authenticate at least two separate times during the setup. We recommend that the steps be done by a Microsoft administrator whose account has been given full administrator access to Control Hub.

Before you begin

  • Make sure that you've met all of the requirements in Requirements for Video Integration for Microsoft Teams.

  • If you haven't already done so, set up your Webex organization.

  • If you haven't already done so, add a subdomain for Webex SIP addresses in your organization.

  • In order to set up the video integration, you need the following administrator access:

    • Microsoft Tenant Global Administrator privileges in your organization

    • Microsoft Teams administration privileges within the tenant

    • Full administrator privileges for your Webex organization, and a web browser that can access Control Hub. (See System Requirements for Cisco Webex Services for browser compatibility.)

  • You also need access to run Microsoft PowerShell commands to complete these setup steps.

1

Sign in to https://admin.webex.com.

2

To check if the subdomain is set for Webex SIP addresses, from the customer view for the organization, go to Settings, and scroll to SIP Address for Cisco Webex Calling. If the subdomain is not set, see Change Your Cisco Webex SIP Address.

3

Go to Services. On the Video Integration card for Microsoft Teams, click Set Up.

If you don't see this card, make sure that your license is active.

4

On the Video Integration Setup screen, click Authorize.

You’re redirected to Microsoft consent prompts.
5

Pick the account for the user with the Microsoft Tenant Global Administrator privileges, and enter the credentials.

6

On the permissions screen, review the requested permissions. Then click Accept to grant the Webex Video Integration application access to your Microsoft tenant.

The browser should redirect you to the Control Hub Video Integration Setup screen when you've finished the authorization steps. If it does not, try these steps again.

7

Open a PowerShell session to Office 365 and sign in as a user with Microsoft Teams administration privileges for the tenant.

8

Download, install, and import the Skype for Business Online Connector PowerShell module:


 

These instructions are provided as an example and may become outdated. For help, see Manage Skype for Business Online with PowerShell on the Microsoft Documentation site.

  1. Download the Skype for Business Online Connector at https://www.microsoft.com/download/details.aspx?id=39366.

  2. Run the executable file and follow the prompts to accept the terms and license and complete the installation.

  3. Restart your computer.

  4. At the PowerShell command prompt, type the following commands:

    Import-Module SkypeOnlineConnector
    $userCredential = Get-Credential
    $sfbSession = New-CsOnlineSession -Credential $userCredential
    Import-PSSession $sfbSession
    
  5. Enter the credentials for the user with Microsoft Teams administration privileges for the tenant.

9

From the Video Integration Setup screen in Control Hub, copy the text of the New-CsVideoInteropServiceProvider command from the first text box (or use the copy to clipboard button) and paste it into the PowerShell session. Then run the command.


 

This command is specific to your tenant. The command will not work unless you have imported the Skype for Business Online Connector PowerShell module.

This command defines a new CVI provider of type Cisco and sets the tenantKey assigned by Webex, the Alternate Instructions URL provided by Webex, and other integration settings.
10

Choose how you want to enable the integration for your users.

For help, see "Grant-CsTeamsVideoInteropServicePolicy" on the Microsoft Documentation web site.

  1. To enable the integration for all users in your organization, copy the text of the Grant-CsTeamsVideoInteropServicePolicy command from the second text box.

    Example:

    To enable all users:
    Grant-CsTeamsVideoInteropServicePolicy -PolicyName CiscoServiceProviderEnabled -Global
  2. To enable the integration for an individual user, copy the text of the Grant-CsTeamsVideoInteropServicePolicy command from the second text box. Replace -Global with -Identity, and add the user's email address after it.

    Example:

    To enable user jamie.smith@company.com:
    Grant-CsTeamsVideoInteropServicePolicy -PolicyName CiscoServiceProviderEnabled -Identity jamie.smith@company.com
  3. Paste the command into your PowerShell session and run it.

11

When you are done with the PowerShell commands, click Ok on the Video Integration Setup screen in Control Hub to complete the setup.

The PowerShell changes to the Microsoft tenant can take time to propagate in the Office365 environment. Microsoft warns this can take up to 6 hours, although it typically takes less than 20 minutes. You can test if the changes have become active by creating test meetings in the Microsoft Outlook or Microsoft Teams. When the changes are done, you should see the video integration join details in the meeting invitation (as shown in Overview).

What to do next

If you need to access the PowerShell command text after leaving the setup wizard, go to Services. On the video interoperability card with the Microsoft Teams logo, click Edit settings.

To add a Webex room or desk device or Webex board, make sure you register it to your Webex organization. For help, see Activate a Cisco Webex Room or Desk Device or Webex Board.

Set up Hybrid Calendar Service if you want OBTP for devices. For help setting up One Button to Push with the Hybrid Calendar Service on Cisco video devices, see Make it Easier for Video Devices to Join Meetings with OBTP.


The default Exchange Online settings for room mailboxes strip the body and subject from meeting invites. As long as meeting organizers are Hybrid Calendar enabled, these defaults are acceptable for most cases. If the organizer is not Calendar enabled, you must ensure that the mail system does not have a policy to automatically delete meeting comments. The following PowerShell command ensures that comments are retained so that the Hybrid Calendar Service can use them to process meetings:

Set-CalendarProcessing -identity "room" -DeleteComments $false

OBTP and Hybrid Calendar Considerations

The Video Integration supports devices calling into the service by dialing the video addresses included in the Microsoft Teams meeting invitation. This calling experience can be enhanced using Cisco’s One Button to Push (OBTP) experience if Hybrid Calendar Service is enabled for your organization. For the most reliable OBTP experience, all meeting organizers should be Hybrid Calendar Enabled in Cisco Webex Control Hub.

There's a list of requirements and potentially some pre-configuration to deploying Hybrid Calendar for all your users and devices. Depending on where you are with that list of requirements, there are some tasks you need to do to bring users and devices into the best state to benefit from the video integration described in this document.

The following scenarios describe how to bring your users from where they are now, to the point where OBTP will be available for meetings they schedule:

Scenario 1:

All users who need to schedule meetings already have some form of Webex license entitlement (meetings, messaging, or calling), are in Control Hub, and are enabled for Hybrid Calendar Service.

These users do not need any additional configuration for Hybrid Calendar or Microsoft Teams scheduling.

The remaining scenarios require some pre-configuration of your organization.

Scenario 2:

All users who need to schedule meetings already have some form of Webex license entitlement (meetings, messaging, or calling), and are in Control Hub, but are not enabled for Hybrid Calendar Service:

  1. Configure Hybrid Calendar Service for your organization. See https://cisco.com/go/hybrid-services-calendar, and follow the guide for your type of Exchange deployment.

  2. Enable Hybrid Calendar Service for all users who will schedule meetings. You can do this one by one, or you can do it in bulk by exporting, modifying, and importing a CSV file.

Scenario 3:
All users who need to schedule meetings already have some form of Webex license entitlement (meetings, messaging, or calling), but they are not yet in Control Hub:
  1. Configure Hybrid Calendar Service for your organization. See https://cisco.com/go/hybrid-services-calendar, and follow the guide for your type of Exchange deployment.

    You cannot yet enable this service for your meeting organizers if they are not in Control Hub.

  2. (Optional, but recommended) Create a license assignment template and use it to enable Hybrid Calendar Service for new users (service is enabled as you bring them into the organization in Control Hub).

  3. (Optional, but recommended) Disable automated email invitations for newly enabled users. You may not want Webex to send these, especially if you are only enabling Calendar Service for users who are otherwise receiving collaboration services in Microsoft Teams.

  4. Import your users to Control Hub.

    Read about how to Add and manage users in Control Hub and choose the best method for your organization.

  5. (Conditional) If you could not (or chose not to) enable Hybrid Calendar Service for new users as they came in:

    Enable Hybrid Calendar Service for all users who will schedule meetings. You can do this one by one, or you can do it in bulk by exporting, modifying, and importing a CSV file.

Scenario 4:
All users who need to schedule meetings are not licensed for Webex.
  1. You need to request an organization-level override for the requirement that users must have Webex licensing before you can enable Hybrid Calendar Service for them.

    Send an email to new-cvi-customer@external.cisco.com with the following information:

    • Your company name.

    • Your subscription ID for new CVI licenses, or the sales order reference.

    • Your Webex organization ID.

    We'll verify that you are entitled to Calendar Service and then enable an override for your organization. The process may take up to 48 hours, and we'll reply to your email when the entitlement is applied to your organization.

  2. Configure Hybrid Calendar Service for your organization. See https://cisco.com/go/hybrid-services-calendar, and follow the guide for your type of Exchange deployment.

    You cannot yet enable this service for your meeting organizers if they are not in Control Hub.

  3. (Optional, but recommended) Create a license assignment template and use it to enable Hybrid Calendar Service for new users (service is enabled as you bring them into the organization in Control Hub).

  4. (Optional, but recommended) Disable automated email invitations for newly enabled users. You may not want Webex to send these, especially if you are only enabling Calendar Service for users who are otherwise receiving collaboration services in Microsoft Teams.

  5. Import your users to Control Hub.

    If you are using Hybrid Calendar without Webex entitlements, we are currently unable to synchronize your users using the cloud-based Webex integration with Microsoft Azure Active Directory. You must use the Cisco Directory Connector to synchronize users from your Active Directory into Control Hub.

  6. (Conditional) If you could not (or chose not to) enable Hybrid Calendar Service for new users as they came in:

    Enable Hybrid Calendar Service for all users who will schedule meetings. You can do this one by one, or you can do it in bulk by exporting, modifying, and importing a CSV file.

OBTP Considerations for Devices

After ensuring meeting organizers are Hybrid Calendar enabled, you need to address how devices can be enabled to display the One-Button-to-Push (OBTP) experience. The factors you need to consider are:

  • How do your devices register?

  • Are your devices shared (in meeting rooms), or personal (on desks)?

  • Which devices are you using?

Registration:
Cloud-registered devices can be configured to get OBTP for Microsoft Teams meetings as personal or shared devices using Hybrid Calendar Service.
On-premises registered devices that use Webex Edge for Devices can be configured to get OBTP for Microsoft Teams meetings as personal or shared devices using Hybrid Calendar Service (requires CE9.14 software).

Support for on-premises registered devices without Webex Edge for Devices depends on your deployment type:

  • Devices scheduled through Cisco TelePresence Management Suite Extension for Microsoft Exchange will get OBTP for Microsoft Teams meetings if Hybrid Calendar Service is also deployed in the organization.

  • Devices scheduled through Cisco TMS integration for Office 365 will not get OBTP for Microsoft Teams meetings at this time. We will address this limitation in a future release.

Personal or Shared Mode:
Personal Mode devices: In Control Hub, associate the device with a user who is enabled for Hybrid Calendar Service.
Shared Mode devices: In Exchange, create a mailbox for the device's room. In Control Hub, create a Workspace to represent the room, add a device to it and enable Hybrid Calendar Service for the device (you need to provide the mailbox address). See Add Shared Devices and Services to a Workspace.
Device types:
The following device types can receive OBTP for Microsoft Teams meetings, depending on the deployment:
  • Webex Desk Series

  • Webex Room Series

  • Webex Board

  • Cisco TelePresence MX and SX Series

Other device types will not support OBTP but can dial the meeting directly, or use the IVR, with the details they get from the Microsoft Teams meeting invite. Adding your organization’s CVI IVR to your devices as a speed dial or macro can also simplify dialing.

Features and Limitations

This section lists limitations and notable behavior for the Video Integration for Microsoft Teams.

Multiple Organizations and Tenants

  • We currently support a 1:1 relationship between Cisco Webex organizations and Microsoft 365 tenants:

    • A single Webex organization can interoperate with only one Microsoft 365 tenant.

    • Your Microsoft tenant can support multiple different video integrations; for example, the tenant can simultaneously interoperate with Cisco and Polycom. However, the tenant can only have one integration of each type; so, one from Cisco, and one from Polycom.

      If you have multiple Webex organizations, choose one to interoperate with your Microsoft tenant using the Cisco Webex Video Integration.

Availability

Video Device Interoperability

  • The integration only supports incoming SIP calls, not H.323 or IP calls. You can interwork these legacy protocols to SIP calls using a Cisco Expressway deployment.

  • The integration doesn't support calling into a Microsoft Teams meeting using the Webex Teams app. In addition, the integration doesn't support features that require pairing or connecting the Webex Teams app to a device. This includes wireless sharing, dialing from the Webex Teams app, and call contol from the Webex Teams app.

  • Webex Board devices can't do interactive white boarding sessions on Microsoft Teams. Users can share whiteboards from the device as content channel (BFCP support).

  • The integration doesn’t support audio-only participants. (Audio-only participants should call in using the PSTN gateway functionality for Microsoft Teams.)

Layouts

  • Participants connected through the video integration can cycle through different layout options, by sending DTMF tones 2 and 8 from the device.

  • Participants connected through the video integration can see up to nine video streams at the same time. The number of visible streams also depends on the selected layout and the device type. Layouts show letter avatars instead of video when participants are not sending video streams to the meeting.

  • Devices negotiate dual screen + content. The integration doesn't support explicit panorama-specific layouts.

  • The iX immersive experience for layouts and switching is not available when three-screen systems connect to a Microsoft Teams meeting. The layouts for three-screen systems are an extension of the single-screen layout experience.

Calendars and Cross-organization Invitations

  • Participants from outside your organization can join your Microsoft Teams meetings from their video devices by dialing your IVR video address (<yoursubdomain>@m.webex.com) and entering the VTC conference ID for the meeting at the prompt, or by using your direct dial alternative (<VTC Conference ID>.<yoursubdomain>@m.webex.com).

  • The video integration for your Microsoft tenant doesn’t enable dialing into meetings hosted by other Microsoft customers. When dialing into a Teams meeting that is hosted by another Microsoft tenant, you must use the video address of the video integration that is enabled for that tenant.

  • Cisco Webex Hybrid Calendar Service does not create OBTP join entries for meetings containing join details supplied by other (non-Cisco) video integrations. (For example, a Hybrid Calendar enabled workspace will not show the One Button to Push (OBTP) Join button for a Pexip invitation.)

  • Known Hybrid Calendar limitations, arising from missing comments/body details or organizer-based processing, also apply when processing OBTP for Microsoft Teams meetings.

Meeting Features

  • Participants using the video integration do not have controls to start or stop meeting recordings. Microsoft Teams users must manage meeting recording.

  • Content sharing uses BFCP and is subject to the limitations of that protocol, including no ability to share applications or allow remote control.

  • Meeting options for limiting sharing do not apply to participants using the video integration; these participants are always allowed to share in a meeting.

  • Microsoft Teams chat is not available to video integration participants.

  • Interactive white boarding is not available to video integration participants.

  • On the roster list, you only see the mute indicators for video integration participants if they muted themselves with DTMF *6 or if they were muted by Teams participants.

  • If you disable Anonymous users can join a meeting in the Microsoft Teams tenant settings, then video integration participants cannot join through the lobby. Video integration participants who would normally bypass the lobby will still be able to join Microsoft Teams meetings.

Networking

  • Calls to the video integration do not use Webex Video Mesh nodes; traffic is direct from the device to the cloud.

  • The specialized media clusters used by Video Integration for Microsoft Teams are not part of the reachability tests that Webex registered devices perform. Failure to open access to any of the media cluster IP ranges can lead to call failures. The integration attempts to use the optimal media cluster for each call based on where the caller originates. However, you must allow access to all media clusters because the media cluster used can vary based on run-time conditions.

Importing Users

  • If you request the organization-wide override to avoid the (temporary) requirement for meeting schedulers to have Webex licenses, you cannot currently import users into your organization with Azure AD. Use the Cisco Directory Connector instead.