Installation guide

Planning for WaveNet 25-5
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
Planning for WaveNet
Connecting multiple Wave Servers together via WaveNet requires thorough planning in order
to have a smoothly running WaveNet network. This includes configuring the TCP/IP
connectivity between network nodes, designing a global extension plan for users across all
network nodes, configuring trunking and dialing access plans between nodes—all have to work
together to make a WaveNet network easy to use.
This section discusses the following WaveNet planning topics:
• TCP/IP connectivity between proposed nodes. See page 25-5.
• Trunking considerations. See page 25-6.
• Dial plan considerations. See page 25-7.
• Virus-scanning issues. See page 25-11.
TCP/IP connectivity between proposed nodes
• Use static IP addresses. WaveNet requires that the IP address of each WaveNet node is a
static IP address. Dynamic (DHCP) addresses are not supported.
• Verify connectivity between nodes. Before WaveNet can be expected to communicate
between nodes, it is essential to first establish that the network connections from each
node to all other nodes are functioning properly.
Ping can be used in both directions between proposed WaveNet nodes to verify basic
network connectivity between the nodes, but it will not determine if the MSMQ port
and/or SIP ports are usable between the nodes (see the next bullet.)
• Configure required ports between nodes. The following ports are required to support
communication between WaveNet nodes:
• Microsoft Message Queue (MSMQ). TCP Port 1801.
• SIP ports. For details on how to set up SIP telephony on a Wave Server, see
Chapter 6.
Release 2.0
September 2010