Microsoft Teams Rooms SIP/H.323 calling

The Pexip Service enables customers who have Microsoft Teams Room devices with Pro licensing to make and receive 1:1 (also referred to as point-to-point) SIP/H.323 video calls with VTCs, and to call into a third-party SIP or H.323 enabled meeting such as Cisco Webex, Zoom, GoTo, and Google Meet.

Diagram of Teams Rooms SIP and H.323 calling options

Teams Room SIP/H.323 calling (packaged as "Pexip Connect for Teams Rooms") supports:

  • Dialing from a VTC (internal or external) into a Teams Room.
  • Dialing from a Teams Room to an internal or external VTC.
  • Dialing from a Teams Room into a third-party SIP or H.323 enabled meeting.
  • Dialing via One-Touch Join into meetings with other third-party providers.
  • Bi-directional screensharing (BFCP or H239) between the Teams Room and the VTC.
  • Single and dual screen systems for meetings and content sharing.
  • Sending DTMF tones from a Teams Room.

Note that:

  • Different calling policies can be applied to certain rooms to, for example, not allow incoming SIP/H.323 calls, while other systems are enabled for this functionality depending on your business requirements.
  • When joining a Teams Meeting the full feature set of a Teams Room is available, including participant list and other advanced meeting interaction features. However, this is not a call to a Teams meeting, thus when calling a SIP/H.323 destination many of the standard Teams meeting features (such as call transfer, share whiteboard, and add participant) are not available, as the functionality for 1:1 calls is focused around bidirectional audio/video communication and content sharing.
  • A Teams Room cannot be called if its name is composed of digits only and the domain used for your Teams Room interoperability is also used for SIP/H.323 CVI into Microsoft Teams, or for Google Meet interoperability.
  • This feature is designed to support calls to/from Teams Room systems. If appropriate routing of domains is configured then SIP devices may also call Teams users, however Pexip support for this is limited and is currently provided only on a best-effort basis.

This article covers:

Licensing requirements

Pexip licensing requirements:

  • Connect for Teams Rooms license count to match your Microsoft Teams Room Pro license count (contact your Pexip authorized support representative for details)

Microsoft requirements:

  • Teams Room Pro license
  • Either:
    • a Windows based device running Microsoft Teams Rooms on Windows version 5.2.115.0 or later
    • an Android device running Microsoft Teams Rooms on Android version 1449/1.0.96.2026129709 or later

      Incoming SIP calls are supported on Android devices from version 1449/1.0.96.2026249711. For more information, see Microsoft's release notes.

Pexip reserves the right to audit the Teams Room Pro license quantity to ensure compliance, for example by requesting a screenshot from the customer's Microsoft 365 admin center:

Screenshot of Microsoft 365 admin center showing Teams Rooms license counts

Enabling your organization for Teams Room calling

This section describes how to enable your organization and Teams Room systems for SIP/H.323 calling.

Enabling your Teams tenant

The steps involved in enabling your Teams Rooms vary slightly depending upon whether or not you are an existing user of the Pexip CVI service. Expand the relevant section below.

Enabling and configuring your Teams calling policy

This section applies to both MTRs on Windows and MTRs on Android.

Your IT administrator must run Teams PowerShell cmdlets to enable the Teams Room calling policy and configure which calls Teams Rooms can receive.

  1. Start a PowerShell session as Administrator and run the following commands:

    Uninstall-Module MicrosoftTeams -AllVersions -Force

    Install-Module MicrosoftTeams -MinimumVersion "4.0.0" -AllowClobber

    These commands ensure the appropriate MicrosoftTeams module is installed and that it replaces any existing SkypeOnlineConnector module that may already be installed.

  2. Run the following commands to connect to your Teams tenant:

    Import-Module MicrosoftTeams

    Connect-MicrosoftTeams

After connecting to your Teams tenant, use the following commands to configure your calling policies.

  • To get a list of your existing policies:

    Get-CsTeamsRoomVideoTeleConferencingPolicy

  • To create a new policy:

    New-CsTeamsRoomVideoTeleConferencingPolicy -Identity "MtrSipCallingPolicy" -Enabled $true -AreaCode "923c9f0a-b883-4efe-af73-54810da59f83" -ReceiveExternalCalls "Enabled" -ReceiveInternalCalls "Enabled"

    where:

    • the -AreaCode given above is the Pexip Service AppID; this should be used in your own command.
    • "MtrSipCallingPolicy" is the name of the policy being created. You can use any name of your choosing.

    ReceiveExternalCalls and ReceiveInternalCalls default to Disabled when not specified. Both properties accept two values: Enabled or Disabled. This allows you to configure whether Teams Rooms can receive internal calls, external calls, or both.

  • Assigning the calling policy

    You can assign the calling policy at one of the following levels, depending on which Teams Rooms need to use it.

    • To assign the policy to all compatible Teams Rooms in the tenant (recommended), run:

      Grant-CsTeamsRoomVideoTeleConferencingPolicy -PolicyName "MtrSipCallingPolicy" -Global

    • To assign the policy to an Azure AD / Microsoft Entra ID group, run:

      Grant-CsTeamsRoomVideoTeleConferencingPolicy -PolicyName "MtrSipCallingPolicy" -Group "<Object ID of the Azure AD / Entra ID group>"

      Replace the placeholder with the object ID of the Azure AD / Entra ID group to which you want to assign the policy.

    • To assign the policy to individual Teams Rooms for pilot testing, run:

      Grant-CsTeamsRoomVideoTeleConferencingPolicy -PolicyName "MtrSipCallingPolicy" -Identity "<UPN of the Teams Room account>"

      Replace the placeholder with the user principal name (UPN) of the Teams Room resource account.

  • Enabling calendar processing

    Enable calendar processing to allow Exchange to process third-party meetings and externally created invitations so that they can be joined from a Teams Room.

    1. Install the Exchange Online PowerShell module if you have not already done so:

      Install-Module ExchangeOnlineManagement -Scope CurrentUser

    2. Connect to Exchange Online and sign in:

      Connect-ExchangeOnline

    3. Set calendar processing for each Teams Room:

      Set-CalendarProcessing <UserPrincipalName> -ProcessExternalMeetingMessages $True -DeleteComments $False

      Replace <UserPrincipalName> with the email address of the Teams Room resource account.

