Conference Room AV Troubleshooting: Video Call Fixes

Why Video Calls Fail in Conference Rooms

A video call that works perfectly on a laptop at someone's desk can fall apart the moment it moves into a conference room. More hardware means more failure points: a room camera, a ceiling mic array, a soundbar, an HDMI switcher, a Zoom Room or Teams Room console, and the network gear tying it all together. When one link breaks, the whole call breaks with it, and it usually happens right as the meeting starts.

Most conference room AV failures fall into five categories: no audio, no video, echo or feedback, frozen or lagging video, and connection drops. Each has a handful of likely causes, and most of them can be fixed in under five minutes without calling IT, if you know where to look first. This guide walks through the most common failures room by room, what causes them, and the fastest fix for each, plus when a problem points to something bigger than a quick reset.

These issues get more frequent as rooms scale up. A huddle room with one screen and a webcam has far fewer things that can go wrong than a 30-person room running dual displays, a ceiling mic array, and a dedicated room PC. If your team is troubleshooting the same room repeatedly, that's often a sign the room's AV setup doesn't match its actual size rather than a hardware defect.

No Audio: The Most Common Failure

Audio problems account for a large share of conference room support calls, and they're usually caused by the wrong device being selected, not a broken speaker. Here's the troubleshooting order that resolves most cases fastest:

• Check the input/output device in the call software. Zoom, Teams, and Google Meet all default to whatever audio device the OS last used. If someone plugged in a laptop and the room defaulted to the laptop's internal speaker instead of the room's soundbar, remote participants hear nothing from the room's mics.
• Confirm the mic isn't muted at the hardware level. Many ceiling mic arrays and tabletop mics have a physical mute button or LED indicator separate from the software mute. A room mic muted at the hardware level won't respond to unmuting in the call software.
• Check volume on the room's amplifier or soundbar, not just the laptop. Conference rooms often run a separate volume control on the AV rack that's independent of the in-call volume slider. If that's turned down or set to zero, no amount of adjusting in Zoom will help.
• Reseat the HDMI or USB cable feeding the room's audio. A loose HDMI connection can drop audio while keeping video active, which confuses people because the picture looks fine.

If audio works for people in the room but not for remote participants (or the reverse), the issue is almost always device selection in the call software, not a hardware failure. That's the fastest thing to check first.

A room-side view of a video call in progress. Most call failures trace back to a handful of predictable causes. Photo: Walls.io / Unsplash.

No Video, Frozen Video, or Lag

Video problems split into two different issues that get mistaken for each other: a camera that isn't sending a picture at all, and a camera feed that's choppy, frozen, or lagging behind audio. They have different causes.

No video signal usually means a source selection or cable problem. If the room display shows a blank screen or "no signal," check that the display is set to the correct HDMI input, especially in rooms with multiple sources (a room PC, a laptop input, and a wireless presentation receiver all fighting for the same screen). Also check that the camera isn't physically covered by a privacy shutter, a feature built into most PTZ and conference cameras that some users forget exists.

Frozen or lagging video almost always points to bandwidth, not the camera itself. A 4K PTZ camera streaming over a congested Wi-Fi network will stutter even though the hardware is fine. The fix is usually one of three things: switch the room's video codec device to a wired ethernet connection instead of Wi-Fi, close other bandwidth-heavy applications running on the same network, or lower the call's video resolution setting if the platform allows it. Most enterprise video platforms recommend at least 3-4 Mbps upload and download per active video stream; a room running dual displays and screen share can need more than that.

If lag happens consistently at the same time of day, that's a strong signal the office network hits a bandwidth ceiling during that window, not a hardware fault in the room. IT teams can usually confirm this by checking network utilization logs rather than swapping equipment.

Echo, Feedback, and Audio Loops

Echo is one of the most disruptive failures because it makes a call nearly unusable for everyone, not just the room having the problem. It has a short list of usual causes:

1. A laptop joined the same call as the room system. This is the single most common cause of echo in conference rooms. If someone in the room also joins the meeting on their own laptop "just in case," their laptop mic picks up the room speakers and creates a feedback loop. The fix is simple: only one device per room should be connected to the call.
2. Mic placement too close to a speaker. Tabletop mics placed directly next to a soundbar or speaker will pick up the room's own output and echo it back. Ceiling mic arrays are less prone to this because they're positioned away from the speakers, which is one reason larger rooms benefit from ceiling-mounted rather than tabletop mic setups.
3. Echo cancellation not enabled or malfunctioning. Most professional conference room mics and soundbars run built-in acoustic echo cancellation (AEC), but this can fail if firmware is outdated or if the device is used outside its rated room size, like a small soundbar overdriven in a room too large for it.

