October 2021

Cisco + Microsoft
Creating better experiences, together.

TDM Presentation (v14.5)

Shared under NDA; GA Information (Subject to Change)
Disclaimer
The Cisco products, service or features identified in this document may not yet be
available or may not be available in all areas and may be subject to change without
notice. Consult your local Cisco business contact for information on the products or
services available in your area. You can find additional information via Cisco’s World
Wide Web server at http://www.cisco.com. Actual performance and environmental
costs of Cisco products will vary depending on individual customer configurations and
conditions. This is a confidential Cisco Internal launch document and not for external
distribution.
 Cisco is a certified Microsoft CVI
1 partner

Cisco and Microsoft Microsoft Teams works with

have come together 2 Webex Rooms via modern web
technologies
to deliver a better user experience
Video devices joining Microsoft Teams meetings
SIP-capable video endpoints can join
Microsoft Teams meetings (hosted by my
company) via VIMT (CVI)
Richer, seamless meeting
experience, without requiring
3rd party interop

Webex web-engine capable devices can join

B2B Microsoft Teams meetings

Limited experience on Webex

devices using Microsoft Teams
meeting web app
Video Integration for
Microsoft Teams
Microsoft Cloud Video Interop
Joining Microsoft Teams meetings – VIMT gateway
One Button to Push experience
 Joining Microsoft Teams meetings– VIMT gateway
Layout example (dual screen)

Active Speaker Active Speaker w/ Content Share

Subject to changes in layouts of Webex Meetings/Webex Rooms

Single screen flexible layouts
VIMT Gateway will provide flexible layouts to video devices while Microsoft Teams users
will see their respective layouts

Active Speaker Overlay Equal

VIMT Architecture
Video Integration for Microsoft Teams (VIMT) gateway

Calendar Service
for OBTP
Connector
Graph and
Communication
Gateway Service Services SDK

Customer’s Org Maintained by Cisco Customer’s Tenant

• Webex Video Integration for Microsoft Teams (VIMT) is a service provided by the Webex Cloud and does
not require on-premises components nor software upgrades on video devices
• Webex video infrastructure and Microsoft SDK are hosted in Azure and maintained by Cisco on behalf of
customers
• Available to On-prem Registered, Cloud Registered/Aware Webex Rooms, and 3rd party SIP endpoints
Video Integration for Microsoft Teams Gateway
Calendar service and OBTP

Calendar Service
for OBTP

Customer’s Org Customer’s Tenant

Calendar Integration: Room

One Button to Push Calendar Meeting Invitation

OBTP traffic • Calendar integration is required for OBTP

Graph API • OBTP is supported for Webex Cloud registered and Webex Edge for Devices (cloud aware) video
devices
Video Integration for Microsoft Teams Gateway - Signaling path

Gateway Service
Connector
Graph and
Communication
Services SDK

Customer’s Org Maintained by Cisco Customer’s Tenant

• On-prem video devices must be able to call the Webex domain for VIMT over SIP
• Interworking to H.323 can be provided by local on-prem infra (i.e. VCS/Expressway)
Webex signaling
Example: Endpoint<->CUCM<->Expressway-C<->Expressway-E<-internet->Webex Cloud
Microsoft signaling
Video Integration for Microsoft Teams Gateway
Media path

Connector
1 video stream per screen + 1 Graph and
content stream Communication
Services SDK

Maintained by Cisco Customer’s Tenant

Multiple media streams per

1 video stream per screen
video device
Single stream media
• Media of Webex cloud registered video devices flows directly to the Azure DC maintained by Cisco
Microsoft Teams
• Media of on-premises-registered video devices flows to the Azure cloud maintained by Cisco via the local SIP
Multistream media infrastructure:
Example: Endpoint<->Expressway-C<->Expressway-E<-Internet->Cisco-maintained Azure Tenant
• No Video Mesh support
Devices connect to closest Azure Datacenter

