Why Remote Participants Hear a Meeting Room Echo You Cannot

A meeting room echo can be invisible to everyone sitting at the table. The remote participant talks, their voice plays through your room loudspeakers, and your room microphone sends part of it back. They hear themselves return. You hear only the original sentence.

That one-way complaint is a clue, not a mystery. Before replacing a microphone or video bar, identify whether the symptom is far-end acoustic echo, two active meeting devices, room reverberation, or feedback. Each has a different fix.

Why the far end hears the meeting room echo

In conferencing, your office is the near end and the remote participant is the far end. Their voice enters your room through the call and plays from the loudspeakers. Some of that sound reaches your microphones directly, and some reaches them after reflecting from the table, walls, glass, and ceiling.

If that captured sound is transmitted back, the remote talker hears a delayed copy of their own words. Shure's conferencing processor guide describes acoustic echo cancellation, or AEC, as the process that identifies the far-end signal and prevents it from being captured and returned by the near-end microphone.

AEC runs in or for your room, but the person across the call receives the benefit. That is why the people sitting under the loudspeakers cannot judge whether cancellation is working. Biamp's AEC documentation makes the same point: the far end hears the echo caused by the near end, and each room needs its own echo-control path.

Call the symptom by the right name

Ask the remote participant what they hear. “Bad audio” is too broad to troubleshoot.

• Far-end acoustic echo: the remote talker hears a recognizable copy of their own voice return after they speak.
• Duplicate meeting audio: two laptops, or a computer and phone, are carrying call audio in the same room. The result can be a fast echo, hollow comb-filtered sound, or escalating noise.
• Reverberation: local voices sound distant, smeared, or as though they are in a hard empty room. The far end struggles with your talkers rather than hearing a clean repeat of its own sentence.
• Feedback: a sustained ring, howl, or tone grows through a microphone and loudspeaker loop.

Shure's feedback guidance explicitly separates ringing feedback from echoes and reverberation caused by room acoustics. Treating all three as “echo” sends the troubleshooting in the wrong direction.

Remove extra audio devices first

Before touching the installed room settings, make sure only one device owns microphone and speaker audio in the room. A second laptop can join for chat, notes, or screen sharing, but it should use the platform's companion or no-audio path.

Zoom lists three common echo causes: computer and telephone audio active together, nearby devices with speakers on, and multiple computers carrying audio in the same room. Its echo troubleshooting article warns that muting a second computer may not be enough because its speaker remains active. Disconnect meeting audio on every device except the designated room endpoint.

Teams automatically mutes a second device's microphone when it joins an existing call to reduce echo risk, but users can change that state. Microsoft's second-device guidance lets the user transfer the call or add the device with controlled audio. In Google Meet rooms, Companion Mode turns off the laptop microphone and meeting audio so the room hardware remains the single audio path.

Also check for a phone dialed into the same meeting while the laptop remains on computer audio. Leave one path completely. Then lower the room loudspeaker level for a short test. If the echo changes sharply, that is useful evidence for the room integrator, even if a lower volume is not the final answer.

If the room cannot hear the problem, put the tester outside the room. Far-end echo has to be judged from the far end.

Run a real far-end test

Schedule ten minutes with authorized testers in separate closed rooms or remote offices. Use a dummy meeting, non-sensitive phrases, and a synthetic slide or audio clip. Do not record or retain the test unless your business policy permits it. Do not stand inside the room with a second unmuted device. Biamp's conference-room commissioning guide recommends calling from a remote location specifically because that is where echo can be evaluated.

Use a simple test sequence:

1. Confirm one room microphone and one room speaker are selected in Teams, Zoom, or Meet.
2. Disconnect audio from every companion laptop and phone.
3. Have the far-end tester speak while the room is quiet. Ask whether they hear a distinct repeat of their own words.
4. Test while someone in the room speaks at the same time. Echo control works hardest during overlapping speech.
5. Play shared content with audio, then stop it. Record which condition creates the echo.
6. If the room has several microphone inputs, have the room administrator or integrator isolate them one at a time.

Write down the platform, laptop, selected device names, room volume, seats in use, and exact time of the failure. If the room has call-quality logs or managed-device telemetry, the timestamp makes those records useful.

Repeat the test on a second meeting platform only after the first setup is documented. If the symptom follows the room across platforms and laptops, the installed audio path deserves attention. If it follows one laptop or app, return to device selection, permission, driver, and duplicate-audio checks.

When the AEC path needs an integrator

An installed room needs an accurate AEC reference, which is a copy of the far-end audio the room is about to play. The processor compares that reference with what the microphone captures. If receive audio is routed straight back to transmit, the reference misses part of the loudspeaker path, or two devices both try to own echo cancellation, the far end can hear residual echo or damaged speech.

Q-SYS lists those conditions in its AEC troubleshooting guidance. Those are programming and commissioning checks. They are not a reason for an office manager to open the DSP design during a live board meeting.

Give the integrator the far-end test notes and ask for the reference routing, loudspeaker level path, microphone inputs, and AEC ownership to be verified. A room processor, conferencing codec, video bar, and laptop app should not all fight over the same job.

Our Q-SYS integration work covers the programmed audio, video, and control path in rooms that need more than an appliance at the display.

Reverberation and feedback need different work

If local voices arrive at the far end sounding hollow or washed out, listen inside the room. Hard parallel surfaces and long reflections can make speech difficult before electronics enter the picture. A microphone farther from the talker captures more room along with the voice.

That issue may call for acoustic treatment, closer pickup, different microphone placement, or a revised loudspeaker plan. It is related to conferencing quality, but it is not the same as a remote participant hearing their own words returned. The published guide to ceiling and table microphones explains how proximity and room acoustics change that trade.

A sustained ring or howl is feedback. Reduce the level and stop the meeting if needed. The permanent fix depends on microphone and loudspeaker placement, open microphone count, gain structure, and the room. Do not buy a microphone advertised as “feedback proof.” No microphone can make that system guarantee.

Close the loop after the echo is fixed

After a change, repeat the same outside-room test. Include quiet speech, loud speech, overlapping talk, and shared content audio. A local microphone meter moving and a speaker producing sound do not prove the far end is clean.

GTZ's conference room AV service covers room assessment, conferencing audio, cameras, displays, control, and commissioning for businesses in Pueblo, Colorado Springs, Fountain, and nearby communities. The goal is a repeatable room, with test evidence and a clear support path when someone says “I hear myself.”