A quick diagnostic: if the echo disappears when everyone but the room system drops off the call, a duplicate device connection was the cause. If it persists with only the room system connected, look at mic placement or AEC settings next.

Loose cables and outdated firmware cause more conference room failures than defective hardware. Photo: Brian Wangenheim / Unsplash.

Connection Drops and Meetings That Won't Start

A call that drops mid-meeting or a Zoom Room/Teams Room console that won't launch the meeting at all is usually one of three things: a network issue, an expired login or calendar sync problem, or an overdue firmware update.

If the room console can't find the scheduled meeting, check that the room's calendar account is still synced correctly; a common failure mode after a company switches calendar systems or updates SSO settings. If the console shows "no upcoming meetings" but the meeting clearly exists on someone's calendar, the room's calendar integration has likely lost its connection and needs re-authentication, not a hardware fix.

Mid-call drops that happen repeatedly in the same room, especially at the same time each day, point to network congestion rather than a one-off glitch. Wired connections are far more stable than Wi-Fi for room systems; if a room's codec or console is still running over Wi-Fi, moving it to a wired ethernet drop resolves a large share of recurring drop issues.

Outdated firmware is an underrated cause of instability. Most enterprise room systems, Poly, Logitech, Yealink, and Crestron alike, release regular firmware updates that fix exactly these kinds of bugs. A room that hasn't been updated in six months or more is more likely to have unresolved stability issues that a five-minute update would fix. If your organization doesn't have a routine firmware update schedule for conference rooms, that's worth setting up alongside your regular AV maintenance.

When to Stop Troubleshooting and Call for Support

Most of the fixes above take less than five minutes and don't require a technician. But some patterns mean the room needs a real inspection rather than another reset:

• The same failure happens in the same room more than twice in a month, regardless of who's running the meeting.
• A problem persists after checking device selection, cables, mute status, and network connection.
• Hardware is more than 4-5 years old and increasingly unreliable, a sign it's nearing end of life rather than having an isolated fault.
• A big meeting (board presentation, all-hands, client pitch) is coming up and the room hasn't been reliable recently. It's worth a pre-check rather than hoping it holds together.

For high-stakes meetings, many companies bring in short-term rental gear as backup rather than risk an unreliable permanent room setup. A rented PTZ camera, wireless mic, or portable soundbar can cover a critical meeting while the permanent room system gets serviced, and it means one flaky HDMI port doesn't sink a client pitch. If your team is repeatedly troubleshooting the same conference room, it may be more cost-effective to have it professionally assessed and, if needed, temporarily supplemented with rental AV equipment than to keep losing meeting time to the same failure.

Frequently Asked Questions

Why does our conference room camera keep freezing during calls?

Frozen video is almost always a bandwidth problem, not a camera defect. Check whether the camera or room codec is connected over Wi-Fi rather than wired ethernet, and see if other bandwidth-heavy activity is happening on the same network during the freeze. Switching to a wired connection resolves most recurring freeze issues.

Why can people in the room hear remote participants but remote participants can't hear us?

This points to the room's microphone, not the speakers. Check that the correct mic is selected as the input device in the call software, confirm the mic isn't muted at the hardware level (separate from the software mute), and reseat the cable connecting the mic to the room's AV rack.

Related: see our guide to choosing the right microphone type for different room sizes and use cases.

How do we stop the echo when someone joins on their laptop too?

Have that person leave the call on their laptop and stay connected only through the room system. A laptop mic picking up the room's own speaker output is the most common cause of conference room echo, and it resolves the moment the duplicate device disconnects.

Should we reset the whole room system when a call fails?

Not as a first step. A full reset can fix some issues but also clears configuration and can introduce new problems. Start with the specific fix for the symptom (device selection, cable check, network connection) and only reset the full system if targeted fixes don't resolve it.

How often should conference room AV firmware be updated?

Check for updates at least quarterly. Manufacturers like Poly, Logitech, and Crestron regularly patch stability and connectivity bugs, and rooms running firmware more than six months out of date see a disproportionate share of avoidable call failures.