Viewing Teams Connector instance, call and participant status
You can view Teams Connector instance, call and participant status via the Pexip Infinity Administrator interface:
For general troubleshooting, call failures and installation issues, see Troubleshooting Microsoft Teams and Pexip Infinity integrations.
Viewing the status of Teams Connector instances
You can view the status of each Teams Connector instance, such as call capacity and current media load, via the Pexip Infinity Administrator interface ( ).
The instances are represented by icons. Each purple square represents a Teams Connector instance and the fill level of the square represents the current media load. A filled square in lighter purple represents an instance that is draining.
More details are shown when hovering over an instance, and you can double-click on an instance to see more detailed information about it.
The instance status could be:
- Active: the instance is operating normally.
- Waiting for termination: waiting for calls to clear so that the instance can be terminated.
- Terminating: there are no calls and the instance is terminating right now.
- Maintenance: the instance is not currently operational (e.g. it is restarting or being reconfigured).
- Failure: occurs when the instance had been in Maintenance status longer than expected. Typically this means that the instance is continually failing to restart.
You can also view a list of all deployed Teams Connector instances via . This provides a summary of information including each node's name, IP address, maximum call capacity, current media load and the date/time of start-up and last update.
Note that the instance status information is only displayed if you have enabled the Azure Event Hub (Configuring your Teams Connector addresses for more information). If the Azure Event Hub is not enabled then only displays Teams Connector instances when a Teams call is in progress.— see
Monitoring calls placed into Teams conferences
When using the Pexip Infinity Administrator interface to monitor calls that are placed into Teams conferences, you should note that:
- Each participant who is gatewayed into a Teams conference is listed as a separate gateway call. However, if multiple participants are connected to the same Teams conference, the Live View (Call Routing Rule. ) shows them as connected to the same external conference — which is identified as "Teams meeting <conference ID>". The name/label shown for each call is based on the name of the associated
When viewing the status of the gateway call (), the tab also lists the other participants in the conference. The format of their alias indicates the type of participant:
- <name>@<domain> (email address) is used for any Teams clients in the call
- trusted:<id> represents another gatewayed participant who joined as a trusted participant
- guest:<id> represents another gatewayed participant who joined as an untrusted participant
These other participants do not have any associated media stream information.
Note that only the gatewayed participant is shown as consuming a port license. The outbound leg of the gateway call (into the Teams Connector), which consumes the second license of each gateway call, is not represented in the participant list.
The media streams associated with the call into the Teams meeting are shown against the conference backplane:
- There is one audio stream and multiple video streams. You also see a presentation stream if any participant is sharing content.
- Multiple video streams are set up to receive video from the Teams Connector to support the Pexip conference layout seen by gatewayed participants; if there are fewer participants than streams then the currently unused streams are shown as "Off stage".
- Pexip Infinity may simultaneously send up to 4 video streams and 4 presentation streams at different resolutions and frame rates to the Teams Connector, as requested by Teams.
- You cannot disconnect or transfer any of the other participants connected to the Teams conference.