Scope Livewire operates using a standard set of multcast addresses. The Livewire channels are simply an alias to a real multicast address. This document defines what addresses are used by Livewire so that if you are doing other, non-Livewire multicast (like AES67 or SMPTE2110) you can stay clear of these addresses. Technical details Livewire was made simple by using the channel number as an "alias" for the real IPv4 multicast address. It's important to know these addresses so that you can keep clear of these ranges when doing other multicast on the same network. A real-world example of this would be using Dante devices in AES67 mode in conjunction with your Livewire devices. It's critical to keep all multicast unique. Address assignments from within this range are specified in RFC 5771. The entire multicast range is from 224.0.0.0 to 239.255.255 …

DESCRIPTION All Livewire channels are an alias to an IGMPv2 multicast address. In a pure Livewire environment, you should never need to know a multicast address. In this document we will discuss how to obtain a multicast address should you need it for other purposes. There are two methods Method 1 - The easy way Download this Excel spreadsheet. Nod to David Linder from The Jim Pattison Broadcast Group in Vancouver, B.C. for the help with improving the functionality of this spreadsheet. When you run it, you can enter a Livewire channel number, exit the cell and the multicast address is displayed. Alternately (thanks David) enter the multicast address and exit the cell to get the Livewire channel number. Here is a screenshot of several examples. Method 2 - The manual way All Livewire multicast channels are in the range 239.192.X.Y or 239.193.X.Y Addresses …

Scope When connecting Cisco switches used for Livewire to other network switches sometimes it is useful to be able to create a filter that specifically blocks certain address ranges. This document will provide you guidance for creating filters. Description Make sure you know what you are blocking. The entire multicast range goes from 224.0.0.0 all the way to 239.255.255.255. If you block the entire range, you could block certain multicast addresses that are used for things other than Livewire. As one example, mDNS (or multicast dns) which is used by Apply Bonjour could block the discovery of other things (like printers). In this example, we're only going to block addresses used by Livewire that are in the Organization-Local Scope range as defined by the IANA Multicast Address Space Registry . Specifically the range of addresses 239.192.0.0 to 239.193 …

Recorded on March 23rd, 2022 - 1:00 PM EST Container University 202 Illustrates different Audio over IP (AoIP) transmission formats such as unicast and multicast, and explains the technical considerations and constraints leading to ideal deployments using the correct technologies. Attendees will examine how both economic and technical constraints factor into AoIP format selections Take me to CU202!

The Telos Infinity family of products supports Livewire+ AES67 and receives its output channel information from Infinity's Dashboard software as a Livewire+ channel. Each Livewire+ channel number has a corresponding multicast IP address. Since Livewire+ channels are assigned by Dashboard, their multicast addresses will inherently fall within the available range which is between 1 and 32767. The range of channels available to Infinity can be managed when setting up the Dashboard software (please see the Dashboard user manual for detailed information). Livewire+ devices on the network will automatically resolve to a Livewire+ channel number while non-Livewire+ AES67 devices will display the multicast address. Avoiding duplicate addresses and the resulting conflicts is critical, and so knowing how to convert a Livewire+ channel number to a multicast address is handy when determining whether or not non-Livewire+ devices exist on the network with a multicast address that falls within …

The Telos Infinity family of products supports Livewire+ AES67 and receives its output channel information from Infinity's Dashboard software as a Livewire+ channel. Each Livewire+ channel number has a corresponding multicast IP address. Since Livewire+ channels are assigned by Dashboard, their multicast addresses will inherently fall within the available range which is between 1 and 32767. The range of channels available to Infinity can be managed when setting up the Dashboard software (please see the Dashboard user manual for detailed information). Livewire+ devices on the network will automatically resolve to a Livewire+ channel number while non-Livewire+ AES67 devices will display the multicast address. Avoiding duplicate addresses and the resulting conflicts is critical, and so knowing how to convert a Livewire+ channel number to a multicast address is handy when determining whether or not non-Livewire+ devices exist on the network with a multicast address that falls within …

The Telos Infinity family of products supports Livewire+ AES67 and receives its output channel information from Infinity's Dashboard software as a Livewire+ channel. Each Livewire+ channel number has a corresponding multicast IP address. Since Livewire+ channels are assigned by Dashboard, their multicast addresses will inherently fall within the available range which is between 1 and 32767. The range of channels available to Infinity can be managed when setting up the Dashboard software (please see the Dashboard user manual for detailed information). Livewire+ devices on the network will automatically resolve to a Livewire+ channel number while non-Livewire+ AES67 devices will display the multicast address. Avoiding duplicate addresses and the resulting conflicts is critical, and so knowing how to convert a Livewire+ channel number to a multicast address is handy when determining whether or not non-Livewire+ devices exist on the network with a multicast address that falls within …

