.

A Dante system can appear to work during a bench test and still fail when the room is occupied, the switch is carrying other traffic, or a contractor reconnects a port without understanding the intended topology. To configure Dante audio networks correctly, treat audio transport as a documented part of the building network, not as an isolated AV task completed after installation.

For commercial projects, the issue is rarely whether Dante devices can pass audio. The issue is whether the network has been designed, specified, installed, and tested to carry the required audio channels under real operating conditions. That requires clear responsibility between AV, IT, electrical, and low-voltage trades.

Start with the system, not the switch

Dante settings should follow operational requirements. Begin by documenting the endpoints, channel counts, room combinations, recording feeds, paging zones, control systems, and third-party network services that will share the infrastructure. A divisible training center, for example, may need local DSP-to-amplifier audio in every room, multicast program audio between rooms, USB audio bridges for conferencing, and a separate feed to a recording system.

Those requirements determine traffic flows. They also determine whether the system needs a dedicated AV network, an AV VLAN on an enterprise switching environment, or separate primary and secondary Dante networks. There is no universal answer. A small boardroom may operate properly on a correctly configured shared AV VLAN. A command center, large auditorium, or facility with critical live operations may justify physically separate redundant networks and more stringent commissioning requirements.

Document the decision in the drawings and specifications. Identify the network boundary, switch locations, port assignments, fiber and copper pathways, uplink capacity, VLAN identifiers, and party responsible for switch configuration. A rack elevation without a port schedule leaves too much interpretation to the field.

Establish a topology that can be built and supported

Dante supports unicast and multicast audio flows. Unicast is commonly appropriate for point-to-point subscriptions. Multicast is useful when one transmitter feeds multiple receivers, but it must be planned because multicast traffic can affect every relevant port if the switching environment is not configured to constrain it.

Avoid treating multicast as a shortcut. Use it where its distribution benefit is clear, then define the required switch behavior. IGMP snooping should be enabled where multicast Dante flows are used, and an active IGMP querier must exist in the applicable VLAN. Snooping without a querier can create intermittent behavior that is difficult to reproduce after turnover.

A star topology using managed switches is normally the most supportable approach. It provides a clear central point for monitoring and isolates a failed edge connection more effectively than an improvised daisy chain. If switches are cascaded, calculate aggregate traffic at every uplink. The number of audio channels at an endpoint is not the same as the traffic load at the switch-to-switch connection carrying multiple rooms or racks.

For Dante redundancy, primary and secondary networks must remain physically separate. They are not two VLANs connected through the same switching fabric, and they should not be patched together for convenience during installation. Each Dante device’s primary and secondary interfaces require independent paths. The drawings should make this distinction unmistakable, including separate switch naming, patch-panel labeling, and cable identifiers.

Configure the network for deterministic audio transport

Managed switches are not automatically ready for Dante. The configuration must prioritize time-sensitive audio and clock traffic while preserving the operating rules of the owner’s network.

Quality of Service is central to this work. Dante uses differentiated traffic classes for audio and Precision Time Protocol clock messages. The switch configuration should recognize and prioritize the markings required by the deployed Dante equipment and firmware. Do not rely on a generic “voice” profile without confirming its queue mappings, trust boundaries, and behavior on uplinks.

Configure QoS consistently from edge port to core. A properly prioritized endpoint port does not solve a congested uplink that rewrites or ignores markings. The IT team should also confirm that WAN, firewall, or routed network policies will not be mistaken for local Dante transport. Dante audio networks are generally designed within a local Layer 2 domain; extending them between facilities or across routed boundaries requires deliberate engineering and manufacturer-supported methods.

Disable Energy Efficient Ethernet on Dante-connected ports unless the equipment manufacturer has confirmed compatibility. EEE power-state transitions can introduce latency or link instability that presents as audio dropouts. Also avoid port settings that introduce unplanned delays, such as aggressive green Ethernet features or poorly understood storm-control thresholds.

Port speed and duplex should normally be set to auto-negotiate when devices and switches support it correctly. Hard-setting one end and leaving the other on auto can create duplex mismatches. The right policy depends on the switch platform and owner standard, so the configuration narrative should state the required approach rather than leaving it to assumption.

Protect clocking before commissioning begins

Dante relies on PTP clocking to keep audio devices synchronized. One device becomes the preferred master based on the system’s election process and configured priorities. That process is reliable when the network is healthy. It becomes a source of audible problems when switches filter timing traffic, devices are repeatedly power-cycled, or an unintended endpoint takes clock-master status.

Identify the intended clocking strategy in the system documentation. In a simple isolated system, automatic election may be appropriate. In a larger or higher-consequence installation, designate preferred master-capable devices and confirm the consequences of their failure. The goal is not to force a particular device into service at all costs. The goal is to make clock behavior predictable and recoverable.

Clocking should be checked during normal operating conditions, not only with a partially built rack. Power amplifiers, video systems, wireless access points, control processors, and other networked equipment can change thermal, electrical, and traffic conditions after the project reaches final configuration.

Coordinate addressing, security, and ownership

IP addressing is often where a technically sound AV design meets a poorly defined project process. Determine early whether Dante devices will use DHCP reservations, static addressing, or an AV-managed address pool. Each method can work. What matters is that the selected method is compatible with facility operations and is recorded in closeout documentation.

A dedicated AV VLAN can reduce exposure to unrelated broadcast and multicast traffic while allowing IT to apply appropriate administration policies. It is not a substitute for capacity planning or QoS. Conversely, placing Dante on the corporate user-data VLAN may be acceptable in limited cases, but it increases coordination demands and can complicate troubleshooting after moves, additions, and changes.

Network security policies require the same early coordination. Port security limits, 802.1X authentication, access-control lists, switch management controls, and monitoring platforms may affect AV endpoints. Do not exempt an entire AV network from security controls by default. Define which controls apply, test them with the actual Dante devices, and record any justified exceptions.

Test failure conditions, not only audio presence

A passing test is more than a green subscription indicator in Dante Controller. Commissioning should verify subscriptions, channel labels, multicast behavior, clock status, latency settings, and audio performance at the required load. It should also validate the installed switch configuration against the approved design.

Test the events that cause service calls: a switch reboot, loss of a primary network path, reconnection of a device, room-combine changes, and restoration after a power outage. For redundant systems, verify that a primary-path loss does not interrupt program audio and that the system returns to its intended state when the path is restored.

Latency should be selected based on network scale and topology, not set arbitrarily to the lowest available value. Lower latency can be appropriate for a compact local system with known switch performance. Larger networks, multiple switch hops, or complex routing requirements may need a more conservative setting. The acceptable value should be confirmed through measured operation, not preference.

Deliver records the facility can use

The final package should include a network diagram, switch and port schedule, VLAN and addressing records, device names, Dante channel labels, multicast-flow records, QoS requirements, and configuration backups where permitted by the owner’s IT policy. These are operating documents, not administrative extras.

AVC Principles approaches Dante infrastructure as coordinated AV and ICT engineering. That means defining the network requirements before procurement, placing them in buildable documents, and verifying the installed result before turnover. No hardware agenda should determine the network design.

The most useful Dante network is not the one that merely passes audio on day one. It is the one a facilities or IT team can understand, troubleshoot, modify, and return to service without guessing what the original installer intended.

One Response

Leave a Reply

Your email address will not be published. Required fields are marked *