About Pexip's Microsoft Teams CVI integration
Pexip's Cloud Video Interoperability (CVI) Service enables professional SIP and H.323 video conferencing systems to join Microsoft Teams as if they were native Microsoft clients.
- Pexip natively integrates with the Microsoft Teams workflow — scheduling meetings from Teams or Outlook automatically inserts video conferencing dial-in details.
- When joining a Teams meeting from a third-party endpoint, everyone benefits from the full Teams experience with HD video, audio, and content sharing.
This article covers:
- Domain hosting and dial strings / Virtual Reception (IVR)
- Trusted devices for lobby bypass
- One company, multiple Teams tenants
- Join workflow, layouts and notifications for Teams meetings
- Integration features (including content sharing, display names and audio participants)
Domain hosting is mandatory for the Teams gateway service to be set up. (This is how the Pexip Service distinguishes between each customer's Teams gateway service on the multitenant Cloud Service.)
For example, if customdomain.com is the video domain chosen, the Microsoft Teams Virtual Receptionist for 2-stage dialing is at firstname.lastname@example.org and direct dialing into the Teams meeting is via <ConferenceID>@customdomain.com.
Note that the Pexip apps cannot join meetings via the Virtual Reception (but they can be used to call directly into the meeting).
Soft clients and video endpoints can be considered "trusted parties" and can enter a Teams meeting without the need for a meeting manager to manually admit/deny entry through the Teams lobby if:
- They are registered on the Pexip Service under the same company as the CVI Service for MS Teams, or
- They are configured as Trusted Devices on the Pexip Service.
The Pexip Service also supports multiple Teams tenants under one company. This means that...
- all registered VTCs (with Pexip's Endpoint subscription), or
- any VTCs that are not registered, but supported by the Trusted Devices feature
...under one company can bypass the lobby into multiple Teams tenants. Each Teams tenant must be set up according to the instructions described here.
Note that all tenants require separate domains, i.e. one Teams tenant per single custom domain.
Participants using a Teams client join a Teams meeting as usual, and any gatewayed third-party participants can be seen and heard in the same way as any other directly-connected Teams clients in that meeting.
Authenticated, trusted VTCs that are located within the organization can join the conference directly, without any additional user interaction, whereas unauthenticated, untrusted external VTCs are admitted via the Teams lobby.
By default, the standard 1+7 layout is used for VTCs connecting to Teams meetings. However, you can choose to use any one of the following layouts:
- Standard 1+7 layout — the default
- Full-screen main speaker only (1 + 0 layout)
- 4 main speakers (2 x 2 layout)
Please contact your account manager at your local certified Pexip Partner if you would like to request a different layout.
When an untrusted guest enters the MS Teams lobby, VTC users hear the usual Teams lobby notification and see an onscreen message with an indication of how many guests are waiting in the lobby. They can then go to the Teams client and admit the waiting guests. If only some guests are admitted, the endpoint's display refreshes the count of waiting users.
If all guests are admitted, the endpoint's display briefly shows a confirmation message.
When using Pexip's integration with Teams:
- Content sharing is supported between Teams clients (via VbSS) and gatewayed participants. Note that a Teams client can only share its desktop or a window with a VTC system; PowerPoint file and whiteboard sharing is not currently supported.
- Pexip provides the participant's display name if it is provided by the participant's device. This is independent of whether the device is trusted or not. If a display name is not provided, Pexip uses the device's SIP URI. Note that many devices use the system name as its display name. However, some older systems might choose, for example, to only provide the first part of the SIP URI (the part before the '@') as the display name.
Teams users who are logged in and have joined via audio-only are represented by an avatar (supplied by Exchange Online) within the VTC's conference layout. If no avatar is available, or it is a guest user from another organization, a substitute graphic is generated based on the participant’s initials.
Teams users joining with PSTN audio (callback and manual dial-in):
- If a Teams user chooses to get a callback from the meeting to their PSTN device (instead of using computer audio) the user appears in the Pexip layout as a video participant and also as an audio-only participant with the avatar of that user. However, the video participant does not get voice-switched into main view when they speak.
- If a Teams user selects "manual dial-in" they appear in the Pexip layout as an audio-only participant without that user's avatar as that audio participant has no association with the Teams user (and is also separate from any video connection).
- If the Teams conference is recorded, recording indicators are included in the video stream sent to gatewayed participants.
- Teams clients cannot mute any VTC endpoints that are gatewayed into the meeting.
For more information on setting up your integration, see:
For more information about joining Microsoft Teams meetings, see: