Echo on VoIP calls
Verified 2026-09-25 · 51 sources · tier 1–3 · 1 disputed
Echo on voice-over-IP (VoIP) calls originates from reflections at network interfaces, which become perceptible due to transmission and signal processing delays 4020. International standards, gateway configurations, and endpoint adjustments define how these echoes are detected, measured, and eliminated across network segments 1832.
How it works
Cisco defines sidetone, or headset feedback, as hearing your own voice in the headset or earpiece while speaking 45. In most telephones, sidetone helps mask some of the echo 46. Cisco states that an echo must be delayed by at least 20 ms before a user perceives it 41. Cisco explains that the packet segment of a VoIP call adds significant delay, typically 30 ms in each direction, which makes echoes from analog tail circuits perceptible when they were previously indistinguishable from sidetone 40. WarmTransfer's reading of the sources is that the packet leg does not itself produce echo, but adds delay that makes an existing hybrid or acoustic reflection perceptible, so fixing jitter or loss will not remove echo 35.
ITU-T G.168 states that the objectionable effect of echo results from reflections at network components such as 2-to-4-wire converters combined with signal processing and transmission delay 20. Echo can also affect the transmission of voiceband data, fax, and text telephones, not only speech 19. For general network planning, ITU-T G.114 recommends that a one-way delay of 400 ms should not be exceeded 14. ITU-T G.131 (11/2003), Talker echo and its control, provides guidance on the effect of talker echo and its control and is listed by ITU as in force 17. ITU-T G.168 Digital network echo cancellers, approved 2015-04-29, is also listed by ITU as in force 18.
RFC 3611 states that for a VoIP gateway, the source of echo is typically line echo occurring at 2-4 wire conversion points in the network 42. The RTCP XR VoIP Metrics block carries an 8-bit residual echo return loss (RERL) field, measured directly by the endpoint's echo canceller or estimated by adding its reported echo return loss (ERL) and echo return loss enhancement (ERLE) 44. An RERL value of 127 signifies that the parameter is unavailable 43.
Diagnosing it
WarmTransfer's reading of the sources is that the party who hears echo is not where it is generated; if the IP or VoIP user hears their own voice, look at the far-end TDM or analog tail and the gateway echo canceller facing it, whereas if the PSTN or far-end user hears it, look at acoustic coupling at the IP endpoint 38. When an IP phone user hears echo, Cisco attributes it to hybrids in the PSTN network 37. Cisco attributes hybrid echo to an impedance mismatch in the hybrid circuit, such as a two-wire to four-wire interface 23. For echo caused by PSTN hybrids that an IP phone user hears, Cisco places responsibility for preventing the echo on the voice gateways 22. Conversely, when a PSTN user hears echo on a call with an IP phone, Cisco identifies the cause as acoustic coupling between the earpiece and the microphone of the IP phone handset 1.
In multi-party environments, Webex attributes echo in a conference to received audio being picked up by the microphone of the same participant or of another device or participant in the same room 48. To identify the source of echo in a conference, Webex recommends muting all participants and unmuting them one at a time while listening for the echo 49. Webex's corrective actions for conference echo include lowering speaker output, using headphones instead of desktop speakers, moving the microphone away from the speakers, and using only one device's microphone and speakers in a shared room 47.
In Webex Calling Control Hub, troubleshooting views grade a call's media quality as good when the endpoint reports packet loss under 5%, latency or RTT under 400 ms, and jitter under 150 ms 51. WarmTransfer's reading of the sources is that because the media quality grade is defined only by loss, latency, and jitter, and the documentation does not mention echo, a call graded good in Control Hub can still carry echo 50.
Gateway and platform echo cancellation
Cisco IOS voice ports provide built-in echo cancellation controls. The Cisco IOS echo-cancel enable command cancels voice that is sent out an interface and received back on the same interface 32. Cisco warns that disabling echo cancellation on a voice port might cause the remote side of the connection to hear echo 27. However, Cisco states that echo-cancel enable does not affect the echo heard by the user on the analog side of the connection 31. Cisco describes echo cancellation as an invasive process that can minimally degrade voice quality, and states it should be disabled if not needed 28.
On Cisco IOS voice ports, the Cisco G.168 echo canceller is enabled by default with the echo suppressor turned off; the suppressor can be turned on only when that default canceller is in use 34. Cisco states that a hybrid circuit typically provides more than 6 dB ERL, so the extended echo canceller is configured for a 6 dB worst case by default, and it can be set lower if measurement shows the circuit gives 6 dB or less 33. Cisco notes that ERL needs to be approximately 6 dB or higher for the gateway echo canceller to engage 13. When tuning to eliminate echo, Cisco gives a target ERL of approximately 20 dB and a minimum of 15 dB 12. Cisco states that the default voice-port impedance of 600 ohms is consistent with most PSTN and PBX lines 24.
Signal levels impact echo canceller operation. On Cisco IOS voice ports, input gain is applied before the echo canceller sees the echo signal, and output attenuation is applied after the echo canceller sees the original output signal 21. Regarding tail coverage, Cisco states that if the local loop—defined as the delay from the interface to the equipment producing the echo—is longer than the configured echo-cancel coverage, coverage should be increased 26. However, Cisco notes that a larger echo-cancel coverage value makes the echo canceller take longer to converge 25. Sources disagree on the baseline coverage default: the 2008 Cisco echo technote gives the IOS gateway echo-cancel coverage default as 8 ms, adjustable up to 32 ms 6. For IP phone handsets, the 2008 Cisco technote states the fix for acoustic echo is a phone load with echo suppression on the handset and headset, noting that phone loads available at that time included echo cancellation only on the speakerphone 36.
In Asterisk chan_dahdi, echocancel accepts values of yes, no, or a power of two from 32 to 256 taps 11. Taps divided by 8 yields milliseconds, making 256 taps equivalent to 32 ms 11. The Asterisk chan_dahdi sample notes that it is generally unnecessary and undesirable to echo cancel when the circuit path is entirely TDM, though echocancelwhenbridged overrides this 10. Asterisk chan_dahdi also provides an echotraining option that mutes the channel briefly and sends an impulse to pre-train the canceller (default delay 400 ms); the configuration sample warns that this can make echo worse in some cases 8.
See also
- See also Choppy and robotic audio on calls.
- See also Webex Calling analytics in Control Hub.
- See also RTP and RTCP quality metrics.
- See also One-way and no-way audio diagnosis.
Applicability
The 2008 Cisco technote guidelines apply to on-premises deployments as documented on 2008-04-02 23137636. Cisco IOS command reference behaviors for voice ports and echo cancellation commands reflect documentation current as of 2026-09-25 323426. Cisco IP Phone 7800 and 8800 Series headset feedback definitions apply as documented on 2017-08-28 45. Webex Calling Control Hub troubleshooting thresholds and Webex conference echo guidelines apply to multi-tenant deployments current as of 2026-09-25 4851. Asterisk chan_dahdi configurations apply to on-premises deployments on the master branch as of 2026-09-25 11108. ITU-T G.168 (04/2015) and ITU-T G.131 (11/2003) remain in force as of 2026-09-25 1817. ITU-T G.114 (05/2003) and RFC 3611 define related delay and echo metrics 1444.
What remains uncertain
Whether CUBE or other SBCs on IP-to-IP calls without DSP transcoding can cancel echo is not covered by the sources below. Echo handling on Teams Direct Routing SBC legs and which side must cancel is not covered by the sources below. Echo on analog telephone adapters and FXS ports (Cisco ATA and VG and third-party) is not covered by the sources below. Webex App and Webex Calling client acoustic echo handling on point-to-point calls is not covered by the sources below. Poly and Yealink desk phone acoustic echo cancellation settings are not covered by the sources below. Non-600-ohm complex impedance settings by country for analog voice ports are not covered by the sources below. SIP vq-rtcpxr (RFC 6035) reporting of echo metrics and vendor support is not covered by the sources below.
See also
Related symptom
- Choppy and robotic audio on calls — Proposed. Both are symptom-first audio troubleshooting topics; echo is driven by delay plus a reflection point while choppy audio is driven by loss and jitter. The target id is taken from the current research queue and has not been checked against the registry.
Referenced by
- Webex Calling analytics in Control Hub — Per-call media metrics in the Control Hub troubleshooting view; Calling analytics give only aggregate trends.
Sources
- 1When a PSTN user hears echo on a call with an IP phone, Cisco identifies the cause as acoustic coupling between the earpiece and the microphone of the IP phone handset.Troubleshooting Echo Problems between IP Phones and IOS Gateways · PSTN user hears echo section · Checked 2026-09-25
- 2On AudioCodes MP-1288 (firmware 7.4), acoustic echo suppression for SBC calls requires Forced Transcoding so that DSP resources are allocated.Configuring Echo Cancellation (MP-1288 User's Manual Version 7.4) · Configuring Echo Cancellation, acoustic echo suppression paragraph · Checked 2026-09-25
- 3AudioCodes MP-1288 (firmware 7.4) offers acoustic echo suppression for SBC calls only, aimed at non-linear acoustical reflections from a loudspeaker into a microphone.Configuring Echo Cancellation (MP-1288 User's Manual Version 7.4) · Configuring Echo Cancellation, acoustic echo suppression paragraph · Checked 2026-09-25
- 4AudioCodes MP-1288 (firmware 7.4) provides adaptive linear (line) echo cancellation according to G.168-2002, enabled by the EnableEchoCanceller parameter.Configuring Echo Cancellation (MP-1288 User's Manual Version 7.4) · Configuring Echo Cancellation, line echo paragraph · Checked 2026-09-25
- 5AudioCodes documents a Non Linear Processor to suppress residual echo and a double-talk detector to prevent false adaptation during near-end speech.Configuring Echo Cancellation (MP-1288 User's Manual Version 7.4) · Configuring Echo Cancellation, line echo paragraph · Checked 2026-09-25
- 6The 2008 Cisco echo technote gives the IOS gateway echo-cancel coverage default as 8 ms, adjustable up to 32 ms.disputedTroubleshooting Echo Problems between IP Phones and IOS Gateways · Step-by-step Procedure to Troubleshoot and Eliminate Echo · Checked 2026-09-25
- 7The current Cisco IOS voice command reference lists echo-cancel coverage values of 24, 32, 48, 64, 80, 96, 112 and 128 ms, with a default of 128 ms.disputedCisco IOS Voice Command Reference - D through I - E · echo-cancel coverage > Syntax Description and Command Default · Checked 2026-09-25
- 8The Asterisk chan_dahdi echotraining option mutes the channel briefly, sends an impulse to pre-train the canceller (default delay 400 ms), and the sample warns it can make echo worse in some cases.asterisk/configs/samples/chan_dahdi.conf.sample · chan_dahdi.conf.sample, echotraining comment block · Checked 2026-09-25
- 9The Asterisk chan_dahdi sample says a hardware echo canceller takes precedence when present, and numeric echocancel values are treated as yes on hardware-equipped cards.asterisk/configs/samples/chan_dahdi.conf.sample · chan_dahdi.conf.sample, echocancel comment block · Checked 2026-09-25
- 10The Asterisk chan_dahdi sample says it is generally unnecessary and undesirable to echo cancel when the circuit path is entirely TDM; echocancelwhenbridged overrides this.asterisk/configs/samples/chan_dahdi.conf.sample · chan_dahdi.conf.sample, echocancelwhenbridged comment block · Checked 2026-09-25
- 11In Asterisk chan_dahdi, echocancel accepts yes, no, or a power of two from 32 to 256 taps, and taps divided by 8 gives milliseconds, so 256 taps is 32 ms.asterisk/configs/samples/chan_dahdi.conf.sample · chan_dahdi.conf.sample, echocancel comment block · Checked 2026-09-25
- 12Cisco gives a target ERL of approximately 20 dB and a minimum of 15 dB when tuning to eliminate echo.Troubleshooting Echo Problems between IP Phones and IOS Gateways · Step-by-step Procedure to Troubleshoot and Eliminate Echo · Checked 2026-09-25
- 13Cisco states that ERL needs to be approximately 6 dB or higher for the gateway echo canceller to engage.Troubleshooting Echo Problems between IP Phones and IOS Gateways · Step-by-step Procedure to Troubleshoot and Eliminate Echo · Checked 2026-09-25
- 14ITU-T G.114 recommends that a one-way delay of 400 ms should not be exceeded for general network planning.ITU-T G.114 (05/2003) Summary · Summary · Checked 2026-09-25
- 15The G.114 summary cautions that highly interactive voice and video applications can be affected by delays well below 400 ms and points to the E-model (G.107) for estimating delay effects.ITU-T G.114 (05/2003) Summary · Summary · Checked 2026-09-25
- 16The G.131 (11/2003) summary relates talker echo to the E-model of ITU-T G.107 and to transmission planning for echo control devices.Summary of ITU-T Recommendation G.131 (11/2003) · Summary, later sentences · Checked 2026-09-25
- 17ITU-T G.131 (11/2003), Talker echo and its control, gives guidance on the effect of talker echo and its control and is listed by ITU as in force.Summary of ITU-T Recommendation G.131 (11/2003) · Summary, first sentence; status from landing page · Checked 2026-09-25
- 18ITU-T G.168 Digital network echo cancellers, approved 2015-04-29, is listed by ITU as in force.G.168 : Digital network echo cancellers · Recommendation landing page: Approved in / Status fields · Checked 2026-09-25
- 19ITU-T G.168 notes that echo can also affect the transmission of voiceband data, fax and text telephones, not only speech.Summary of ITU-T Recommendation G.168 (04/2015) · Summary, final sentence · Checked 2026-09-25
- 20ITU-T G.168 says the objectionable effect of echo results from reflections at network components such as 2-to-4-wire converters combined with signal processing and transmission delay.Summary of ITU-T Recommendation G.168 (04/2015) · Summary, sentence 2 · Checked 2026-09-25
- 21On Cisco IOS voice ports, input gain is applied before the echo canceller sees the echo signal, and output attenuation is applied after the echo canceller sees the original output signal.Troubleshooting Echo Problems between IP Phones and IOS Gateways · Step-by-step Procedure to Troubleshoot and Eliminate Echo · Checked 2026-09-25
- 22For echo caused by PSTN hybrids that the IP phone user hears, Cisco places responsibility for preventing the echo on the voice gateways.Troubleshooting Echo Problems between IP Phones and IOS Gateways · IP Phone User Hears Echo section · Checked 2026-09-25
- 23Cisco attributes hybrid echo to an impedance mismatch in the hybrid circuit such as a two-wire to four-wire interface.Troubleshooting Echo Problems between IP Phones and IOS Gateways · Step-by-step Procedure to Troubleshoot and Eliminate Echo (echo types) · Checked 2026-09-25
- 24Cisco states that the default voice-port impedance of 600 ohms is consistent with most PSTN and PBX lines.Troubleshooting Echo Problems between IP Phones and IOS Gateways · Step-by-step Procedure to Troubleshoot and Eliminate Echo · Checked 2026-09-25
- 25Cisco says a larger echo-cancel coverage value makes the echo canceller take longer to converge.Cisco IOS Voice Command Reference - D through I - E · echo-cancel coverage > Usage Guidelines · Checked 2026-09-25
- 26Cisco says that if the local loop, meaning the delay from the interface to the equipment producing the echo, is longer than the configured echo-cancel coverage, the coverage should be increased.Cisco IOS Voice Command Reference - D through I - E · echo-cancel coverage > Usage Guidelines · Checked 2026-09-25
- 27Cisco warns that disabling echo cancellation on a voice port might cause the remote side of the connection to hear echo.Cisco IOS Voice Command Reference - D through I - E · echo-cancel enable > Usage Guidelines · Checked 2026-09-25
- 28Cisco describes echo cancellation as an invasive process that can minimally degrade voice quality, and says it should be disabled if not needed.Cisco IOS Voice Command Reference - D through I - E · echo-cancel enable > Usage Guidelines · Checked 2026-09-25
- 29The Cisco echo-cancel loopback command puts the echo canceller in loopback for diagnostics; if cancellation fails in loopback, the interface is the source of the problem.Cisco IOS Voice Command Reference - D through I - E · echo-cancel loopback > Usage Guidelines · Checked 2026-09-25
- 30Cisco documents echo-cancel mode 2 for the extended G.168 canceller as fast convergence with improved double-talk detection, most useful on analog interfaces with multiple echo reflectors and low-volume double-talk.Cisco IOS Voice Command Reference - D through I - E · echo-cancel mode > Syntax Description and Usage Guidelines · Checked 2026-09-25
- 31Cisco states that echo-cancel enable does not affect the echo heard by the user on the analog side of the connection.Cisco IOS Voice Command Reference - D through I - E · echo-cancel enable > Usage Guidelines · Checked 2026-09-25
- 32The Cisco IOS echo-cancel enable command cancels voice that is sent out an interface and received back on the same interface.Cisco IOS Voice Command Reference - D through I - E · echo-cancel enable > Usage Guidelines · Checked 2026-09-25
- 33Cisco says a hybrid circuit typically provides more than 6 dB ERL, so the extended echo canceller is configured for a 6 dB worst case by default, and it can be set lower if measurement shows the circuit gives 6 dB or less.Cisco IOS Voice Command Reference - D through I - E · echo-cancel enable > Usage Guidelines; echo-cancel erl worst-case · Checked 2026-09-25
- 34On Cisco IOS voice ports the Cisco G.168 echo canceller is enabled by default with the echo suppressor turned off, and the suppressor can be turned on only when that default canceller is in use.Cisco IOS Voice Command Reference - D through I - E · echo-cancel enable > Usage Guidelines · Checked 2026-09-25
- 35The packet leg does not itself produce echo. It adds delay that makes an existing reflection, hybrid or acoustic, perceptible, so fixing jitter or loss will not remove echo.inferredSummary of ITU-T Recommendation G.168 (04/2015) · Summary, sentence 2 · Checked 2026-09-25
- 36The 2008 Cisco technote says the fix for acoustic echo from an IP phone handset is a phone load with echo suppression on the handset and headset, and that the loads available then included echo cancellation only on the speakerphone.Troubleshooting Echo Problems between IP Phones and IOS Gateways · PSTN user hears echo section · Checked 2026-09-25
- 37When the IP phone user hears echo, Cisco attributes it to hybrids in the PSTN network.Troubleshooting Echo Problems between IP Phones and IOS Gateways · IP Phone User Hears Echo section · Checked 2026-09-25
- 38The party who hears echo is not where it is generated. If the IP or VoIP user hears their own voice, look at the far-end TDM or analog tail and the gateway echo canceller facing it; if the PSTN or far-end user hears it, look at acoustic coupling at the IP endpoint.inferredTroubleshooting Echo Problems between IP Phones and IOS Gateways · IP Phone User Hears Echo; PSTN user hears echo · Checked 2026-09-25
- 39On Cisco 8800 multiplatform phones, sidetone gain can be set to Off, Very Low, Low or High (default Low), and cannot be adjusted for the phone speaker or USB headsets.Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later - Audio Configuration · Audio Configuration > Sidetone · Checked 2026-09-25
- 40Cisco explains that the packet segment of a VoIP call adds significant delay, typically 30 ms in each direction, which makes echoes from analog tail circuits perceptible when they were previously indistinguishable from sidetone.Troubleshooting Echo Problems between IP Phones and IOS Gateways · IP Phone User Hears Echo section · Checked 2026-09-25
- 41Cisco states that an echo must be delayed by at least 20 milliseconds before a user perceives it.Troubleshooting Echo Problems between IP Phones and IOS Gateways · Introduction · Checked 2026-09-25
- 42RFC 3611 states that for a VoIP gateway the source of echo is typically line echo occurring at 2-4 wire conversion points in the network.RTP Control Protocol Extended Reports (RTCP XR) · Section 4.7.4 Signal Related Metrics, RERL field · Checked 2026-09-25
- 43In RFC 3611 an RERL value of 127 means the parameter is unavailable.RTP Control Protocol Extended Reports (RTCP XR) · Section 4.7.4 Signal Related Metrics, RERL field · Checked 2026-09-25
- 44The RTCP XR VoIP Metrics block carries an 8-bit residual echo return loss (RERL) field, measured directly by the endpoint's echo canceller or estimated by adding its reported ERL and ERLE.RTP Control Protocol Extended Reports (RTCP XR) · Section 4.7.4 Signal Related Metrics, RERL field · Checked 2026-09-25
- 45Cisco defines sidetone (headset feedback) as hearing your own voice in the headset or earpiece while speaking.Cisco IP Phone 7800 and 8800 Series Accessories Guide for Cisco Unified Communications Manager - Headsets · Configure a Headset on the Phone > Adjust the Headset Feedback · Checked 2026-09-25
- 46Cisco states that in most telephones sidetone helps mask some of the echo.Troubleshooting Echo Problems between IP Phones and IOS Gateways · Introduction · Checked 2026-09-25
- 47Webex's corrective actions for conference echo are lowering speaker output, using headphones instead of desktop speakers, moving the microphone away from the speakers, and using only one device's microphone and speakers in a shared room.Troubleshooting Guide for Echo in a Conference · Corrective actions section · Checked 2026-09-25
- 48Webex attributes echo in a conference to received audio being picked up by the microphone of the same participant or of another device or participant in the same room.Troubleshooting Guide for Echo in a Conference · Opening section (cause of echo) · Checked 2026-09-25
- 49To find the source of echo in a conference, Webex recommends muting all participants and unmuting them one at a time while listening for the echo.Troubleshooting Guide for Echo in a Conference · Section on identifying the source · Checked 2026-09-25
- 50The Webex Calling media quality grade is defined only by loss, latency and jitter and the article does not mention echo, so a call graded good in Control Hub can still carry echo.inferredTroubleshoot Webex Calling calls in Control Hub · Hop details view (threshold list); whole article checked for 'echo' · Checked 2026-09-25
- 51Webex Calling Control Hub troubleshooting grades a call's media quality as good when the endpoint reports packet loss under 5%, latency or RTT under 400 ms, and jitter under 150 ms.Troubleshoot Webex Calling calls in Control Hub · Hop details view · Checked 2026-09-25
Documents
G.168 : Digital network echo cancellers
ITU-T G.114 (05/2003) Summary
RTP Control Protocol Extended Reports (RTCP XR)
Summary of ITU-T Recommendation G.131 (11/2003)
Summary of ITU-T Recommendation G.168 (04/2015)
Cisco IOS Voice Command Reference - D through I - E
Cisco IP Phone 7800 and 8800 Series Accessories Guide for Cisco Unified Communications Manager - Headsets
Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later - Audio Configuration
Configuring Echo Cancellation (MP-1288 User's Manual Version 7.4)
Troubleshoot Webex Calling calls in Control Hub
Troubleshooting Echo Problems between IP Phones and IOS Gateways
Troubleshooting Guide for Echo in a Conference
asterisk/configs/samples/chan_dahdi.conf.sample
Cite this page
APA
WarmTransfer. (2026, September 25). Echo on VoIP calls. WarmTransfer. https://warmtransfer.net/knowledge/echo-on-calls
BibTeX
@misc{warmtransfer-echo-on-calls,
title = {Echo on VoIP calls},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/echo-on-calls},
note = {Verified 2026-09-25}
}