CQD grades a call based on average (normalized) data – as such it misses instances of severe packet loss and round trip numbers that are way too high. As a result a person can label a call as terrible but your tool will grade the call as good (because the call averaged out to be okay – within the thresholds). As we are not able to change the thresholds this will be an issue.
ooking for a way to work around this from an alerting perspective.
We will need ability to set up reporting that is based on the debug values we saw in the tool (the deeper dives does show more meaningful data such as max packet loss rates and max delay rounbd trip - these measureables are more likely to reflect poor quality calls in alignment with user experience).