These seven tests take about 90 minutes across a working week. Run them first.

The numbers you're testing against

Every platform publishes slightly different targets, but the working thresholds converge. Microsoft's network requirements documentation on Microsoft Learn is the clearest public reference, and Zoom's own guidance lands in the same neighbourhood.

Write those five numbers on a sticky note. Everything below produces a value you compare against this table.

Test 1: Measure from the room, not the closet

The most common testing mistake is running the check from a laptop in the network closet or from your desk on a different VLAN. That path skips the exact cable run, patch panel port and edge switch that the room device actually uses.

Unplug the room device, plug a laptop into the same wall port, and put it on the same VLAN. Then test. A pattern we see constantly: the closet reports clean, the room port reports 1.4% loss, and the culprit is a punched-down keystone from a build-out three tenants ago.

Run a sustained ping to a stable public endpoint for at least 15 minutes and log it:

bash

ping -i 1 -c 900 8.8.8.8 | tee room-baseline.txt

Then pull the max and standard deviation, not the average. Averages hide the exact behaviour that breaks a call. A room that averages 22ms with 180ms spikes every 40 seconds sounds terrible and tests fine on any summary dashboard.

Test 2: Test for 15 minutes, not 15 seconds

Speed test sites give you a two-second burst under ideal conditions. Meeting rooms fail over duration.

Use iperf3 against an internal server or a known-good external one, and run UDP rather than TCP, because that's what real-time media uses:

bash

iperf3 -c your-server -u -b 4M -t 900 -i 10

The -b 4M matches a realistic 1080p room stream. Watch the jitter and loss columns per interval. What you're hunting for is periodicity. Loss that appears every 5 minutes points at a backup job, an antivirus sweep or a scheduled sync. Loss that appears at 9am and 2pm points at contention.

One honest observation from doing this repeatedly: about a third of the time the offending traffic turns out to be a workstation imaging process or a cloud backup client that nobody thought of as network load.

Test 3: Read the switch port counters

Log into the edge switch and look at the interface the room lands on. You want three things.

Duplex and speed. A gigabit device negotiated down to 100 Mbps half duplex is a bad cable, a bad patch or a bad port. It will pass a speed test and destroy a call.

Error counters. CRC errors, input errors and late collisions should be zero or near zero over the port's uptime. Anything climbing means a physical layer problem, and no amount of QoS configuration fixes a physical layer problem.

Uptime. If the port has flapped recently, note when. Flap timestamps that match meeting complaints close the case immediately.

Clear the counters, wait a day, check again. Rate of change tells you more than the absolute number, because a port that's been up for 400 days will show historical errors from events long resolved.

Test 4: Audit the PoE budget properly

This is the test people skip, and it produces the strangest symptoms: devices that reboot mid-meeting, a ceiling microphone array that drops off the network at random, a touch panel that goes dark when the camera starts tracking.

The standards, in order:

• 802.3af (PoE): 15.4W at the port, about 12.95W delivered

• 802.3at (PoE+): 30W at the port, about 25.5W delivered

• 802.3bt Type 3 (PoE++): 60W at the port

• 802.3bt Type 4: 90W at the port

The trap is switch-level budget rather than port-level capability. A 24-port switch might support 802.3bt on every port and still carry a total power budget of, say, 370W. Load it with three high-draw AV devices, a dozen access points and a handful of phones and you'll exceed it. Most switches then start shedding ports by priority, silently, and the device that drops is whichever one the switch decided mattered least.

Pull the current draw per port and total allocated power. Leave 20% headroom. If you want the deeper version of this, including how power classes interact with DSCP marking on the same runs, this breakdown of PoE budgets and QoS tagging covers the switch-side configuration in detail.

Also check cable length and gauge. Long runs of thin cable lose meaningful power to resistance, and a 90-metre run near the standard's limit delivers less than a 20-metre run from the same port.

Test 5: Confirm media is going over UDP

Real-time media wants UDP. When UDP is blocked, platforms fall back to TCP or to a TURN relay, and both add latency and retransmission behaviour that audio codecs handle badly.

Verify the ports are actually open outbound:

• Microsoft Teams: UDP 3478 to 3481

• Zoom: UDP 8801 to 8810

• Google Meet: UDP 19302 to 19309

• Webex: UDP 5004 and 9000

Run a packet capture on the room port during a live call and confirm you're seeing UDP flows on those ranges rather than everything tunnelled over TCP 443.

bash

sudo tcpdump -i eth0 -n 'udp portrange 3478-3481 or udp portrange 8801-8810'

Empty output during an active call means your firewall is the problem. Fixing that costs nothing and frequently resolves the entire complaint.

