RTP statistics: Difference between revisions

Document new RTP statistics tabs: RTP connections and Incidents
No edit summary
(Document new RTP statistics tabs: RTP connections and Incidents)
Line 10: Line 10:
for both receive and transmit directions.
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.
'''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:
  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:
* G.711 A-Law and μ-Law
* G.722
* G.729




Line 37: Line 49:
The packet loss graph displays the percentage of lost packets to expected packets based on the sequence number in the RTP packets.
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%.
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.
183

edits