How to Troubleshoot Acoustic Echo Cancellation That Is Not Working

Acoustic echo cancellation removes the sound coming from your speakers from what your microphone sends. This stops other people from hearing themselves. When it fails, someone on the call hears their own voice repeated a moment after they speak. The steps below help you find where the echo is created and fix it without risky changes.

Identify the symptom and environment

First, work out who hears the echo. If you hear your own voice coming back, the echo is usually produced on another participant's side, because their microphone is picking up their speakers. If others say they hear themselves while you are connected, the problem is most likely on your side. Fixing the wrong side wastes time, so confirm this before changing anything.

Write down the app or browser you use for the call, the input device and output device (built-in, USB, Bluetooth or headset), and whether you listen through speakers or headphones. Also note whether the echo happens on every call or only some, and whether it started after a change such as a new device, an update or newly installed audio software.

Isolate where the fault occurs

• Switch to wired headphones for one call. If the echo stops, speaker sound reaching the microphone was the source and the canceller was not removing all of it.
• Mute your microphone for a moment while others speak. If they stop hearing themselves, your microphone is capturing the echo.
• Join the same call in a different app or browser with the same devices. If the echo appears in only one of them, focus on that app's audio settings rather than the hardware.
• If you have a second input device, try it. If the echo disappears, the placement, built-in processing or driver of the first microphone is a likely factor.
• Check whether more than one device in the same room has joined the call. Two computers in one room often create echo that a canceller cannot remove.

Permissions rarely cause echo on their own. However, if microphone access is blocked for one device, an app may fall back to a different input than the one you expect. Check the operating system's privacy settings and the browser's site permissions to confirm which microphone the app is actually using.

Try reversible fixes in order

Setting names and locations differ between operating system versions, browsers and apps. If a label described here is missing, look in the app's audio or device settings and in the operating system's sound settings for the input device's properties. Test after each change so you can undo any that do not help.

• Lower the speaker volume and move the microphone away from the speakers. Expected result: the other side reports less echo or none. Echo cancellers handle moderate playback more reliably than loud playback.
• In the app's audio settings, choose the input and output devices explicitly instead of leaving a system default. The canceller compares what is played with what is recorded. If sound is routed somewhere the app does not track, the canceller may not have the playback signal it needs.
• If the app offers echo cancellation or noise suppression, make sure it is enabled. Also check whether other layers process the same audio, such as a microphone utility or operating system audio enhancements. Several processors in a row can interfere with each other, so disable extra layers one at a time and retest.
• Temporarily remove virtual audio devices, mixers or routing tools from the signal chain by selecting the physical microphone and speakers directly.
• Check the input level. A very high microphone gain picks up more room sound and background noise, including your speakers. Lower it in the input settings until your voice is still clear but the room is quieter.
• With a Bluetooth headset, reconnect it before the call, or compare with a wired connection. Bluetooth headsets often switch to a separate hands-free mode during calls, which can behave differently.
• If your operating system lets you set the sample rate for each device, check whether the input and output are set to very different formats. Setting them to match may help; which options are available depends on the system and driver.
• Restart the app after changing devices, because some apps only read the device list at startup. Install pending app or browser updates through their normal update mechanism.

In browser-based calls, the website asks the browser to apply echo cancellation, and the site decides whether to request it. If the echo appears only in the browser, compare with another browser or with the service's desktop app, if one exists.

Confirm the result

Recreate the conditions under which the echo appeared: the same devices, speaker volume, app and room. Ask the other participant to talk for a while, including moments when you both speak at once, and to tell you whether they hear themselves. If your app has a test call or recording feature, record with the speakers playing and listen back. A short test in a quiet moment is not enough to confirm the fix. Avoid factory resets, drivers from unknown sources and turning off security software. None of these are needed to check echo cancellation.

If the problem remains

Keep a short record of what you observed: which devices, apps and browsers you tested, which steps changed nothing, whether the echo stops with headphones, and who hears it. This record will make any support contact faster.

• If the echo happens in only one app even though the correct devices are selected, contact that app's support with your notes.
• If the echo follows one particular microphone or headset across several apps, contact the device manufacturer's support and ask about its settings or known issues.
• If the echo comes from another participant's side, share the isolation steps with them, because changes on your device will not fix it.

A symptom that persists is not proof that the hardware has failed. Placement, routing and processing settings explain most cases. Consider repair only after the manufacturer's support has reviewed your observations and recommends it.