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

If the quality score doesn’t match the quality, this could be for a few reasons.

  • The suspected issue is related to an associated call_UUID. 
  • 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 will not be affected.
Was this article helpful?
0 out of 0 found this helpful
Didn’t find what you are looking for? Create new ticket