Filter
Top Products
Avaya Modular Messaging Concepts and Planning Guide
12-18 November 2004
Avaya Modular Messaging Concepts and
Planning Guide
market are supported to capacity. For larger systems,
configurations with 12- port analog cards should be used.
Identifying which Modular Messaging offer a customer needs
The Modular Messaging offers make it simpler for planners to estimate
the number of voice ports the system would require for a given number of
subscribers. In addition, the offers also provide information on the
number of messaging application server (MAS) units and e-mail readers a
system needs for a given combination of voice ports and subscribers.
To identify which Modular Messaging offer a customer needs, planners
must know:
! The approximate number of subscribers
! The telephony protocol that the system will use
An Example Consider the example of an organization implementing a Modular
Messaging—Microsoft Exchange system to provide services to
approximately 4,000 subscribers.
Further specifications include:
! The customer has purchased a software-only configuration
(Avaya-provided software and customer-provided hardware)
! The Modular Messaging system connects to the telephone system
using H.323-based IP integration.
For such an implementation, a planner could consider the Modular
Messaging H.323-based IP integration offer for Modular Messaging—
Microsoft Exchange. See Table 12-13 on page 12-12.
The Modular Messaging H.323-based IP integration offer provides
support for 60 voice ports that service 4,300 subscribers of Modular
Messaging—Microsoft Exchange.
The system requires three messaging application server (MAS) units to
support 60 ports.
Estimating the additional e-mail readers required
When Modular Messaging subscribers use the telephone user interface
(TUI) to retrieve e-mail messages, Modular Messaging renders the
messages in a computer-generated spoken voice. This
computer-generated voice reads out the envelope information of
messages and contents of e-mail messages.