Installation guide

About WaveNet 25-2
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
•A user is a Wave user on one of the Wave Servers in the WaveNet network:
•A local user is a Wave user whose “home” is the local Wave Server.
•A Gateway user is a Wave user whose “home” is another node in the WaveNet
network, from the point of view of the local node. A Gateway user acts as a place
holder, and is really an off-premise extension that points to the real user who is
“local” on another Wave Server.
This section discusses the following topics:
• About users in a WaveNet network. See page 25-2.
• About publication and subscription. See page 25-3.
• About automatic trunking and routing configuration. See page 25-3.
• About performing a system backup or restore on a WaveNet node. See page 25-4.
• Limitations in this version. See page 25-4.
About users in a WaveNet network
By replicating local users on one Wave Server to other nodes in the WaveNet network, it appears
as if the system administrator had added each user locally.
The following user information is replicated from a Gateway user’s home node to subscribing
remote nodes:
•
User information. Name, extension, greetings, voice title, and so forth.
•
Personal status. Available, Do Not Disturb, In A Meeting, Out Of The Office, or On
Vacation, or any other personal statuses that have been defined.
•
Availability. On-hook, off-hook, ringing.
•
Contacts. A Gateway user’s contacts that have PIN numbers are replicated to subscribing
nodes. This allows a call to be identified as from that contact no matter which node in the
WaveNet network handled the call. A voice message left by that contact at a remote node
will also be identified as from the contact when it is delivered to the user’s home node
voice mailbox. (Contacts that do not have PIN numbers, and any other contact
information—for example, phone numbers—are not currently replicated.)
Release 2.0
September 2010