The Challenge of Interoperability in Modern Communication Systems

Modern communication environments, whether in broadcasting, live event production, corporate offices, or public safety, rely heavily on intercom systems to connect operators, talent, and support staff. Historically, these systems were built on proprietary analog or digital technologies, creating silos where equipment from one manufacturer could not communicate with another. As organizations adopt audio-over-IP (AoIP) networks, the need for a universal standard that enables seamless interoperability has become critical. AES67, an open standard developed by the Audio Engineering Society, answers this need by providing a common layer for transporting high-quality audio across IP networks. By bridging the gap between disparate AoIP platforms, AES67 allows intercom systems to integrate with a wide range of devices, reducing costs and complexity while opening new possibilities for scalable, flexible deployments. The shift from dedicated point-to-point cabling to packet-switched networks also simplifies system expansion and maintenance, making AES67 a cornerstone for future-proof communication infrastructure.

What Is AES67?

AES67, formally known as AES67-2018 (and originally AES67-2015), is a standard for the transport of high-quality audio over IP networks. It specifies a set of protocols and formats that ensure audio signals can be exchanged reliably between devices from different manufacturers. At its core, AES67 defines the use of the Real-time Transport Protocol (RTP) for streaming audio, the Session Initiation Protocol (SIP) for connection management and stream negotiation, and the Precision Time Protocol (PTPv2, IEEE 1588-2008) for synchronization. This combination enables low-latency, synchronized audio streams over standard Ethernet infrastructure. The standard was designed to be media-agnostic, meaning it works equally well for intercom, program audio, and monitoring feeds.

The standard does not prescribe a specific network topology or transport layer; instead, it focuses on interoperability at the payload and timing level. It supports audio sampling rates of 48 kHz or 96 kHz, bit depths up to 24 bits, and channel counts from mono to multichannel streams. By adhering to these specifications, AES67-compliant devices can discover each other, negotiate stream parameters, and begin transmitting audio with deterministic latency. This makes AES67 a foundational technology for modern AoIP intercom systems, where multiple vendors’ products must work together in real time. Unlike proprietary systems that lock users into a single ecosystem, AES67 empowers integrators to mix and match components from leading manufacturers such as Riedel, Clear-Com, RTS, and others.

Key Technical Specifications

  • Audio Formats: Linear PCM, 48 kHz or 96 kHz sample rate, up to 24-bit depth. Payload is formatted per AES3 or SMPTE ST 2110-31.
  • Transport: RTP over UDP/IP; uses multicast for efficient distribution and unicast for point-to-point links.
  • Synchronization: IEEE 1588 Precision Time Protocol (PTPv2) with a profile specified in AES67. All devices must share a common grandmaster clock for sub-microsecond alignment.
  • Connection Management: SIP-based signaling for session setup and teardown; Session Description Protocol (SDP) describes stream parameters.
  • Latency: Configurable, typically between 1 ms and 10 ms depending on network design and buffer settings. For intercom, 1–2 ms is common.
  • Network Requirements: IGMP snooping, PTP-aware switches, and QoS marking (DSCP EF for audio, CS7 for PTP) are essential for reliable operation.

These specifications ensure that AES67 devices can interoperate regardless of underlying AoIP ecosystem—for example, a Dante‑to‑AES67 bridge or a Ravenna device speaking AES67 can exchange audio with a Livewire+ system. This interoperability is the cornerstone of flexible, future‑proof communication networks. The standard is also backward-compatible with earlier IP audio implementations when properly configured.

Benefits of AES67 in Intercom Systems

True Interoperability

Perhaps the single greatest advantage of AES67 is its ability to connect devices from different manufacturers without custom gateways or protocol converters. In intercom applications, this means a broadcast console from one vendor can communicate directly with a beltpack from another, or a third‑party software intercom can receive audio from a hardware panel. This freedom allows integrators to select best‑in‑class components rather than being locked into a single ecosystem. For example, a public safety dispatch center can use a legacy intercom matrix alongside new IP‑based endpoints, extending the life of existing investments. In practice, this eliminates the need for expensive middleware and reduces the risk of vendor lock-in.

Scalability and Flexibility

Because AES67 operates over standard Ethernet networks, expanding a system is as simple as adding a new IP‑connected device and configuring the network to handle additional multicast streams. This contrasts with traditional analog or TDM‑based intercoms, which require dedicated cabling and central switch matrices. In a large broadcast facility, engineers can add intercom panels, talkback circuits, and audio monitoring points without rewiring. Similarly, for live event setups, AES67 enables rapid deployment and teardown, as all devices share a common IP backbone. The ability to dynamically adjust stream routing via software means that system topology can be reconfigured on the fly to adapt to changing production needs.