The Telos Infinity family of products supports Livewire+ AES67 and receives its output channel information from Infinity's Dashboard software as a Livewire+ channel. Each Livewire+ channel number has a corresponding multicast IP address. Since Livewire+ channels are assigned by Dashboard, their multicast addresses will inherently fall within the available range which is between 1 and 32767. The range of channels available to Infinity can be managed when setting up the Dashboard software (please see the Dashboard user manual for detailed information). Livewire+ devices on the network will automatically resolve to a Livewire+ channel number while non-Livewire+ AES67 devices will display the multicast address. Avoiding duplicate addresses and the resulting conflicts is critical, and so knowing how to convert a Livewire+ channel number to a multicast address is handy when determining whether or not non-Livewire+ devices exist on the network with a multicast address that falls within …

Livewire+ Channel Numbers and Multicast Addresses The Telos Infinity family of products supports Livewire+ AES67 and receives its output channel information from Infinity's Dashboard software as a Livewire+ channel. Each Livewire+ channel number has a corresponding multicast IP address. Since Livewire+ channels are assigned by Dashboard, their multicast addresses will inherently fall within the available range which is between 1 and 32767. The range of channels available to Infinity can be managed when setting up the Dashboard software (please see the Dashboard user manual for detailed information). Livewire+ devices on the network will automatically resolve to a Livewire+ channel number while non-Livewire+ AES67 devices will display the multicast address. Avoiding duplicate addresses and the resulting conflicts is critical, and so knowing how to convert a Livewire+ channel number to a multicast address is handy when determining whether or not non-Livewire+ devices exist on the network with …

SCOPE Version 1.3.35 of the Omnia MPX Node Decoder added the ability to receive a multicast stream. While the encoder, and network also must support multicast, this document assumes these conditions have already been met. For information about configuring Omnia devices that support µMPX to send a multicast stream, please see the following: MPX Node Encoder Omnia 9 Encoder DESCRIPTION In cases where the same MPX signal needs to be delivered to multiple transmitter sites, multicast delivery may be the most efficient method of transport. This document explains how to configure the Omnia MPX Node Decoder to receive a multicast stream from a µMPX Encoder. Requirements Version 1.3.35 or later of MPX Node software is required. If the MPX Node needs to be updated please click here . A license key is required in order for an MPX Node Decoder to receive multicast streams. In the …

… ability to send a multicast stream. While the decoder and network also must support multicast, this document assumes this these conditions have already been met. For information about configuring a decoder MPX Node click here . DESCRIPTION In cases where the same signal needs to be delivered to multiple transmitter sites, multicast may be the most efficient method of transporting streams. Rather than a "push" method of sending to a single IP address, clients in a multicast setup subscribe to a stream and pull from it. Multicast traffic can not be routed over the Internet, meaning multicast transport can be deployed only on closed networks and VPNs. This document explains how to configure the Omnia MPX Node Encoder to transmit a multicast stream. Requirements Version 1.3.35 or newer software is required. If the MPX Node needs to be updated please click here . Know the multicast address to send on …

As of the date of this writing (June - 2019), some of our customers have made us aware of an anomaly in certain Cisco firmware for their Catalyst 3850 and 3650 switches. The situation we have been informed of relates to memory usage that can lead the switch to crash, which will stop all Livewire multicast traffic. There are very few specific details available, however, research suggests that this problem is in the Denali version of their switch software (noted as version 16.3.X) and the specific version of firmware is 16.3.6. Cisco forums and Google indicates this was introduced in 16.3.5b. There is no specific information as to what dates this particular version was shipped or what serial number ranges are affected. Customers who have Cisco 3650 or 3850 switches are encouraged to check their versions and update accordingly. We have information from a …

ined multicast address can also be used instead of a Livewire+™ channel number, simply entered into the text box on the UI. Spkr/HS LW Output Channel Label This is the Livewire+™ AES67 user label associated with the headset speakers and internal Panel loudspeaker multicast stream. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. Aux Input LW Channel Number This is the Livewire+™ AES67 channel associated with the multicast stream created by the audio feed from the XLR input (where fitted) of the INF-MP-16. Users can route this stream to other Livewire+™ AES67 devices such as another intercom Panel. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. A user defined multicast address can also …

