RTP statistics: Difference between revisions

RTP statistics (view source)

Revision as of 13:57, 28 January 2022

2 bytes added , 28 January 2022

m

Typo fixes

Hartmut

183

edits

@@ Line 5: / Line 5: @@
 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. Paket 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.
 The graph column shows the history graphs of the traffic, lost and overhead packets as well as the jitter over time
@@ Line 14: / Line 14: @@
 '''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 informations 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. 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, bitrate, jitter, MOS and the max audio level of clinet 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
@@ Line 37: / Line 37: @@
 :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 fot 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.
 :To stop capture, click on the same button again (which turned to a STOP symbol), or go to the capture traffic.
@@ Line 45: / Line 45: @@
 The RTP overall quality tab provides graphs about the jitter and packet loss.
-There one graph for the overall jitter and packet loss. Additionaly, 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 packet loss graph displays the percentage of lost packets to expected packets based on the sequence number in the RTP packets.