Your AV System Lives on the Network Now: Who Owns Your Networked AV Systems?

Modern AV systems are network endpoints, and most support failures are ownership failures. Here's what AV and IT have to settle before install: VLANs, PoE budget, multicast, security review, and why the cleanest answer is one accountable party.

---

Somewhere right now there is a ticket that reads: "Conference room B won't join the call."

It gets assigned to IT. IT looks at it, determines the network is fine, and reassigns it to the AV vendor. The AV vendor remotes in, finds the codec can't reach its cloud service, and says it's a network issue. It goes back to IT. Two days later somebody power-cycles the switch and it works, nobody knows why, and the room is quietly labeled "flaky" by everyone who has to book it.

That loop is not a technology failure. It's an ownership failure, and it exists because the system was split across two organizations that answer to different people and have no shared definition of "done."

What Actually Changed With Networked AV Systems

A conference room used to be a display, a cable, and maybe a speakerphone. Today a well-equipped room is a collection of network endpoints: the codec or room PC, a PoE camera or three, a DSP, network-attached amplifiers, a scheduling panel outside the door, an occupancy sensor, a control processor, a touch panel, and displays with their own management agents. Audio increasingly runs as Dante or AES67. Video may run as AV-over-IP.

It is entirely normal for one modern conference room to put fifteen to thirty devices on the network. Multiply that by a floor. Nobody planned for that in the switch count.

That is the reality of networked AV systems. The old division of labor, where AV hangs the hardware and IT owns the wire, describes a building that no longer exists. The wire is the system.

The Five Things That Have to Be Settled Before Install

1. VLAN Design and Segmentation

AV traffic gets its own VLAN, or several. This isn't preference; networked audio protocols have real requirements that generic office VLANs don't meet.

Dante and AES67 need QoS configured with the correct DSCP markings so clock traffic is prioritized above audio, and audio above everything else. They need PTP clock traffic to pass cleanly. They need IGMP snooping with an active querier so multicast doesn't flood the segment. And Energy Efficient Ethernet needs to be disabled on those ports. EEE's power-saving behavior introduces exactly the kind of jitter that breaks clock sync.

Get these wrong and the symptom is not "no audio." The symptom is intermittent clicks and dropouts that appear three weeks after go-live and take a week to diagnose.

2. PoE Budget, Not Just PoE Ports

This is the most common miss.

A 48-port PoE switch does not deliver maximum power to 48 ports. It has a total power budget, often somewhere between 370W and 740W, shared across all of them. A single 802.3bt Type 3 device can draw up to 60W at the port, and Type 4 up to 90W. Fill a switch with PTZ cameras and PoE displays and you'll exhaust the budget well before you exhaust the ports.

Count the devices, add their actual draw, and size the switch to that number with headroom. Then decide whether those switches are on UPS, because a room that loses its cameras during a building power blip is a room that fails during exactly the meeting that mattered.

3. Bandwidth and Multicast

Uncompressed video over IP is bandwidth-hungry. A single stream can consume most of a gigabit link, and higher formats push you to 10G infrastructure. Lightly compressed transports reduce that substantially at a small latency cost.

Either way, most AV-over-IP is multicast, and multicast on an unprepared network is a broadcast storm with extra steps. IGMP snooping, a querier on the VLAN, and appropriate uplink sizing are prerequisites, not optimizations.

The design question is whether the system shares the production network, rides a dedicated VLAN on shared hardware, or runs on physically separate switching. All three are legitimate answers, and the right one depends on the building, the budget, and the risk tolerance. What isn't legitimate is discovering that nobody chose.

4. Security Review: Start It Early

Every one of those endpoints is an IoT device on the network, and the security team will eventually treat it that way. Reasonably.

Default credentials have to be changed and documented somewhere that isn't a sticky note in the rack. Firmware needs an update path and an owner. Cloud-managed devices phone home, which means somebody has to approve the outbound destinations and understand what data leaves. Management portals need SSO and MFA. Some organizations require a full vendor security assessment before a single device is racked.

That review takes weeks. It routinely gets started the month before go-live, and then the project waits on it.

5. Identity, Licensing, and Enrollment

Microsoft Teams Rooms and Zoom Rooms aren't just hardware. Each room needs a resource account, a license, a calendar mailbox, and often device management enrollment. Those are deliverables with their own procurement and provisioning lead times.

If they don't exist on install day, the rack is finished and the rooms still don't work, and the schedule slips for reasons that have nothing to do with the AV system.

The Ownership Question

Every item above sits on the seam between two disciplines. That seam is where projects lose weeks and where support tickets go to die.

Before go-live, these need answers on paper, with names attached:

• Who owns the switch the AV devices are on?

• Who applies firmware updates to the DSP, the codec, and the cameras, and on what cadence?

• Who holds administrative credentials, and where are they stored?

• Who is the first call at 8:58 AM when a room won't start a meeting, and what's the escalation path?

• What's covered under the AV agreement, what's covered under IT, and what falls between them?

Most organizations have never written this down. Writing it down is worth doing regardless of who ends up in each box.

But the cleaner structural answer is to reduce the number of boxes. When the same partner designs the networked AV systems, specifies and configures the switching that carries them, handles the security documentation, and holds the support agreement, the seam disappears because there's no second organization to hand the ticket to. The room either works or it's one company's problem.

That isn't the right model for everyone. Organizations with strong internal network teams often want to own their own infrastructure, and they should. The point isn't that AV integrators should run your network. It's that somebody has to be accountable for the whole path from the microphone to the far end, and if that accountability is split, the split is where the failures live.

Rooms That Report Their Own Failures

The last piece worth budgeting: remote monitoring and management.

Modern AV platforms report device health, offline status, filter and lamp hours, firmware drift, and whether a display actually powered on this morning. A monitored room tells you it's broken before a user does. An unmonitored room gets discovered by whoever walks in for the 9:00.

Across more than a handful of spaces, that shifts support from reactive to scheduled, which is where the real operational savings are. But it requires somebody actively watching. Monitoring nobody reads is just logging.

As networked AV systems become more common, the ownership question becomes harder to ignore. The technology may span AV, IT, networking, security, and cloud services, but somebody still has to be accountable for the complete path from the room to the far end.