Low Latency and High Reliability

Real‑time intercom communication demands extremely low latency—often below 10 milliseconds end‑to‑end. AES67’s use of PTP synchronization and optimized RTP payloads can achieve latencies as low as 1 ms, making it suitable for demanding applications like live sports broadcasting or concert monitoring. Combined with QoS (Quality of Service) features in managed switches, AES67 streams can be prioritized over other network traffic, ensuring reliable, glitch‑free audio even during peak usage periods. Furthermore, AES67 supports redundant streams and dual-path configurations to provide fault tolerance, a critical requirement for mission-critical public safety communications.

Cost Savings

By leveraging existing IP infrastructure, organizations reduce the need for dedicated audio cabling, custom interface cards, and proprietary converters. AES67 also encourages competition among vendors, driving down hardware costs. Furthermore, because AES67 is an open standard, it avoids the licensing fees associated with some proprietary AoIP solutions. Over the lifecycle of a system, these savings can be substantial. Training staff on a single open standard rather than multiple proprietary platforms also reduces ongoing operational expenses.

Future-Proof Investment

AES67 is not a static standard; it continues to evolve alongside the broader AoIP ecosystem. Devices that support AES67 today are well-positioned to integrate with emerging standards such as SMPTE ST 2110 and IEEE 802.1 Audio Video Bridging (AVB). This means that an investment in AES67-based intercom equipment will remain relevant as professional audio and video converge on IP networks.

Implementing AES67 in Intercom Systems

Successful deployment of AES67‑based intercom systems requires careful planning, starting with device selection and ending with rigorous testing. While AES67 simplifies interoperability, it does not automatically guarantee performance; the network must be designed to handle multicast audio traffic, maintain accurate timing, and prioritize real‑time streams. Below is a step-by-step guide covering the key phases of implementation.

Step 1: Verify Device Compatibility

Not all devices labeled “AES67‑compatible” implement every feature of the standard. Check that the intercom products you choose support the required sampling rates, bit depths, and PTP profiles. Many professional audio devices include an AES67 mode that must be enabled manually. Consult the manufacturer’s documentation to ensure all endpoints in the system use the same audio payload format (e.g., L16 or L24). Some devices may require firmware updates to achieve full AES67 compliance. Always verify compatibility using the manufacturer’s official AES67 conformance test or a third-party validation tool.

Step 2: Configure Network Infrastructure

AES67 relies on Layer 3 multicast for efficient distribution of audio streams. Therefore, the network must support IGMP snooping (IGMPv2 or v3) to prevent flooding switches and to allow devices to subscribe only to the streams they need. Join leaves should be optimized to reduce latency when starting a stream. Managed switches should also support PTP transparent clock or boundary clock functionality to keep time synchronization accurate across hops. Additionally, apply QoS markings (DSCP EF for media, CS7 for PTP) to guarantee bandwidth and minimize jitter. Ideally, separate VLANs for audio, control, and data traffic should be used to isolate intercom streams from non-critical traffic.

Step 3: Set Up PTP Time Synchronization

All AES67 devices must be synchronized to a common PTP grandmaster clock. Configure one device (often a network switch or dedicated PTP server) as the grandmaster, and ensure all intercom endpoints and switches are properly slaved. Use the AES67‑specified PTP profile (default profile, with a sync interval of 0.125 seconds and announce interval of 1 second) to achieve sub‑microsecond timing accuracy. Verify clock synchronization using tools like Wireshark or vendor‑provided diagnostics. For large networks with many hops, boundary clocks should be deployed at each switch to prevent timing degradation.

Step 4: Assign IP Addresses and Stream Management

Each AES67 device requires a valid IP address and subnet. For larger networks, use a DHCP server with reservations to simplify configuration. Streams are typically unicast for point‑to‑point intercom or multicast for group communication. Use SIP‑based signaling or session descriptions (SDP) to negotiate stream parameters. Some intercom systems have built‑in stream management; others rely on external controllers like the Audinate Dante Controller or Ravenna’s AVB controller. Ensure that multicast addresses are coordinated to avoid conflicts and that each stream has a unique session name.

Step 5: Test and Validate

