Tech Docs

Viewing historical information about conferences

To see a list of all the completed conferences on the Pexip Infinity platform, go to Status > Conference history. This shows a list of the most recent completed conferences (up to a limit of 10,000). To view details of a particular conference, including the ability to rewind and replay the conference graph, click on the Service name.

To view information on conferences currently running on Pexip Infinity, see Viewing current conference status.

The Administrator interface uses color coding when reporting media statistics, such as perceived call quality, packet loss and jitter. In general, statistics that are shown in green represent good quality, orange represents intermediate quality, and red is used for bad quality. See media statistics and perceived call quality for more information.

The following information is available for each completed conference:

Field Description
Service name

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.

For Virtual Receptions and Test Call Services, if there were multiple concurrent users of that service you will see a single instance of that service (rather than one instance per participant, as all participants are using the same service even though they cannot see or hear each other).

Click on the service name to view more information.

Start time The date and time that the first participant connected to the service.
End time The date and time that the last participant's call ended.
Duration

The length of time that the conference or service was in use.

Participant count

The total number of participant calls made to this conference. Note that if a single participant disconnects from the conference and then reconnects to it, this will be counted as two participant calls.

Service type * The type of conference, e.g. Virtual Meeting Room.
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.
Instant message count * The total number of instant messages sent during the 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 were in the conference.

For more details about a particular participant, including media stream statistics, click on the Participant alias. This takes you to the Participant history page.

Field Description
Participant alias

The name of the user or the registered alias of the endpoint.

Start time The date and time that the participant's call reached Pexip Infinity.
End time The date and time that the participant's call ended.
Duration

The length of time that the participant was connected to Pexip Infinity. This includes time connected to the Virtual Meeting Room or Virtual Auditorium, and any time spent at the Virtual Reception or PIN entry screens.

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. 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.
Role

Host indicates that either:

  • the conference had no PINs configured (in which case all participants had 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 one of the following:

  • the participant reached the Virtual Reception but did not proceed to a Virtual Meeting Room or Virtual Auditorium
  • the participant reached the PIN entry screen but did not successfully enter a PIN
  • the call was via the Pexip Distributed Gateway.

For more information, see About PINs, Hosts and Guests.

Backplanes

The Backplanes section provides information about the media streams being transmitted between Transcoding Conferencing Nodes for the selected conference. Backplane links are unidirectional, so for a conference involving two transcoding 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 SfB/Lync meeting is identified by the address of the SfB/Lync client that initiated the SfB/Lync meeting.

System location * The system location of the Conferencing Node that is transmitting media.
Start time The date and time that the connection was established.
End time The date and time that the connection was brought down.
Backplane 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.

External indicates a link between a Conferencing Node and an external node, such as a Skype for Business / Lync meeting.

* 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.
Start time The time that the media stream started.
End time The time that the media stream ended.
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.

Graph

This section displays a dynamic graphical view of the connections for this conference, as described below.

Initially the graph shows the midpoint state of the conference. You can use the interactive timeline and controls to go forwards or backwards to replay the graph and review the entire conference.

You can use the timeline controls at the bottom of the graph to rewind and replay the graph at a variety of speeds. When viewing or replaying the graph you can:

  • See when participants and Conferencing Nodes joined or disconnected from the conference.
  • See when participants started and stopped presenting.
  • View participant packet loss statistics during the conference by hovering over a connection.
  • View summary details of individual participants, such as the protocol they are using and their bandwidth usage, by hovering over a participant. You can double-click on a participant to see more information.
  • View summary details of individual nodes, such as its media load or any alarms, by hovering over a node. You can double-click on a node to see more information.
  • Click within the graph to use your mouse to pan and zoom.

(See Rewinding and replaying status for more information about how to use the controls.)

Conference statistics and issues: the number of Conferencing Nodes and participants that are involved in the conference is displayed at the top left of the graph.

If any participants are experiencing call quality issues then the number of affected participants is also displayed (in orange). You can click on this number to reveal the affected participants and also drill down to view more details about each of those participants.

Colored areas: each colored area highlights a system location and shows the Conferencing Nodes and endpoint connections within that location. A different color is used for each location.

Small dark blue dots: all participant endpoints. Some may have an icon next to their name, as follows:

You can hover over an endpoint to view participant information.


Large green circles: the Transcoding Conferencing Nodes to which the endpoints are connected, or are processing conference media. The amount of green fill within the circle indicates the current media load (in terms of percentage of estimated HD ports in use), so an unused node is white and a fully loaded node is filled entirely green.


Large blue circles: the Proxying Edge Nodes to which the endpoints are connected. The amount of green fill within the circle indicates the current media load (in terms of percentage of proxying capacity in use), so an unused node is white and a fully loaded node is filled entirely green.
Large pale blue circles: an externally-hosted conference, such as Google Hangouts Meet or a Skype for Business / Lync meeting.
Green lines: backplane links between Conferencing Nodes, or links to external nodes. These become dashed green lines if total packet loss is greater than 1%.
Gray lines: connections between an endpoint and a Conferencing Node. These become dashed gray lines if total packet loss is greater than 1%.
Red dashed lines: any connections with total packet loss greater than 2%.
Blue lines: a media-forwarding link between a Proxying Edge Node and a Transcoding Conferencing Node. Only one link is shown regardless of how many connections/streams are being proxied. Packet loss information is not available on media-forwarding links.
Padlock: a padlock in the top right of the screen indicates that the conference is locked.