The four major call quality metrics are latency, jitter, packet loss, and mos-score.
Latency refers to the time it takes to transmit a packet from the source to the destination. When latency is high, users will experience a lag in their audio call. Calls tend to experience significant audio lags when the latency increases beyond 200ms.
Packet loss is caused by network congestion. High loss of packets results in robotic or broken audio. Calls tend to experience issues when the packet loss is higher than 2%.
Jitter is caused when the packets arrive out of order. High measurements of jitter can cause muffled audio in voice calls. Calls tend to experience issues when jitter increases beyond 30ms.
How to enable MediaMetrics to access the call quality:
- Go to the Plivo GitHub page to find an example of how to implement MediaMetrics on your application. If you want to see a MedaiMetrics demo, use the online link. Select the network link conditioner for MacOs or Clumsy for Windows to simulate different network conditions.
- When you set “enableTracking” to “true” in an SDK configuration, you'll start to receive all network and audio-related WARNING events under the "MediaMetrics" event listener.
- Please refer to Plivo documentation to check the list of event names and their threshold limits.