547
edits
RTP statistics: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The RTP statistics shows the complete list of all RTP traffic and a distribution of the used codecs. | The RTP statistics shows the complete list of all RTP traffic and a distribution of the used codecs. | ||
=== Meaning of measured values === | |||
* Packet loss: This is the number of RTP packets that have not been seen, according to the RTP sequence counter. | |||
* Double packet: The number of duplicate packets for which the RTP sequence counter is identical. | |||
* Jitter: This value models the difference of seen arrival time vs. expected arrival time based on the RTP timestamp. It is calculated according to the RTP RFC 3550. | |||
* Jitter buffer exceeded: | |||
* Packet time delta: The is the arrival time delta value between two consecutive packets. Large value does not necessarily indicate a problem as there could be a silence or no video changes. In other cases, like constant video or audio streams, large values might indicate network delays. | |||
* Clock skew: | |||
* Max video frame duration: | |||
==== '''IP addresses''' ==== | |||
This tab provides an overview of all IP addresses with RTP traffic. | This tab provides an overview of all IP addresses with RTP traffic. | ||
[[File:RTP dashboard.png|thumb|RTP overview]] | [[File:RTP dashboard.png|thumb|RTP overview]] | ||
For each IP traffic counters are displayed for receive and transmit direction of that IP. Packet loss counters, jitter and packet time delta | For each IP traffic counters are displayed for receive and transmit direction of that IP. Packet loss counters, jitter and packet time delta are also shown. | ||
are also shown. | |||
The graph column shows the history graphs of the traffic, lost and overhead packets as well as the jitter and packet time delta over time | The graph column shows the history graphs of the traffic, lost and overhead packets as well as the jitter and packet time delta over time for both receive and transmit directions. Also, in firmware 4.0, the clock skew and video frame duration can be selected as a graph view. | ||
for both receive and transmit directions. | |||
By clicking on an IP address, the RTP statistics tab of the IP detail page is shown. | By clicking on an IP address, the RTP statistics tab of the IP detail page is shown. | ||
==== IP groups ==== | |||
This tab shows similar information as the IP addresses tab, but for IP groups instead. | |||
'''RTP connections''' | ==== '''RTP connections''' ==== | ||
This tab shows statistics (if available) of all RTP connections. | This tab shows statistics (if available) of all RTP connections. | ||
| Line 30: | Line 39: | ||
*G.729 | *G.729 | ||
==== '''RTP codecs''' ==== | |||
'''RTP codecs''' | |||
The RTP codecs tab shows the distribution of the used codecs. | The RTP codecs tab shows the distribution of the used codecs. | ||
| Line 51: | Line 58: | ||
:To stop capture, click on the same button again (which turned to a STOP symbol), or go to the capture traffic. | :To stop capture, click on the same button again (which turned to a STOP symbol), or go to the capture traffic. | ||
==== '''RTP overall quality''' ==== | |||
'''RTP overall quality''' | |||
The RTP overall quality tab provides graphs about the jitter and packet loss. | The RTP overall quality tab provides graphs about the jitter and packet loss. | ||
| Line 63: | Line 68: | ||
If, for a given RTP flow, 40 packets were received, but the last sequence number (relative to the start of the flow) is 50, 10 packets were lost. This means there is a packet loss of 20%. | If, for a given RTP flow, 40 packets were received, but the last sequence number (relative to the start of the flow) is 50, 10 packets were lost. This means there is a packet loss of 20%. | ||
==== '''Incidents''' ==== | |||
'''Incidents''' | |||
The incidents tab allows to configure and display custom events. | The incidents tab allows to configure and display custom events. | ||
Configuration is done on a separate page, which can be accessed by clicking on the Configure incidents button. | Configuration is done on a separate page, which can be accessed by clicking on the Configure incidents button. | ||
A list of already triggered incidents is shown in a table, providing information on severity of the incident, the time of first occurrence and the reason for triggering. Filters can be used to show only incidents of certain severity levels (low, medium, high) or incident trigger type. | A list of already triggered incidents is shown in a table, providing information on severity of the incident, the time of first occurrence and the reason for triggering. Filters can be used to show only incidents of certain severity levels (low, medium, high) or incident trigger type. | ||