In addition to all of the end-user functionality provided with
its previous releases, Avaya Modular Messaging Release 2 offers
the following new or enhanced capabilities:
Note: Modular Messaging Release 2 supports the
Avaya Message Storage Server (MSS.)
Choice of telephone user interfaces (TUI)
With this release of Modular Messaging, administrators can assign
subscribers either of the following TUIs on a class-of service (COS)
basis:
- Aria TUI for Modular Messaging, an Octel Aria-based TUI, which
was also available in previous releases
- AUDIX TUI for Modular Messaging, an Intuity AUDIX-based TUI
(new to this release)
Both of the above TUIs are similar to, but not exactly the same
as, the Aria and Intuity AUDIX messaging systems. For more information
about the TUIs, see the Modular
Messaging TUI Guide (pdf). You can also search on "aria
tui" and "audix tui."
Common Caller Interface
All Modular Messaging subscribers use the same Avaya Common Caller
Interface (CCI) up to the point of logging in to their mailboxes.
And all callers who want to leave a message hear a common set of
prompts, regardless of the TUI option for the target mailbox.
For more information about the Common Caller Interface, see the
Modular Messaging TUI Guide
(pdf). You can also search on "cci."
Personal distribution lists
Subscribers who frequently send messages to the same group of people
can create a personal distribution list (PDL) for the group. When
the subscriber uses the PDL to address a message, Modular Messaging
sends the message to each member on the list.
Modular Messaging supports 500 lists for each subscriber, so Avaya
has enhanced Subscriber Options to help manage lists. Subscribers
can:
- Create PDLs that contain fax numbers, email addresses, other
PDLs, and Enhanced-List Application (ELA) lists
- Access their PDLs from either Modular Messaging TUI, the graphical
user interface (GUI) of your computer, and Avaya Speech Access
PDLs are available to local and remote subscribers.
Note: A personal distribution list is created
and managed by the subscriber, who is the only person who can use
the list. Enhanced-List Application (ELA) is a system list that
is created and managed by a system administrator, who can make the
list available for other subscribers to use.
For more information about personal distribution lists, see the
Concepts and Planning Guide
(pdf), Chapter 5, or search on "personal distribution list."
For more information about ELA, see Administering
the Enhanced-List Application, or search on "ela."
Broadcast messages
Modular Messaging enables an administrator to designate any Enhanced-List
Application (ELA) to be a local broadcast list. When subscribers
send a message to an appropriately configured enhanced-list mailbox,
the system sends the message to all local subscribers and to all
list members. Administrators can also set up system-wide or enterprise-wide
broadcast lists.
Broadcast messages are:
- Announced by the TUI. After subscribers log into the system,
the TUI presents new broadcast messages before other messages.
It also announces the number of broadcast messages in the subscriber's
mailbox.
- Identified on the GUI. Modular Messaging Web Client and Client
Add-in for Microsoft Outlook mark broadcast messages with an icon.
(Standards-based clients do not. If you use these clients you
can recognize broadcast messages from the address of the broadcast
ELA, unless the broadcast message has been sent via BCC.)
- Managed by the Message Storage Server (MSS). The MSS:
- Does not turn on the message waiting indicator for broadcast
messages, but does activate the Call Me feature.
- Allows up to 16 active broadcast messages at a time.
- Copies your broadcast messages to your inbox after you login.
For more information about broadcast messages, see the Concepts
and Planning Guide (pdf), Chapter 5. You can also search on
"broadcast message."
Message privacy
Modular Messaging supports message privacy by providing system
administrators with the ability to:
- Set a system-wide Privacy Enforcement Level (PEL). Each level
(full, partial, and notification only) determines how the system
manages private messages. See Configuring
the Privacy Enforcement Level for more information about the
PELs.
- Restrict access to mailboxes that use certain clients. When
a system administrator activates the Restrict Client Access COS,
subscribers can only access their mailbox through the TUI or through
the Modular Messaging Web Client. Restrict Client Access prohibits
subscribers from using clients that may not enforce forwarding
restrictions for private messages. At the "full" PEL
setting, this restriction is enforced for all users regardless
of the COS setting.
Modular Messaging also supports message privacy by:
For more information, see the Concepts
and Planning Guide (pdf), Chapter 5, Message
privacy, or search on "message privacy."
Modular Messaging Web Client
Avaya Modular Messaging Web Client enables subscribers to use a
Web browser for visual access to their Modular Messaging messages
and to their corporate e-mail messages.
Similar to UCC Web Messaging Application (WMA) and www.messenger,
the Modular Messaging Web Client enables subscribers to complete
the following tasks on their PCs:
- Create, send, receive, reply to, forward, and organize messages
from their Modular Messaging mailbox.
- Listen to voice messages from a telephone or from their desktop
PC.
- View fax messages from their desktop PC.
- Send messages to any personal distribution lists (PDLs) that
they own.
- Identify broadcast messages, priority messages, private messages,
and delivery failures.
For more information see the Concepts
and Planning Guide (pdf), Chapter 4. You can also search on
"web client."
Data migrations
Avaya Global Services and authorized Business Partners offer the
migration of subscriber data such as mailboxes and COS. For more
information, see your account representative.
Simple Network Management Protocol (SNMP)
Modular Messaging Release 2 supports the following versions of
SNMP:
- For the MSS, SNMP versions 1, 2c, and 3
- For the MAS, SNMP versions 1 and 2c
SNMP, a current working standard of the TCP/IP protocol suite,
is used to transfer network management information among various
elements of a network, regardless of their underlying architecture.
Modular Messaging provides alarm notifications via SNMPv2 trap to
an administered SNMP manager using an administered community string.
SNMP can be used with Modular Messaging to perform the following
tasks:
- A network management station (NMS) can perform queries of system
status information from Modular Messaging. SNMP is read-only in
the Modular Messaging system, meaning that an NMS can query a
Modular Messaging system for information, but cannot change that
information.
- Modular Messaging can send alarm and resolution event notifications
to specified Network Management Stations (NMS).
See Simple Network Management Protocol
overview for more information.
Top of page
|