While you're in there, check whether the room traffic is being SSL-inspected. Deep packet inspection on media streams adds latency and occasionally mangles them outright.

Test 6: Get room devices off Wi-Fi

Wi-Fi is fine for a laptop. It's a poor choice for a fixed device that runs 1080p bidirectional media for six hours a day and never moves.

The issues are airtime contention, roaming events between access points, and the fact that a room full of people with phones and laptops is a room full of competing clients on the same channel. A conference room device sitting at the edge of two AP cells will roam mid-call, and that roam is a 200 to 800ms gap.

Every fixed room device should be wired. If a wired run genuinely isn't possible, at minimum pin the device to a single AP, use 5GHz or 6GHz only, and give it its own SSID with WMM prioritisation.

Test it both ways if you can. Run the same call wired and wireless from the same room within an hour, and compare the platform-side quality metrics. The delta is usually obvious.

Test 7: Pull the platform's own call quality data

Every major platform records per-call telemetry, and it's better data than anything you can synthesise.

Microsoft's Call Quality Dashboard, Zoom's Dashboard under the admin panel, and the Meet quality tool in Google Workspace admin all expose per-participant jitter, loss and round-trip time. Filter to the room device, then sort by worst.

Two questions to answer from that data:

1. Is the room device consistently worse than other participants on the same calls? That points at the room's network path.

2. Is everyone on those calls degraded? That points at the WAN, the ISP or the far end.

If the room device looks clean in the platform data and users still complain, you've got an audio problem, not a network problem, and now you know where to spend.

When it actually is the hardware

Being straight about this matters. Three situations where no network fix helps:

The room is too big for the device. A single all-in-one bar covering a 20-foot table with the far talkers 18 feet from the mic array will sound thin no matter how clean the packets are. Distance beats codecs.

The room sounds bad in person. Stand in the empty room and clap once. If the decay is obvious, reverberation is your problem. A reverberation time above about 0.6 seconds needs treatment before any hardware upgrade earns its cost.

The device is out of support. Firmware that no longer receives updates will eventually break against a platform-side change, and there's no configuration that outruns that.

If you've run all seven tests and everything reads clean, then the quote in the other tab is probably justified. At that point the question shifts from network diagnostics to matching device capability to room dimensions, and this rundown of how conference room AV systems are specified by room size is a reasonable place to start scoping it.

The 90-minute version

If you only have one afternoon:

1. Wired laptop on the room port, 15-minute ping log. Check max and standard deviation.

2. Switch port counters. Duplex, errors, flaps.

3. Total PoE allocated versus switch budget. Need 20% headroom.

4. Packet capture during one live call. Confirm UDP.

5. Platform quality dashboard, filtered to the room, sorted worst first.

Those five produce enough evidence to either close the ticket or justify the spend. Both outcomes beat guessing, and one of them saves five figures.

Written by the team at Video Conferencing NY, a commercial AV and video conferencing integrator based in Manhattan. We spend a lot of time in network closets that were supposed to be someone else's problem.

The better approach is getting IT involved before the install, not after. Audio visual installation services touch network infrastructure, room acoustics and user experience all at once, and the technical side of that project deserves the same scrutiny as any other systems rollout.

Start with the network, not the hardware

Video conferencing hardware is only as good as the network it sits on. A conference room camera and codec can push a meaningful amount of bandwidth, especially with multiple rooms running simultaneously across an office. If a vendor shows up and starts mounting displays without asking about existing network topology, VLAN segmentation or QoS policies, that's a sign the install is being treated as a furniture job instead of a systems integration.

Good audio visual installation services should ask about your network before they ask about your room. Questions worth expecting: is the AV traffic going on a separate VLAN, is there PoE capacity for the endpoints being installed, and what happens to call quality if someone in the same office starts a large file transfer during a meeting. If nobody's asking these questions upfront, they'll be answered later as support tickets instead.

Acoustics are an engineering problem, not a shopping decision

It's tempting to treat audio as a spec sheet comparison, more microphones, better speakers, done. In practice, the room itself does most of the work. Glass walls, hard flooring, and open ceiling plans, all common in newer office buildouts, create reflections and echo that no amount of microphone quality fixes on its own. This is where a lot of commercial av companies differ. Some do a walkthrough and measure the space before recommending gear. Others sell a standard package regardless of room shape and hope for the best.

A short way to test this during vendor evaluation: ask how they'd handle a room with a glass wall on one side and an open ceiling. If the answer is vague or defaults straight to a product name, that's useful information before signing anything.

What "installation" should actually include

