Installation guide

Installing WaveNet 25-12
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
2 Obtain the following logon accounts:
• A logon account with Enterprise rights on your Wave Server.
• Logon accounts for other nodes:
•
If you are adding your Wave Server to an existing WaveNet network. Obtain an
Enterprise logon account from any other node in the network.
•
If you are building a new WaveNet network. Obtain an Enterprise logon account
from each other Wave Server that you will add as a node.
Note: Providing valid credentials when adding a Wave Server helps ensure that only
approved nodes are added to the network.
3 Manually eliminate off-premise extension conflicts:
•
Local off-premise extension conflicts. Delete any off-premise extensions configured
on your local Wave Server that would be duplicated by Gateway user extensions to be
published from remote nodes to your local Wave Server.
•
Remote off-premise extension conflicts. Delete any off-premise extensions
configured on remote nodes that would be duplicated by Gateway user extensions that
you plan to publish to those remote nodes after you add your local Wave Server to the
WaveNet network.
See “Non-WaveNet off-premise extension issues” on page 25-9 for more information.
4 Manually eliminate First Digit Table conflicts.
•
Local First Digit Table conflicts:
• Any local First Digits that match the first digit of any Gateway user extensions
that will be published on the local Wave Server, must either be
Unassigned, or set
to
Extension, with the correct length for those Gateway user extensions.
• Any local First Digits set to
External that utilize an SCP that points to a Wave
Server that is also a WaveNet node must be manually deleted before publishing
any users to the Server. Once the WaveNet SCP has been automatically created,
the First Digit can be re-added sharing the WaveNet SCP to restore external
dialing.
•
Remote First Digit Table conflicts:
• Any remote node First Digits that match the first digit of any Gateway user
extensions that will be published on the those remote Wave Servers, must either
be
Unassigned, or set to Extension with the correct length for those Gateway user
extensions.
Release 2.0
September 2010