Analyzing a Bad Microsoft Teams Call
When a call goes bad, resist the urge to blame the first thing you see. Follow a repeatable sequence.
A five-step method
- Access the call data for the affected meeting.
- Spot the affected participants — degradation is usually not symmetric.
- Analyze each participant’s experience — was it audio, video or screen share; send or receive side?
- Pinpoint potential sources — device load, Wi-Fi, ISP, or cloud path.
- Diagnose and remediate the root cause, then validate on a follow-up call.
Reading the media metrics
Map symptoms to metrics: choppy audio points to jitter and packet loss; lag points to round-trip time; frozen video often follows bandwidth starvation on a congested link.
Isolate the side
If only one participant is affected, the cause is almost always local to that participant (device or Wi-Fi), not the service.
If only one participant is affected, the cause is almost always local to that participant (device or Wi-Fi), not the service.