Use Call Analytics to troubleshoot poor call quality

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/use-call-analytics-to-troubleshoot-poor-call-quality

Published

2025-09-15

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Microsoft Learn terms of use; no-redistribution; short excerpts and locators only

Source notes citing this source

• Teams per-user Call Analytics shows each leg of a call or meeting, with device, network and connectivity details, so an admin can isolate the problem area. It lists the user's calls and meetings for the last 30 days. in context
• In Teams Call Analytics session details, yellow items are outside the normal range but unlikely to be the main cause, while red items are significant and likely the main cause of poor quality. 'Audio network classified poor call' covers packet loss, jitter, NMOS degradation, RTT or concealed ratio. in context
• Microsoft's 'Use Call Analytics to troubleshoot poor call quality' article describes an earlier Teams admin center experience that has been replaced by the 'Monitor and troubleshoot Teams meetings and calls' experience. in context
• In Teams Call Analytics an Ms-diag error code in the range 20-29 marks a failed call setup, one of the conditions that classify an audio session as poor. in context
• In Teams per-user Call Analytics, phone numbers are shown with the last four digits obfuscated for all communications support roles, and this cannot be changed or disabled. in context
• In the earlier Teams Call Analytics experience the Teams Communications Support Specialist (Tier 1) cannot see the Call Details Advanced and Debug tabs, which the Support Engineer (Tier 2) can see. in context
• In per-user Call Analytics the last four digits of caller and recipient phone numbers are obfuscated for every communications support role, and this cannot be changed or disabled. in context
• Microsoft's per-user Call Analytics article describes an earlier troubleshooting experience in Teams admin center, now replaced by the Monitor and troubleshoot Teams meetings and calls experience. in context
• The legacy Call Analytics article says Real-Time Analytics let admins troubleshoot scheduled meetings in progress and for 72 hours after the meeting ends. disputed in context

Cite this source record

APA

WarmTransfer. (2025, September 15). Use Call Analytics to troubleshoot poor call quality. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-call-analytics-troubleshoot

BibTeX

@misc{warmtransfer-ms-learn-call-analytics-troubleshoot,
  title  = {Use Call Analytics to troubleshoot poor call quality},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-call-analytics-troubleshoot},
  note   = {Microsoft, accessed 2026-09-24}
}