Cisco Webex Room Kit Integration with Microsoft Teams: Complete Setup Guide

In enterprise boardrooms, a common infrastructure conflict occurs: an organization standardizes on Microsoft Teams for daily collaboration, but possesses hundreds of thousands of dollars of premium Cisco Webex Room Kits (Room Bar, Room Kit Plus, Room Kit Pro, Room 55/70) equipped with Touch 10 or Room Navigator controllers.

Historically, connecting a Cisco SIP/H.323 room endpoint to a Microsoft Teams meeting required expensive third-party Cloud Video Interop (CVI) licenses (from Cisco, Poly, or Pexip). Today, Cisco RoomOS provides a free, native solution: Direct Guest Join (DGJ) via an embedded Chromium WebRTC engine. When configured correctly, the Cisco touch panel automatically displays a green “One Button to Push” (OBTP) join button for any calendar invite containing a Teams link.

However, getting DGJ to work reliably requires precision across three distinct layers: Exchange Online calendar parsing, Cisco Control Hub / xAPI web engine parameters, and Teams tenant anonymous join policies. This guide provides the complete, field-tested deployment runbook.

Architecture: How Direct Guest Join (WebRTC) Works

Unlike standard Cisco SIP calls that route through Expressway or a Unified Border Element (CUBE), Direct Guest Join runs entirely over an internal web browser inside the Cisco Room Kit:

Step 1: Exchange Online Mailbox Setup (The OBTP Regex Prerequisite)

For the Cisco Touch 10 or Room Navigator to display the green “One Button to Push” button, the Exchange Online mailbox must preserve the Teams meeting URL inside the calendar body. If Exchange strips the body comments, the Cisco device sees an empty invite and the button will never appear.

# 1. Connect to Exchange Online
Connect-ExchangeOnline

# 2. Provision the Room Mailbox for the Cisco device
New-Mailbox -Room `
  -Name "Conf-Room-Cisco-Plus" `
  -DisplayName "London Boardroom (Cisco Room Kit)" `
  -PrimarySmtpAddress "cisco-boardroom@contoso.com"

# 3. CRITICAL: Preserve Comments & Enable External Meetings
Set-CalendarProcessing -Identity "cisco-boardroom@contoso.com" `
  -AutomateProcessing AutoAccept `
  -DeleteComments $false `
  -DeleteSubject $false `
  -ProcessExternalMeetingMessages $true

Why -DeleteComments $false is mandatory: Teams invites store the meeting join coordinates in the HTML body. By default, Exchange strips comments from room calendar appointments. Setting this to $false allows the Cisco parser to extract the URL.

Step 2: Enabling Direct Guest Join in Cisco Control Hub

If your Cisco Room Kit is registered to the Webex Cloud, configure the WebRTC policy directly in Cisco Control Hub (admin.webex.com):

Step 3: Device-Side xAPI CLI Commands (On-Premises / Expressway)

If your Cisco Room Kit is registered to on-premises infrastructure (Cisco Unified Communications Manager / Expressway) or you prefer using the SSH command line, execute these exact xAPI configuration commands:

# 1. Enable the embedded Chromium Web Engine
xConfiguration WebEngine Mode: On

# 2. Enable native Microsoft Teams WebRTC parsing
xConfiguration WebEngine Features MicrosoftTeams: On

# 3. Ensure the One-Button-To-Push (OBTP) booking interface is visible
xConfiguration UserInterface Bookings Visibility: Always

# 4. Enable WebRTC content sharing from local HDMI ingest
xConfiguration WebEngine Features InCallContentSharing: On

# 5. Commit and verify status
xStatus WebEngine
*s WebEngine Availability: Available
** end

GUI Web Admin Alternative: Access the phone’s web interface (https://<cisco-ip>) ➔ Setup ➔ Configuration ➔ WebEngine ➔ Set Mode: On and MicrosoftTeams: On.

Step 4: Microsoft Teams Tenant Setting — Anonymous Join Policy

Direct Guest Join operates by having the Cisco Room Kit connect as an authenticated external guest or anonymous participant via WebRTC. If your Teams tenant strictly blocks anonymous participants from joining meetings, the Cisco device will hit a wall when attempting to connect.

Step 5: Perimeter Firewall & WebRTC Port Requirements

Direct Guest Join connects directly from the Cisco hardware over your corporate LAN to Microsoft’s Azure cloud. Ensure your perimeter firewall does not perform SSL/TLS deep inspection on WebRTC traffic to Microsoft:

Touch 10 / Room Navigator User Experience: Before vs. After

The Top 3 Real-World Troubleshooting Gotchas

Gotcha 1: The Green “Join” Button Never Appears on Touch 10

Root Cause: The Exchange Online calendar engine stripped the HTML invite body. If the Cisco endpoint cannot locate teams.microsoft.com in the invite, OBTP will not trigger.

The Fix: Run Get-CalendarProcessing -Identity "cisco-boardroom@contoso.com" | Format-List DeleteComments. If it returns True, execute Set-CalendarProcessing -Identity "cisco-boardroom@contoso.com" -DeleteComments $false. Then send a fresh test invite.

Gotcha 2: Device Clicks “Join” but Hangs on White/Black Screen

Root Cause: The enterprise firewall is performing SSL Decryption / Deep Packet Inspection on HTTPS traffic to Microsoft, breaking WebRTC client certificate validation inside RoomOS.

The Fix: Add an explicit SSL Decryption bypass rule on your Palo Alto / Fortinet / Zscaler firewall for the Cisco Room Kit’s voice VLAN targeting *.teams.microsoft.com and *.skype.com.

Gotcha 3: Stuck at “Someone in the meeting should let you in soon”

Root Cause: The Teams meeting organizer’s tenant policy enforces a strict Meeting Lobby for anonymous or external participants.

The Fix: In the Teams meeting options (or tenant-wide meeting policy), configure “Who can bypass the lobby?” to “People in my organization and guests” or allow callers to bypass the lobby automatically.

Frequently Asked Questions (FAQ)

Related Meeting Room & Infrastructure Guides

• Microsoft Teams Rooms (MTR) Intune & Pro Portal: Custom Compliance Policies, Peripheral Health & Remote Log Analysis
• Microsoft Teams Rooms (MTR) Setup: Step-by-Step Exchange Online, CA & Console Guide
• Microsoft Teams SIP Gateway: Onboarding Cisco & AudioCodes Desk Phones
• Microsoft Teams Call Queues & Auto Attendants: Complete Setup Guide
• Teams Dynamic Emergency Calling (E911): RAY BAUM’S Act & Compliance
• Teams Direct Routing SIP 403 Forbidden: User Licensing & FQDN Gotchas
• How to Configure AudioCodes SBC for Microsoft Teams Direct Routing