What Is Audio over IP?

Audio over IP (AoIP) refers to the transmission of uncompressed or compressed digital audio streams over an IP network. It has become the backbone of modern broadcast studios, live sound reinforcement, intercom systems, and corporate AV installations. Standards such as AES67, Dante, Ravenna, and Livewire+ enable interoperability between equipment from different manufacturers. While AoIP offers flexibility, scalability, and cost savings compared to traditional analog or MADI-based systems, it depends entirely on the health of the underlying network. Even a small amount of packet loss can cause audible clicks, dropouts, or synchronization failures, making network troubleshooting a critical skill for audio engineers and IT professionals alike.

Common AoIP Network Issues

Before diving into analysis tools, it helps to understand the specific problems that degrade AoIP performance. These issues often overlap, and a network analyzer can help isolate the root cause.

Packet Loss

Packet loss occurs when data packets fail to reach their destination. In AoIP, every lost packet represents a gap in the audio waveform. Even a loss rate of 0.1% can produce noticeable artifacts. Causes include faulty cabling, overloaded switches, buffer overflows, or RF interference.

Latency

Latency is the time it takes for an audio packet to travel from sender to receiver. Excessive latency causes echo, lip-sync errors, or delays in live monitoring. The accepted maximum for live sound is typically under 10 milliseconds end‑to‑end, though many AoIP systems operate at 1–5 ms.

Jitter

Jitter is the variation in packet arrival times. AoIP receivers rely on a steady clock to reconstruct the audio stream. When jitter exceeds the receiver’s buffer depth, it results in buffer underruns or overruns, causing pops and dropouts. Network congestion, improper QoS, or clock drift are common sources.

Network Congestion

Congestion happens when traffic exceeds the capacity of a link or switch. Even on gigabit networks, a single broadcast domain flooded with multicast traffic can cause packet drops. Non‑audio traffic (data backups, video streams) can steal bandwidth if not properly prioritized.

Hardware Failures and Misconfiguration

Bad Ethernet cables, failing port transceivers, or misconfigured VLANs can silently corrupt traffic. Duplex mismatches (one device set to half‑duplex, the other to full) cause collisions and retransmissions. Network analyzers can reveal these physical‑layer issues.

Understanding Network Analyzers

Network analyzers (also called packet sniffers or protocol analyzers) capture raw network traffic and decode the packets for inspection. They range from free, open‑source tools like Wireshark to enterprise suites such as SolarWinds Network Performance Monitor and PRTG Network Monitor. Dedicated hardware analyzers like NetScout offer high‑precision timestamping, but software solutions are usually sufficient for AoIP troubleshooting.

An analyzer can filter traffic by IP address, port, protocol, or even specific payload patterns. This allows you to focus only on AoIP streams (e.g., UDP port 4321 for Dante, or multicast groups associated with AES67). Many analyzers also generate statistics on throughput, packet loss, jitter, and round‑trip time.

Step‑by‑Step Troubleshooting with Network Analyzers

The following process assumes you have access to a device running Wireshark (or a similar tool) and can capture traffic on the same network segment as your AoIP endpoints.

1. Choose the Right Capture Point

Place your analyzer on a span (mirror) port of the switch that connects your AoIP devices, or install it on a device that shares the same VLAN. Avoid capturing across routed links if possible, as routers may alter packet headers. For wireless AoIP (rare in professional use), capture on the access point’s wired side.

2. Install and Configure the Analyzer

Download and install Wireshark on a laptop with a wired Ethernet connection – wireless adapters cannot capture full‑duplex traffic reliably. Set the capture filter to limit what you collect. For example, if your AoIP system uses multicast address 239.255.0.1 on port 4321, apply:

udp port 4321 and ip host 239.255.0.1

This reduces the amount of traffic to analyze and prevents disk overflow in high‑throughput networks.

3. Capture Traffic During Normal and Abnormal Conditions

Start a capture when audio is playing cleanly to establish a baseline. Then, reproduce the problem – for instance, by walking with a wireless microphone or by running a network stress test (use tools like iperf to generate background traffic). Compare the two captures side by side.

4. Analyze Packet Flow and Timing

Look for retransmissions (TCP only – AoIP is usually UDP, so no retransmissions) but even with UDP, you can detect duplicate packets or out‑of‑order sequences. Use Wireshark’s built‑in telephony tools: go to Telephony → RTP → Show All Streams to see jitter and packet loss for each RTP stream. For non‑RTP AoIP streams (e.g., Dante’s proprietary protocol), you may need to decode the payload manually or rely on vendor‑specific analysis tools.

5. Identify Bottlenecks with I/O Graphs and Statistics

