Source record · tier 2 current vendor documentation
Stream classification in Call Quality Dashboard (CQD)
- Publisher
- Microsoft
- URL
- https://learn.microsoft.com/en-us/microsoftteams/stream-classification-in-call-quality-dashboard
- Published
- 2026-06-16
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- Microsoft Learn terms of use (CC BY 4.0 for docs content per repo; not re-checked); no-redistribution; short excerpts and locators only
Source notes citing this source
- The current Teams CQD audio classifier uses only three network metrics (round trip, packet loss rate, jitter) and lists no MOS or concealment metric. in context
- Teams CQD marks an audio stream Poor when packet utilization exceeds 500 packets and any one of these holds: average round trip over 500 ms, average packet loss rate over 0.1, or average jitter over 30 ms. in context
- Microsoft states that a Poor audio classification in CQD does not mean the stream was actually poor or that the user perceived a quality problem, because the Teams media stack can mitigate degradation beyond the thresholds. in context
- The metrics CQD uses for classification come from a QoE report sent at the end of a call, and some third-party endpoints may not send QoE. in context
- CQD marks a stream Unclassified when ICE connectivity fails or when required metrics are missing, for example no QoE report, a short call, or low packet utilization such as a muted microphone. in context
- Teams Call Quality Dashboard marks an audio stream Poor if Packet Utilization exceeds 500 packets and any one of these holds: average round trip above 500 ms, average packet loss rate above 0.1, or average jitter above 30 ms. in context
- Microsoft states that a CQD Poor audio classification means a network threshold was broken, not that the audio was actually poor or that the user perceived a problem, because the Teams media stack can mitigate considerable network degradation. in context
- CQD marks a stream Unclassified when ICE connectivity fails, when QoE reports are not received (e.g. some third-party endpoints do not send QoE), on short calls, or on low packet utilization such as a mostly-muted microphone. in context
- 'Poor quality' thresholds are product-specific classifiers and should not be carried from one platform to another: Teams CQD flags audio at average jitter above 30 ms, while Webex Calling grades an endpoint good below 150 ms jitter and a cloud hop good below 75 ms. inferred in context
- Teams CQD marks an audio stream Poor if packet utilization exceeds 500 packets and any one of round trip over 500 ms, packet loss rate over 0.1, or jitter over 30 ms is met. in context
- Microsoft states that a CQD Poor audio classification does not mean the stream was actually poor or that the user perceived a quality issue. in context
- CQD marks a stream Unclassified when ICE connectivity fails or the required metrics are not reported, for example because no QoE report arrived, the call was short, or packet utilization was low. in context
Cite this source record
APA
WarmTransfer. (2026, June 16). Stream classification in Call Quality Dashboard (CQD). WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-cqd-stream-classification
BibTeX
@misc{warmtransfer-ms-learn-cqd-stream-classification,
title = {Stream classification in Call Quality Dashboard (CQD)},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/ms-learn-cqd-stream-classification},
note = {Microsoft, accessed 2026-09-24}
}