Unsurpased Compatibility
In addition to being compatible with the Zephyr Xstream, the Zephyr/IP is compatible with a number of VoIP devices, and may even be able to talk to your PBX.
To achieve compatibility with other IP broadcast devices, the Z/IP is compliant to the Norm/Audio Codec over IP (N/ACIP) standard. This standard establishes that codecs from various vendors can work with one another by using a core set of functional components.
SignalingSession Initiation Protocol, or SIP, was developed by the Internet Engineering Task Force (IETF) as part of the Internet Multimedia Conferencing Architecture and was designed to work with other Internet protocols such as TCP, UDP, DNS and others.
SIP has been steadily gaining popularity from office PBXs, VoIP phones, to software applications like Google Talk and Microsoft Communicator. N/ACIP uses SIP as the signaling protocol for devices exchanging audio data over IP. (see the N/ACIP document TECH3326 
for more details).
The Z/IP fully supports SIP to connect to other devices, negotiate a common audio codec, and establish the media connection.
TransportThe Z/IP uses the Real-time Transport Protocol (RTP) to transmit audio data over the network. RTP, another protocol developed by the IETF, is used for VoIP telephony and is becoming standard for broadcast codecs. RTP avoids the delay inherent with TCP/IP. The Z/IP is capable of using RTP either as part of a two-way session or as a one-way, push stream.
CodecsThe last piece of the compatibility puzzle is to negotiate a common audio codec. In addition to the more advanced codecs , such as AAC-ELD, the Z/IP supports all mandatory codecs from the N/ACIP standard. This allows the Z/IP to connect to other codecs that adhere to the TECH3326 specification.