Displaying statistics for a participant

The audio codec in use, along with the current packet size (in milliseconds) if known.

If the MCU has received information that an endpoint has been muted at the far end, this will be indicated here.

The IP address and port from which the media is originating.

Whether or not encryption is being used on the audio receive stream by this endpoint.

This field will only appear if the encryption feature key is present on the MCU.

The apparent variation in arrival time from that expected for the media packets (in milliseconds). The current jitter buffer also displays in parentheses.

You should expect to see small values for this setting. Consistently large numbers typically imply potential network problems.

The jitter buffer shows the current playout delay added to the media to accommodate the packet arrival jitter. Large jitter values indicate a longer buffer.

Represents the audio volume originating from the endpoint.

The number of audio packets destined for the MCU from this endpoint.

The number of packet errors, including sequence errors, and packets of the wrong type.

You should expect to see small values for this setting. Consistently large numbers typically imply potential network problems.

Frame errors, as A/B where A is the number of frame errors, and B is the total number of frames received.

A frame is a unit of audio, the size of which is dependent on codec.

You should expect to see small values for this setting. Consistently large numbers typically imply potential network problems.

If the time stamps or marker bits (or both) are detected to be unreliable in the incoming video stream, information will be displayed here.

This field is not displayed when there is no problem with the time stamps and marker bits. Where there is a problem the following text is displayed: "Media timestamps unreliable", "Media marker bits unreliable", or both if both conditions detected.

The audio codec being sent from the MCU to the endpoint, along with the chosen packet size in milliseconds.

The IP address and port to which the media is being sent.

Whether or not encryption is being used on the audio transmit stream by this endpoint.

This field will only appear if the encryption key is present on the MCU.

A count of the number of packets that have been sent from the MCU to the endpoint.

The IP address and port to which RTCP (Real Time Control Protocol) packets are being sent for the audio and video streams.

A count of the number of "receiver report" type RTCP packets seen by the MCU.

A single RTCP packet may contain more than one report of more than one type. These are generally sent by any device receiving RTP (Real Time Protocol) media from the network and are used for auditing bandwidth, errors, and so on by the MCU.

A count of the reported packet loss on the control channel.

A count of the number of "sender report" type RTCP packets sent by the MCU.

These are typically sent by any device that is sending RTP media.

The IP address and port to which the MCU is sending RTCP packets about this stream.

A count of the number of "receiver report" type RTCP packets seen by the MCU.

A single RTCP packet may contain more than one report of more than one type. These are generally sent by any device receiving RTP (Real Time Protocol) media from the network and are used for auditing bandwidth, errors, and so on by the MCU.

A count of the number of "sender report" type RTCP packets received by the MCU.

These are typically sent by any device that is sending RTP media.

A count of the number of packets that have been sent from the MCU to the endpoint.

The codec in use and the size of the picture that the MCU is receiving from the specific participant. If the picture is a standard size (for example, CIF, QCIF, 4CIF, SIF) then this name is shown in parentheses afterwards.

If ClearVision is enabled on the Settings > Conferences page, and if it is in use on this video stream, then the original and enhanced resolutions are both displayed here.

The IP address and port (<IP address>:<port>) of the device from which video is being sent

Whether or not encryption is being used on the video receive stream from this endpoint.

This field will only appear if the encryption key is present on the MCU.

The negotiated bit rate available for the endpoint to send video in.

This value represents the maximum amount of video traffic that the remote endpoint will send to the MCU. It may send less data than this (if it does not need to use the full channel bit rate or the MCU has requested a lower rate), but it should not send more.

The bit rate (in bits per second) that the MCU has requested that the remote endpoint sends. The most-recently measured actual bit rate displays in parentheses.

This value might be less than the Channel bit rate if:

• the MCU detects that the network path to the remote endpoint has insufficient capacity to maintain a higher traffic rate
• that endpoint's video stream's position in the active conference compositions does not require it
• it has been necessary to reduce the video bit rate because of the overall call bit rate; the audio bit rate plus the video bit rate should not exceed the call bit rate

For example, if all participants in the conference were watching a single participant at full screen, no other participants' video streams would be needed at all. So the MCU would request that those streams were sent at a low bit rate in order to avoid needless use of network bandwidth.

If the receive bit rate has been limited to below the maximum channel bit rate, the reason for this limitation can be seen by moving over the icon.

Represents the variation in video packet at arrival time at the MCU.

The number of milliseconds by which the video follows the audio. Some endpoints send audio and video out-of-sync. The MCU ensures audio and video are played together.

The number of video packets destined for the MCU from this endpoint

Video packet-level errors such as sequence discontinuities, incorrect RTP details, and so on. This is not the same as packets where the content (the actual video data) is somehow in error.

This value does not represent packets in which the actual video data in the packets is in error.

The frame rate of the video stream currently being received from the endpoint.

The number of frames with errors versus the total number of video frames received.

The codec, size and type of video being sent from the MCU to the endpoint.

The IP address and port of the device to which the MCU is sending video.

Whether or not encryption is being used on the video transmit stream to this endpoint.

This field will only appear if the encryption key is present on the MCU.

The negotiated available bandwidth for the MCU to send video to the endpoint in.

The bit rate the MCU is attempting to send at this moment, which may be less than the channel bit rate which is an effective maximum. The actual bit rate, which is simply the measured rate of video data leaving the MCU, displays in parentheses.

The Transmit bit rate value might be less than the Channel bit rate if :

• the remote endpoint receiving the video stream from the MCU has sent flow control commands to reduce the bit rate
• it has been necessary to reduce the primary video bit rate to allow sufficient bandwidth for a content video stream

If the transmit bit rate has been limited to below the maximum channel bit rate, the reason for this limitation can be seen by moving over the icon.

The number of video packets sent from the MCU to this endpoint.

The frame rate of the video stream currently being sent to the endpoint.

A number that represents the tradeoff between video quality and frame rate.

A smaller number implies that the MCU prioritizes sending quality video at the expense of a lower frame rate. A larger number implies that the MCU is prepared to send lower quality video at a higher frame rate.

The IP address and port to which RTCP (Real Time Control Protocol) packets are being received for the audio and video streams

A count of the number of "receiver report" type RTCP packets seen by the MCU.

A single RTCP packet may contain more than one report of more than one type. These are generally sent by any device receiving RTP (Real Time Protocol) media from the network and are used for auditing bandwidth, errors, and so on by the MCU.

Media packet loss reported by receiver reports sent to the MCU by the far end.

A count of the number of "sender report" type RTCP packets received by the MCU.

These are typically sent by any device that is sending RTP media.

A count of the number of reports seen by the MCU that are neither sender nor receiver reports.

The IP address and port to which the MCU is sending RTCP packets about this stream.

The number of packets sent.

The IP address and port to which RTCP (Real Time Control Protocol) packets are being sent for the audio and video streams.

A count of the number of "receiver report" type RTCP packets seen by the MCU.

A single RTCP packet may contain more than one report of more than one type. These are generally sent by any device receiving RTP (Real Time Protocol) media from the network and are used for auditing bandwidth, errors, and so on by the MCU.

A count of the reported packet loss on the control channel.

A count of the number of "sender report" type RTCP packets sent by the MCU.

These are typically sent by any device that is sending RTP media.

A count of the number of reports seen by the MCU that are neither sender nor receiver reports.

The IP address and port to which the MCU is sending RTCP packets about this stream.

The number of packets sent.

The number of fast update requests sent and received.

The number of flow control messages sent and received.