Audio-visual systems have moved well beyond dedicated AV cables and isolated equipment racks.

Today, microphones, DSPs, amplifiers, speakers, conferencing systems and other AV devices can communicate across standard Ethernet networks. That shift brings AV much closer to the world of IT.

For IT managers, this creates a new responsibility. AV decisions may now involve VLANs, QoS, multicast traffic, IP addressing, switching, network security and monitoring.

One technology that has become particularly important in professional networked audio is Dante networking.

Dante, developed by Audinate, uses standard IP networking to transport and manage digital media between compatible devices. Audinate specifically positions Dante AV-over-IP as a technology that can operate alongside enterprise data networks using conventional network infrastructure. 

So, what does that actually mean for an IT team?

Let’s break it down without turning the article into a networking exam.

What Is Dante Networking?

Dante is a networked media technology developed by Audinate. It allows compatible professional AV devices to exchange digital audio over Ethernet networks.

Instead of connecting every microphone, processor, mixer and amplifier with a separate point-to-point audio cable, Dante can route audio through the network.

A simplified example looks like this:

Microphone → Dante-enabled device → Ethernet switch → Network → DSP → Amplifier

The physical network carries the traffic, while Dante provides the mechanisms needed to discover devices, route media and maintain synchronisation.

This approach can make AV systems more flexible. If an audio source needs to reach another compatible destination, the routing can often change through software rather than by physically replacing an audio cable.

For IT teams, the important point is that Dante uses familiar network infrastructure. However, real-time AV traffic has different performance requirements from ordinary business traffic.

That is where good network design matters.

What Is Dante AV-over-IP?

Dante AV-over-IP means using IP-based network infrastructure to transport AV media.

Dante originally became widely known for networked audio, and Dante audio networking remains a major part of the platform. The broader Dante ecosystem also supports video and other AV workflows.

Audinate’s guidance for IT managers explains that modern AV-over-IP solutions such as Dante are designed around common IT standards and can operate on conventional switches and cabling. 

This gives organisations several practical advantages.

A networked AV system can make it easier to:

• Add compatible AV endpoints
• Route signals between devices
• Expand systems
• Centralise management
• Connect AV across larger facilities
• Integrate AV with existing IT infrastructure

But there is an important caveat.

AV-over-IP does not mean “plug everything into the nearest switch and forget about it.”

The network still needs appropriate planning.

How Does AV-over-IP Networking Work?

At a basic level, AV-over-IP networking connects AV sources and destinations through Ethernet switches.

The general flow looks like this:

AV source → Dante endpoint → Ethernet switch → IP network → Dante destination

The network provides the transport layer, while Dante handles media routing and timing between compatible devices.

This changes how teams approach AV network design.

A traditional AV design may focus heavily on physical signal paths and cable distances. A networked AV design must also consider:

• Network topology
• Switch capacity
• IP addressing
• VLANs
• QoS
• Multicast requirements
• Network latency
• Security
• Redundancy
• Monitoring

The good news is that IT teams do not need to learn an entirely new networking universe. Dante uses familiar Ethernet and IP concepts. The challenge is understanding how those concepts apply to real-time media.

Can Dante Run on an Existing IT Network?

Yes. Dante is designed to work across standard Ethernet networks, and Audinate states that it can operate on conventional network infrastructure. 

However, “can run” and “should run without planning” are two very different statements.

A small Dante system with a few devices may work with minimal configuration. Larger or shared networks require more attention to traffic management, switch capabilities and network architecture.

Audinate’s current guidance says managed switches are generally preferred because they allow features such as QoS and IGMP to be configured when needed. 

The right approach is therefore to assess the existing network rather than automatically creating a completely separate AV infrastructure.

Dante VLAN Configuration: What IT Managers Should Know

VLANs allow organisations to logically separate network traffic.

An enterprise might already use VLANs for users, voice, guests, security systems and other services. AV can also have its own network segment when the architecture and security requirements justify it.

There is no blanket rule that every Dante installation must use a dedicated VLAN.

The decision depends on factors such as:

• Network architecture
• System size
• Security requirements
• Routing requirements
• Multicast behaviour
• Existing IT policies
• Whether AV shares infrastructure with other services

For larger deployments, segmentation can make administration and troubleshooting easier.

