Xilica networked audio solutions utilize standard Ethernet networking protocols for configuration, communication, and control, as well as audio over Ethernet via Dante®. Within a single Xilica system, these standard protocols allow for many devices to share control data, DSP resources, and networked audio – effectively enabling a system comprised of many devices to function as one unified system. The standard networking protocols behind a Xilica audio solution allow for inherent scalability and futureproofing as the world of AV over IT expands.

Port Configuration 

Although all Xilica devices utilize Ethernet for control and networked audio, the port configurations differ: 

• Solaro Series audio processors utilize two physically and logically isolated ports, with the LAN port handling all communication with Xilica Designer configuration software and third-party devices, while the Dante® port handles audio networking using the Dante® protocol. No traffic is shared between these two ports within the Solaro processor. However, depending on your network and how a system is designed and deployed, network traffic of the Ethernet control port and the Dante audio port may be maintained as two separated networks, or merged together on a converged network. 
• Networked-audio endpoints such as Gio Series and Sonia amp use a single Ethernet port that’s shared for both control and Dante® networked audio. Though shared on one physical port, individual IP settings can be assigned to LAN control vs. Dante®.
• Control interfaces such as XT80 and Lucia do not incorporate Dante®, and only provide control communication over Ethernet. 

Ethernet Communication 

The LAN ports on all Xilica devices support both 1Gb and 100Mbps links. For proper operation of Xilica devices, including auto-discovery and third-party communication, please ensure your network allows communication on the following ports: 

• TCP port 19150 – main control connection (unicast)
• TCP port 19151 – data subscription/update (unicast)
• TCP port 19152 – inter-device TCP connection (unicast) 
• UDP port 19153 – device heartbeat and auto-discovery (UDP broadcast)
• TCP port 10007 – third-party control TCP connection (unicast) 
• UDP port 10008 – third-party control UDP connection (UDP broadcast)

Network Device Compatibility 

Communication 

All Xilica network devices utilize standard Layer 3 Ethernet communication, and therefore are compatible with all managed and unmanaged network switches. 

Power-over-Ethernet 

The following products are powered over the network using standard PoE (IEEE 802.3af, Class 0), and Xilica has not noted any compatibility issues with standard PoE network switches or PoE injectors. 

• Solaro QR1 audio processor 
• Gio Series Network Endpoints 
• XT80 Touch Controller 
• Lucia Wall Controller 

Sonia Amp is powered by PoE+ (IEEE 802.3at, Type 2) and PoE++ (IEEE 802.3bt Type 3 and 4). The application of IEEE 802.3at and 802.3bt is not as consistent across networked power devices such as network switches and PoE injectors. As a result, Xilica continues to verify operation of Sonia Amp with various manufacturers, and highly recommends the use of Netgear M4250 series switches for optimal results. For a list of other verified PoE+/PoE++ enabled network switches and injectors, please see: Compatibility of PoE power delivery devices for Xilica products

General Network Configuration Best Practices 

1. Disable any EEE (energy efficient ethernet) power-saving features in the network switches as these features can disrupt system communication.
2. Ensure all CAT cables used for interconnects are at least Cat5e and confirmed terminated correctly by testing them with a network cable tester/certifier.
3. Connect the Ethernet control port of all Xilica devices within the system, including any native or third-party control devices, to the same network subnet – preferably to the same physical switch or switch stack.
4. Connect the host computer running the Xilica Designer software to the same subnet as the devices’ Ethernet control ports. A hardwired connection from the host computer to the network is preferred. When hardwired, disable the computer’s WIFI. A hardwire Ethernet connection is required for Dante® information in Xilica Designer. 
5. Ensure Xilica Designer is allowed through the host computer’s firewall and any antivirus software.
6. Xilica devices are DHCP-enabled from the factory. For initial setup, ensure that the network is DHCP- enabled so the network server will automatically allocate appropriate IP addresses to all devices 
   in the system. Ensure that the host computer running the Xilica Designer software is also DHCP- enabled. Once communication has been established and all devices are discovered and online in Xilica Designer’s Network View, the devices can then be assigned static IP addresses if needed. If DHCP is not detected by the Xilica devices or host computer while in DHCP mode, then the devices will eventually revert to and establish communication via a link-local IP address in the 169.254.x.x range.
7. If using a third-party control system, ensure the Xilica devices are ultimately set to static IP addresses when commissioned. If left on DHCP, the device could be allocated a different IP address and break communication with the control system.

Dante Network Configuration Best Practices 

1. Disable any EEE (energy efficient ethernet) power-saving features in the network switches as these types of features will disrupt networked audio.
2. Ensure that Dante traffic does not exceed more than 70% of the total bandwidth of any network link.
3. If using an unmanaged switch, ensure it does not have EEE because on an unmanaged switch it can not be disabled.
4. Dante®-enabled Xilica devices utilize gigabit (FR1) and 100Mbps (QR1) Dante cards. Unless you have a purely 100Mbps network, we recommend using gigabit switches as best-practice.
5. CAT5e or CAT6 cable is recommended as best-practice. For purely 100Mbps networks, CAT5 may be used.
6. Ensure the Dante® port of each device in the system using networked audio is physically connected to the same network segment, subnet, or VLAN. Dante does not work over WIFI.
7. Ensure your Dante® network supports unicast and multicast UDP for Dante® audio distribution.
8. Ensure your Dante® network is DHCP-enabled. If it is not DHCP-enabled the Dante® cards of each device will eventually revert to and establish communication via a link-local IP address in the 169.254.x.x subnet. Some (but not all) Dante® devices allow the setting of static IP addresses.
9. Dante® implements IGMPv3/v2 to assist with multicast management. Support for IGMP is not required in a network – it is in Dante® to make integration into mixed-use networks simpler.
10. Dante® can utilize DiffServ QoS and will tag packets. Dante®’s tags can be integrated into an existing IT network’s QoS scheme. Ensure QoS with strict priority is enabled for 100Mbps or mixed 1Gbps/100Mbps networks. QoS is not required for Dante®-only, gigabit networks.

Additional Resources 

For more detailed information on Dante® audio networking, please see the following resources from Audinate: 

Dante® Information for Network Administrators 

Adding Dante® to Your Network 

Dante® Network Ports 

Dante® Domain Manager