Troubleshooting · Symptoms
Echo on VoIP Calls: Finding the Real Cause
Echo — hearing your own voice bounce back at you — is the fault users describe worst and engineers misdiagnose most, because three entirely different mechanisms produce the same complaint. The mechanism matters: the fix for acoustic echo (a loud speakerphone in a tiled room) has nothing in common with the fix for hybrid echo (an analog conversion leaking) or for delay making normal sidetone feel like echo.
The first diagnostic fact is always the same: who hears the echo? You hear echo when the far end returns your voice to you. So the echo is almost always generated at the far end or on its path — your own equipment is the last suspect, however close it sits.
The three mechanisms
| Mechanism | How it happens | Signature |
|---|---|---|
| Acoustic coupling | Far end's speaker output reaches their microphone (speakerphone, loud handset, room echo) | Echo varies with their volume/room; worse with speakerphone users |
| Hybrid / analog leakage | A 2-wire to 4-wire conversion (ATA, analog gateway, PSTN hybrid) reflects signal back due to impedance mismatch | Consistent echo on calls crossing that gateway/ATA; often one site or one trunk group |
| Delay exposure | Network delay grows so large that normal return paths and sidetone become perceptible as echo | Accompanies high latency; echo feels 'distant'; often with choppy audio too |
How professionals isolate it
Echo cancellers (ITU-T G.168) are built into phones, gateways and carrier systems, and they cancel return signal within a time window (the 'tail'). Echo becomes audible when the return arrives outside the canceller's tail or is too loud to cancel — which is why long-delay paths expose echo that the same equipment hides on short paths. Isolation is elimination with controlled calls: call the same person on different endpoints (desk phone vs mobile), call different destinations through the same trunk, and call the same destination from a different site. The matrix of results points at a room, a gateway, or a path. Also ask the question that solves a third of tickets instantly: 'Did this start when someone got a new headset, moved desks, or started using speakerphone?'
Isolation and fix sequence
- Establish who hears echo (one side or both), on which call types (internal, external, one site, one destination), and since when.
- Run the endpoint matrix: same far party via their handset vs speaker vs headset. Echo that follows their speakerphone is acoustic — fix volume, room, or headset use at their end.
- If echo tracks calls through one ATA, analog gateway or site, suspect hybrid leakage: check that device's echo-canceller is enabled, update firmware, and for ATAs try the alternate impedance/FXC settings the vendor documents.
- Measure delay on echoing calls (capture → RTP analysis). One-way delay above ~150 ms makes echo intrusive and defeats cancellers; fix the delay (queueing, path) and the echo often resolves with it.
- Check for double cancellers or a disabled canceller after equipment changes — echo features are frequent casualties of firmware updates and profile pushes.
- Verify by repeating the exact call that echoed, at the same volumes, and confirming with the party who heard it.
Frequently asked questions
- Why do I only hear echo with certain people?
- Because the echo is generated at their end: their speakerphone, their room, their gateway. Your phone faithfully delivers the returned copy of your voice. Calling someone else tests your equipment; the pattern of who echoes tells you where to look.
- Can turning my volume down fix it?
- For acoustic echo, yes — if you are the far end for the person hearing echo, lowering your speaker volume (or using a handset/headset) reduces the coupled signal below annoyance. It is a legitimate immediate mitigation while the real fix is arranged.
- Our echo started after switching providers. Why?
- The media path changed: different routing can add delay (longer tail needed), and the new platform's gateways have their own cancellers and settings. Report it with examples — providers can adjust echo-cancellation settings on their gateways, and your capture showing healthy local metrics makes that conversation short.