Before going live, conduct thorough testing of audio quality, latency, and reliability. Use a test signal (e.g., 1 kHz tone) and measure round‑trip latency with an oscilloscope or software. Check for audio dropouts or clock drift over extended periods. Engage all intercom stations simultaneously to stress‑test the network. Monitor switch CPU load and multicast traffic levels to ensure no single device or link is overwhelmed. Finally, implement security measures such as VLAN segmentation and 802.1X authentication to protect the control and media streams from unauthorized access.

Step 6: Ongoing Monitoring and Management

After deployment, use SNMP or vendor‑specific tools to monitor PTP lock status, stream health, and network congestion. Establish a baseline for normal operation and set alerts for deviations. Firmware updates should be tested in a staging environment before rollout to production. Regular performance audits help maintain the high reliability expected in critical intercom applications. Many modern intercom systems also offer web-based dashboards that display real-time statistics for all AES67 streams.

Use Cases for AES67 Intercom Systems

Broadcast and Media Production

Television and radio stations increasingly adopt AoIP infrastructures. AES67 allows intercom panels, commentary units, and IFB (Interruptible Foldback) systems from different manufacturers to coexist. For example, a Grass Valley production switcher’s intercom can talk to a Riedel Artist beltpack over a shared AES67 network. This flexibility is invaluable in live news, sports, and studio productions where quick reconfiguration is common. In large broadcast facilities with multiple control rooms, AES67 makes it possible to route intercom audio between floors or buildings without installing dedicated copper or fiber cables.

Live Event and Touring

In concert touring and festival settings, intercom systems must be set up quickly and communicate with all technical departments. AES67 enables sound, lighting, video, and stage management crews to use a unified intercom network. Wireless beltpacks, wired panels, and software clients on laptops can all participate, regardless of brand. The low latency ensures natural conversation, even when participants are hundreds of feet apart. Touring companies particularly benefit from AES67 because they can bring their own equipment and integrate seamlessly with venue infrastructure without needing custom adapters.

Corporate and Education

Large corporations, universities, and convention centers use intercoms for security, maintenance, and event coordination. AES67 allows integration of legacy analog systems via gateways, while new IP‑based endpoints can be added as budgets allow. For example, a school district can connect its VMS‑linked intercom to a modern VoIP telephone system through an AES67 bridge, enabling streamlined communication between security officers and administrators. In corporate headquarters, AES67 intercoms can be used for paging, emergency notifications, and room scheduling announcements over the same network infrastructure.

Public Safety and Mission‑Critical Communication

Police, fire, and emergency medical services require resilient, interoperable communication. AES67 intercom systems can be deployed in dispatch centers, command vehicles, and incident command posts. Because AES67 standardizes audio transport, public safety agencies can mix equipment from multiple vendors without compromising reliability. The use of PTP synchronization also ensures that recordings from different sources can be precisely aligned for post‑incident analysis. Redundant PTP grandmasters and network paths ensure that even if a switch fails, intercom audio continues without interruption.

Comparing AES67 with Other AoIP Standards

AES67 is not the only AoIP standard on the market. Competing technologies include Dante (Audinate), Ravenna (ALC Network), Livewire+ (The Telos Alliance), and SMPTE ST 2110‑30 (a professional media standard). Understanding the differences helps integrators choose the right tools for their intercom systems.

  • Dante: Proprietary but dominant in the pro‑audio world. Dante implements AES67 as an optional interoperability mode, allowing Dante devices to exchange audio with non‑Dante AES67 gear. Dante’s native protocol offers lower latency and easier discovery, but AES67 mode sacrifices some features for compatibility. Many intercom manufacturers now include both Dante and AES67 modes.
  • Ravenna: Developed by ALC, Ravenna is also based on RTP and PTP and is fully compatible with AES67. It adds advanced features like high‑density multichannel transport and redundant streams. Many broadcast manufacturers, such as Lawo and Neumann, use Ravenna in their products. Ravenna is often preferred in large-scale broadcast plants that require many channels.
  • SMPTE ST 2110‑30: This is the broadcast industry standard for transporting uncompressed audio in professional media environments. It uses the same RTP and PTP foundations as AES67 but adds requirements for video synchronization and timing. AES67 can be considered a subset of ST 2110‑30; therefore, intercom systems designed for ST 2110‑30 networks are often AES67‑compatible. As broadcasters transition to IP-based production, ST 2110 adoption is accelerating.
  • Livewire+: The Telos Alliance’s AoIP ecosystem is used widely in radio. Livewire+ incorporates AES67 support, enabling connectivity with IP audio codecs and third‑party intercoms. It also offers proprietary advantages like automatic stream routing and integrated phone system integration.