• US East 2 (VA)
• West Europe (Amsterdam)
• South UK (London)
•
•
Southeast Asia (Singapore)
Australia East (Sydney)
April 2021
VIMT Functionality
Webex VIMT (CVI) Features - Summary
Supported video devices Unique features for Webex Rooms (*)
• Webex Cloud registered OBTP Join (One Button To Push)
• Webex on-prem registered
Multi-screen support
• Webex Edge for Devices
Integrated Participants List
• SIP standard based
(H.323 via on-prem interworking) Active Layout Control (via Touch 10)
Server/Local Mute status sync
Features available to any device
Unidirectional Whiteboarding from Webex Board and DeskPro
• Family of layouts for Video devices
• Layout control via DTMF (*) Some features require cloud registration or Webex Edge for Devices
• 2-way content sharing Local in-call device features are supported for any deployment model (i.e. best
overview, speaker track, noise canceling, etc)
• Server-side Mute/Unmute management via DTMF
• Recording Indicator
• Configurable lobby management policy
(guest access / lobby bypass)
Caveats
• No Video Mesh (Hybrid Media)
• IVR address is based on the primary SIP address of the Webex Org and is not currently customizable
• VIMT only supports one Microsoft Tenant per Webex Org
• Microsoft Teams Live Events not supported today (backlog item)
 Lobby Bypass for Trusted Video Devices
Webex Org ID used to trust a customers’ devices
On-prem registered and Webex Cloud Registered and
Webex Edge for Devices Webex Edge with native experience

VIMT Config & Devices

in same Webex Org
Trusted Device Server Certificate CH Verified Domain: example.com Trusted Device
SAN: example.com

Meeting Policies (admin center) Meeting Options (meeting invite)

Webex configuration documents: https://help.webex.com/article/ebbjqz

 Local and server (remote) mute sync status
Summary

Cloud Registered Webex Edge for Devices (Native Webex Edge for Devices SIP Devices NOTES
Webex Devices Webex Meetings Experience) (non-Native Webex Meetings Experience)

Is the Local mute button status on the Webex device synced with the roster list?

*Must use DTMF *6 on

Local Mute No Sync* No Sync* No Sync* No Sync* devices to update server
(from Touch10/Touchscreen) mute status in roster

*Must use DTMF *6 on

Local unmute Synced Synced Synced No Sync* devices to update server
(from Touch10/Touchscreen) mute status in roster

Remote mute from *Must use DTMF *6 on

MS Teams client Synced Synced No Sync* No Sync* devices to update server
(AKA server side) mute status in roster

Remote unmute from Feature not available in Feature not available in Feature not available in Feature not available in Microsoft Teams doesn’t
MS Teams client
(AKA server side)
Microsoft Teams Microsoft Teams Microsoft Teams Microsoft Teams allow remote unmuting
Setup
Webex VIMT provisioning - Setup page

Click
Set Up

Hybrid Services
Set up Flow
Set up Flow (Microsoft Authorizations)

[email protected]
Azure App Permissions

Microsoft 365 Global Admin must Accept the Azure consent flow
Required by Microsoft for a Certified CVI Provider to use the Media SDK
• Read domains: needed to look up verified domains
• Access media streams in a call as an app: service accessing media streams
Read domains
• Initiate outgoing 1 to 1 calls from the app: future use for 1:1 calls
• Initiate outgoing group calls from the app: needed to create call to access media
• Join group calls and meetings as an app: for bypass lobby
• Join group calls and meetings as a guest: join as a guest
• Read online meetings details: retrieve join URL from VTC Conf ID

https://docs.microsoft.com/en-us/microsoftteams/cloud-video-interop
Automatic Setup Test Succeeds

Video Integration Setup

Microsoft Teams
✅ We verified the admin permissions required for the integration exist and are valid.

To complete the setup, copy & paste the following commands, which enable the integration for all users in your
organization, to Microsoft PowerShell.

