No Audio or Echo in Meeting Room: 7 Fixes
Most 'no audio' and echo problems are not faults - they are muted mics, sleeping speakers, or the wrong device selected in Teams or Zoom, and they clear in under a minute.
Start at the room console: check the hardware mute isn't lit, wake the system, and reseat cables. The seven fixes below run from most to least common.
Work top to bottom - most common causes first
1. The mic or speaker is muted, or the device is asleep
A red ring or button glows on the video bar, mic pod or ceiling mic, or the room screen shows a crossed-out microphone icon. The touch panel is dark and hasn't woken up for the call.
- 1Look for a lit red mute indicator on the video bar, mic pod or ceiling mic and press it once to unmute.
- 2Wake the console or touch panel by tapping the screen or stepping in front of the camera.
- 3Check the in-call software itself (the Teams Rooms or Zoom Rooms on-screen controls) for its own mute toggle - hardware mute and software mute are separate, and both need to be off.
- 4If a wireless mic pod is unmuted but still silent, check its battery or charge indicator.
If every mute indicator is off and there's still no sound, move on to checking cables and device selection rather than assuming it's fixed.
2. A cable, power supply or USB connection has come loose
The video bar, speaker or mic pod shows no power light, or a device drops out mid-call.
- 1Check the video bar, speaker and mic pod all show a power light.
- 2Reseat the USB cable at both ends (the device and the console or room PC) - a loose or faulty USB connection is the single most common physical cause.
- 3If the mic or speaker is plugged into a USB hub, connect it directly to the room PC or console instead; hubs can starve power-hungry audio peripherals.
- 4Check any PoE injector or power adapter feeding a ceiling mic or speaker has a live light.
If all lights are on and every cable is firmly seated but audio still fails, the fault is more likely a software setting - check which device is selected in the app next.
3. The app has the wrong microphone or speaker selected
Audio works fine on the room screen or laptop itself but not inside the call, or it works one way only - you can hear the far end but they can't hear you, or the reverse.
- 1Open the in-call audio settings menu inside Teams or Zoom (not general Windows or macOS sound settings) and check the microphone and speaker dropdowns show the room's actual hardware, not 'Default' or a laptop's built-in mic.
- 2If joining from a personal laptop plugged into the room screen, manually select the room's USB or Bluetooth speaker and mic rather than the laptop's own.
- 3On a dedicated Teams Rooms or Zoom Rooms system, restart the conferencing app on the console - it usually re-selects the correct devices automatically.
- 4An IT admin can check the room PC's sound settings to confirm the correct device is set as default and that nothing unrelated (like a monitor's HDMI audio) has been picked instead.
If the right devices are selected and confirmed but the fault continues, check for a two-device echo loop or a feedback issue next.
4. Two devices have joined the same meeting in the same room
Echo only happens when a specific person also has the meeting open on their own laptop or phone in the room.
- 1Ask everyone in the room to check they haven't also joined the same meeting from their own laptop or phone.
- 2If someone needs their laptop for screen content, have them join without their laptop's audio (many platforms offer a 'phone call' or 'no audio' join option), using only the room system for sound.
- 3Also check no other device, such as a personal headset still paired to the room panel or an old dial-in, is still connected to the call.
If only one device is in the call and the echo persists, it's more likely feedback from mic placement or volume - check that next.
5. Microphone placement, gain or volume is causing feedback
A whine, hum or echo that gets worse as the volume increases, or an echo the far end hears but the room itself doesn't notice.
- 1Move the microphone or mic pod further from the room's loudspeaker, and keep any personal laptop speakers well away from the room mic.
- 2Turn the room speaker volume down a few notches - loud output feeding back into the mic is the most common live cause of echo.
- 3If using a soundbar, keep it centred under the screen at roughly seated ear height and away from ceiling mics that could pick up its output.
- 4An IT admin or installer can check the microphone gain hasn't been set too high in the device's admin settings.
If placement and volume are already reasonable and the echo continues, suspect a software conflict grabbing the audio device.
6. Another app or a Windows exclusive-mode setting has taken over the audio device
Audio works normally until another app plays sound, then the meeting goes silent; or the microphone works in one app but not another on the same room PC.
- 1On the room PC, go to Settings > System > Sound > Advanced > More sound settings, right-click the room's microphone and speaker, open Properties > Advanced, and untick 'Allow applications to take exclusive control of this device' for each.
- 2Close any other app that might be using the microphone or camera, such as a second conferencing app or a recording tool.
- 3Restart the room's conferencing app so it reclaims the correct devices.
This step needs IT admin access to the room PC. If exclusive mode is already off and the fault repeats, log it as a recurring issue rather than retrying the same fix.
7. The room system needs a restart or a pending update
The problem has built up gradually over days or weeks, or started right after an update; the console feels sluggish or unresponsive.
- 1Restart the room console or touch panel - Teams Rooms systems typically restart nightly in a maintenance window and Zoom Rooms weekly (by default Saturday overnight), so a manual restart now can clear a stuck audio driver without waiting for the next scheduled one.
- 2An IT admin can check the device's health status in the Microsoft Teams Rooms Pro Management portal (separate from the general Teams admin center) or the Zoom Rooms dashboard, and apply any pending firmware or app update.
- 3After updating or restarting, make a quick test call before the next real meeting to confirm audio is working both ways.
If a fresh restart and up-to-date firmware still leave the same fault, treat it as a hardware issue and get it looked at.
Vendor-specific quirks worth knowing
Neat: On Neat Bar, Bar Pro, Board and Board 50, an LED that stays permanently red after boot (rather than briefly then turning white) is abnormal. Try a factory reset before assuming the microphone is faulty, and raise a support ticket with the serial number if it persists.
HP Poly: Poly's mute LED only reflects the meeting's mute status if the Poly device's own microphone is the one selected in your call software. If a different mic is selected, the light won't match reality - and echo cancellation only works properly if Poly's speaker is also selected as the output.
Cisco: On Room Kit, Board and Desk devices paired with a non-Cisco USB microphone system, leave echo cancellation switched off on the Cisco device itself and let the external audio system handle it. Cisco requires this for non-asynchronous USB audio - the device flags 'USB microphone not supported' otherwise - and running two echo cancellers on the same audio path is poor practice that risks echo and audio artefacts.
Logitech: Rally mic pods need correct spacing to avoid feedback and coverage gaps: Logitech's placement guide recommends the first pod sit around 12 feet from the video bar, with each additional pod spaced about 8 feet apart for overlapping pickup.
When to stop and call an engineer
- ·The fault returns in the same room across multiple meetings after you've checked mute states, cables and device selection - a recurring fault points to a failing mic, speaker or codec rather than a one-off glitch.
- ·A cable, power supply or connector shows physical damage, exposed wiring or a burning smell - stop using it immediately and call an engineer for safety, don't attempt a self-repair.
- ·The device is still inside its manufacturer or MAV Reality warranty period, where opening it or attempting a repair yourself could void that cover.
- ·Audio fails on every platform tested (Teams, Zoom and a standalone dial-in are all affected) - this points to a room-wide hardware or network fault rather than a single app's settings.
- ·The fix requires admin access to the Teams admin center, Zoom Rooms dashboard or room PC that you don't have, and the room needs to be working again before someone with that access is available.
We support all five major vendors - Neat, HP Poly, Logitech, Yealink and Cisco - and it doesn't matter who installed the room. Tell us what you're seeing and an engineer will take it from here.