Network Configuration and Ports

The WAVE 3000 Server unit has two primary connections, the Radio System Adapter connects with the Connect Plus radio system, and the Broadband adapter to connect with the rest of the network.

These adapters reside on the WAVE 3000 Server unit, and are configured prior to shipping. They can be user-configured through the WAVE 3000 Server in Setup > Network Adapters.

The WAVE 3000 Server unit dispatches specific packets (both control and media) to both adapters.

Important:

Do not use IP addresses between 172.31.254.0 through 172.31.254.255. This address range is reserved for internal WAVE 3000 Server connections.

The following network configuration diagram illustrates the connections of the two adapters.

Understanding Ports and Firewalls

If any firewall(s) exist between the WAVE 3000 Server and the external network, then the following ports must be opened.

TCP Ports 443 and 80. The Broadband Adapter always connects with the external network over TCP ports 443, 80,

The WAVE client Connection Port The WAVE client Connection Port (default TCP 4502) is determined by the WAVE 3000 Server administrator and set in Setup > WAVE Mobile Communicator > Connection Port.

If any firewall(s) exist between the WAVE 3000 Server and the XRT 9000/9100 Gateway, then the following ports must be opened.

UDP Ports 7000-7999. The Radio System Adapter always connects with the XRT 9000/9100 Gateway over a UDP port range of 7000-7999. When the WAVE 3000 Server initially connects with the XRT 9000/9100 Gateway, the WAVE 3000 Server obtains this port range from the XRT. If a firewall exists between the XRT and the WAVE 3000 Server, then open the port specified in the XRT UDP Start Port + the next 1000 ports bidirectionally.

The XRT Port Number The XRT Port Number (default TCP 10001) is determined by the WAVE 3000 Server administrator and set in Setup > Radio System Interface. This port is also configured in the XRT 9000/9100 in Settings > Configuration > Client TCP port. The two port settings must match. If any firewall(s) exist between the WAVE 3000 Server and the XRT 9000/9100 Gateway, then this port must be opened bidirectionally.

Potential Network Failure Points

Potential network misconfiguration when deploying a WAVE 3000 Server unit.

Loops via Misrouting If the Enterprise network can communicate directly to the Connect Plus system, then the WAVE 3000 Server may (depending on configuration) attempt to use the Enterprise network to communicate with the Connect Plus system. This configuration can result in loops, degradation of audio, doppelgangers, disconnections, and other problems. Ensure the Enterprise network remains isolated from the Connect Plus network. All traffic from the Enterprise network must route through the WAVE 3000 Server.

WAVE Mobile Communicator Client Connectivity Another potential misconfiguration is failure to route traffic from a DNS address specified in Setup > WAVE Mobile Communicator > Connection Address and Connection Port. If you elect to use a DNS address, then you must ensure the address routes to the IP address specified. In all cases, the WAVE 3000 Connections address must be accessible to WAVE clients for the clients to connect.

Port Blocking As listed in the diagram and in the instructions, ensure the appropriate ports are opened for the WAVE 3000 Server unit if a firewall exists between the Enterprise Network and the WAVE 3000 Server, or between the WAVE 3000 Server and the XRT 9000/9100 Gateway.

About the Anonymous User Field

The Anonymous User Field allows you to conserve radio IDs. The Anonymous User field applies only to those WAVE users without a Subscriber ID. These WAVE users cannot initiate or receive Private Calls with radios, but may still make Private Calls with other WAVE users. If you have a limited number of radio IDs in your radio system, then you can use the Anonymous User field to associate WAVE users with one anonymous radio ID.

The Anonymous User Field contains a single Subscriber ID. This Subscriber ID is sent to the radio system by the WAVE 3000 Server whenever a WAVE user without a Subscriber ID transmits. Its purpose is to identify the WAVE user to the radio system. If you assign Subscriber IDs to all WAVE users in the WAVE 3000 Server, then the Anonymous User ID is never used. This field is required by design, and must be a unique ID that does not occur in the radio system or in the WAVE 3000 Server.

About Broadband-Only Talk Groups

Broadband-only Talk Groups do not integrate with the radio system. Only WAVE clients can use broadband-only Talk Groups. The Supports Radios selection is available when you create or edit a Talk Group in the WAVE 3000 server. Clearing this field creates a Broadband-only Talk Group.

Broadband-only Talk Groups do not use a Talk Group ID and will not conflict with Talk Groups in the radio system.

Note:

The Supports Radios selection is cleared by default. Select Supports Radios to create Talk Groups for use between WAVE and radio users.