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.
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 email@example.com and direct dialing into the Teams meeting is via <ConferenceID>@customdomain.com.
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.
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.
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.
For more information on setting up your integration, see:
For more information about joining Microsoft Teams meetings, see: