… but if I'm trying to talk to 100 people at once, I'd need 100 connections to my phone. That could be a problem. Instead, I might choose to use a radio to address them to reduce the load on my phone. Furthermore, multicast only sends to those devices that wish to receive it, so in order to hear me talking on the radio, someone would have to "tune in" to get my signal. Multicast works a little different than the radio example above. Since the devices themselves are not communicating one-on-one with Devices will first send a request, or "query", to receive a specific multicast stream. While this method is fantastic for reducing the load on a device, it can add considerable load to the switch, as the switch is managing which devices subscribe and unsubscribe to/from the multicast stream. This is a "Callout" that …

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.255 …

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.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 239 …

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 …

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 a …

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 …

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 …

… 3 outputs, and vice versa Tech note: this is implemented by unit A establishing a TCP connection to unit B's LWRP server on port 93. Unit A then subscribes to unit B's port 3 GPIs; whenever it gets a report of a state change it will change its port 2 GPOs to match. Multicast GPIO If you configure a GPIO port with a Livewire channel number (e.g. "12003"), then that is using multicast GPIO. Multicast GPIO is used to establish a connection between an "end point" (e.g. an xNode or a PDM II) and a "console", where the end point's GPIs trigger events on the console, and the console can control the GPOs of the end point. The key to understanding this is that there are two types of GPIO multicast messages. One type is always sent by end points and received by consoles; the …

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 …

Scope This document covers the TTL value assigned to the Telos Vset. It applies to the Vset1 (discontinued), the Vset6, and Vset12 Do not attempt to install this version in any other VX product. It is for Vsets only. Description For most users, the TTL value is not an issue; changing it is unlikely to be the root of the problem that brought you here. If you are here and TTL is your issue, please read on. The TTL value is not a user setting and requires a Vset firmware update to an unreleased version of the firmware, which will set the TTL value to 64. click here for a Description and purpose of TTL The following is based on insights from ChatGPT; The TTL (Time-to-Live) value in networking is crucial in determining the lifespan of data packets in a network. Its primary function is to prevent packets …

… 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 …

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 event …

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 number …

… same make/model (C9300), then any one of them should be able to handle the IGMP querier role at any time, and a mesh network with switches all configured as querier would make sense. However, if budget requires the purchase of less powerful edge switches, then one must consider if a mesh topology is actually of any benefit, and if an IGMP querier failure on an edge switch would be better than all switches flooding multicast traffic across all ports. How much traffic is too much IGMP traffic? The amount of IGMP traffic a switch can handle is limited. To determine if your network is small, medium, or large, Telos as put together a document that can help you find the correct switch to purchase. Also, if in doubt, purchase the more powerful switch. The core switch will be one of the most critical parts of any AoIP network. Conclusion …

multicast subscriptions forbidden Livewire GPIO disabled Is remembered across reboots Preserves Livewire settings that were in use State is reflected on frontpanel (menu reworded) When Livewire is disabled, Livewire source webpage replaced with enable page Warning on Wizard webpage when Livewire is disabled, but audio settings require it Prevent subscription to high-speed Livewire clocks if Livewire clock priority is 0 (always slave) Correct source IP address for Livewire streams that have not been reconfigured since boot Ensure that Livewire streams are never sent with a multicast source address of 0.0.0.0 Ensure that Livewire stream multicast sources are updated when network settings change Never subscribe to Livewire channel 0 or To:0 Calling after seizing a line on hybrid from VX protocol remembers hybrid assignment Fix for some calls not dropping on reorder tone and with CPTD drop enabled Added an option to webpage to change timing …

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 …