RTP statistics: Difference between revisions
m (Typo fixes) |
(RTP connections: add screenshots) |
||
| Line 5: | Line 5: | ||
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]] | |||
For each IP traffic counters are displayed for receive and transmit direction of that IP. Packet loss counters and jitter | For each IP traffic counters are displayed for receive and transmit direction of that IP. Packet loss counters and jitter | ||
are also shown. | are also shown. | ||
| Line 14: | Line 17: | ||
'''RTP connections''' | '''RTP connections''' | ||
This tab shows statistics (if available) of all RTP connections. A list shows all connections with client and server IP addresses and ports. The RTP payload type is shown as well as timing information and counters, jitter and MOS values and SSRC (synchronization source) of both client and server. The min and max audio levels (decibel relative to full scale, dBFS) per direction are shown if G.711 A-Law or μ-Law is used. For calculation, raw A-Law or μ-Law values are converted to 16 bit PCM values. Those values are then converted to dbFS: | This tab shows statistics (if available) of all RTP connections. | ||
[[File:RTP_connections.png|thumb|RTP connections]] | |||
A list shows all connections with client and server IP addresses and ports. The RTP payload type is shown as well as timing information and counters, jitter and MOS values and SSRC (synchronization source) of both client and server. The min and max audio levels (decibel relative to full scale, dBFS) per direction are shown if G.711 A-Law or μ-Law is used. For calculation, raw A-Law or μ-Law values are converted to 16 bit PCM values. Those values are then converted to dbFS: | |||
value_dBFS = 20 * log10(abs(pcm_value) / 32768) | value_dBFS = 20 * log10(abs(pcm_value) / 32768) | ||
Values range from 0 dBFS (loudest) to -96 dBFS (absolute silence). | Values range from 0 dBFS (loudest) to -96 dBFS (absolute silence). | ||
Graphs per connection can show packets, packet loss and packet duplication, bit rate, jitter, MOS and the max audio level of client and server over time. A PCAP button allows for PCAP capturing. If a proper codec is used, audio capture buttons for both directions are available allowing downloads in MP3 format. Following codecs are supported for audio extraction: | Graphs per connection can show packets, packet loss and packet duplication, bit rate, jitter, MOS and the max audio level of client and server over time. A PCAP button allows for PCAP capturing. If a proper codec is used, audio capture buttons for both directions are available allowing downloads in MP3 format. Following codecs are supported for audio extraction: | ||
* G.711 A-Law and μ-Law | *G.711 A-Law and μ-Law | ||
* G.722 | *G.722 | ||
* G.729 | *G.729 | ||
| Line 27: | Line 34: | ||
The RTP codecs tab shows the distribution of the used codecs. | The RTP codecs tab shows the distribution of the used codecs. | ||
[[File:RTP_codecs.png|thumb|RTP codecs]] | |||
For each codec, the table contains the following information: | For each codec, the table contains the following information: | ||
* Codec | *Codec | ||
:The Codec name describes the format of the RTP payload. | :The Codec name describes the format of the RTP payload. | ||
* Packets and Bytes | *Packets and Bytes | ||
:This is the number of packets and bytes for that codec. It includes both sent and received bytes. | :This is the number of packets and bytes for that codec. It includes both sent and received bytes. | ||
* Packets/s and Bits/s | *Packets/s and Bits/s | ||
:These both numbers describe the current throughput for that codec. | :These both numbers describe the current throughput for that codec. | ||
* Graph | *Graph | ||
:The graph column shows the history graph of the traffic for that codec. It shows the timestamp on the x-axis and the bytes on the y-axis. The resolution can be changed by using the control buttons on the top of the web page. | :The graph column shows the history graph of the traffic for that codec. It shows the timestamp on the x-axis and the bytes on the y-axis. The resolution can be changed by using the control buttons on the top of the web page. | ||
* PCAP | *PCAP | ||
:It is possible to download the traffic for that codec by clicking on the download button. | :It is possible to download the traffic for that codec by clicking on the download button. | ||
:The captured packets are not stored on the system but they are directly sent over the HTTP connection to your computer. | : The captured packets are not stored on the system but they are directly sent over the HTTP connection to your computer. | ||
: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. | ||
| Line 45: | Line 55: | ||
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. | ||
[[File:RTP_quality.png|thumb|RTP overall quality]] | |||
There one graph for the overall jitter and packet loss. Additionally, there is a separate graph per network interface. | There one graph for the overall jitter and packet loss. Additionally, there is a separate graph per network interface. | ||
The jitter is calculated according to RFC 3550 Appendix A.8 (https://tools.ietf.org/html/rfc3550#appendix-A.8). | The jitter is calculated according to RFC 3550 Appendix A.8 (https://tools.ietf.org/html/rfc3550#appendix-A.8). | ||
Revision as of 13:01, 3 February 2022
The RTP statistics shows the complete list of all RTP traffic and a distribution of the used codecs.
RTP overview
This tab provides an overview of all IP addresses with RTP traffic.
For each IP traffic counters are displayed for receive and transmit direction of that IP. Packet loss counters and jitter are also shown. The graph column shows the history graphs of the traffic, lost and overhead packets as well as the jitter over time for both receive and transmit directions. By clicking on an IP address, the RTP statistics tab of the IP detail page is shown.
RTP connections
This tab shows statistics (if available) of all RTP connections.
A list shows all connections with client and server IP addresses and ports. The RTP payload type is shown as well as timing information and counters, jitter and MOS values and SSRC (synchronization source) of both client and server. The min and max audio levels (decibel relative to full scale, dBFS) per direction are shown if G.711 A-Law or μ-Law is used. For calculation, raw A-Law or μ-Law values are converted to 16 bit PCM values. Those values are then converted to dbFS:
value_dBFS = 20 * log10(abs(pcm_value) / 32768) Values range from 0 dBFS (loudest) to -96 dBFS (absolute silence).
Graphs per connection can show packets, packet loss and packet duplication, bit rate, jitter, MOS and the max audio level of client and server over time. A PCAP button allows for PCAP capturing. If a proper codec is used, audio capture buttons for both directions are available allowing downloads in MP3 format. Following codecs are supported for audio extraction:
- G.711 A-Law and μ-Law
- G.722
- G.729
RTP codecs
The RTP codecs tab shows the distribution of the used codecs.
For each codec, the table contains the following information:
- Codec
- The Codec name describes the format of the RTP payload.
- Packets and Bytes
- This is the number of packets and bytes for that codec. It includes both sent and received bytes.
- Packets/s and Bits/s
- These both numbers describe the current throughput for that codec.
- Graph
- The graph column shows the history graph of the traffic for that codec. It shows the timestamp on the x-axis and the bytes on the y-axis. The resolution can be changed by using the control buttons on the top of the web page.
- PCAP
- It is possible to download the traffic for that codec by clicking on the download button.
- The captured packets are not stored on the system but they are directly sent over the HTTP connection to your computer.
- To stop capture, click on the same button again (which turned to a STOP symbol), or go to the capture traffic.
RTP overall quality
The RTP overall quality tab provides graphs about the jitter and packet loss.
There one graph for the overall jitter and packet loss. Additionally, there is a separate graph per network interface. The jitter is calculated according to RFC 3550 Appendix A.8 (https://tools.ietf.org/html/rfc3550#appendix-A.8). The packet loss graph displays the percentage of lost packets to expected packets based on the sequence number in the RTP packets. 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
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. 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.