Filter
Top Products
Avaya Modular Messaging Concepts and Planning Guide
5-42 November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Message Privacy
Modular Messaging uses a two-pronged approach to achieve message
privacy:
! Flexible support for message privacy
This includes the ability to create, send, and access private
messages from the Modular Messaging telephone user interfaces
and from Avaya graphical user interface (GUI) clients. It also
includes the restrictions that these clients and interfaces impose
on the recipients of private messages. The support that Client
Add-in for Microsoft Outlook and standards-based e-mail clients
provide is subject to the enforced privacy parameters.
! Enforcement of message privacy
This includes privacy parameters that administrators can
configure using the Voice Mail System Configuration (VMSC)
tool on a messaging application server (MAS) and on the Avaya
Message Storage Server (MSS).
System administrators can set the levels of privacy support and privacy
enforcement. These administered levels also determine the behavior of
user interfaces and clients, with respect to privacy.
Note: Modular Messaging does not restrict recipients of private
messages from playing the messages on a speakerphone or
recording the message with a tape recorder. Likewise,
Modular Messaging does not restrict recipients of private fax
messages or private messages with attachments from printing
and then circulating the fax or attachments. Modular
Messaging cannot restrict the operation of programs that
subscribers may use to view private message attachments.
Creating private messages
When creating new messages, Modular Messaging subscribers can mark
messages as private, from the following interfaces, clients, or
applications:
! The Modular Messaging telephone user interfaces (TUIs)
— Aria TUI for Modular Messaging
— AUDIX TUI for Modular Messaging
! Modular Messaging Web Client