Viewing participant status
To see a list of all the current conference participants across all Pexip Infinity services, go to . This shows a list of all participants; to view a particular participant's details, click on the Participant alias.
When viewing a participant's details you can also use the controls at the bottom of the page to:
- the participant
- the participant from the conference
- the participant to another conference
Note that when viewing participants in a gateway call, these controls cannot be used on any remote participants that are connected to an externally-hosted conference.
To view historical information on participants after a conference has finished, see Viewing historical information about participants.
The following table lists the information shown for each participant. Note that some information, such as the Call ID, is not always available for participants who are directly connected to an externally-hosted conference, such as a Microsoft Teams or Skype for Business meeting, or Google Hangouts Meet.
|Perceived call quality
A graphical representation of the participant's call quality over time.
A blue line at the top of the graph indicates Good, down to a red line at the bottom which indicates Terrible. The percentage number indicates the amount of the call where the quality is perceived as Good or OK (above the line in blue). For example:
Note that call quality is not reported for calls made over RTMP.
See media statistics and perceived call quality for more information.
The name of the user or the registered alias of the endpoint.
Click on the participant alias to view detailed information about the call.
The name of the Virtual Meeting Room, Virtual Auditorium, Virtual Reception, Test Call Service or Call Routing Rule. For Pexip Distributed Gateway calls, the rule name is followed by a unique identifier to distinguish between separate calls.
Selectto view the current status of the conference.
The current quality of the call based on packet loss and jitter over the 3 most recent 20 second time windows.
See media statistics and perceived call quality for more information.
||The date and time that signaling was established between the participant's endpoint and Pexip Infinity.|
The length of time since this participant joined the conference or accessed the service.
|Display name||The name that has been configured on the participant's endpoint.|
For participants that have dialed in to the conference or service themselves, this is the alias that they dialed.
|System location||The system location of the Conferencing Node to which the endpoint is connected. However, when the participant is connected to a Proxying Edge Node, this is the location of the Transcoding Conferencing Node that is processing the conference media for this participant.|
|Proxying system location
The system location of the Proxying Edge Node that is handling the call, if applicable.
|Signaling node||The IP address and name of the Conferencing Node to which the endpoint is connected. This node is handling the call signaling but may or may not be handling the call media (for more information, see Handling of media and signaling in locally distributed conferences).|
|Media node||The IP address and name of the Transcoding Conferencing Node that is processing the call media for this participant (for more information, see Handling of media and signaling in locally distributed conferences).|
|Media proxying node
||The IP address and name of the Proxying Edge Node that is proxying the call media for this participant, if applicable.|
Virtual Meeting Room, Virtual Auditorium, Virtual Reception, Test Call Service or Gateway: the participant has successfully accessed the service indicated.
PIN collection IVR: the participant is currently accessing the Interactive Voice Response screens (where they are asked to enter a valid PIN).
Waiting for Host: the participant is being shown a holding screen while they wait for a conference Host to join.
Insufficient Capacity Screen: the participant is being shown a holding screen indicating that they cannot join the conference due to a lack of capacity on Pexip Infinity, or because the service's participant limit has been reached.
Insufficient Licenses Screen: the participant is being shown a holding screen indicating that they cannot join the conference due to a lack of available call licenses on Pexip Infinity. For more information, see Insufficient licenses.
Invalid License Screen: the participant is being shown a holding screen indicating that they cannot join the conference because there are no valid licenses available on Pexip Infinity. For more information, see Invalid license.
|Protocol||The communication protocol used by the endpoint.|
Host indicates that either:
Guest indicates that the participant accessed the conference using the Guest PIN.
Unknown indicates one of the following:
For more information, see About PINs, Hosts and Guests.
The number of licenses consumed by this participant. Media participants consume 1 license but API-only participants (e.g. Infinity Connect users who are not sending media) do not consume a license.
Participants who are directly connected to an externally-hosted conference, such as a Microsoft Teams or Skype for Business meeting, or Google Hangouts Meet, do not consume a license.
The type of license used, either:
|Is presentation stream supported
||Indicates whether the endpoint is able to support a separate media stream for presentations negotiated by H.239 or BFCP.|
|Is presenting||Indicates whether the endpoint is currently sending a presentation stream.|
|Is muted||Indicates whether the endpoint's audio has been muted (using an Infinity Connect client, the Administrator interface, or by a third party using the Pexip API).|
||Indicates whether the endpoint has been put on hold (usually by the endpoint user).|
In: the call was placed by an external endpoint and received by Pexip Infinity.
Out: the call was placed by Pexip Infinity to an endpoint or other device.
||The maximum bandwidth, in kbps, negotiated for use between the Conferencing Node and the endpoint. Actual bandwidth used is shown in the Media streams section (Tx bitrate and Rx bitrate).|
|Streaming or recording device
||Indicates if the participant is a streaming or recording device.|
||Indicates whether the media stream being sent to and from the Conferencing Node towards the endpoint is encrypted.|
||Information about the endpoint's manufacturer and software.|
|Remote IP address
||The IP address of the system from which signaling from this endpoint is being sent and received. This may be the endpoint itself, or it may be a call control system if one is in use in your network.|
||The port on the system from which signaling from this endpoint is being sent and received.|
Selectto see a filtered view of the support log showing only events containing this Call ID.
Selectto see a condensed view of the call signaling messages in the support log for this Call ID.
Calls made via the Virtual Reception generate two separate participant calls but these both have the same Call ID.
|Is disconnect / transfer / mute supported
||Indicates whether the participant can be disconnected, transferred or muted via the Management Node.|
Media stream details are displayed when you view the details of an individual participant. Note that media streams are not displayed for any participants who are directly connected to an externally-hosted conference, such as a Microsoft Teams or Skype for Business meeting, or Google Hangouts Meet.
Indicates whether the information is for the Audio, Video, or Presentation stream.
When viewing the stream details of a completed VMR call you may see multiple instances of each stream type (for example, if the participant had started presenting, stopped and then started presenting again). For in-progress VMR calls you only see a maximum of one instance of each stream type (reflecting what the participant is currently doing).
In gateway calls to an externally-hosted conference you may see a separate stream for every resolution/framerate being sent.
Note that a presentation stream is not shown for Infinity Connect clients that are sending or receiving still images or PDF pages (as opposed to screen sharing, or receiving full motion presentation).
|Start time||The date and time that the media stream started.|
|Node||The address of the Transcoding Conferencing Node handling the media.|
|Tx codec||The format used by the Conferencing Node to encode the media stream being sent to the endpoint.|
|Tx bitrate (kbps)||The quantity of data currently being sent from the Conferencing Node to the endpoint, in kilobits per second.|
|Tx resolution||The display resolution of the image being sent from the Conferencing Node.|
|Tx framerate||The video framerate per second being sent from the Conferencing Node.|
|Tx packets sent||The total quantity of packets sent from the Conferencing Node to the endpoint since the start of the conference.|
|Tx packets lost||
The total quantity of packets sent from the Conferencing Node but not received by the endpoint.
This value is reported to the Conferencing Node by the endpoint. Endpoints that do not support RTCP are not able to supply this information, so the value will always be 0.
|Tx jitter (ms)||
The variation in the expected periodic arrival of packets being sent from the Conferencing Node to the endpoint, in milliseconds.
This value is reported to the Conferencing Node by the endpoint. Endpoints that do not support RTCP cannot supply this information, so the value will always be 0.
The format used by the Conferencing Node to decode the media stream being sent from the endpoint.
Off indicates that no decodable media for this stream has been received in the last 10 seconds or so from the codec. For example, for an Infinity Connect client being used for presentation and control-only, there will be no video transmitted.
Off stage indicates that the participant is currently not being shown in the main video or thumbnails, so Pexip Infinity is not attempting to decode the media stream.
Telephone event may be displayed if an audio codec that use silence suppression (such as G729B) is muted and sends DTMF.
If this field is blank, this may mean that Pexip Infinity has negotiated which codec to use but it is yet to receive any media from the endpoint to determine which codec it is actually sending.
|Rx bitrate (kbps)||The quantity of data currently being received by the Conferencing Node from the endpoint, in kilobits per second.|
|Rx resolution||The display resolution of the image being received by the Conferencing Node.|
|Rx framerate||The video framerate per second being received by the Conferencing Node. This can fluctuate over time as it is measured by the Conferencing Node.|
|Rx packets received||The total quantity of packets received by the Conferencing Node from the endpoint since the start of the conference.|
|Rx packets lost||The total quantity of packets sent from the endpoint but not received by the Conferencing Node.|
|Rx jitter (ms)||The variation in the expected periodic arrival of packets being received by the Conferencing Node from the endpoint, in milliseconds.|