Audinate’s current guidance on designing Dante networks at scale recommends using a dedicated VLAN where Dante shares infrastructure with general IT traffic and specifically highlights the need to consider multicast behaviour between VLANs. 

Before deployment, IT teams should document the VLAN, IP addressing and routing requirements instead of leaving them to chance.

Dante QoS: Why It Matters

Quality of Service, or Dante QoS, is one of the most important networking concepts for IT teams supporting Dante.

QoS allows network switches to give selected traffic preferential treatment.

Why does that matter?

Because real-time audio does not appreciate waiting in line behind a large file transfer.

If an ordinary download experiences a small delay, nobody is likely to notice. Real-time audio is less forgiving.

Dante uses standard VoIP QoS mechanisms to prioritise clock synchronisation and audio traffic. Audinate’s current documentation specifies DSCP-based QoS with strict priority and multiple queues for appropriate switch configurations.

QoS becomes particularly important when Dante traffic shares network infrastructure with other services or when lower-speed links exist.

The important lesson is not to copy a random QoS configuration from another network.

Check the switch manufacturer’s implementation and configure the network according to the Dante deployment requirements.

Choosing Dante Switches

One common misconception is that Dante requires a special type of proprietary AV switch.

It does not.

Audinate states that Dante is designed to work with standard Ethernet switches. Managed switches are generally preferred when teams need features such as QoS, IGMP or detailed network monitoring. 

For professional deployments, IT teams should evaluate switch capabilities rather than simply looking for a “Dante switch” label.

Important features can include:

• Gigabit Ethernet
• QoS with appropriate queues
• DSCP support
• Managed configuration
• IGMP support where required
• Sufficient uplink capacity
• Network monitoring
• Ability to disable Energy Efficient Ethernet where required

Audinate’s current switch guidance recommends Gigabit connectivity for larger channel counts and identifies QoS, DSCP support and the ability to disable EEE as important considerations. 

The exact requirement depends on the size and design of the system.

Multicast Networking for AV

Multicast networking for AV can sound complicated, but the basic idea is straightforward.

With unicast, a source sends traffic to a specific destination.

With multicast, a source can send traffic to a multicast group, allowing multiple receivers to subscribe to the same stream.

Dante can use both unicast and multicast. Unicast is the default for Dante audio flows, while multicast can be useful when the same audio needs to reach multiple destinations. 

This distinction matters because multicast traffic needs appropriate network handling as systems grow.

IGMP snooping can help switches identify which ports actually need multicast traffic. Cisco explains that IGMP snooping allows switches to constrain multicast forwarding rather than simply flooding multicast traffic throughout the local network. 

Dante’s current guidance also notes that IGMP snooping is not automatically required for every deployment. Incorrect configuration can create problems, so IT teams should enable it based on the actual network requirements. 

That is an important point: more configuration does not automatically mean better configuration.

AV and IT Network Integration

Successful AV and IT network integration depends as much on communication as technology.

The AV team understands the rooms, signal flows, device requirements and user experience.

The IT team understands network architecture, security, switching, monitoring, change control and organisational standards.

Both teams need to be involved before installation.

A useful pre-deployment discussion should cover:

1. Network architecture
2. VLAN requirements
3. IP addressing
4. Switch selection
5. QoS
6. Multicast
7. Security
8. Monitoring
9. Documentation
10. Support ownership

This avoids a common problem: the AV system works perfectly during installation, then something changes on the network and suddenly the conference room becomes everyone’s favourite troubleshooting project.

AV Network Security

An AV device connected to the corporate network should be treated as part of the organisation’s connected infrastructure.

That makes AV network security an IT consideration, not just an AV consideration.

Security measures can include:

• Network segmentation
• Role-based access
• Restricted administrative access
• Secure device management
• Firmware updates
• Appropriate firewall policies
• User authentication
• Monitoring and logging

For larger Dante deployments, Audinate’s Dante Domain Manager provides additional IT-oriented management capabilities, including authentication, user roles, device organisation and monitoring. 

The exact security architecture should follow the organisation’s existing IT policies.

The microphone may be sitting in a meeting room, but from the network’s perspective, it is still an endpoint.

Enterprise AV Networking: What Changes at Scale?

A few Dante devices in one room are very different from hundreds of devices distributed across an enterprise.

As enterprise AV networking grows, network planning becomes more important.