A complete install covers more ground than mounting a screen and plugging in a codec. It should include structured cabling and labeling so future troubleshooting doesn't mean tracing wires blind, calibration specific to the finished room rather than factory defaults, and testing from multiple seats, not just the seat closest to the microphone. It should also include documentation IT can actually use later, network diagrams, device IPs, firmware versions, not a generic manual that ships with the hardware.

Teams researching audio visual installation services for a New York office are usually dealing with additional constraints most vendors elsewhere never touch: high-rise elevator access, building management coordination, after-hours install windows and shared-floor logistics. Any vendor unfamiliar with navigating those specifics is going to burn time and budget relearning them on your project.

A short checklist before signing anything

Before committing to a vendor, it's worth getting clear answers on a handful of practical points. Will the vendor do a site visit before quoting equipment, or is the quote based on square footage alone? Who handles firmware updates and support once installation wraps, is that included or a separate ongoing cost? What's included in testing, does it stop at "the light turned green" or does it include a live call from every seat in the room? And who's responsible if the finished install doesn't meet the network or security requirements IT actually needs?

None of this is about distrust of vendors generally. It's about recognizing that a conference room is now part of the technical stack, not separate from it. The rooms that get used consistently are the ones where someone thought through the network load, the room acoustics and the day-to-day support burden before a single cable got run. The rooms that get avoided are usually the ones where none of that happened, and everyone just quietly stopped scheduling meetings in the room with the bad camera angle.

If IT is going to inherit the support burden either way, it's worth being in the room for the decision that created it.

The gap isn't always obvious until someone points it out. A client dials in and can't hear half the room. A remote employee spends the meeting staring at the back of someone's head because the camera never adjusted. A presentation won't cast to the screen, so the meeting starts fifteen minutes late while someone hunts for the right cable. None of these problems are dramatic on their own, but they add up to a workplace where people quietly start avoiding video calls altogether, which defeats the entire purpose of hybrid work.

The audio problem nobody notices until it's fixed

Ask any office manager what breaks meetings and audio comes up before video almost every time. A camera that's slightly blurry is forgivable. A voice that cuts in and out, or a room with an echo that makes every sentence sound like it's underwater, is not. People stop contributing when they're not sure they'll be heard clearly, and remote participants disengage fast when they have to strain to follow the conversation.

Good audio isn't about buying the most expensive microphone on the market. It's about placement, room acoustics and calibration that accounts for hard surfaces, glass walls and the specific shape of the space. A room with soft furniture and carpet behaves completely differently from one with exposed brick and floor-to-ceiling windows, which is common in a lot of converted New York office space. Fixing this properly usually means someone actually walking the room before recommending equipment, not just shipping a box of gear and hoping for the best.

Video that makes remote employees feel present, not tacked on

The second piece is video, and this is where a lot of offices cut corners. A single wide-angle camera mounted above the screen can work in a small huddle room, but it falls apart in anything larger. People at the far end of the table become tiny, unreadable figures, and remote participants end up watching a meeting rather than joining one. The fix isn't always more expensive hardware. Sometimes it's camera placement, sometimes it's a second camera for a longer room, and sometimes it's simply better lighting so the existing camera has something usable to work with.

This is where the real value of professional video conferencing installation comes from. The equipment matters, but the assessment that happens before anything gets installed matters more. Companies offering video conferencing solutions in New York that actually visit the space first tend to avoid the mismatch between what a room looks like on paper and how it performs once real meetings start happening in it.

Why the installation itself is half the outcome

Even the right equipment underperforms when it's installed poorly. Cables run loose across the floor, mounts at awkward angles, systems that were never calibrated to the room they sit in, all of this shows up as unreliability months later, not as a defect on day one. This is the part that's easy to underestimate when a business is comparing quotes on equipment alone.

Working with an established AV installation company in NY that treats installation as an engineering process rather than a delivery job tends to produce systems that keep working long after the initial setup. That includes proper cable management, testing from every seat in the room and training so staff can run the system without calling IT every time. It's the difference between a room that works on the day it's commissioned and one that keeps working two years later.

What this means for offices planning an upgrade

None of this requires ripping out an entire office and starting over. Most upgrades start with a single problem room, the one everyone complains about, and expand from there once the improvement is obvious. Start by identifying whether the issue is audio, video, connectivity or a combination of all three, then bring in someone who assesses the space before recommending equipment. A room that's designed around how a team actually works, rather than around a generic package, is the one that gets used instead of avoided.

Hybrid work isn't going away in New York offices, and the businesses getting the most out of it are the ones treating their meeting rooms as infrastructure rather than furniture. Getting that right starts with a proper site visit, not a product catalog.