Understanding AoIP Interoperability
Tieline Gateway codecs speak the language of AES67, ST 2110-30, ST 2022-7, RAVENNA, Livewire+, NMOS, Ember+, AES3 and include analog and AES3 I/O as standard. An optional WheatNet-IP or Dante card can also be installed at purchase and this provides a flexible platform for routing audio between a range of equipment using proprietary and open source AoIP protocols. These standards provide the framework for transporting uncompressed PCM audio around the broadcast plant.
The AES67 and ST 2110-30 standards support Session Description Protocol (SDP) for configuring the number of audio channels per stream, encoding format, bits per sample, sampling frequency and number of samples in a packet. AES67 and ST 2110-30 only address stream transport, packet setup and synchronization (timing). Nothing is mandated regarding discovery. This is where protocols such as WheatNet-IP, Livewire+, Dante and RAVENNA can assist with support stream advertisement, discovery and control.
If studios install equipment supporting AoIP protocols such as WheatNet-IP, Livewire+ or Dante, in the real-world broadcast engineers still often need the ability to connect and stream between equipment from different vendors. This is where AES67, RAVENNA, and ST 2110-30 for those in the TV world, provide a high degree of interoperability with proprietary protocols such as Dante and Livewire+.
Gateway and Gateway 4 codecs are also compliant with AMWA NMOS standards IS-04 and IS-05, which delivers discovery, registration, and ultimately control for ST 2110 AoIP streaming. NMOS data models and open standard APIs deliver interoperability and control with networked equipment throughout stations and networks. The codecs also support Ember+, which is an openly available control protocol designed to integrate devices from different vendors into a single software interface.
In summary, broadcast engineers seek AoIP devices that can transcend multiple technological standards and traverse seamlessly across LANs, WANs and the public internet, with simple monitoring and control. This interoperability delivers greater flexibility when integrating IP audio streams into the broadcast plant from a range of sources. Other Tieline codecs such as the MPX I, MPX II, Bridge-IT II and Bridge-IT XTRA II, also include and leverage many of these AoIP protocols.
IP Protocols: Compliance v Compatibility
With so many open source and proprietary IP protocols in the world of broadcast, it’s little wonder there’s confusion amongst some engineers about compatibility and compliance. While these two terms may seem similar, compliance and compatibility refer to different levels of adherence to important IP standards and protocols.
ST2110 is designed to address timing issues in broadcast workflows, ensuring low-latency transmission and accurate synchronization between audio and video streams. Products that comply with this standard are designed to minimize delay and maintain synchronization, which is essential in live production and broadcasting environments.
Compliant Codecs are Crucial
From an audio codec perspective, a compliant codec will work in any system or network designed and built around the same standard. Essentially delivering interoperability, predictable performance, and reliable integration with other compliant equipment. On the other hand, a compatible codec may work with a standard or system, but not meet all the formal requirements of the standard. It may lack certain features that a fully compliant device would offer.
Tieline always prefers to deliver compliance with standards as this is what most engineers expect. Compliant products:
- Meet expected performance metrics like low latency and reliable synchronization.
- Work seamlessly with other equipment, minimizing manual adjustments and custom setups.
- Are preferred by system integrators.
- Provide future proofing as they are more likely to adhere to evolving standards and be supported by ongoing updates.
In our experience, working with products that are simply ‘compatible’ requires greater technical support and sometimes they are less reliable.
SIP Standards
Similar principles apply to SIP and adherance to the EBU N/ACIP Tech 3226 standards that were formalized to develop connectivity standards for IP streaming using Session Initiation Protocol (SIP) between different brands of audio codecs. EBU N/ACIP Tech 3326 provides a minimum set of requirements necessary to ensure interoperability between broadcast and non-broadcast equipment for transport of audio over IP networks. It employs Session Description Protocol (SDP) and standardizes the use of ports, encoding, transport protocols and signaling, to ensure codecs, and other devices like smartphones and VoIP phones can connect successfully.
To learn more about Tieline Gateway and Gateway 4 codecs, visit www.tieline.com/Gateway, or contact Tieline sales:
- For USA, Canada & Latin America contact: sales@tieline.com
- For Australia and International: info@tieline.com
