Avaya 11-300244 User Manual
Modular Messaging
Concepts and Planning Guide
Release 2 with Avaya Message Storage Server
Release 1.1 with Microsoft Exchange or IBM Lotus Domino
Message Stores
11-300244
Issue 2
November 2004
2004, Avaya Inc.
All Rights Reserved, Printed in U.S.A.
Notice
Every effort was made to ensure that the information in this book was complete
and accurate at the time of printing. However, information is subject to change.
Avaya Web Page
The world wide web home page for Avaya is:
www.avaya.com.
To download an electronic version of this document, visit the Avaya web page.
Preventing Toll Fraud
Toll Fraud is the unauthorized use of your telecommunications system by an
unauthorized party (for example, a person who is not a corporate employee,
agent, subcontractor, or working on your company’s behalf). Be aware that
there is a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications
services.
• Any other equipment networked to your Avaya products
Avaya does not warrant that this product is immune from or will prevent unauthorized use of telecommunication services or facilities accessed through or
connected to it. Avaya is not responsible for any damages or charges that result from either unauthorized uses or from incorrect installations of the security
patches that are made available from time to time.
Suspected security vulnerabilities with Avaya products should be reported to
Avaya by sending mail to securityalerts@avaya.com.
Federal Communications Commission Statement
Part 15: Class A Statement. This equipment has been tested and found to
comply with the limits for a Class A digital device, pursuant to Part 15 of the
FCC Rules. These limits are designed to provide reasonable protection against
harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instructions, may cause
harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference, in which case the user
will be required to correct the interference at his own expense.
Avaya Fraud Intervention
If you suspect that you are being victimized by toll fraud and you need technical
assistance or support, call PBX Security at 1 800 643 2353, for domestic access or 720 444 3728, for international access.
Providing Telecommunications Security
Telecommunications security of voice, data, and/or video communications is
the prevention of any type of intrusion to, that is, either unauthorized or malicious access to or use of, your company’s telecommunications equipment by
some party.
Your company’s “telecommunications equipment” includes both this Avaya
product and any other voice/data/video equipment that could be accessed via
this Avaya product (that is, “networked equipment”).
An “outside party” is anyone who is not a corporate employee, agent, subcontractor, or working on your company’s behalf. Whereas, a “malicious party” is
Anyone, including someone who may be otherwise authorized, who accesses
your telecommunications equipment with either malicious or mischievous intent.
Such intrusions may be either to/through synchronous (time-multiplexed and/
or circuit-based) or asynchronous (character-, message-, or packet-based)
equipment or interfaces for reasons of:
• Utilization (of capabilities special to the accessed equipment)
• Theft (such as, of intellectual property, financial assets, or toll-facility
access)
• Eavesdropping (privacy invasions to humans)
• Mischief (troubling, but apparently innocuous, tampering)
• Harm (such as harmful tampering, data loss or alteration, regardless of
motive or intent)
Be aware that there may be a risk of unauthorized intrusions associated with
your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a variety of losses to your company, including but not limited to, human/data privacy, intellectual property, material assets,
financial resources, labor costs, and/or legal costs).
Industry Canada (IC) Interference Information
This digital apparatus does not exceed the Class A limits for radio noise emissions set out in the radio interference regulations of Industry Canada.
Le Présent Appareil Nomérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A préscrites
dans le reglement sur le brouillage radioélectrique édicté par le Industrie Canada.
Trademarks
All trademarks identified by ® and ™ are registered trademarks or trademarks
of Avaya Inc. All other trademarks are the property of their respective owners.
Obtaining Products
To learn more about Avaya products and to order products, visit
www.avaya.com.
European Union Declaration of Conformity
The “CE” mark affixed to the equipment means that it conforms to the referenced European Union (EU) Directives listed below:
EMC Directive89/336/EEC
Low-Voltage Directive73/23/EEC
For more information on standards compliance, contact your local distributor.
Warranty
Avaya Inc. provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warranty. In addition, Avaya’s
standard warranty language as well as information regarding support for this
product, while under warranty, is available through the following web site:
www.avaya.com/support.
Your Responsibility for Your Company’s Telecommunications Security
The final responsibility for securing both this system and its networked equipment rests with you – an Avaya customer’s system administrator, your telecommunications peers, and your managers. Base the fulfillment of your
responsibility on acquired knowledge and resources from a variety of sources
including but not limited to:
• Installation documents
• System administration documents
• Security documents and anti-virus patches
• Hardware-/software-based security tools
• Shared information between you and your peers
• Telecommunications security experts
To prevent intrusions to your telecommunications equipment, you and your
peers should carefully program and configure your:
• Avaya provided telecommunications systems and their interfaces
• Avaya provided software applications, as well as their underlying hardware/software platforms and interfaces
Preface
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Conventions and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Avaya Modular Messaging documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Avaya Modular Messaging support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Customer’s responsibility for their system’s security. . . . . . . . . . . . . . . . . . . . . . . . xiv
Section 1 Introduction
Chapter 1 Introducing Avaya Modular Messaging
Contents
Benefits of Avaya Modular Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Mobility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Familiar telephone user experience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Multiple language support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Ease of administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Switch integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Industry standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Section 2 Concepts
Chapter 2 Modular Messaging versions
Avaya Modular Messaging versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Modular Messaging—MSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Avaya Modular Messaging Concepts and
Planning Guide
iiiNovember 2004
Avaya Modular Messaging Concepts and Planning Guide
Modular Messaging—Exchange and Modular Messaging—Domino . . . . . . . . . . . . . . . . . 2-4
Comparing characteristics of Modular Messaging versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Chapter 3 Modular Messaging server components
Messaging application server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
MAS services and functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Modular Messaging software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Distributing server components and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Message store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Functions of a message store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Avaya Message Storage Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Microsoft Exchange server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
IBM Lotus Domino server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Directory server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Chapter 4 Modular Messaging interfaces
Telephone user interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
The caller interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
The subscriber interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Multilingual support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Graphical user interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Client Add-in for Microsoft Outlook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Subscriber Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Desktop deployment of Client Add-in for Microsoft Outlook and Subscriber Options . . . 4-22
Avaya Modular Messaging Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Standards-based clients with Modular Messaging—MSS . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
IBM Lotus Notes with IBM Lotus DUC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Unified Communication Center Speech Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Administrative and management interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Message Storage Server administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Messaging application server administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Reporting capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Voice mail domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Chapter 5 Modular Messaging features
Key features and capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Modular Messaging—MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Modular Messaging—Exchange and Modular Messaging—Domino . . . . . . . . . . . . . . . . . 5-8
iv November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Text-to-speech conversion capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9
Multilingual text-to-speech. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9
SNMP with Modular Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11
SNMP system queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11
Logs and notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12
MAS alarms and logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12
MSS alarms and logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13
SNMP alarm notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-15
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-17
Audio encoding formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-18
GSM 6.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-18
G.711 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-18
Binary size and MIME transfer size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19
Offline messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-21
Offline Call Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-22
Offline access to Call Answer messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23
When a Microsoft Exchange message store goes offline . . . . . . . . . . . . . . . . . . . . . . . . . . .5-24
When an IBM Lotus Domino message store goes offline . . . . . . . . . . . . . . . . . . . . . . . . . .5-25
Messaging with e-mail clients in offline mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-25
N+1 server configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27
Added redundancy with N+1 server configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27
Distributing ports in an N+1 server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-28
Communities and sending restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-29
System lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-31
Modular Messaging—MSS Enhanced-List Application . . . . . . . . . . . . . . . . . . . . . . . . . . .5-31
Modular Messaging—MSS Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32
Modular Messaging—Exchange and Modular Messaging—Domino system lists . . . . . . .5-33
Personal Distribution Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-34
PDL members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-34
PDL labels and identifiers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-35
Working with PDLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-36
Addressing messages to PDLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-38
Other concepts related to PDL addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-41
Message Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-42
Creating private messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-42
Accessing private messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-43
Creating private Call Answer messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-44
The Privacy Enforcement Level privacy parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-45
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
v
Avaya Modular Messaging Concepts and Planning Guide
Restricting client access to mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
Standard RFC822 Privacy Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Summary of the privacy parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Subscriber data migrations and system upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Chapter 6 Addressing and networking
Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Primary mailbox address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Local mailbox numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Numeric Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Additional forms of addressing from the TUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Additional forms of addressing from the PC user interface . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Multiple mailboxes and alias extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Multiple extensions per mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Multiple mailboxes per extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Networking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Modular Messaging—MSS and the Message Networking Server . . . . . . . . . . . . . . . . . . . 6-15
Message Networking server among multiple Modular Messaging—MSS systems . . . . . . 6-16
Chapter 7 Modular Messaging and fax servers
Modular Messaging—MSS native fax server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Providing interoperability with third-party fax servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
An overview of third-party fax servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Requirements for fax server interoperability with Avaya Modular Messaging . . . . . . . . . . 7-6
Enabling subscribers for fax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Routing inbound fax calls to the third-party fax server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Working with fax messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Fax messaging from the TUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Fax messaging from the PC user interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Chapter 8 Telephony concepts
Voice ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Switch integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Switch integration options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Integration features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Telephony protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Hunt groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
vi November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Types of hunt groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11
Chapter 9 Support for message and call notification
Message notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
Call Me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
Notify Me - Automatic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4
Overview of Message Waiting Indicator (MWI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6
Call notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9
Caller-requested Notify Me . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9
Find Me. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10
Intercom paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13
Call screening from the Automated Attendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13
Combining features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-14
Section 3 Planning
Chapter 10 Designing voice mail domains
General rules for voice mail domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2
Rules for MSS messaging environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5
Rules for Microsoft Exchange messaging environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-6
Rules for IBM Lotus Domino messaging environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7
Considering the proximity of the switch to e-mail message stores. . . . . . . . . . . . . . . . . . . .10-8
Chapter 11 System capacities
Voice mail domain capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2
Avaya Message Storage Server capacities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4
Messaging application server capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-5
MAS port capacities (Modular Messaging—MSS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-6
MAS port capacities (Exchange and Domino) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8
Chapter 12 Port Sizing
Port sizing using Modular Messaging offers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-2
Port usage patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-2
Modular Messaging—MSS offers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-3
Modular Messaging Aria TUI offers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-5
Modular Messaging AUDIX TUI offers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-8
Offers for Modular Messaging with Exchange and Domino message stores . . . . . . . . . . .12-10
Identifying which Modular Messaging offer a customer needs . . . . . . . . . . . . . . . . . . . . .12-18
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
vii
Avaya Modular Messaging Concepts and Planning Guide
Estimating the additional e-mail readers required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
Port sizing without using Modular Messaging offers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
Concepts a planner must know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
Estimating port requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Calculating the number of messaging application servers required . . . . . . . . . . . . . . . . . 12-26
Evaluating the additional load on the network and e-mail servers . . . . . . . . . . . . . . . . . . 12-27
Chapter 13 Other planning considerations
Planning for redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Messaging application server redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Message Store Server redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Messaging application server load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Distribution of server components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Recommendations for the Tracing Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Recommendations for the Offline Call Answer Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Hunt algorithm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Calculating the message storage capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
Storage space available on the MAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
Storage space available on the MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
Calculating the storage space on e-mail servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
Storage planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
Fax port and storage planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
Message retention estimate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
Calculating the number of desktop users per voice mail domain . . . . . . . . . . . . . . . . . . . . . . 13-20
IMAP4 client limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
POP3 client limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21
Port requirement planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
Appendix A Grade of service
Appendix B Customer environment
Site requirements for Avaya servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Environmental requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Weight and space considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Customer-provided cabinet requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Modular Messaging and the Microsoft Windows domain infrastructure . . . . . . . . . . . . . . . . . . B-5
Modular Messaging and the Windows domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
viii November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Subscriber and administrator authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Considerations when implementing Modular Messaging—MSS . . . . . . . . . . . . . . . . . . . . . . . . B-7
Considerations when implementing Modular Messaging with e-mail servers . . . . . . . . . . . . . B-10
Minimum hardware requirements and supported software (MSS version). . . . . . . . . . . . . . . . B-12
MAS specifications with Modular Messaging—MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12
Client Add-in for Microsoft Outlook requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13
Subscriber Options requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
Modular Messaging Web Client requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15
Tracing Server requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17
Tracing Server or Offline Call Answer store requirements . . . . . . . . . . . . . . . . . . . . . . . . B-18
Mailbox Manager Minimum Requirements for Single User Implementation . . . . . . . . . . B-20
Administration Client requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21
Browser requirements for the MSS administration interface . . . . . . . . . . . . . . . . . . . . . . . B-21
Compatibility with Avaya Integrated Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22
Minimum hardware requirements and supported software (Exchange and Domino). . . . . . . . B-23
Messaging application server requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23
Tracing Server requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Tracing Server or Offline Call Answer store requirements . . . . . . . . . . . . . . . . . . . . . . . . B-28
Administration Client requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29
Caller Applications Editor requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-30
Client Add-in for Microsoft Outlook requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-31
Subscriber Options requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32
Subscriber Administration Extension requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-34
Peer Exchange Server requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-35
Peer Domino Server requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36
Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37
Appendix C Considerations with Message Networking server
Glossary
Index
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
ix
Avaya Modular Messaging Concepts and Planning Guide
x November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Overview
Preface
This guide provides:
! The concepts underlying Avaya Modular Messaging, including
discussions of voice mail domains, addressing, and telephony.
! A description of the hardware and software components of Avaya
Modular Messaging.
! A glossary of Avaya Modular Messaging terms.
Important: Modular Messaging Release 2 does not support Microsoft
Exchange and IBM Lotus Domino message stores.
All information related to Modular Messaging—Microsoft
Exchange and Modular Messaging—IBM Lotus Domino is
specific to Modular Messaging Release 1.1.
Audience
November 2004
This guide is intended for use by anyone learning more about Avaya
Modular Messaging, including those recommending, purchasing,
designing, or installing Avaya Modular Messaging. In addition, readers
that are interested in implementing and planning for Modular Messaging,
either the Microsoft Exchange version or the IBM Lotus Domino version,
should also be familiar with the concepts and operation of Microsoft
Windows and Microsoft Exchange or IBM Lotus Domino server, as
appropriate.
Avaya Modular Messaging Concepts and
Planning Guide
xi
Avaya Modular Messaging Concepts and Planning Guide
Conventions and definitions
This guide uses the following conventions:
Convention Description
Initial capital letters Names of applications, programs, menu
italic type Book titles
items, and dialog boxes
Information applicable only to Avaya
Modular Messaging—Avaya Message
Storage Server (MSS) version.
Information applicable only to Avaya
Modular Messaging—Microsoft Exchange
version.
Information applicable only to Avaya
Modular Messaging—IBM Lotus Domino
version.
This guide uses the following terms and definitions:
Term Definition
Text messages The term ‘text messages’ refers to e-mail
messages or messages with binary
attachments, stored on the message store.
The message store may be a Microsoft
Exchange server, an IBM Lotus Domino
server, or an Avaya Message Storage Server
(MSS).
Corporate e-mail The term ‘corporate e-mail messages’ refers
to e-mail messages stored on the corporate
e-mail system. The corporate e-mail system
may be a Microsoft Exchange server, an
IBM Lotus Domino server, or any other
e-mail system.
Modular Messaging—
MSS
Modular Messaging—
Exchange
Refers to the Modular Messaging—Avaya
Message Storage Server system.
Refers to the Modular Messaging—
Microsoft Exchange system.
Modular Messaging—
Domino
xii November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Refers to the Modular Messaging—IBM
Lotus Domino system.
Aria TUI Unless otherwise noted, Aria TUI refers to
the Aria telephone user interface for Modular
Messaging.
AUDIX TUI Unless otherwise noted, AUDIX TUI refers
to the AUDIX telephone user interface for
Modular Messaging.
Avaya Modular Messaging documentation
The CD-ROM Avaya Modular Messaging Release 2 Documentation,
11-300121 contains all documentation about Avaya Modular Messaging,
including instructions for administration, installation, and maintenance.
For switch integration documentation, see the configuration notes
available from the Avaya Modular Messaging support representative or
from the Avaya Support Center at http://support.avaya.com.
Configuration notes are general guidelines that provide integration
information for several types of switches and fax devices. The
configuration notes include comprehensive step-by-step instructions on
various tasks including configuring the Modular Messaging system for
switch integration and the related switch programming.
Preface
Important: Avaya has taken stringent security measures to address
security concerns of Modular Messaging customers. This
guide does not cover these security features.
For information on security, see ‘System security’ on the
CD-ROM Avaya Modular Messaging Release 2
Documentation, 11-300121. The document informs owners
of the steps that Avaya has taken to secure the Modular
Messaging system. It describes how to use the system
administration tools to minimize unauthorized intrusions and
provides safeguards and measures that customers should take
to ensure that the Modular Messaging servers operate in a
secure manner.
Avaya Modular Messaging support
For Avaya Modular Messaging support and for important, up-to-date
information on Avaya Modular Messaging, visit the Avaya Support
Center at http://support.avaya.com
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
xiii
Avaya Modular Messaging Concepts and Planning Guide
Customer’s responsibility for their system’s security
No telecommunication system can be entirely free from the risk of
unauthorized use.
Customers have ultimate control over the configuration and use of the
product and are solely responsible for ensuring the security of their
systems. Customers who administer and use the system can tailor the
system to meet their unique needs and are in the best position to ensure
that the system is secure to the fullest extent possible. Customers are
responsible for keeping themselves informed of the latest information
such as security patches, anti-virus updates and other relevant information
for configuring their systems to prevent unauthorized use. System
managers and administrators are also responsible for reading all the
recommendations, installation instructions, and system administration
documents provided with the product in order to understand the features
that can introduce risk of toll fraud and the steps that need to be taken to
reduce that risk.
Avaya does not warrant that this product is immune from or will prevent
unauthorized use of telecommunication services or facilities accessed
through or connected to it. Avaya will not be responsible for any damages
or charges that result from either unauthorized uses or from incorrect
installations of the security patches that are made available from time to
time. To aid in combating these crimes, Avaya intends to strengthen
relationships with its customers and its support of law enforcement
officials in apprehending and successfully prosecuting those responsible.
Suspected security vulnerabilities with Avaya products should be reported
to Avaya by sending mail to securityalerts@avaya.com. Reported
vulnerabilities are prioritized and investigated. Any corrective actions
resulting from the vulnerability investigation are posted at
http://support.avaya.com/security. Whether or not immediate support is
required, please report all toll fraud incidents perpetrated on Avaya
services to Avaya Corporate Security. In addition to recording the
incident, Avaya Corporate Security is available for consultation on
product issues, investigation support, law enforcement, and education
programs.
See ‘Modular Messaging and Security’ on CD-ROM Avaya Modular
Messaging Release 2 Documentation, 11-300121.
xiv November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Section 1
Introduction
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Avaya Modular Messaging Concepts and Planning Guide
Avaya Modular Messaging Concepts and
Planning Guide
November 2004
1
Introducing Avaya Modular
Messaging
Avaya Modular Messaging is a unified messaging solution that addresses
the different unified messaging needs of customers through the following
versions:
! Modular Messaging—MSS version. With this version, voice and
fax messages are stored on a separate message store from
corporate e-mail messages. While corporate e-mail messages are
stored on any existing e-mail infrastructure, voice and fax
messages are stored on an Avaya-produced Message Storage
Server (MSS).
! Modular Messaging—Microsoft Exchange version. This version
makes use of a common, unified message store (Microsoft
Exchange) for all types of messages.
Note: Modular Messaging Release 2 does not support this
version.
! Modular Messaging—IBM Lotus Domino version. This version
makes use of a common, unified message store (IBM Lotus
Domino) for all types of messages.
Note: Modular Messaging Release 2 does not support this
version.
Depending on the version, Modular Messaging can be used as any one of
the following:
! A voice and fax messaging system, where all voice and fax
messages are stored on an internal Modular Messaging Message
Storage Server, the MSS. For more information, see Modular
Messaging—MSS on page 2-2.
! A part of a unified messaging solution for access to messages.
Voice, text, and fax messages are stored on the Avaya MSS, and
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
1-1
Avaya Modular Messaging Concepts and Planning Guide
corporate e-mail is maintained on a separate corporate e-mail
system. For more information, see Modular Messaging—MSS
page 2-2.
! A voice, fax, text, and e-mail messaging system, where all
messages are stored on a common message store—either
Microsoft Exchange or IBM Lotus Domino. For more
information, see Modular Messaging—Exchange and Modular
Messaging—Domino on page 2-4.
While all Modular Messaging versions have such functionality in
common as Call Answer and telephone access to voice messages, they
differ in their implementation, architecture, and configuration.
on
For more information, see Avaya Modular Messaging versions
2-2.
on page
1-2 November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Introducing Avaya Modular Messaging
Benefits of Avaya Modular Messaging
Scalability
Avaya Modular Messaging is compatible with several industry
telecommunications systems, offering service from 4 to 690 ports
to 100,000
capabilities, thus supporting international operations of customers.
Depending on the product version, Modular Messaging supports from 4
to 690 ports within a single voice mail domain. For more information on a
voice mail domain, see Voice mail domain
Modular Messaging—MSS supports a maximum of 144 ports per voice
mail domain.
Modular Messaging—Microsoft Exchange and Modular Messaging—
IBM Lotus Domino support a maximum of 690 ports per voice mail
domain.
For more information on the number of subscribers Modular Messaging
supports, see Chapter 11, System capacities.
A voice mail domain can serve a network of switches, provided the
administrator ensures that the network uses a single switch as a gateway
to the voice mail domain.
1
subscribers. Modular Messaging provides multilingual
on page 4-33.
1
and up
Mobility
With Avaya Modular Messaging, subscribers can send and retrieve
messages even when they are away from the office.
Modular Messaging provides subscribers mobile access to their messages
from any touch-tone telephone, using the Modular Messaging telephone
user interfaces (TUIs). With the Microsoft Exchange or IBM Lotus
Domino versions, the TUI provides access to voicemail and corporate
e-mail messages. With the MSS version, the TUIs provide access only to
voice, fax, and text messages stored on the Avaya message store server
(MSS), and not to corporate e-mail messages stored on the corporate
e-mail store. However, MSS subscribers that desire mobile access to
corporate e-mail messages can use the Unified Communication Center
(UCC) Speech Access client or Modular Messaging Web Client. UCC
Speech Access provides speech access and voice control of corporate
e-mail and voicemail messages, regardless of whether they are stored in
1. The Modular Messaging version determines the number of ports and subscriber mailboxes the
system supports. For more information, see Voice mail domain capacities
on page 11-2.
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
1-3
Avaya Modular Messaging Concepts and Planning Guide
separate or unified message stores. For more information, see Unified
Communication Center Speech Access on page 4-27. Modular Messaging
Web Client is a visual interface to the Modular Messaging mailbox. Using
that interface, subscribers can create, send, receive, and organize
messages. Subscribers can listen to voice messages, read text and
corporate e-mail messages, view fax messages, and manage file
attachments, all from your PC.
Modular Messaging also provides enhanced notification functionality,
enabling quick response to any type of incoming communication, whether
on site or remote. Subscribers can reply to a message, regardless of its
original form.
Avaya Modular Messaging supports real-time Find Me capability,
telephone notification, message waiting indicator (MWI), and other
advanced notification mechanisms, thus increasing subscriber
availability.
Note: Find Me is not supported for analog integrations.
Familiar telephone user experience
Subscribers can use the Modular Messaging TUIs from any touch-tone
telephone to access, compose, and send messages, and to configure their
mailboxes.
Current Avaya Octel 250/350 subscribers (using the Aria TUI), Avaya
Intuity AUDIX, and DEFINITY AUDIX subscribers will have a
consistent and familiar telephone user experience with the Avaya
Modular Messaging telephone user interfaces.
Avaya Modular Messaging comes with the Aria TUI for Modular
Messaging and the AUDIX TUI for Modular Messaging. Administrators
can assign subscribers their preferred TUI, based on a class-of-service
(COS). The Aria TUI for Modular Messaging and the AUDIX TUI for
Modular Messaging are similar to, but not exactly the same as, the
respective Aria or AUDIX product.
For more information on the TUIs, see Telephone user interfaces
4-2.
Multiple language support
on page
Modular Messaging supports multiple languages and allows multinational
companies to use the system in virtually any of their offices worldwide.
1-4 November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Language
Language
Introducing Avaya Modular Messaging
Table 1-1 describes the different announcement languages that Modular
Messaging supports. Of the languages that Modular Messaging supports,
one language is defined as the system default language, up to three
languages can be defined for the system Automated Attendant and Call
Answer, and one language can be specified per mailbox for logged in
messaging sessions.
Table 1-1. Modular Messaging multiple language support
Aria Caller interface
Modular Messaging Release 1.1
Common Caller Interface
Modular Messaging Release 2
Modular Messaging Aria TUI
Modular Messaging AUDIX TUI
Text-to-Speech1Subscriber Options
Client Add-in for Microsoft Outlook
(Modular Messaging— MSS)
Client Add-in for Microsoft Outlook
(Modular Messaging—Exchange)
Modular Messaging Web Client
Chinese
! Simplified Y Y Y
! Traditional Y Y Y
! PRC Y Y Y Y Y
! Taiwan Y Y Y Y Y
Dutch
Y Y Y Y Y Y Y Y
English
! Australia Y Y
! United
Y Y Y Y Y
Kingdom
! US Y Y Y Y Y Y
! US-123 Y Y Y Y
! US-ABC Y
! US-TTY
2
Y Y Y Y
Avaya Voice Player
French
! Canada Y Y Y Y
! France Y Y Y Y
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
1-5
Avaya Modular Messaging Concepts and Planning Guide
! Standard Y Y Y Y Y Y
German
Italian
Japanese
Y Y Y Y Y Y Y Y Y Y
Y Y Y Y Y Y Y Y Y Y
Y Y Y Y Y Y Y Y
Portuguese
! Brazil Y Y Y Y Y Y Y Y Y Y
Spanish
! International Y Y Y Y Y
! Latin American Y Y Y Y Y
1. In Modular Messaging—Microsoft Exchange version and Modular Messaging—IBM Lotus Domino
version, the TUIs automatically provide text-to-speech (TTS) conversions based on the language of the
e-mail message.
2. Customer systems that use TDD/TTY must use G.711 audio encoding.
Note: Callers calling from TTY devices may not be able to leave
Call Answer messages if their TTY device cannot dial
touchtones after a call is in progress.
Ease of administration
All versions of Modular Messaging, irrespective of whether they have
unified or separate message stores, provide certain administrative
benefits.
Modular
Messaging—MSS
Modular Messaging—MSS is based on industry standards, including
Lightweight Directory Access Protocol (LDAP). Modular Messaging—
MSS interoperates with the following Avaya administrative tools to
facilitate common administration across multiple Avaya products:
! Avaya Site Administration (Release 2.0 or later) and Avaya
MutliSite Administration (Release 2.1 or later): These
applications support Modular Messaging subscriber data. For
more information, see Avaya Integrated Management
on page
4-29.
! ProVision: This application is used to provision users on an
Avaya Communication Manager or a DEFINITY switch and
Modular Messaging.
! The Mailbox Manager application: Modular Messaging—MSS
administrators can use this application for mailbox
1-6 November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Introducing Avaya Modular Messaging
administration. For more information, see Mailbox Manager on
page 4-28.
The MSS supports subscriber administration and subscriber directory
updates from these products via LDAP. The internal LDAP directory is
the primary storage location for names, e-mail addresses, extensions, and
other subscriber data of subscribers of the Modular Messaging system.
Web-based administration of the MSS facilitates common
organization-wide administration, diagnostics, and reporting.
Administrators can use these Web-based administration pages to perform
general system administration for the MSS and subscriber administration.
Administration tasks include subscriber management and password
administration. These administration pages also provide diagnostic logs.
Modular Messaging
(Exchange and
Domino)
Switch integration
Modular Messaging—Microsoft Exchange and Modular Messaging—
IBM Lotus Domino offer the following administrative benefits:
! Leveraging the existing Microsoft Exchange or IBM Lotus
Domino infrastructure eliminates the need to retain and manage
separate voice and corporate e-mail systems.
! For each subscriber, all voicemail, telephone answering,
corporate e-mail, and fax messages are stored on the same
message store server.
! A single administrator can handle all messaging administration.
! Management tools are combined into one application.
! A single directory for addressing of voice and corporate e-mail
simplifies system management.
! Updates to the directory are automatically replicated to all
systems, so that changes need to be made only once for voice and
e-mail.
Industry standards
November 2004
Modular Messaging supports multiple switch integrations (SWINs) for
switches and private branch exchanges (PBXs) from several major
manufacturers. Customers can choose a switch integration that requires
only minimum changes to the current infrastructure to implement
Modular Messaging.
Modular Messaging supports the following industry standards:
Avaya Modular Messaging Concepts and
Planning Guide
1-7
Avaya Modular Messaging Concepts and Planning Guide
! Industry-standard platforms, telephony interfaces, and operating
systems:
— Intel processors
— Dialogic Tip/Ring boards, Dialogic T1 and E1 port boards,
and Dialogic Digital Set Emulation (DSE) port boards
— Linux operating system (Avaya MSS) and Microsoft
Windows operating system (Messaging application server)
! IP and Internet standards: IP for server-to-server transport, IP
Networking, IMAP4 and POP3 client access to messages,
SMTP/MIME for sending and receiving messages, and LDAP for
attribute storage (for example, user and system data) and
directory queries (for example, name, address)
! Switch integrations: H.323-based IP integration, Q.Signaling
(QSIG), Enhanced Inband Analog, RS232 for serial switch
integrations (SMSI/SMDI), and Digital Set Emulation (DSE)
! Audio encoding formats: Global System for Mobile
Communications (GSM) and G.711 (A-law and µ-law). The
amount of space required to store GSM-encoded messages is
considerably smaller than the amount of space required to store
G.711-encoded messages. For example, a voice message that is
one minute long would require approximately 95.2 KB when
encoded using the GSM format and approximately 468.8 KB
when encoded using the G.711 format.
! Modular Messaging complies with standards established by the
government and standards bodies, for mandatory compliance
areas, such as Product Safety, Electro Magnetic Compliance
(EMC), and Telecommunications.
1-8 November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Section 2
Concepts
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Avaya Modular Messaging Concepts and Planning Guide
Avaya Modular Messaging Concepts and
Planning Guide
November 2004
2
Modular Messaging versions
This chapter introduces the Modular Messaging versions and provides a
comparison of some key characteristics of these versions.
This chapter includes the following topics:
! Avaya Modular Messaging versions on page 2-2
! Comparing characteristics of Modular Messaging versions on
page 2-6
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
2-1
Avaya Modular Messaging Concepts and Planning Guide
Avaya Modular Messaging versions
To suit the particular architectural needs and e-mail infrastructure of
customers, Avaya Modular Messaging is available in the following
versions:
! Avaya Modular Messaging—Avaya Message Storage Server
(Modular Messaging—MSS)
This configuration, also known as Avaya S3400-family of
servers, contains one or more Avaya MAS units and a single
Avaya MSS (MSS—S, standard availability or MSS—H,
high-availability). A private Ethernet LAN provided with the
product connects the MAS and MSS.
! Avaya Modular Messaging—Microsoft Exchange version
(Modular Messaging—Exchange)
This configuration contains one or more MAS units connected to
one or more Microsoft Exchange servers. The MAS units may be
provided by Avaya, or may be provided by the customer. Avaya
provides the Modular Messaging software that must be installed
on the customer-provided MAS. The Microsoft Exchange servers
are customer-provided.
For information on the hardware and software requirements of a
customer-provided MAS, see Messaging application server
software requirements in Appendix B, Customer environment.
! Avaya Modular Messaging—IBM Lotus Domino version
(Modular Messaging—Domino)
This configuration contains one or more MAS units connected to
one or more IBM Lotus Domino servers. The MAS units may be
provided by Avaya, or may be provided by the customer. Avaya
provides the Modular Messaging software that must be installed
on the customer-provided MAS. The IBM Lotus Domino servers
are customer-provided.
For information on the hardware and software requirements of a
customer-provided MAS, see Messaging application server
software requirements in Appendix B, Customer environment.
Modular Messaging—MSS
A Modular Messaging—MSS system can be configured for use as a
voicemail system providing only voice and fax messaging, or as part of a
unified messaging solution for access to messages. In the latter scenario,
voice, text, and fax messages are stored on the MSS, and corporate e-mail
2-2 November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Modular Messaging versions
is stored on the corporate e-mail system. Subscribers can use the Modular
Messaging telephone user interfaces (TUIs) to access messages stored on
the MSS, and use Unified Communication Center (UCC) Speech Access
for telephone access to voice messages and e-mails stored on Microsoft
Exchange or IBM Lotus Domino. From the desktop, an IMAP4
compatible e-mail client provides access to messages stored on both the
MSS and the corporate e-mail system.
As a standalone messaging solution, Modular Messaging—MSS is an
ideal solution for organizations that have traditional voicemail usage and
that intend to maintain separate e-mail and voicemail systems.
This configuration is likely to be attractive to customers that desire
independent voicemail and corporate e-mail systems for reasons of
overall messaging reliability. Modular Messaging mailboxes on the
Avaya MSS store voice messages, fax messages, text messages, and
binary attachments that subscribers receive. These Modular Messaging
mailboxes are independent of the mailboxes on the corporate e-mail
system that receive and store corporate e-mail messages. Because the
voicemail and e-mail systems are independent of each other in this
configuration, if one of the systems is down, the other is still likely to be
available.
Subscribers can use different devices, such as a touch-tone telephone or a
desktop PC, to access messages stored in their Modular Messaging
mailboxes.
The following access media provide subscribers unified access to
messages:
! A touchtone telephone for access to voice and fax messages.
! Unified Communication Center Speech Access (UCC Speech
Access) for telephonic access to voice and fax messages and to
corporate e-mail messages.
! Avaya Client Add-in for Microsoft Outlook for Outlook access to
all messages. Voice, fax, and text messages in the Modular
Messaging inbox can be accessed with the same client used to
access corporate e-mail messages.
! Modular Messaging Web Client for access to voice, fax, and
corporate e-mail messages from a Web browser.
! A standards-based e-mail client for desktop access to voice, text,
and fax messages. Modular Messaging—MSS supports IMAP4
and POP3 e-mail standards and text messages, allowing
subscribers to access their Modular Messaging mailbox by means
of standards-based e-mail clients. These messages are stored in an
inbox separate from the corporate inbox that receives e-mail
messages from the corporate e-mail system.
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
2-3
Avaya Modular Messaging Concepts and Planning Guide
Note: Access to a subscriber mailbox from standard-based
clients can be restricted by means of administrative
settings. For more information, see The Privacy
Enforcement Level privacy parameter on page 5-45.
A fax-capable solution, Modular Messaging—MSS makes use of native
fax resources to enable subscribers to send fax messages and to enable
callers to leave fax messages. Callers can also leave a message that
contains a voice introduction, followed by a fax, resulting in a single
message with both voice and fax components.
Note: H.323-based IP integration currently does not support fax
messaging.
Modular Messaging—Exchange and Modular Messaging—Domino
A Modular Messaging—Microsoft Exchange or Modular Messaging—
IBM Lotus Domino system is a voice messaging front-end that integrates
with an existing Microsoft Exchange or IBM Lotus Domino e-mail
system, providing a unified message store for all messages.
The existing e-mail system serves as the message store for corporate
e-mail messages, voice messages, and fax messages.
In Modular Messaging with e-mail servers, voicemail is merged into, and
hence relies on, the Microsoft Exchange or IBM Lotus Domino e-mail
infrastructure. Modular Messaging is designed in a ‘store-and-forward’
fashion, so it continues to operate during network or e-mail outages.
During such outages, full functionality is not available, but the system
continues to provide basic Call Answer and limited access to recent Call
Answer messages.
Modular Messaging—Microsoft Exchange and Modular Messaging—
IBM Lotus Domino provides subscribers access to voice, fax, and e-mail
messages from a single graphical user interface (GUI) - their existing
e-mail client.
For unified access to messages, subscribers can use the following access
media:
! A touchtone telephone for access to all messages.
! Unified Communication Center Speech Access (UCC Speech
Access) for telephonic access to all messages.
! Microsoft Outlook e-mail client for desktop access to all
messages, using the Client Add-in for Microsoft Outlook (Not
applicable to Modular Messaging—IBM Lotus Domino).
2-4 November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Loading...