12 · Troubleshooting
CQD is how you see a subnet. It is only as honest as the building map.
CQD aggregates streams by dimensions such as subnet and user agent. Separate jitter, loss, and round-trip in your head. High jitter with DSCP 0 suggests a mark that never survived. High loss with EF still set suggests a congested or dirty link. Long RTT with almost no loss suggests distance or a hairpin.
If the VPN pool is labeled headquarters, headquarters looks terrible and the real LAN is fine. Fix the map before you present the dashboard. Power BI on top of CQD inherits the same map.
CQD is the building view. Split loss, jitter, and delay, and fix the subnet map first.
I split loss, jitter, and RTT, and I trust CQD only after I trust the subnet map.
If it fails: HQ is red because the VPN pool was typed in as HQ.
A colleague reports: Three vendors change three boxes and the call starts working for an unknown reason. Where do you start?
Three vendors change three boxes and the call starts working for an unknown reason. Write the hypothesis, the change, and the capture you expect. Source: https://learn.microsoft.com/en-us/microsoftteams/use-call-analytics-to-troubleshoot-poor-call-quality accessed 2026-10-14.
Which description of Admin roles for CQD is accurate?
CQD is an admin report, not a personal call history. The people who can open it are the roles you grant, not every user. A manager with no role will ask for a screenshot instead of access. Source: https://learn.microsoft.com/en-us/microsoftteams/cqd-what-is-call-quality-dashboard accessed 2026-10-14.
A colleague reports: CQD credentials are shared. Where do you start?
CQD credentials are shared. Grant the smallest role that can see the report. Source: https://learn.microsoft.com/en-us/microsoftteams/cqd-what-is-call-quality-dashboard accessed 2026-10-14.
Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.
HQ is red because the VPN pool was typed in as HQ.
Cisco CUBE is one of the SBC families named in this lab’s certification lesson. A certified release can be the Direct Routing SBC between Unified CM and Teams.
The tenant still needs a verified domain on the SBC FQDN, and the user still needs Teams Phone. The studio translator does not open a live AXL session. Confirm the current certified release before you build.
Teams Phone and Webex Calling are separate clouds. This lab does not describe a feature that registers a Webex Calling user into a Teams tenant.
A number move is usually a carrier port, a certified SBC, or a meetings interop product. Confirm before relying.
Unified CCE stays the ACD until you migrate it. Microsoft’s contact-center articles name Connect, Extend, and Unify. They do not name a UCCE connector in the notes this lab cites.
Voice into Teams is still Direct Routing or Operator Connect. The routing script stays on the contact-center product you bought. Confirm the vendor’s current model. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-contact-center.
Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.
Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.