defined multicast address can also be used instead of a Livewire+™ channel number, simply entered into the text box on the UI. Spkr/HS LW Output Channel Label This is the Livewire+™ AES67 user label associated with the headset speakers and internal Panel loudspeaker multicast stream. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. Aux Input LW Channel Number This is the Livewire+™ AES67 channel associated with the multicast stream created by the audio feed from the XLR input (where fitted) of the INF-MP-16. Users can route this stream to other Livewire+™ AES67 devices such as another intercom Panel. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. A user defined multicast address can also …

defined multicast address can also be used instead of a Livewire+™ channel number, simply entered into the text box on the UI. Spkr/HS LW Output Channel Label This is the Livewire+™ AES67 user label associated with the headset speakers and internal Panel loudspeaker multicast stream. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. Aux Input LW Channel Number This is the Livewire+™ AES67 channel associated with the multicast stream created by the audio feed from the XLR input (where fitted) of the INF-MP-16. Users can route this stream to other Livewire+™ AES67 devices such as another intercom Panel. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. A user defined multicast address can also …

defined multicast address can also be used instead of a Livewire+™ channel number, simply entered into the text box on the UI. Spkr/HS LW Output Channel Label This is the Livewire+™ AES67 user label associated with the headset speakers and internal Panel loudspeaker multicast stream. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. Aux Input LW Channel Number This is the Livewire+™ AES67 channel associated with the multicast stream created by the audio feed from the XLR input (where fitted) of the INF-MP-16. Users can route this stream to other Livewire+™ AES67 devices such as another intercom Panel. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. A user defined multicast address can also …

ined multicast address can also be used instead of a Livewire+™ channel number, simply entered into the text box on the UI. Spkr/HS LW Output Channel Label This is the Livewire+™ AES67 user label associated with the headset speakers and internal Panel loudspeaker multicast stream. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. Aux Input LW Channel Number This is the Livewire+™ AES67 channel associated with the multicast stream created by the audio feed from the XLR input (where fitted) of the INF-MP-16. Users can route this stream to other Livewire+™ AES67 devices such as another intercom Panel. It will appear in the Dashboard software as an input. Each Livewire+™ AES67 channel number must be unique across the whole installation. A user defined multicast address can also …

ork. The channel number or the multicast address can be manually entered into the text field. Alternately, the Channel Picker , a button to the right of the text field, can be used to find and assign a stream. On pressing the button, a larger pane will appear which give a list of stream discovered through advertisement protocols. Physical object properties will be covered in the unique chapters dedicated to each of the specific models. Meters The meter page is available in audio xNode2s (excludes GPIO model). The meter page provides peak metering for the Senders, Receivers, Hardware Inputs and Hardware Outputs. These meters are confidence metering so you know what state the audio is on the various objects. Sync The sync page has two “tabs” to chose from which defines the type of sync the xNode2 will participate in. The options are Livewire or PTP. Livewire The clock mode option …

… containing an edge switch will continue to function properly independent of the core, if the network connection to the core is lost. This is an important redundancy feature for keeping studios on the air in the case of certain network equipment failures or human error. Pass criteria: Audio and sync operation continues normally when the connection to the core switch is lost. No loss or distortion of audio, no persistent sync light blinking, and no multicast flooding occurs in the edge or the core. Fail criteria: When the connection to the core switch is interrupted, audio loss or distortion occurs or sync light blinking persists. When reconnecting to the core switch, the core does not become IGMP querier again, and all multicast traffic is sent from core to the edge, or multicast flooding at the core or edge. Test configuration: Arrange the network as two edge switches connected to the …

inks: Activating an MPX Node Licensed Features Setting up Multicast: Decoder to receive Multicast MPX Node Encoder Omnia 9 Encoder Configuring MPX Nodes for redundant streams Enhancements Each network interface supports its own unique gateway DNS is now user-configurable Internal log files are now accessible on the standard system page Slider controls now operate more smoothly Ability to set Encoder stream DSCP and TTL settings implemented improved sonic performance With major changes to the Network stack, MPX Node is now capable of sending/receiving redundant streams over separate networks. Sending to the same IP address on both Net1 and Net2 provides packet redundancy to the decoder. Version 1.1.5 (Jan 9, 2020) Features Maintenance release only, no new features in this version. Fixes Fixes a rare issue where an ill-timed reboot could result in corruption of the flash memory.