How to Configure Echo Cancellation for VoIP Calls

Echo on a VoIP call usually means sound from a speaker reaches a microphone and is sent back to the person who spoke. Calling apps and browsers include acoustic echo cancellation to remove that returning sound, but it works best when the audio path is simple and correctly configured. This guide helps you find where the echo starts and adjust settings in an order that is easy to undo.

Identify the symptom and environment

Start by working out who hears the echo. If you hear your own voice come back a moment after you speak, the sound is usually being picked up on the other participant's side. Their speakers play your voice, their microphone captures it, and their app sends it back. If other people say they hear themselves while talking to you, the likely source is your setup.

Write down a few details before changing anything, because they help you compare results later:

• Who hears the echo and whether it happens with every contact or only one
• The calling app or browser in use, and whether the call is desktop, web or mobile
• The input device and output device selected for the call, such as built-in laptop speakers and microphone, a USB headset, a Bluetooth headset or a conference speakerphone
• When it happens: from the start of the call, only at higher speaker volume, after switching devices, or only when several people talk at once
• Whether the echo sounds like a clear repeat of speech or more like a hollow, metallic tail

Isolate where the fault occurs

Echo cancellation compares what is played through the output device with what the microphone captures. Anything that makes the two hard to match can let echo through. Check each layer separately.

Hardware and room: open speakers placed close to a microphone, high speaker volume and hard, reflective rooms all make echo harder to remove. Wearing headphones is the quickest way to tell whether the acoustic path is the cause. If the echo disappears when the affected person uses headphones, the hardware is working and the issue is speaker sound reaching the microphone.

Connection and device switching: Bluetooth headsets can switch to a different mode when the microphone is in use, and some apps lose track of the correct output device after a headset connects or disconnects mid-call. Note whether the echo began right after such a change.

Operating-system audio routing: features that monitor the microphone, mix it back into the speakers, or route audio through virtual devices can create a loop that the app cannot cancel. On Windows, a recording device's properties in the classic Sound settings include an option to listen to the device. If that is enabled, microphone audio plays through your speakers.

App and browser selection: confirm that the call uses the microphone and speakers you expect. If the app is set to a different device than the operating system default, or two programs process the same microphone, the echo canceller may not be using the right reference signal. Testing the same devices in a second calling app can help show whether the problem follows the hardware or stays with one app.

Try reversible fixes in order

Change one thing at a time and make a short test call after each change, so you know which step made the difference. Menu names and locations vary between apps, operating systems and versions, so look for wording with the same meaning rather than an exact label.

• Use headphones or a headset on the side that is causing the echo. This removes most of the acoustic path, and the echo should stop immediately.
• Lower the speaker volume and move speakers away from the microphone. Point them away from it if you cannot use headphones. The echo should become quieter or shorter.
• Select the input device and output device explicitly in the calling app instead of relying on the default. Prefer a matched pair, such as the microphone and speaker of the same headset. The app's own audio test should show input from the expected microphone and play sound through the expected output.
• Check the app's audio settings for an echo cancellation option. If the app offers one, make sure it is turned on. Some apps handle echo automatically and offer no switch, which is normal.
• Turn off microphone monitoring or listen-to-device features in the operating system and in any headset or audio-interface software. After this change you should no longer hear your own microphone through your speakers outside a call.
• Avoid stacking processing. If audio-enhancement software, a virtual audio device or a driver-level effect processes the microphone before the calling app does, try the call with that layer bypassed or disabled. Some drivers expose their own echo or noise options; use either those or the app's processing, not both, and compare the results.
• Set a reasonable input level. A microphone driven so hard that it distorts, or one with aggressive automatic gain, can make leftover echo louder. The input level meter in the app or operating system should move clearly with your voice without staying at the maximum.
• Check the sample rate if you use an external audio interface or a professional microphone. Where your system lets you set the device format, a common rate such as 48 kHz for both input and output avoids conversion problems in some setups. Note the original value before changing it.
• Reconnect Bluetooth devices before the call rather than during it, then reselect them in the app if needed.

Background noise suppression and echo cancellation are separate functions. Turning noise suppression up or down may change how the call sounds, but it does not replace echo cancellation or fix an audio routing loop.

Confirm the result

Repeat the conditions from your notes. Call the same contact if possible and ask them to speak at a normal volume while you listen for a delayed repeat of their voice, or of yours if you were the one hearing it. Try a stretch where both people talk at the same time, because residual echo often shows up during overlapping speech.

If the calling app has a test call or recording feature, use it to listen back for echo without involving another person. Before treating the fix as done, confirm that normal behavior still works: the other side hears you clearly, the correct devices remain selected after restarting the app, and system sounds still play through the intended output device.

Avoid drastic steps such as factory resets, drivers from unknown sources or disabling security features. They are rarely needed for echo, and they make it harder to tell which change actually helped.

If the problem remains

Keep the observations that narrow down the cause: which side hears the echo, the exact devices and app version, whether headphones remove it, and whether it appears in more than one app. This information is what app or device support usually needs, and it saves you from repeating basic checks.

If the echo stays with one app while other apps are fine on the same devices, contact that app's support or check its documentation for known audio issues in your version. If it follows a specific headset, speakerphone or interface across apps and computers, ask the manufacturer's support about its audio settings or firmware. Persistent echo is not proof that the hardware has failed. Room acoustics, device placement and routing settings often explain it. Consider repair or replacement only after the device behaves the same way in a simple setup with default settings.