AV-over-IP Is Mainstream. So Why Are Projects Still Breaking?

AV-over-IP is no longer experimental.

It’s no longer “the future.”

It’s the default architecture in most mid-to-large corporate AV deployments.

Yet something interesting is happening in the field:

Projects still fail.

Not because AV-over-IP doesn’t work.

But because the network it depends on wasn’t designed for it.

 

---

AV-over-IP Didn’t Replace Infrastructure, It Merged With It

Traditional AV lived in isolation.

Dedicated matrices.
Dedicated cabling.
Limited dependency on enterprise IT.

AV-over-IP changed that.

Now:

• Endpoints live on corporate VLANs
  
• Multicast traffic shares switches
  
• QoS policies matter
  
• Network segmentation impacts performance
  
• Firmware updates affect security posture

AV is no longer a parallel system.

It’s riding on the same backbone as everything else.

And that’s where friction begins.

 

---

The Real Issue: Network Assumptions

Most enterprise networks were not designed with AV multicast traffic in mind.

Common issues we continue to see:

• Multicast disabled or misconfigured
  
• IGMP snooping inconsistently implemented
  
• QoS not properly aligned with AV traffic
  
• Insufficient bandwidth planning for video streams
  
• No documentation of AV VLAN segmentation

From the IT perspective, the network is stable.

From the AV perspective, performance is inconsistent.

Neither side is wrong.

But neither side planned together.

 

---

AV and IT Are Solving Different Problems

IT optimizes for:

• Security
  
• Stability
  
• Standardization
  
• Risk control

AV optimizes for:

• Low latency
  
• Visual reliability
  
• Immediate user experience
  
• Demo-day performance

When AV-over-IP enters a corporate environment without early architectural alignment, tension is inevitable.

Because the objectives are not identical.

 

---

The Hidden Risk: Late-Stage Coordination

In many projects, AV network requirements are introduced too late:

• After switch selection
  
• After VLAN architecture is defined
  
• After security policies are locked
  
• After firewall rules are finalized

At that point, workarounds begin.

Temporary fixes.

Isolated switches.

Exceptions to policy.

And every exception adds fragility.

 

---

AV-over-IP Doesn’t Fail. Planning Does.

The technology is mature.

The standards are established.

The hardware is stable.

What breaks projects is:

• Lack of early IT involvement
  
• No shared documentation framework
  
• Assumptions about bandwidth and multicast
  
• Undefined ownership of monitoring

AV-over-IP is not a product decision.

It’s a network architecture decision.

And architecture must be coordinated from day one.

 

---

What Mature Projects Are Doing Differently

Organizations that are succeeding with AV-over-IP typically:

• Involve IT in pre-design workshops
  
• Define AV traffic profiles early
  
• Document VLAN and multicast strategy clearly
  
• Align QoS policies before installation
  
• Plan for monitoring and lifecycle management

They treat AV-over-IP as infrastructure.

Not as equipment.

 

---

The Industry Is in a Transition Phase

AV-over-IP is mainstream.

But operational maturity hasn’t caught up everywhere.

The convergence between AV and IT is real.

What’s still evolving is how organizations plan for that convergence.

The question is no longer:

“Does AV-over-IP work?”

The real question is:

“Is your network designed for it?”