Group Play: no sound at receiving devices
No sound in some zones, slow controls, blocked network during group play with Installer Line products, or during InStreamer play with Multicast option active.
1. Update your trivum Installer Line (Reg,Flex,Audiobox) devices to software V 8.68 or higher. After that, make sure that this does not appear in the system status: Group play notice: If group play does not work between devices disable IGMP at the network switch, or you may have to repeat the update.
2. If problems occur while using the trivum InStreamer device then you may disable the Multicast option under: System / Basic Setup / Enable InStreamer Multicast. You can then no longer use the same InStreamer directly in multiple zones. But you can still listen to the same InStreamer in multiple zones by creating a group.
3. Use the Unicast Audio Option available with V9 software, available in the web configuration under:
System / Basic Setup / Stream Group Play: Use Unicast Audio For Group Play
With this option, audio data in group play is no longer sent by multicast, but by UDP unicast, which should work with every network switch. This works only if not too many trivum devices are part of a group, as it creates a higher load at the master zone that sends the data. It should work safely with 3 devices, for example 3x SC344. It may still work with more devices, so you can just try the option and see if group playback still sounds stable. But, for example, with 10x AudioBox or 10x RP310 systems this option will no longer work. Here you will have to use Multicast and apply Switch configurations as described under 4. below.
4. Use an IGMP capable network switch. At the switch, make sure that IGMP snooping is really used (via the switches configuration surface), including an active "Querier" (possibly Switch dependent).
The group audio play produces a high network traffic. The IGMP protocol makes sure that this traffic reaches only those devices interested in that traffic. But for this the switch needs to understand IGMP, and the trivum device requires the software version listed above.
Switches supporting IGMP are, for example, HP 1920G, HP-E2620-24-PoEP, Cisco SG300-10.
Furthermore, if the system is controlled by iPads, an Apple Airport Express WLAN access point is recommended.
Example configuration with HP 1920G switch:
Enable: IGMP, version 3, with Querier. Then select "Save" at the right top to store all settings permanently. If you think there may be a network loop in your cabling, also enable: MSTP/Global/Enable STP Globally/Enable
Possible problems of network topology at the customer: If multiple switches are used then care must be taken that either all support IGMP, or that the one supporting IGMP is placed at the top, containing all trivum devices. So the network should look like, for example:
to avoid flooding of non trivum devices by unwanted audio messages.
Further technical infos on Switch features can be found on this cisco page.
Configuration of further switches:
With a HP-E2620-24 switch there is only an option "IGMP" by default, without details. It seems that no extra global save option is required. It seems that this switch uses Querier by default. With our tests the IGMP filtering worked immediately. You may also configure details, but for that you need to connect by RS232 cable to that switch. When restarting the switch, to get again to the switch config, you may have to enter it's IP without any path behind. Same as with 1920G, in case there are still network problems you may enable: Spanning Tree/Tree Management/STP
At a Cisco SG300-28 switch select:
Multicast Properties/Bridge Multicast Filter: Enable IGMP snooping/Status: Enable IGMP Table: Edit IGMP Snooping Status: Enable IGMP Querier Status: Enable IGMP Querier Version: IGMPV3
After setting these values, wait 2-3 Minutes before filtering becomes active. Select the blinking "save" button at the top then select: source/running config, destination/startup. The Cisco also supports STP in case of network loops.