Clear-Com HMS-4X, HelixNet Partyline, HRM-4X, HLI-4W2, HLI-2W2 Technical Manual
...
TECHNICAL
GUIDE
IP Network Guidance:
HelixNet Digital Partyline
Introduction
HelixNet Digital Partyline
The HelixNet Digital Partyline system offers a tremendous amount of flexibility and
performance to broadcast and live productions requiring partyline/group
communications. HelixNet Digital Network Partyline System delivers all the features and
functions of industry-standard analog partyline systems along with digital audio clarity
over 24 channels and IP connectivity via Powerline or connected Power-over-Ethernet
(PoE). HelixNet operates over any standard single, twisted-pair, shielded cable (like
microphone cable) using our Powerline technology. As this paper will explain, it can also
be interconnected over standard IT network infrastructures via IP/LAN or IP connected
Powerline.
HelixNet
Network
Guidance
This guide provides specifications, best practices and guidance for the integration of
HelixNet into an existing or new IP network. Several of the terms used in this paper are
technical in nature, please see the glossary at the end of the document for explanations
and definitions.
Technical Guide | HelixNet IP Network Guidance Page 2
HelixNet
“Network”
Digital
Partyline
In Figure 1 (below) teams in separate studios (A and B) can communicate with an
outside broadcasting truck on the same digital partyline system over their existing IP
network. With cabling integration possibilities in either XLR or CAT5/6, HelixNet
becomes a flexible solution in multiple scenarios.
- Live Production
- Performing Arts and Theatre
- House of Worship
- Theme Park Ride Communications (Figure 2)
Because of its IP capability, HelixNet is an excellent solution for intercom
communication for Theme Park Rides as shown in Figure 2 (below). A Park’s Network
Operations Center houses sets of HelixNet Main Stations per ride – one HMS is live
production, the second is a redundant back up. The HMS connects to a local switch, the
local switch then connects via CAT5/6 to a second PoE switch at the ride locale. HelixNet
endpoints (HKB and HXII-BP) are placed at strategic positions within the ride to connect
operators and provide a safe experience for the customer.
Technical Guide | HelixNet IP Network Guidance Page 3
Figure 1
HLI-ET2
Network
Topology
The HelixNet Main Station (HMS-4X), Remote Station (HRM-4X), Speaker Station (HKB2X) and Beltpack (HXII-BP) use a 100Mb Network Interface Card (NIC). Devices are
physically added to the network by connecting the RJ45 LAN port on the device to an
Ethernet switch port using a shielded CAT5 or CAT6 cable. HRM, HKB and HXII-BP units
can be powered using PoE Ethernet switches or a local power supply. To connect the
HMS-4X to the Ethernet switch, it must be fitted with a HLI-ET2
2-port Ethernet module (pictured). There are two ports
available on each module. The HLI-ET2 ports act as two normal
switch ports. They can be daisy chained together, but they do
not use Spanning Tree Protocol - connecting both ports to the
same switch can cause redundant paths or loops which will
cause a packet storm and severely degrade both networks.
Best practice would be to use one port to connect to the
network switch, and the second port to daisy chain to other
HelixNet or LQ devices.
Figure 2
Module
Technical Guide | HelixNet IP Network Guidance Page 4
HelixNet devices can be paired/linked together across subnets. They use the mDNS
protocol to auto-discover each other. Figure 3 below shows a typical network topology
with HelixNet endpoints connected directly to the HMS-4X mainstation, endpoints with
a local power supply connected via a switch, and endpoints connected via a PoE switch.
Technical Guide | HelixNet IP Network Guidance Page 5
Figure 3
HMS Network Configuration:
Network
Configuration
Connecting Across Routable Subnets
Company networks typically have multiple subnets or VLANs. IP routers are already configured
to route IP traffic across those subnets. The HMS and HRM/HKB/HXII-BP must have their IP
address, Subnet mask and Gateway set properly (all automatically done when there is a DHCP
server available on the network). If the HRM/HKB/HXII-BP is deployed on a different subnet,
you will need to Pair to Station by entering the IP address of the HMS (Pair to Station by Name
is not available in the Figure 4 example below). “Pair to Station by Name” is discussed later in
this document.
Figure 4
IP Address: 192.168.30.10
Subnet Mask: 255.255.255.0
Gateway: 192.168.30.1
HRM Network Configuration:
IP Address: 172.30.10.67
Subnet Mask: 255.255.0.0
Gateway: 172.30.10.1
Pair to Station:192.168.30.10
HKB Network Configuration:
IP Address: 172.30.10.25
Subnet Mask: 255.255.0.0
Gateway: 172.30.10.1
Pair to Station:192.168.30.10
Technical Guide | HelixNet IP Network Guidance Page 6
Connecting Across Non
-
Routable Subnets
HMS Network Configuration:
The second scenario occurs when an HMS is in a private/separate network, not directly
reachable from where the HRM/HKB is located. A reachable IP router/gateway, on the network
where the HMS is located, must be configured to forward all the IP traffic for port 6001 TCP/UDP
to the HMS (Figure 5):
Figure 5
IP Address: 192.168.30.10
Subnet Mask: 255.255.255.0
Gateway: 192.168.30.1
Here the Router on the HMS side must port-forward everything from 6001 TCP/UDP to
192.168.30.10:6001
HRM Network Configuration:
IP Address: 172.30.10.67
Subnet Mask: 255.255.0.0
Gateway: 172.30.10.1
Pair to Station: 69.70.166.37
HKB Network Configuration:
IP Address: 172.30.10.25
Subnet Mask: 255.255.0.0
Gateway: 172.30.10.1
Pair to Station: 69.70.166.37
Technical Guide | HelixNet IP Network Guidance Page 7
Loading...