Meeting Room Audio Crackling or Cutting Out? Fix It
Crackling, popping or dropping audio is almost always a connection problem, not a broken microphone.
Do the three easy checks first: push every cable in fully, power-cycle the one misbehaving device, and ask whether anything changed on the network recently. The fixes below then work through the deeper causes in order.
Work top to bottom - most common causes first
1. A cable has worked loose, at either end
Check if it happens more when someone moves the table, brushes a cable, or if it started right after furniture or cabling was touched.
- 1Trace the cable from the affected mic or speaker back to its wall plate, table box or the room's AV rack/credenza.
- 2Check both ends - the connector at the device and the connector at the wall plate or rack are equally likely culprits.
- 3Unplug and firmly reseat every connector in that run, including any joiners or extension couplers.
- 4Look for a cable that's kinked, trapped under furniture, or visibly damaged where it exits a cable channel or floor box.
- 5If the room uses table boxes with captive cables, check the box hasn't come loose from the table's central connection point.
If the crackling continues after every connector in the chain has been reseated, the fault is unlikely to be a loose cable and points to the device or its power/network feed instead.
2. The one affected mic or speaker just needs a restart
This fits when only one device in an otherwise multi-mic or multi-speaker room is affected while everything else works normally.
- 1Identify exactly which single unit is misbehaving - don't restart the whole room system yet.
- 2Disconnect that device's power (or pull its Ethernet/USB cable if it's powered over the cable) for at least 10-15 seconds.
- 3Reconnect and give it 60-90 seconds to fully boot and rejoin the system before testing again.
- 4If the room uses a central codec or hub (the box under the table or in a rack), power-cycle that too if restarting the one device alone doesn't help.
- 5Test with a fresh call rather than just talking in the room, so you can hear it from the far end.
If the same single device is silent or crackling again within a few minutes of restarting, or the fault has moved to a different mic, that points to a hardware or wiring fault on that device rather than something a restart can clear.
3. Something changed on the network recently
Worth asking before touching hardware: did IT install a new switch, run a firmware update, change VLANs, or do cabling work in the last few days?
- 1Ask IT or facilities whether any network switches, cabling, or Wi-Fi access points near the room were touched recently.
- 2Ask whether a Windows update, Teams Room firmware update, or device firmware push happened around the time the problem started.
- 3Check whether the issue affects just this room or several rooms on the same switch or network segment - several rooms at once points to a shared network cause rather than one faulty microphone.
- 4If a change is confirmed, ask whether it can be rolled back, or whether your AV support provider was consulted before it was made - networked microphones are often sensitive to switch settings that seem unrelated to audio.
If nothing changed on the network and the fault is isolated to this one room, move on to the device-specific checks below rather than continuing to chase a network cause.
4. A USB cable or hub is the problem (USB microphones and speakerphones)
Common in huddle rooms and smaller spaces using a USB tabletop mic, USB speakerphone, or a hub feeding several devices into the room PC or Teams/Zoom appliance.
- 1Plug the microphone directly into a USB port on the computer or room appliance, bypassing any hub, dock or extension cable, and test again.
- 2If that fixes it, the hub or extension is the fault - swap in a powered hub (one with its own mains power supply) rather than a cheap unpowered one, since USB ports alone often can't supply consistent power for audio devices.
- 3Move the microphone to a different USB port, ideally one on a different internal USB controller (rear ports on a desktop, or a different side of a laptop, are often on separate controllers).
- 4Check what else shares that USB hub or port - webcams, extra mics or storage devices competing for the same USB bandwidth can cause exactly this crackling and dropout pattern.
- 5Try a shorter or known-good USB cable - extension cables, especially longer or coiled ones under a table, are a common point of failure.
If the crackling follows the microphone even when it's plugged straight into the computer with a fresh cable and no hub, the fault is more likely in the microphone itself or the computer's audio drivers - see the firmware/driver cause below.
5. Wireless mic interference or a low battery
Applies to handheld, lapel or tabletop wireless microphones (not fixed ceiling or wired table mics) - listen for crackling that gets worse as the meeting goes on, or the mic cutting in and out as people move.
- 1Check and replace or recharge the microphone's battery first - a wireless mic on a low battery often keeps transmitting but with a weaker signal, which shows up as crackling or dropouts rather than the mic simply switching off.
- 2Check whether the number of wireless devices nearby has increased - extra laptops, phones on a Wi-Fi hotspot, new Wi-Fi access points, or Bluetooth devices all share the same radio spectrum as wireless mics and can cause interference.
- 3Move the receiver or base station away from walls, other electronics and Wi-Fi access points where possible.
- 4If your mic system lets you scan for a clearer wireless channel, run a scan and switch to a less congested one.
- 5Note whether dropouts correlate with a time of day or nearby equipment use - intermittent sources such as microwave ovens can cause intermittent-looking mic dropouts.
If dropouts continue on a fresh battery with no obvious increase in nearby wireless devices, ask IT to check whether nearby Wi-Fi access points overlap the mic's frequency range - this needs access to both the Wi-Fi controller and the mic system's channel settings, so it's a good point to loop in your AV support provider.
6. A firmware or software mismatch between the room's devices
Worth suspecting if the problem started right after any device in the room, the PC, or the room's software updated itself, and reseating cables or restarting didn't help.
- 1Check Windows Device Manager (or the room appliance's admin/settings menu) for any audio device shown with a warning icon, or listed as an unknown or generic device.
- 2Check whether the microphone or speakerphone manufacturer has published a firmware update for that model, and whether it's been applied.
- 3If several devices in the room (mic, speaker, codec, room PC) are from the same manufacturer's ecosystem, check they're all running compatible, currently supported firmware versions rather than a mix of old and new.
- 4Update one device at a time and test in between, rather than updating everything at once, so you can tell which change actually fixed things.
Firmware and driver updates need admin rights on the room PC or the device's management portal, and getting an update wrong can take a working room offline - if you don't have that access, this is a job for IT or your AV support provider rather than something to try live before a meeting.
7. The room's mics and speakers talk to each other over the network - and something in that link has failed
Most likely in rooms with several ceiling mics, several speakers, or mics and speakers from different points in the room all feeding into one system - if the fault sticks to one specific mic or zone while others are fine, or comes and goes in a pattern that doesn't match cables or Wi-Fi, this is often the cause.
- 1Note whether the crackling or dropout affects one specific mic or zone consistently, or seems to move around - this detail is useful to whoever investigates.
- 2Check whether the room's audio and video devices sit on a dedicated network switch, and whether that switch has had any recent changes (see the network-change check above).
- 3Don't attempt to change switch settings, network timing/clock settings or VLAN configuration yourself - these systems keep every device in the room in sync down to fractions of a millisecond, and a single misconfigured switch port or a setting called Energy Efficient Ethernet can cause exactly this kind of intermittent crackling and dropout without showing up as a hard fault.
- 4This needs your AV integrator to log in with the system's own diagnostic software (for example Dante Controller on Audinate Dante-based installs) to check the health and clock sync status of every device's network audio connection - it isn't visible from the microphone or speaker itself.
This is the point to stop self-diagnosing and call it in - if cables, power-cycling, network changes, USB, wireless and firmware have all been ruled out and the fault remains (especially if it sticks to specific mics/zones or spans several rooms sharing infrastructure), it's a networked-audio configuration fault that needs an engineer with the right diagnostic access, not something fixable from inside the room.
Vendor-specific quirks worth knowing
Shure: Shure's MXA ceiling array microphones run over a wired, PoE-powered network connection carrying networked audio - there is no wireless option, and Shure strongly recommends a gigabit-capable managed switch. A general office network segment isn't a substitute for a properly configured AV network: connecting one to an unmanaged switch, or a switch with Energy Efficient Ethernet (802.3az) enabled, is a common and well-documented source of exactly this crackling/dropout pattern.
Sennheiser: Sennheiser's own support guidance for wireless systems (e.g. ADN-W, XSW D) recommends scanning the local Wi-Fi spectrum and coordinating channel choice with IT rather than assuming interference can't be fixed - both the 2.4GHz and 5GHz bands used by these systems are shared with Wi-Fi, Bluetooth and other devices.
Poly: Some Poly speakerphone and expansion-mic pairings have a documented limitation where the microphones on one paired unit stop working while the rest of the device keeps functioning normally - this looks exactly like a single dead mic but is a pairing/compatibility issue rather than a hardware fault.
Logitech: Logitech Rally Mic Pods cannot be daisy-chained when fitted in ceiling pendant mounts - multiple pods in that mounting style need a Mic Pod Hub instead, so a pod behaving differently to its neighbours can point to an installation that skipped the hub.
Yealink: Yealink's expansion microphones are designed to be daisy-chained together, which means on a Yealink system a broken link partway along the chain can silence every mic downstream of that point, not just the one closest to the fault.
When to stop and call an engineer
- ·The fault is isolated to one mic or zone in a room with several networked mics or speakers, and reseating cables plus a power-cycle hasn't fixed it - this points to a network-audio configuration fault that needs specialist diagnostic software to see.
- ·The problem affects several rooms on the same network switch at the same time - a shared network cause needs someone with switch access, not device-level troubleshooting.
- ·You need to update firmware or drivers on a room PC or device and don't have admin rights to do it safely.
- ·Dropouts started right after AV or network cabling work and reseating cables hasn't resolved it - there may be a wiring or termination fault behind a wall or in the ceiling void.
- ·Wireless mic interference persists after a fresh battery and checking nearby Wi-Fi and Bluetooth devices - this needs coordinated access to both the Wi-Fi controller and the mic system.
- ·The same device keeps failing repeatedly even after a replacement cable and a clean restart - this suggests a hardware fault that needs a warranty check or service exchange.
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.