Avaya 11-300244 Manuel D’Utilisation
Avaya Modular Messaging Concepts and Planning Guide
5-52
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
!
Automated Attendant mailboxes and applications
Modular Messaging supports upgrading the following systems to
Modular Messaging—MSS Release 2:
Modular Messaging—MSS Release 2:
!
Modular Messaging Release 1.0
!
Modular Messaging—MSS, Release 1.1
For upgrades from these systems, the TUI type for each assigned
class-of-service (COS) defaults to Modular Messaging Aria.
class-of-service (COS) defaults to Modular Messaging Aria.
Notes:
!
Systems that are initially configured with all Modular Messaging
Aria TUI mailboxes that later deploy the Modular Messaging
AUDIX TUI must be engineered at that time to meet the
capacities noted in Table 11-5 on page 11-7.
Aria TUI mailboxes that later deploy the Modular Messaging
AUDIX TUI must be engineered at that time to meet the
capacities noted in Table 11-5 on page 11-7.
!
Upgrades are done by service personnel, not the customer.
Modular Messaging also supports upgrading the following systems to
Modular Messaging Release 1.1:
Modular Messaging Release 1.1:
!
Unified Messenger for Microsoft Exchange, Release 5.0 to
Modular Messaging—Microsoft Exchange, Release 1.1
Modular Messaging—Microsoft Exchange, Release 1.1
!
Unified Messenger for IBM Lotus Domino, Release 5.0 to
Modular Messaging—IBM Lotus Domino, Release 1.1
Modular Messaging—IBM Lotus Domino, Release 1.1
Note: Earlier releases of Unified Messenger must be upgraded to
Unified Messenger Release 5.0, prior to upgrading to
Modular Messaging, Release 1.1.
Modular Messaging, Release 1.1.