|
In addition to the many features and capabilities provided in previous
releases, Avaya Modular Messaging Release 4.0 offers the following
new or enhanced features and capabilities:
Note: The availability of the features and capabilities
described in this topic depends on your system's configuration.
Some features and capabilities are available only with the Avaya
Message Storage Server (MSS), the Microsoft Exchange server, or
with the IBM Domino server.
User interface improvements
Modular Messaging Release 4.0 provides the following user interface
improvements:
All TUIs (Aria, AUDIX, and Serenade) and all system configurations
(MSS, Exchange, and Domino) support these user interface feature
improvements.
Message ordering urgent FIFO
Previously, Modular Messaging administrators and subscribers could
specify the order in which the telephone user interface (TUI) played
back messages. With this release, message ordering options now include
the capability to play urgent messages first followed by remaining messages with the oldest first.
Administrators can implement this feature for a subscriber or a
group of subscribers. Subscribers also can configure their own message
ordering using Subscriber Options or Web Subscriber
Options.
Extended Absence
Greeting
Previously, the TUI deleted the Extended Absence Greeting when
subscribers switched from the Extended Absence Greeting back to
their regular personal greeting. With Modular Messaging Release 4.0, a recorded Extended
Absence Greeting is preserved unless a subscriber specifically deletes
that greeting.
Additional
optional greetings
Subscribers can now record and use up to nine optional greetings.
Subscribers can also set up greeting rules to determine which optional
greeting a caller hears. For example, subscribers can set up rules that play different greetings for different combinations of internal and external callers, during business hours and outside business hours, busy and no answer calls.
Subscribers can record optional greetings and set up greeting rules
using their TUI, Subscriber Options, or Web Subscriber Options.
Note: The implementation of this feature for internal and external call differentiation depends on the switch integration of your Modular Messaging system. For more information, see the Modular Messaging switch integration notes
on the Avaya Support Site.
Multilingual
greetings
With this new feature, subscribers can record each optional greeting
in up to three languages, if subscribers have enabled the Multilingual
Call Answer feature. The languages in which subscribers can record
their optional greetings coincide with the call answer languages
they have already specified. If a greeting rule causes playback
of an optional greeting to a caller, the system plays the optional
greeting in the caller's preferred language, if that recorded optional
greeting exists.
This feature allows callers to hear greetings in their preferred
language only.
Subscribers can record multilingual greetings using their TUI,
Subscriber Options, or Web Subscriber Options.
Top of page
Native fax server and client support
Modular Messaging Release 4.0 offers improved capabilities for the
fax server. Previously, only the MSS supplied its own fax server,
but this capability is extended to the Exchange and Domino configurations
for Release 4.0. Modular Messaging now supports a native fax server
for all configurations. Modular Messaging continues to support a
third-party fax server for the Exchange and Domino configurations
only.
This release also improves the fax client sending experience when
the native fax server is used. Subscribers can now create a fax
with a fax printer driver and more easily address the fax by using
the fax telephone number only. Subscribers can create a fax using
Web Client, the Outlook Client, the Lotus Notes Client, or any other
Windows application that can print.
Administration features
The following improvements to the administration capabilities of
the Messaging Application Server (MAS) are included in this release:
Role-Based Access Control
Previously, Role-Based Access Control (RBAC) gave customers the
capability to create administration accounts (logins) on the MSS based
on customer-defined roles. Customer-defined roles can be tailored
to give each administrator only the access privileges that were
needed to perform that administrator's job.
For Release 4.0, this capability is extended to the MAS. The
RBAC feature now includes standard administrator roles for all Modular
Messaging Windows-based administration applications, including the
Voice Mail System Configuration (VMSC) tool. Customers can define
the roles, assign members to roles, and assign tasks to roles. The
system then uses assigned roles for all operations that apply to
the voice mail domain.
Improved logging of MAS administration activity
Modular Messaging Release 3.1 improved logging capabilities for
administration on the MSS. Modular Messaging Release 4.0 expands these capabilities
to the MAS. Now the MAS can be configured to send logging of all
RBAC-controlled administration activities to an external, customer-provided
server using the syslog protocol (RFC 3164). Customers can also
store and view the same information directly on the MAS.
Top of page
Currency of adjunct software applications
Modular Messaging Release 4.0 offers improved support for more current
releases of adjunct software. Improved support includes the following:
- MAS support for Microsoft Exchange 2007, with the exception
of Octel Analog Networking. The MAS continues to support Exchange
2003 and Exchange 2000.
- Internet Explorer browser currency. All Web-based applications,
including Web Client, Web Subscriber Options, and MSS Web-based
administration, now support Internet Explorer 7. These applications
continue to support Internet Explorer 6.
- Microsoft Outlook Client support for Outlook 2007 with Windows
XP Professional SP2 or Windows Vista SP1. This support applies
to the Outlook Client and the Restricted Outlook Client. Both
clients continue to support Outlook 2003, Outlook XP (2002), and
Outlook 2000.
- Support of all clients for the Windows Vista SP1 operating system.
This support applies to the Outlook Client, Avaya Voice Player,
Web Client, and Web Subscriber Options, including restricted versions.
This support also applies to the clients used to administer the
Modular Messaging system, including the Voice Mail System Configuration
(VMSC) application and Port Monitor. All clients continue to support
Windows XP Professional SP2 and Windows 2003 Server.
- Support for Lotus Domino Unified Communications (DUC) software,
version 1.2.4.
Top of page
Serviceability
features
The following improvements to serviceability are included in this
release:
DCT and installation enhancements
Modular Messaging Release 4.0 offers enhancements to the Data Collection
Tool (DCT) that simplifies installation. DCT now incorporates
the information that was included in the installation planning
forms for previous releases.
Individual MAS alarming
In previous releases, Modular Messaging assigned one unique ID
to the MSS and one to the MAS, regardless of the number of MASs deployed
for the system. This made it difficult to identify which MAS was
having an issue. For Modular Messaging Release 4.0, each MAS is assigned
a unique ID, so alarms point to the appropriate server.
Software version alarming
This feature ensures that multiple servers in a Modular Messaging
system use consistent software versions. If software versions are
inconsistent across servers, the system generates an alarm.
This feature applies to multiple servers in a single voice mail
domain, not including the Web Client, Web Subscriber Options, or
supplementary servers. For this feature to work, the MAS
service must be running.
SNMP enhancements
Modular Messaging Release 4.0 supports enhancements to SNMP, including dual
alarming and the capability to configure SNMP ports for alarming. With
dual alarming, alarm notifications can be relayed to two different
destinations. Dual alarming is supported for both Avaya Technical
Support gateways and Customer Network Management Stations (NMSs).
This release brings SNMP options into alignment for the MAS, the
MSS, and the Message Networking server.
Connectivity alarming changes
This feature includes the removal of the Avaya Remote Maintenance
Board (RMB) for new installations and support for alarming and connectivity
changes. The RMB is replaced with the Avaya SPIRIT Agent on both
the MAS and MSS. The Avaya SPIRIT Agent relays alarms, SNMP traps,
and software inventory records to Technical Support and customer
NMSs.
Avaya support for connectivity and alarming changes includes the
following:
- Remote access through a Virtual Private Network (VPN) or Secure
Access and Control (SAC)-Light
- Continued support for an external modem
- RMB support for upgrades only
System and software inventory
For Modular Messaging Release 4.0, the software for the MAS, the MSS, and
the Message Networking server includes summary information about
all server versions and the components that are installed on servers.
Technicians and administrators can access this information remotely.
Top of page
Restrictive Features in Client Applications
Modular Messaging Release 4.0 introduces Restricted Web Client and Restricted Web Subscriber Options (WSO) to compliment the Restricted Outlook Client introduced with Modular Messaging 3.1. These clients “restrict” functionality with the goal of maintaining voice and email messages separately. These clients also restrict the functionality to deter users from downloading messages to the system or from sending messages to users outside the Modular Messaging system. This enhances compliance with the policy requirements of the customer.
For the Web Client, administrators can restrict features through
the Web Client Administration user interface. For Web Subscriber
Options, administrators can restrict features through the VMSC application.
Restricted features also apply to Avaya Voice Player (AVP).
The restricted version of the Web Client is available only with
the MSS configuration. The restricted version of Web Subscriber
Options is available for all system configurations.
Top of page
|