Wireshark’s Statistics menu provides throughput graphs and conversations. A sudden drop in throughput concurrent with audio dropouts points to congestion. Check the IO Graph (Statistics → IO Graph) to see spikes in traffic. If you observe sustained utilization above 80% on a 1 Gbps link, that’s a red flag. Also examine Conversations to see which endpoints are generating the most traffic.

6. Test Network Changes

After adjusting QoS settings, VLAN segmentation, or replacing a suspect cable, perform another capture. The goal is to see reduced jitter, zero packet loss, and stable latency. Compare numerical metrics before and after: average jitter should ideally stay below 1 ms for RTP streams.

Advanced Analysis Techniques

Calculating Jitter

Jitter is usually reported by the analyzer. The standard formula from RFC 3550 (RTP) measures the variance of inter‑arrival times. A jitter value above 3 ms is problematic for low‑buffer AoIP receivers. If your tool doesn’t compute it, you can manually inspect the time between consecutive packets of the same stream; any large gap indicates a delayed packet that will cause buffer issues.

Verifying QoS Markings

Audio traffic should be marked with Differentiated Services Code Point (DSCP) values for high priority – typically DSCP 46 (Expedited Forwarding) for real‑time audio. In Wireshark, apply a display filter: ip.dsfield.dscp == 46. If audio packets lack proper DSCP markings, the network may treat them the same as bulk data. Misconfigured QoS is one of the most common causes of AoIP problems in enterprise networks.

Multicast Group Management

Many AoIP systems use multicast to send one stream to multiple receivers. Use the analyzer to list all active multicast groups (Statistics → Multicast). Verify that only needed groups are present. Orphaned multicast streams consume bandwidth. Also check that IGMP snooping is enabled on your switches; without it, multicast traffic floods every port.

Deep Packet Inspection of AoIP Payloads

For standards‑based protocols like AES67 (RTP payload type 96), you can view the payload header to confirm sample rate, bit depth, and number of channels. Inconsistent payload headers between sender and receiver can cause audio corruption even if the network is flawless. Wireshark’s RTP analysis shows these details under RTP Stream Analysis.

Best Practices for Reliable AoIP Networks

Preventive measures reduce the need for reactive troubleshooting. Implement the following recommendations based on industry standards and real‑world experience.

Segment AoIP Traffic on Dedicated VLANs

Place all AoIP devices on a separate VLAN to isolate audio traffic from data, voice, and video. This simplifies QoS configuration and prevents non‑audio broadcasts from affecting performance. Most AoIP controllers allow you to specify a VLAN ID.

Enable and Configure Quality of Service

Priority queuing must be enabled on every switch along the path. Use strict priority for DSCP 46 traffic. Ensure that switches trust incoming DSCP markings from AoIP devices (these devices usually mark their own packets correctly). Test with an analyzer to confirm markings survive end‑to‑end.

Use Multicast Filtering

Enable IGMP snooping on all switches. This ensures multicast traffic only goes to ports that have subscribed to that group, reducing unnecessary load. If your AoIP system uses unicast (e.g., point‑to‑point Dante), still enable IGMP snooping if any multicast control traffic exists.

Choose Appropriate Network Hardware

Not all switches are suitable for AoIP. Look for switches with:

  • Non‑blocking backplane (wire‑speed forwarding on all ports)
  • Low port‑to‑port latency (under 10 µs)
  • Support for DiffServ QoS and IGMP snooping
  • Managed capabilities (needed for VLANs and port mirroring)

Switches from Cisco, Netgear, or Aruba are common in AoIP installations, but always check compatibility with your protocol (e.g., Audinate provides a list for Dante).

Regular Monitoring and Logging

Deploy a network analyzer like PRTG for continuous monitoring. Set up alerts for packet loss exceeding 0.01% or jitter spikes. Combining real‑time monitoring with periodic full captures (e.g., during system start‑up) helps spot trends before they cause failures.

Keep Firmware and Software Updated

Switch firmware updates often include bug fixes for clock synchronization (PTP) and IGMP handling. AoIP endpoint firmware can improve jitter buffers and QoS compliance. Schedule updates during maintenance windows and verify performance with a capture after each change.

Document the Network Topology

Wire a map of all AoIP devices, switch ports, VLANs, and multicast groups. Update it whenever changes are made. During troubleshooting, you can quickly identify which switch port an affected device is connected to and configure SPAN on that port.

Conclusion

Network analyzers are indispensable for diagnosing and resolving Audio over IP issues. From identifying packet loss and jitter sources to verifying QoS markings and multicast behavior, a well‑executed capture provides the evidence needed to correct network faults. By combining the step‑by‑step analysis approach outlined above with proactive best practices, audio professionals can maintain the low latency and high reliability that modern AoIP systems demand. Master these techniques, and you’ll be equipped to keep audio streaming cleanly in any IP‑based sound environment.