To enable or disable the integration for specific users, see the Microsoft documentation on Grant-
CsTeamsVideoInteropServicePolicy.
Creates CVI Provider Policy
New-CsVideoInteropServiceProvider -Name Cisco -TenantKey
“[email protected]" -InstructionUri
"https://webex.com/msteams?confid={ConfId}&tenantkey=example&dom
ain=m.webex.com" -AllowAppGuestJoinsAsAuthenticated $true -
AadApplicationIds “7968d647-6a0f-4476-8931-206eff6c4d55”
Applies CVI Policy to…
Grant-CsTeamsVideoInteropServicePolicy-PolicyName Cisco -Global used to enable all users
ServiceProviderEnabled -Global
-Identity can be used to enable a
Once you’ve run the commands, click Ok. single user at a time

https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install
 Example Teams invite (generated by Microsoft)

MSFT Teams
Join Info

Join Link for App & Web

App

IVR Video Address

CVI Specific Conference

ID MSFT
CVI JoinTeams
Info
CVI info
(enabled via
Link to CVI Partner PowerShell)
web page
Alternate Dialing Instructions Page

[email protected]

[email protected]
Webex Video Integration for Microsoft Teams - Joining
Methods overview
VIMT-enabled meetings are available through:
One Button To Push – adding the Webex Rooms’ email address to the MS Teams calendar invite
IVR – calling a customer-specific address (i.e. [email protected]) and manually dialing the "Video
Conference ID" available in the MS Teams calendar invite
Direct Dial-in – calling directly the meeting’s address (i.e. [email protected]) available
through the “Alternate VTC dialing instructions” link in the calendar invitation

See next slide for a summary of the supported joining methods for the different
devices' deployment models
Webex Video Integration for Microsoft Teams (VIMT)
- Supported joining methods

0 Joining method

OBTP VIMT IVR Direct dial-in

(Hybrid Calendar) (Alternate VTC dialing instructions)

Webex Registered
(Cloud)
Deployment Model
Devices

Webex Edge for Devices

(Cloud with on-premises registration)
(Native Webex experience independent)

Webex and 3rd party SIP capable

(On-Premises registered)
What you need to use VIMT (CVI)
Required (deployment guide here)
qWebex Org w/ at least one user license (included for new customers)
q When A-MST-WX is ordered, the email address from the order will get a bootstrapped admin user sent if a Webex Org
does not already exist.

q An Org internal Administrator with Full Access

External admins and access from Partner Portal are not sufficient for VIMT Setup/administration

Recommended (for OBTP)

qSync users and enable for Calendar Service
• Hybrid Directory Service Sync Tool or Azure AD SCIM API Setup
qConfigure Hybrid Calendar Service to provide OBTP
• How OBTP Works with Cloud-Registered Devices
qWebex Rooms must be registered directly or indirectly to the cloud
• Webex Cloud Registered (direct)
• Webex Edge for Devices – Cloud Aware (indirect)
Webex Rooms running
Microsoft Teams meeting
web app (WebRTC)
Joining Microsoft Teams meetings - WebRTC
One Button to Push experience
 In-Meeting Experience – using WebRTC 33

Basic, single screen layout controlled by Microsoft Teams

• Up to 4 Active Speakers are shown on video
• Ability to view content share + live video streams (bottom bar)

Sharing content from Webex Device is not supported

• Requires use of separate Microsoft Teams client

In-meeting controls are available via Touch10 with Interactive

mode (Webex Devices feature)

Additional local device specific features such as Speaker

Tracking are fully supported
WebRTC Architecture
Webex Rooms for Microsoft Teams meeting
Room Kits, Room Series, Boards, Desk Pro
(web-engine enabled devices) - devices must be
cloud registered or cloud aware (Webex Edge
for Devices)

Microsoft
OBTP via Calendar Service Teams

Calendar interactions Microsoft Web

