Installation guide

About WaveNet 25-3
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
The following user information is transferred from remote nodes to a GateWay user's home
node:
•
Voice Mail. Messages recorded on remote nodes are sent to the GateWay user's home
node voice mailbox.
About publication and subscription
The process of replicating users is called “publishing”. You publish one or more users from the
Wave Server where those users live to other nodes. Publication pushes the user information
listed above, as well as any subsequent updates to that information for those users, to the other
nodes that you specify.
On each other Wave Server, a Gateway user is created for each published user. Those users are
said to be “subscribed”.
Important: You do not need to publish all of the users on a Wave Server. Since initial
publication and subsequent updates can generate a substantial amount of network traffic, you
should publish only those users or extensions that need to be directly dialed from other nodes.
Publication steps are described in “Publishing local users on remote nodes” on page 25-20.
What happens when users are deleted from the network
If you delete a published user from a node, that user’s off-premise extension representation is
deleted from the subscribing node. When the last user published from a node is deleted, the SCP,
routing table, and routing rule used to route calls back to that node are automatically deleted
from the subscribing node.
About automatic trunking and routing configuration
When you publish the first local user to another node, WaveNet automatically sets up the
following on the subscribing node:
•One SIP signaling control point (SCP), used to route calls back to the Gateway user’s
home node. (SIP signaling control points determine how IP calls are handled to and from
specific IP addresses.)
• One routing table with one SIP trunk routing rule per table.
Release 2.0
September 2010