Other useful commands

  • To grant a particular policy configuration to a specific user/room ("mtr01@pexample.com" in this example):

    Grant-CsTeamsRoomVideoTeleConferencingPolicy -Identity "mtr01@pexample.com" -PolicyName "MtrSipCallingPolicy"

  • To remove a policy from a specific user/room ("mtr01@pexample.com" in this example):

    Grant-CsTeamsRoomVideoTeleConferencingPolicy -Identity "mtr01@pexample.com" -PolicyName $null

  • To update properties on an existing policy:

    Set-CsTeamsRoomVideoTeleConferencingPolicy -Identity "MtrSipCallingPolicy" -ReceiveExternalCalls "Disabled"

    This example disables external calls for the MtrSipCallingPolicy policy. The Identity parameter is mandatory.

  • To view Teams Rooms assigned to a policy:

    Get-CsOnlineUser -Filter {TeamsRoomVideoTeleConferencingPolicy -eq "MtrSipCallingPolicy"} | Select-Object DisplayName, UserPrincipalName

    This command lists the Teams Rooms assigned to the MtrSipCallingPolicy policy.

  • To view the policy assigned to a particular Teams Room:

    Get-CsOnlineUser -Identity "<Mailbox Identity>" | Select-Object DisplayName, UserPrincipalName, TeamsRoomVideoTeleConferencingPolicy

    Replace <Mailbox Identity> with the identity of the Teams Room mailbox.

  • To delete a policy:

    Remove-CsTeamsRoomVideoTeleConferencingPolicy -Identity "MtrSipCallingPolicy"

    The example above deletes the MtrSipCallingPolicy policy.

In Set-CsTeamsRoomVideoTeleConferencingPolicy and Remove-CsTeamsRoomVideoTeleConferencingPolicy commands, -Identity specifies the policy name. In Grant-CsTeamsRoomVideoTeleConferencingPolicy, -Identity specifies the Teams Room being configured, while -PolicyName specifies the policy name. When assigning a policy to a group, use -Group to specify the group's object ID.

Enabling calling to meetings hosted on other platforms

Microsoft's "Cross-Platform meetings via SIP join" feature lets you use a Teams Room to join meetings hosted on other meeting platforms as easily as you can join meetings hosted on Microsoft Teams. Note that third-party meeting providers drive the experience of their platform on the Teams Room device.

This section only applies to MTRs for Windows, and needs to be enabled per device for each specific meeting type required. For MTRs for Android, Enabling and configuring your Teams calling policy via PowerShell is enough to enable all the supported third-party meeting providers for both scheduled and Join with an ID calls.

To enable third-party meetings directly via your device:

  1. From the console, go to More > Settings > Meetings.
  2. Enable the Third-party meetings providers you want to support.

    Teams Rooms Meetings settings with third-party providers enabled

    The device will reboot when you change the settings.

Alternatively, you can use the Teams Rooms Pro Management portal to enable the third-party meeting providers on your devices.

For more information see this Microsoft article on third-party meetings on Teams Rooms.

Placing and receiving calls

Teams Room console home screen with calling options

You have various options to place a call from the Teams Room console:

  • For One-Touch Join calling into a scheduled meeting via the integrated calendar: select Join for the displayed meeting.

    For MTRs for Windows: To use One-Touch Join for guest dialing into a Zoom Meeting, the invitation must be from a Zoom environment that is enabled for either Zoom's CRC (Conference Room Connector) or Zoom's Video Interop for Meetings.

    MTRs for Android will always try to use SIP to connect to Zoom meetings, whether or not SIP details are included in the meeting invitation.

  • For calling by a meeting ID (Teams meetings or meetings with other third-party providers): select Join with an ID, select the meeting provider (for example Teams, Zoom, Cisco Webex, Google Meet), and then enter the meeting ID and passcode.
  • To call a VTC: select Call, then select SIP or H.323 as appropriate, and enter the address of the VTC you want to call.

Note that the Teams Room software is regularly updated, thus some images shown here may not directly match the current appearance and options.

Placing a call

Teams Room screen for placing a SIP or H.323 call

Receiving a call

Incoming call screen on a Teams Room device

Entering DTMF tones

In-call keypad on a Teams Room for entering DTMF tones

Known issues

There are some current known issues when joining a call.

Join via calendar

  • (MTRs on Windows only) Normal SIP addresses not belonging to one of the predefined services (i.e. sip:meeting@domain) are not yet picked up by the Teams Room calendar. Calendar-based join for Zoom meetings without SIP addresses (e.g. free Zoom) will fall back to Direct Guest Join.

Join with meeting ID / passcode

  • Zoom Meetings that do not allow SIP will not be joinable via join by meeting ID / passcode. Zoom recently updated their service to default to SIP Video Interop for Meetings on paid Zoom accounts.

Finding the Teams Room "calling URI" / email address

  1. Select the More ellipsis on the room console.
  2. Select Settings.
  3. Enter the password.
  4. Select the Account tab.
  5. The Email address is the Teams Room calling URI to dial from a VTC device.

Teams Room account settings showing the calling URI email address

mtr