Media & Signaling App Single Screen
layout
Joining Microsoft Teams meetings– WebRTC
Calendar Service and OBTP

Calendar Service

Calendar Integration
Customer’s org One Button to Push - Endpoint booking Customer’s tenant
- Invite parsing

• Enabling Webex Calendar Service is required (WebRTC is available only via OBTP)
• OBTP is supported for both cloud registered and cloud aware (Webex Edge for Devices)
OBTP traffic
• Cloud solution requires no on-premises infrastructure – uses embedded browser in endpoint to
Graph API directly join a Microsoft Teams meeting as a guest
Modern web technology – WebRTC
In-meeting signaling and media

Customer’s tenant
WebRTC streams

• WebRTC traffic for both cloud registered and cloud aware video devices
• direct flow from the customer’s premises to the Microsoft Teams’ bridge
Microsoft signaling • does not traverse through Expressway
Microsoft media • Ports 80, 443, 3478-3481
 Example Teams invite (generated by Microsoft)

MSFT Teams
Join Info

Join Link for App & Web

App

Direct Guest Join is designed for

Business-to-Business non VIMT-enabled meetings
 Direct Guest Join (WebRTC)
- Joining Methods overview
The only Joining Method available for Direct Guest Join is One Button To Push:

Might require Exchange policy adjustments

Business-to-Business scenarios require additional considerations
0 Joining method

OBTP
(Hybrid Calendar)
Deployment Model
Webex Registered
(Cloud)
Devices

Webex Edge for Devices

(Cloud with on-premises registration)

Webex Devices
(On-Premises registered)
What you need to use VIMT (WebRTC)
Required
qWebex Org w/ at least one user license or device license
qConfigure Hybrid Calendar Service to provide OBTP

• How OBTP Works with Cloud-Registered Devices

qWebex Rooms must be registered directly or indirectly to the cloud

• Webex Cloud Registered (direct)

• Webex Edge for Devices – Cloud Aware (indirect)

Recommended
qSync users and enable for Calendar Service

• Hybrid Directory Service Sync Tool or Azure AD SCIM API Setup

One Button to Push
for VIMT and WebRTC
One Button To Push for VIMT and WebRTC
Overview

One Button To Push

Supported on Webex Rooms when Webex Registered or enabled with Webex Edge for Devices

No support for TMS-XE calendar integration

This functionality has been thoroughly evaluated by the BU and found not possible due to technical limitations

Might require Exchange policy adjustments

Business-to-Business scenarios require additional considerations

Edge for devices requires CE9.14.3+

One Button To Push for VIMT and WebRTC
Shared Mode vs Personal Mode
When configuring Hybrid Calendar service for OBTP, customers have two choices (same as Webex Meetings):
1) Shared Mode devices
• Hybrid Calendar service is configured to monitor the resource mailbox assigned to the Webex Room for new invites that include Microsoft
Teams meetings
• Shared devices require a resource mailbox in Exchange
• Might require Exchange policy adjustments
• Additional considerations about Business-to-Business scenarios are covered with following slides
Personal Mode devices
Hybrid Calendar service is configured to monitor the user mailbox for new invites that include Microsoft Teams meetings
Users linked to personal devices must be available in Control Hub with Hybrid Calendar enabled

NOTE: Deployments can have a mix of Shared Mode and Personal Mode devices
One Button To Push for VIMT and WebRTC
OBTP decision tree

Microsoft Teams invite Personal mode Enable Hybrid Calendar

Devices
(new/forwarded) for Users

Shared mode Y

Can you change the N Can you import users

Exchange room
into Control Hub?
calendar policy?

Y N

Enable Hybrid Calendar for No OBTP

Devices (Fallback to IVR/Direct Dial-in)
One Button To Push for VIMT and WebRTC
Shared Mode Devices - Exchange Calendar policy requirements

