Voicemail Pro Installation and Maintenance Guide
Page 71
IP Office
15-601063 Issue 15b (31 May 2006)
Installing Centralized Voicemail
Overview
A single Voicemail Pro server on a central IP Office system can be used to provide voicemail services for
other remote IP Office systems. This is called Centralized Voicemail Pro.
Centralized Voicemail Pro requires the IP Office systems to be linked by an IP Office Small Community
Network (SCN). To avoid the likelihood of two Voicemail Pro servers answering for the same user, only
one centralized Voicemail Pro server can be installed on a single Small Community Network (SCN). For
more information about restrictions that need to be considered before installing Centralized Voicemail,
see Restrictions.
Note
For information about small community networking and setting up VoIP lines, see the IP Office
Manager User Guide.
Notes
By default each IP Office is set to use a broadcast IP address to locate a voicemail server. It can
therefore appear that centralized voicemail is operating before the remote system is set to the
Voicemail Type of Line.
Leaving the systems in this arrangement rather than setting the remote system's Voicemail Type
to Line can cause problems and is not supported.
Planning Requirements
The following factors must be remembered during planning of the centralized Voicemail Pro system:
The Voicemail Server PC is attached to the central system.
A Feature key and Voicemail Pro license key are required for the central system hosting the
Voicemail Pro.
Small Community Networking (SCN) is required between the central system and remote
systems. This document assumes that this has already been set up and tested.
On networked IP Office systems it is possible for centralized voicemail to appear operational
without Small Community Networking. However this operation tends to be unpredictable and so
we support centralized Voicemail Pro only when using Small Community Networking.
VCM modules or VoIP channels are required in the remote and central systems.
The extension and group numbering on all systems must be unique.
The extension and group names on all systems must be unique.
We also recommend that all names and numbers (groups, line, services, etc) on the separate IP
Office systems are kept as unique as possible. This will reduce potential maintenance confusion.
