VoIP.info Troubleshooting

Echo on VoIP calls

Identify the returning audio path before adjusting cancellation or blaming latency.

Reviewed 2026-09-07Asterisk 22 LTS · FreePBX 17 / Debian 12 checksIntermediateDocumentation based · not lab tested

Who hears the echo?

Ask which participant hears their own voice returning and whether it occurs on handset, headset or speakerphone. Echo often involves acoustic coupling or an analog boundary, while delay makes the returned sound more noticeable. The hearing participant is not necessarily where the echo originates.

Compare the device path

Switch one side from speakerphone to handset at a reasonable volume. Check headset fit, microphone placement and damaged accessories. If the echo disappears with that change, focus on acoustic behavior before reconfiguring the trunk.

For analog adapters or gateways, review the exact device's impedance and echo-cancellation guidance. Do not apply electrical settings intended for a different country or line interface.

Check timing separately

High latency can make an existing echo more disruptive. Compare the network path and queueing during the affected calls, but do not assume reducing a jitter buffer repairs the acoustic source.

Accept the repair

Repeat the call using the original device and volume conditions, then test double-talk where both people speak. Excessive processing can suppress legitimate speech while hiding echo. Record the component and setting that changed rather than applying a blanket gain reduction to every endpoint.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.