https://docs.truedem-stage.com/en/docs/admin/troubleshooting/teams/Recent content in Microsoft Teams Call Quality on TrueDEM Knowledge BaseHugoenhttps://docs.truedem-stage.com/en/docs/admin/troubleshooting/teams/analyzing-a-bad-call/Mon, 01 Jan 0001 00:00:00 +0000https://docs.truedem-stage.com/en/docs/admin/troubleshooting/teams/analyzing-a-bad-call/<p>When a call goes bad, resist the urge to blame the first thing you see. Follow a repeatable sequence.</p> <h2 id="a-five-step-method">A five-step method</h2> <ol> <li><strong>Access the call data</strong> for the affected meeting.</li> <li><strong>Spot the affected participants</strong> — degradation is usually not symmetric.</li> <li><strong>Analyze each participant&rsquo;s experience</strong> — was it audio, video or screen share; send or receive side?</li> <li><strong>Pinpoint potential sources</strong> — device load, Wi-Fi, ISP, or cloud path.</li> <li><strong>Diagnose and remediate the root cause</strong>, then validate on a follow-up call.</li> </ol> <h2 id="reading-the-media-metrics">Reading the media metrics</h2> <p>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.</p>