Large deployments may involve multiple rooms, floors, buildings or campuses. At that scale, teams need consistent standards and clear operational processes.

Consider:

• Network segmentation
• Switch capacity
• Redundancy
• Device naming
• Monitoring
• Configuration management
• Firmware management
• Documentation
• Change control
• Troubleshooting procedures

Audinate’s current guidance for designing Dante networks at scale recommends managed Gigabit switching on the audio path and highlights QoS, IGMP, VLAN design, topology and redundancy as areas that become increasingly important in larger systems. 

The objective is not to make the network complicated.

It is to make it predictable.

Common Dante Networking Problems

When a Dante system develops an audio problem, the AV equipment is not always responsible.

The network deserves a seat at the troubleshooting table.

Common areas to investigate include:

Incorrect VLAN Configuration

Devices may fail to communicate correctly if VLANs, routing or network policies do not match the system design.

QoS Problems

Poor traffic prioritisation can affect time-sensitive traffic, particularly on busy or mixed-use networks.

Multicast Configuration

Where multicast is used, incorrect IGMP configuration can cause unwanted traffic behaviour.

Network Congestion

Heavy traffic can introduce delays and affect Dante audio performance. Audinate recommends appropriate traffic management for networks carrying significant non-Dante traffic. 

Energy Efficient Ethernet

EEE can create problems for Dante traffic. Audinate recommends disabling EEE on ports carrying Dante traffic and advises against unmanaged switches where EEE cannot be disabled. 

Insufficient Switching Capacity

Higher channel counts and larger deployments require appropriate network capacity. Audinate’s current guidance recommends Gigabit switches for higher-channel-count applications. 

The lesson is simple: troubleshoot the entire signal path, including the network.

Dante Networking Checklist for IT Managers

Before deploying Dante AV-over-IP, IT teams should confirm:

• Network architecture has been reviewed
• VLAN requirements are documented
• IP addressing is planned
• Switch capabilities have been verified
• QoS requirements have been assessed
• Multicast requirements have been assessed
• IGMP configuration has been reviewed where required
• EEE settings have been checked
• Security requirements have been documented
• Monitoring responsibilities are defined
• AV and IT support ownership is clear
• Network documentation is complete

This checklist is intentionally practical. You do not need 47 configuration rules to start a conversation between AV and IT.

You need the right questions.

Frequently Asked Questions

What is Dante networking?

Dante networking is Audinate’s IP-based media networking technology that allows compatible professional AV devices to exchange digital audio over Ethernet networks.

Does Dante require a dedicated network?

No. Dante can operate on standard Ethernet infrastructure. Whether it should use a dedicated VLAN or shared network depends on the deployment, network architecture and organisational requirements. 

Does Dante require QoS?

Not every Dante network has the same QoS requirements. Audinate recommends QoS as part of Dante network design and identifies it as particularly important where network conditions or lower-speed links require traffic prioritisation. 

Does Dante use multicast?

Dante supports both unicast and multicast. Dante audio uses unicast by default, while multicast can support one-to-many distribution. 

What switches work with Dante?

Dante is designed to work with standard Ethernet switches. Managed switches are generally preferred for deployments that require features such as QoS, IGMP and detailed network monitoring. 

Does Dante need a separate VLAN?

Not necessarily. A dedicated VLAN can be useful in larger or shared enterprise environments, but the appropriate design depends on the organisation’s network and security requirements. 

How should IT managers approach Dante AV-over-IP?

IT managers should treat Dante as part of the connected network infrastructure and evaluate switching, VLANs, QoS, multicast, security, monitoring and support responsibilities before deployment.

Final Thoughts

Dante networking has helped move professional AV closer to mainstream IT infrastructure.

For IT managers, the important takeaway is not that they need to become AV engineers overnight.

It is that they need to understand how networked AV behaves on the infrastructure they already manage.

Dante AV-over-IP can use standard Ethernet networks, but successful deployments still depend on thoughtful network design.

VLANs, QoS, multicast, switching, security and monitoring all have a role. The right configuration depends on the size, architecture and requirements of the deployment.

The strongest results usually come when AV and IT teams design the system together from the beginning.

Because when the conference room suddenly loses audio five minutes before an executive presentation, “we thought the other team handled that” is not exactly a great troubleshooting strategy.