Installation guide

Configuring WaveNet 25-20
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
6 Resolve any issues or timeouts identified. For example:
Check that non-WaveNet network communications to the affected Wave Servers are
functioning normally.
Verify that the problem Wave Servers are up and running.
Verify that WaveNet is running correctly (not stopped, no errors, and so forth) on the
problem nodes.
7 Select another Wave Server in the left pane and repeat these steps to test the connections
between that node and other nodes.
Publishing local users on remote nodes
You can publish local users from any Wave Server displayed in the left pane of the WaveNet
Management applet to one or more other nodes.
Once a user has been successfully published, that user will be displayed in the
Subscribed
Extensions
list for each node that you specified. Note that even though you publish users via a
named extension group, the users are listed individually in the Subscribed Extensions list.
How publishing requests are processed
A new publication request is queued on the home node of the user to be published to other
nodes. WaveNet operates at a relatively lower priority than call processing on a Wave Server.
On a quiet system or network without much phone activity, publication will complete almost
instantaneously. On a very busy system or network, there may be some delay before publication
is complete, with subscribed Gateway users displayed for remote nodes and any errors
displayed in the Publication Error list for the Gateway users home node.
Release 2.0
September 2010