The default Exchange settings for resource mailboxes strip the body and subject from meeting invites
To provide the best user experience, Cisco and Microsoft guidelines for Shared Devices recommend:
Ensure Exchange is configured to retain the meeting comments, so that the Hybrid Calendar service can process meetings for shared
rooms’ mailboxes
Ø PowerShell: “set-calendarprocessing -deleteComments $false”
In addition, in order to use the subject as the OBTP meeting title instead of the organizer name
Ø PowerShell: “set-calendarprocessing -deleteSubject $false -AddOrganizerToSubject $false”

Sub-optimal case:
Customers unable to change the default “-deleteComments $true” setting will have to import all users hosting meetings in Control Hub

Continue…
 One Button To Push for VIMT and WebRTC
Shared Mode devices – Business-to-Business scenarios
Additional requirement for Business-to-Business scheduling of Shared Devices:

Exchange default policies prevent an external meeting organizer from booking your local resource mailboxes (resource mailboxes auto-accept
settings are ignored). This is true also when the external meeting invite is forwarded to the room by an internal user

Customers will have to choose one of the following options:

1) Modify the Exchange calendar policy to auto-accept External Invitations for Shared Devices*

Ø Powershell: “set-calendarprocessing –ProcessExternalMeetingMessages $true”

2) Set a room mailbox delegate for manual processing (meeting accept/decline)*

3) Copy and paste the meeting info (i.e. URI) into a new calendar invite to book the local room resource mailbox (intra-company scenario)

4) Fallback to IVR/Direct Dial-in (AVAILABLE ONLY WITH VIMT)

*NOTE: When processing OBTP for B2B meetings, Hybrid Calendar is not able to parse the meeting information from the external organizer’s
mailbox. Therefore, Exchange must be configured to retain the meeting comments (Powershell: “set-calendarprocessing -deleteComments $false”)
One Button To Push for VIMT and WebRTC
– additional steps for Business-to-Business scenarios
Incoming B2B MS
Teams invite

Shared Are external Is there a Copy & paste

What kind of N N
resource reservations delegate able to accept the invite into a new local N
device do you the resource reservation? No OBTP
want to book? automatically accepted? resource reservation

Y Y Y

Personal

Go to OBTP decision tree to select the

proper device mode
Summary of Meeting
Interoperability
Two Methods to join Microsoft Teams meetings
VIMT Cloud Gateway (CVI enabled) WebRTC web app
Intended for Hosted by my company Join any other Microsoft Teams meeting

Microsoft Teams experience - single screen with

Webex experience - multi Screen with flexible layouts
Microsoft Teams layout
Experience Bi-directional content share (using a cable or
Ability to receive share only (Microsoft Teams
wireless*)
layout)
Roster list with touch screen only
Roster Full roster list
(Webex Board & Desk Pro)
Room Kits, Room Series, Boards, Desk Pro
Devices Webex and any SIP-capable video devices
(web-engine enabled devices) - devices must be
supported Cloud and on-premises registered devices
cloud registered or cloud aware
OBTP join with Calendar Service, direct dial in, or IVR
Join Experience OBTP join with Calendar Service for B2B meetings
join experience

Licensing Add on license required Webex Room registration (included in Flex)

*Requires on prem registration (or cloud aware)

