Avaya 11-300244 사용자 설명서
Avaya Modular Messaging Concepts and Planning Guide
5-2
November 2004
Avaya Modular Messaging Concepts and
Planning Guide
Key features and capabilities
Table 5-1 discusses the key features of Avaya Modular Messaging. These
features are common to all versions of Modular Messaging.
features are common to all versions of Modular Messaging.
Table 5-1. Key features and capabilities
Feature and capability
Description and benefits
Modular Messaging supports many
Octel Aria-type, single-digit menus
in the form of caller applications.
Octel Aria-type, single-digit menus
in the form of caller applications.
These are separate applications, such as complex automated
attendants, listen-only mailboxes, and bulletin boards that
can be designed using a Microsoft Windows
graphical-user-interface (GUI)-based editor tool that is
deployed across voice mail domains.
Caller applications can be used to accomplish most of the
same functions as automated attendants, (including nested
automated attendants) in Intuity AUDIX.
attendants, listen-only mailboxes, and bulletin boards that
can be designed using a Microsoft Windows
graphical-user-interface (GUI)-based editor tool that is
deployed across voice mail domains.
Caller applications can be used to accomplish most of the
same functions as automated attendants, (including nested
automated attendants) in Intuity AUDIX.
Telephone user interface (TUI) for accessing messages
Reply to sender or all recipients
When replying to messages, subscribers can reply only to
the sender or to all recipients that Modular Messaging is
aware of.
When replying to messages that are received through a
Message Networking system, subscribers can reply only to
the sender. Messages coming via a Message Networking
server will not contain a complete list of recipients because,
the Message Networking server cannot be sure that it
received a complete list of recipients from the originating
node. Modular Messaging respects the use of BCC when
used with a GUI client.
the sender or to all recipients that Modular Messaging is
aware of.
When replying to messages that are received through a
Message Networking system, subscribers can reply only to
the sender. Messages coming via a Message Networking
server will not contain a complete list of recipients because,
the Message Networking server cannot be sure that it
received a complete list of recipients from the originating
node. Modular Messaging respects the use of BCC when
used with a GUI client.
Priority of messages
Subscribers can assign a priority to messages.
Print fax messages
Subscribers can print fax messages with TIFF attachments.
Cross-media response
Subscribers can reply to messages in one medium (for
example, fax) with another medium (for example, voice).
example, fax) with another medium (for example, voice).
Graphical user interface clients for accessing messages
Receive, respond to, and send
messages
messages
Subscribers can use a standards-based e-mail client or a
supported GUI client to receive, reply to, forward, and send
messages.
For more information, see
supported GUI client to receive, reply to, forward, and send
messages.
For more information, see
on page
4-14.
Manage and respond to all
messages
messages
Subscribers can store, organize, delete, or respond to all
types of messages.
types of messages.