Viewing current conference status

To see a list of all the conferences currently in progress, go to Status > Conferences.

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 Call Routing Rule being used. For Pexip Distributed Gateway calls, 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 calls: 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 Participants 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 name of the user or the registered alias of the endpoint.
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: the conference has no PINs configured (in which case all participants will have a role of Host) the participant accessed the conference using the Host PIN. Guest indicates that the participant accessed the conference using the Guest PIN. Unknown indicates that either: the participant is at the PIN entry screen and has not yet successfully entered a PIN the participant is connected via an AVMCU conference (these participants will appear in the Infinity Connect participant list with a role of External). 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 Backplanes section provides information about the media streams being transmitted between 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.

Field	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, as follows:

• blue dots: all endpoints (note that Infinity Connect control-only participants will not appear on this graph because they have not established a media connection)
• large orange dots: the Conferencing Nodes to which the endpoints are connected
• small orange dots: an external node (e.g. an AVMCU conference)
• green lines: backplane links between Conferencing Nodes. These will become dashed green lines if packet loss is greater than 1%
• gray lines: connections between an endpoint and a Conferencing Node. These will become dashed gray lines if packet loss is greater than 1%
• red dashed lines: any connections with packet loss greater than 2%.

Note that a Conferencing Node with (seemingly) no participants connected to it may appear in the graph. In such cases, the Conferencing Node will have one or more control-only participants connected but no media connections.

To view details of a particular participant, double-click on the participant node.

Example graph showing two Conferencing Nodes and nine participant endpoints, with packet loss between one endpoint and a node, and between the two nodes