Installation guide

Planning for WaveNet 25-8
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
• Different lengths. You may need to implement extensions of different lengths if you
are using a prefix system, since the prefix will be prepended onto the local
extensions before they are published. Users may find it confusing to have to dial
extensions of different lengths depending on whether they are dialing a local user or
a published Gateway user. However, there is no risk of duplication between local
user extensions and Gateway user extensions.
First Digit Table issues
You need to carefully coordinate the First Digit Tables of all the nodes in the network. In order
for any Wave extension (local user extension or Gateway user extension) to be dialed
successfully:
• The first digit of that extension must match an entry in the First Digit Table.
• That First Digit must be configured as
Extension.
• The extension length for that First Digit must match the actual length of the extension.
For example, for extension 3005 to be dialed successfully, the following entry must be defined
in the First Digit Table:
Digit (Type) = 3 (Extension)
Extension Length = 4
When you publish one or more local users to a remote note, the extensions of those users are
compared against the First Digit Table on the subscribing node. WaveNet will not accept a
publication request when the First Digit Table on the subscribing node cannot meet the
requirements listed above.
The possible scenarios are:
•
First digit not yet configured. If the first digit of a user’s extension is currently not in use
(set to
Not Configured) in the First Digit Table, WaveNet automatically updates the First
Digit Table and sets the digit type to
Extension and extension length to the actual length
of the user’s extension. The publication request for this user is accepted, and the
corresponding Gateway user is created on the subscribing node.
Release 2.0
September 2010