Viewing current conference status
To see a list of all the conferences currently in progress, go to
.To view historical information on conferences after they have finished, see Viewing historical information about conferences.
The pages showing conference status information do not refresh automatically — you must refresh them manually. A "Conference instance no longer active" message indicates that the conference whose details you were viewing has now finished.
Each conference has the following information available:
Field | Description |
---|---|
Service name | The name of the Virtual Meeting Room, Virtual Auditorium, Virtual Reception or Gateway Routing Rule being used. For the Pexip Distributed Gateway, the rule name is followed by a unique identifier to distinguish between separate calls. |
Duration |
For Virtual Meeting Rooms and Virtual Auditoriums: the length of time since the first participant joined the conference. For Virtual Receptions: the length of time that this instance of the service has been in continuous use (note that this could involve more than one participant if their usage overlapped). For Pexip Distributed Gateway: the length of time since the call was received by the Pexip Distributed Gateway. |
Participant count | The number of participants currently in the conference or using the service. |
Service tag * | The unique identifier that an administrator has assigned to this service. If this field is blank, no tag has been assigned. For more information, see Tracking usage with a service tag. |
Is locked * | Indicates whether a conference has been locked to prevent further participants from joining. For more information, see Locking a conference and allowing participants to join a locked conference. |
* Only displayed when you have selected an individual conference to view. |
To view more information about the conference, click on the service name. You will then see 3 tabs for the selected conference: Participants, Backplanes and Graph.
Participants
The
section lists all the participants that are currently in the conference.For more details about a particular participant, including media stream statistics, click on the Participant alias. This will take you to the Participant details page.
Field | Description |
---|---|
Participant alias |
The URI of the endpoint used to join the conference or access the service. Note that Infinity Connect participants are identified as Infinity_Connect_<endpoint_IPaddress>. The alias is appended with _via_<reverse_proxy_IPaddress> if the client has connected via a reverse proxy. |
Duration | 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. |
System location | The system location of the Conferencing Node to which the endpoint is connected. |
Signaling node | The IP address of the Conferencing Node to which the endpoint is connected. This Conferencing Node will be handling the call signaling but may or may not be handling the media (for more information, see Handling of media and signaling in locally distributed conferences). |
Media node | The IP address of the Conferencing Node that is handling the call media for this endpoint (for more information, see Handling of media and signaling in locally distributed conferences). |
Role |
Host indicates that either:
Guest indicates that the participant accessed the conference using the Guest PIN. Unknown indicates that either:
For more information, see About PINs, Hosts and Guests. |
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). |
On hold | Indicates whether the endpoint has been put on hold (usually by the endpoint user). |
Streaming or recording device | Indicates if the participant is a streaming or recording device. |
Backplanes
The Conferencing Nodes for the selected conference. Backplane links are unidirectional, so for a conference involving two Conferencing Nodes there will be two backplane links: one from node A to node B, and another from node B to node A.
section provides information about the media streams being transmitted betweenField | Description |
---|---|
Media node |
The IP address of the Conferencing Node that is transmitting media. For details about the media streams being sent over a particular backplane link, click on the Media node's IP address. |
Remote media node |
The IP address of the Conferencing Node that is receiving media. Note that the remote media node of a merged AVMCU conference is identified by the address of the Lync client that initiated the AVMCU conference. |
System location * | The system location of the Conferencing Node that is transmitting media. |
Duration | The length of time since the connection was established. |
Type |
Geographic indicates that the two Conferencing Nodes are in different system locations. Local indicates that the two Conferencing Nodes are in the same system location. |
* Only displayed when you have selected an individual media node to view. |
Backplane media streams
Media stream details are displayed when you have selected an individual node to view.
Field | Description |
---|---|
Type | Indicates whether the information is for an Audio, Video, or Presentation stream. |
Tx codec | The format used by the transmitting Conferencing Node to encode and decode the media stream being transmitted. |
Tx bitrate (kbps) | The quantity of data currently being sent from the transmitting Conferencing Node to the recipient Conferencing Node for this particular media stream. |
Tx resolution | The display resolution of the image being sent from the transmitting Conferencing Node. |
Tx packets sent | The total quantity of packets sent from the transmitting Conferencing Node to the recipient Conferencing Node since the start of the conference. |
Tx packets lost | The total quantity of packets sent from the transmitting Conferencing Node but not received by the recipient Conferencing Node. |
Tx jitter (ms) | The variation in the expected periodic arrival of packets being sent from the transmitting Conferencing Node to the recipient Conferencing Node, in milliseconds. |
Rx jitter (ms) | The variation in the expected periodic arrival of packets being received by the recipient Conferencing Node, in milliseconds. |
Graph
This section displays a graphical view of the media connections for this conference, showing:
- all endpoints (as blue dots)
- the Conferencing Nodes to which they are connected (as orange dots)
- the backplane links between Conferencing Nodes (as orange lines)
- any connections with packet loss > 1% as dashed lines
- any connections with packet loss > 2% as red dashed lines.
To view details of a particular participant, double-click on the participant node.