Installation guide
Planning for WaveNet 25-10
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
As long as there are no duplicate extension numbers, non-WaveNet off-premise extensions are
supported on the same Wave Server as the ones that WaveNet creates automatically for Gateway
users published from other nodes.
• If any non-WaveNet off-premise extensions already exist on a Wave Server with the same
extensions as users that will be published from any other nodes in the WaveNet network,
those off-premise extensions must first be deleted or assigned a different extension
number before publication will be successful.
• If you want to create new non-WaveNet off-premise extensions on a Wave Server that is a
node in a WaveNet network, you must either:
• Assign extension numbers to the new off-premise extensions that do not duplicate
any existing subscribed Gateway users’ extensions.
• Delete the subscribed Gateway users before creating the non-WaveNet off-premise
extensions using those extension numbers.
Also, any SCP currently used for off-premise extensions that points to a Wave Server that is also
a WaveNet node must be manually deleted before publishing any users to the Server.
Private networking issues
To dial an extension via a private network, a user must dial the following:
•
External access code of 2 or more digits to access the private network.
•
Location code of 2-6 digits to identify the Wave Server of the extension being dialed.
•
Called party’s extension.
A WaveNet network and a private network can coexist, however note the following:
• External access code + location code + called party extension digit combinations used for
private networking cannot be duplicated by any Gateway user extensions used with
WaveNet.
• Any SCP currently used for private networking that points to a Wave Server that is also a
WaveNet node must be manually deleted before publishing any users to the Server.
For details on setting up a private network, see “Configuring private networking” on page 9-29.
Release 2.0
September 2010