Filter
Top Products
Avaya Modular Messaging Concepts and Planning Guide
13-2 November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Planning for redundancy
When planning a Modular Messaging implementation, Avaya
recommends that planners include redundancy.
Planning for redundancy includes planning for:
! Messaging application server redundancy
! Message Store Server redundancy
In addition, power redundancy must be considered. Avaya requires that
all servers are connected to a UPS for power backup.
Messaging application server redundancy
Messaging application server (MAS) redundancy means that when one of
the MAS units in a multi-MAS voice mail domain goes out of service, the
system can continue to send and receive messages.
Use the following guidelines when planning for MAS redundancy:
! Ensure that the voice ports are distributed evenly across MAS
units in the voice mail domain. To do this, install a balanced
number of voice cards on each MAS. This ensures that if one or
more MAS units are out of service, an adequate number of voice
ports are still available.
For more information on voice ports, see Voice ports
on page 8-2.
! With Digital Set Emulation or QSIG telephony, ensure that
incoming port groups for all MAS units are in the same hunt
group. If incoming port groups are in different hunt groups, calls
presented to a port group on an MAS that is out of service may
not be routed to another voice port on an available MAS.
For more information on hunt groups, see Telephony protocols
on
page 8-8.
! When using an integration device, such as PBXLink, one can
plan for redundancy by using a separate integration device for
each MAS in the voice mail domain. This ensures that if an MAS
goes out of service, all remaining MAS units are still connected
to the switch.
! When using analog telephony, use wiring to enable two MAS
units to be serviced by a single extension on the switch. This
ensures that if one MAS is not available, calls from the switch
extension can go to the other MAS.