For most intercom applications, AES67 provides the best balance of interoperability, performance, and cost. When a facility is committed to a single vendor’s ecosystem, the native protocol may offer advantages, but AES67 ensures that no device becomes an island. For new installations, choosing equipment that supports AES67 as a primary or secondary transport method is a safe long-term strategy.

Challenges and Considerations

While AES67 is a powerful tool, implementers must address several challenges to achieve reliable intercom operation.

Network Design Complexity

Deploying AES67 over a network not originally designed for professional audio can lead to packet loss, jitter, and clock drift. Unmanaged switches are typically unsuitable. Engineers must plan for adequate bandwidth, multicast filtering (IGMP), and PTP topology. In large networks, boundary clocks or transparent clocks are required to maintain timing accuracy across multiple switch hops. Network design should also account for redundancy—spanning tree protocol (STP) settings must be tuned to avoid convergence delays during switch failures.

Latency Budget Management

Although AES67 can achieve very low latency, the end‑to‑end delay accumulates through codec buffering, network transmission, and device processing. Intercom systems that mix multiple streams (e.g., listen‑while‑talk) must keep total latency below 20 ms for natural conversation. Careful buffer sizing and use of low‑latency network hardware are essential. Using 1 ms buffer settings on all devices can help, but requires a very clean network with minimal jitter.

Coexistence with Other Traffic

IP networks carry data, video, and control traffic in addition to audio. Without proper QoS, a large file transfer can starve intercom streams of bandwidth, causing audio gaps. Implement strict DSCP marking on all AoIP equipment and enforce rate limiting on non‑critical traffic. Separate VLANs for audio, video, and data can further isolate streams. In mission-critical environments, dedicated switches for audio traffic should be considered.

Vendor Interpretation Variability

Though AES67 is an open standard, manufacturers may implement optional features differently—for instance, the handling of stream discovery or the PTP profile. It is critical to test inter‑vendor connectivity in a lab environment before full deployment. Consult the Audio Engineering Society for the latest conformance test specifications. Many vendors provide interoperability matrices that list tested combinations.

Training and Skill Gaps

Network engineers accustomed to IT practices may not be familiar with the timing and latency requirements of professional audio. Similarly, audio engineers may lack network configuration skills. Organizations should invest in cross-training or hire specialists who understand both domains. Certification programs like Dante Certification and Ravenna training can help bridge the gap.

Future Directions: AES67 and Beyond

The adoption of AES67 continues to grow, driven by the shift to IP‑based production workflows. The standard is also a foundation for newer initiatives such as SMPTE ST 2110, which bundles audio, video, and metadata over IP. For intercom systems, the future will likely see tighter integration with network‑wide clocking, redundant stream paths, and intelligent stream management. Additionally, the emerging IEEE 802.1 Audio Video Bridging (AVB) standard builds on PTP and includes stream reservation (SRP) for guaranteed bandwidth, potentially enhancing AES67 performance in mixed‑media networks.

Another trend is the adoption of NMOS (Networked Media Open Specifications) for discovery and registration, making AES67 devices even easier to deploy in large networks. The combination of AES67 with NMOS IS-04 and IS-05 allows for automated stream routing and system monitoring. Public safety and defense sectors are also exploring AES67 as a standard for secure, interoperable communication.

To stay ahead, system designers should select intercom equipment that not only supports AES67 but also offers a clear upgrade path to ST 2110‑30 and AVB. Training staff in AoIP fundamentals and network troubleshooting will become as important as traditional audio engineering skills. The open nature of AES67 ensures that it will remain relevant as new technologies emerge, making it a wise investment for organizations that prioritize long-term flexibility.

Conclusion

AES67 has established itself as the essential standard for achieving interoperable intercom and communication systems. By providing a common framework for audio transport, synchronization, and connection management, it allows devices from different vendors to work together seamlessly. The benefits in terms of scalability, flexibility, low latency, and cost savings are compelling for broadcast, live events, education, and public safety organizations. However, successful implementation requires careful network design, proper device configuration, and ongoing monitoring. As the industry moves toward fully networked, software‑defined communication solutions, AES67 will remain a cornerstone technology, enabling the interoperability that modern intercom systems demand.

For further reading on AES67 implementation best practices, refer to the Audinate technical whitepapers and the Ravenna network design guide. Additionally, the AES Standards Committee website provides official documentation and updates to the AES67 specification. For practical case studies, check the Riedel Solutions page which includes many AES67-based intercom deployments.