Webex Meetings advantages
Not available in Microsoft Teams meetings
• Market Leader in video conferencing • Companion Mode
• High Frame Rate wireless content sharing • Face recognition / name labels
• Multi-stream with additional layout options • People Insights
• Bi-directional whiteboarding • Room panorama
• In-meeting Webex Assistant • Localized media via Video Mesh
Licensing overview
Licensing
VIMT: Provides the best video experience requiring additional license per device
• Subscription pricing for video endpoints connecting to your Microsoft
Teams meetings* (List $49.50/month/active video endpoint)
• Two offers now available;
1) Active Devices including guests in use more then once per 30 days
2) All Devices customer owns/operational
• Order using A-MST-WX or A-FLEX-3
• Subscription of 1,3,or 5 years, pay annual/monthly/prepay, auto-renewal optional
WebRTC: Direct guest join supported on modern Webex Room Series rooms registered to
Cloud or Cloud Aware with experience limitations
• Cloud Device Registration (via Flex or standalone $29.50/month list price)
*Video Endpoints: Shared room systems as well as desktop video endpoints (e.g. Desk Pro, DX80, DX70), Webex and 3rd party endpoints
Video Integration for MS Teams (VIMT) Offers
VIMT Active Devices VIMT All Devices
• Any device using service more then once in 30- • Subscription for all devices customers has
day period needs a license operational (Rooms & desktops)
• Avg over last 3 months, can be used to • Customer keeps subscription current as they
compute True Forward deploy new devices within 60 days
• 10% overage allowed • Annual True Forward review of devices in use
• Include devices owned or guests • Guest devices can join without additional
licensing costs – fixed price
• Min 5 devices: initial order only
• Min 25 devices: Initial order only
• $49.50 per device/month
• $49.50 per device/month
Device Registration options for VIMT customers
• Majority of VIMT customers don’t have Flex subscription today
• VIMT works best with Cloud Registration or Edge for Devices (OBTP)

• Customers have two buying options:

Ø A-FLEX-3 VIMT as add-on option
• A-Flex-3 Active User most economical solution to get device registration
• VIMT + device registration + Webex (AU) Meetings with Webex App with one subscription
giving access to all services as a bundle

Ø A-MST-WX Existing top-level SKU for VIMT without Flex or device reg

• Ordering guide for more details A-MST-WX or A-FLEX-3

Active Video Endpoints defined
• Unique endpoints counted on 30 day rolling window
• Bursting above subscription available, support based on value purchased
• Endpoints counted if joining more than once per 30 days rolling
• Customers allowed 10% overage, otherwise increasing subscription required

• 30-day average usage monthly reporting planned

• Initially internal reports; manual follow-up until automation
• Customers in consistent overage: Customer & partner notified to change
subscription (buy more) for future usage
• Roadmap to automate usage and overage notifications via Control Hub
• Able to reduce subscription quantity @ end-of-term (like FLEX)

• Customers advised to purchase at least 50% of total endpoints owned

Appendix
 Webex VIMT Configuration

Login as Customers will need to

Redirect O365
Control O365 grant Cisco Azure App
Consent Admin
Hub access to their O365
Portal
Tenant
Redirect
Webex
Admin
Control Hub

Customers will be provided

TenantKey a tenantKey for their
Customer will need a Webex and Webex Org
PowerShell config
Org
Strongly recommend syncing
users from Microsoft AD/Azure
AD and enabling Hybrid Calendar
Service
PowerShell
O365 Admin (SkypeOnlineConnector module)
CVI Provider Config
 Webex VIMT (CVI) Feature summary
Features Device Deployment Model
Webex Webex Edge Webex
3rd party SIP Device
Cloud-registered for Devices enabled On-prem
Native Webex Non-Native Webex
Experience (SIP) Experience

Family of layouts (Flexible Layouts) þ þ þ þ þ

Layout control via DTMF þ þ þ þ þ
Active layout control (Touch10) þ þ þ þ ý
2-way content sharing þ þ þ þ þ
Recording indicator þ þ þ þ þ
(Out of band icon) (Out of band icon) (in-band transcoded indicator) (in-band transcoded indicator) (in-band transcoded indicator)

Configurable Lobby bypass þ þ þ þ þ

One Button To Push þ þ þ ý ý
Multi-screen support þ þ þ þ ý
Integrated participants list þ þ þ þ ý

Mute Sync þ þ þ þ þ
(Partial – on-screen & *6 DTMF) (Partial – on-screen & *6 DTMF)

Unidirectional Whiteboarding from -

Webex Boards and DeskPro (non-interactive) þ þ þ þ (receive only)