Why is Plivo’s quality score "good" when a call had suspected issues?

Plivo’s quality score is the standard mean opinion score (MOS). The MOS is computed based on factors of jitter, packet loss, and RTT. Unless the suspected issue is broken audio, robotic audio, and audio lag, the quality score computation is not affected.

In addition, the quality score may not match the quality if the suspected issue is related to an associated call_UUID. 

Was this article helpful?
0 out of 0 found this helpful
Didn’t find what you are looking for? Create new ticket