Avaya Modular Messaging
From Partnumber.org Part Numbers, SKUs, Product Information Directory
|
Contents |
[edit] Product Name
Avaya Modular Messaging
[edit] Manufacturer Part Number
Modular Messaging
[edit] Product Date
circa May 2008
[edit] Product Image
[edit] Manufacturer Provided Specifications and Description
- Overview
Modular Messaging is a powerful IP- and standards-based unified messaging platform designed for single- or multi-site global enterprises. Modular Messaging offers exceptional scalability and a superior feature package of call answering and voice messaging capabilities. Messages are accessible any time, anywhere from a wide array of access devices including telephones, fax machines, or PC graphical user interfaces.
With the release of Modular Messaging 4.0, Avaya one-X® Speech will also be included as a standard functionality.
What's New With This Release
Modular Messaging 4.0 focuses on a new wave of customer satisfaction and serviceability enhancements that address demanding enterprise class unified messaging and mobility requirements. This release is highlighted by the inclusion of Avaya one-X Speech software licenses as standard functionality.
- Description
Modular Messaging is all about delivering more flexibility and choice in the best messaging productivity tools to improve customer satisfaction, lower costs and drive revenue for an enterprise or organization. Not all businesses and organizations are alike, so messaging systems should have no limitations for managing messages.
With Modular Messaging, enterprises can add new IP-based messaging capabilities while preserving current messaging infrastructure and capital investments. It combines the power of Avaya messaging systems into a single, highly scalable platform that seamlessly integrates with existing Avaya Octel® 250/350, Octel 200/300 and Intuity® AUDIX® systems without any changes to current voice and data infrastructures.
Modular Messaging 4.0 with Avaya one-X® Speech is a major step forward for many customers and sales teams. This release of Modular Messaging will now include Avaya one-X ™ Speech as standard functionality which allows Avaya to increase the value of the Modular Messaging offer and meet customer needs.
The TUI has been enhanced to include Multiple Greeting Support, Expanded Multi-lingual and Messaging Ordering Capabilities, and Retaining the Extended Absence Greeting (EAG) for re-use. This release also introduces Restricted Web Client and Restricted Web Subscriber Options (WSO) to to address customer’s policy and compliance concerns. Support for Microsoft Exchange 2007 and Microsoft Vista with Modular Messaging 4.0 allows customers to remain current on their infrastructure.
Modular Messaging 4.0 extends the MSS Role Based Access Control (RBAC) and Logging capabilities that were introduced with Modular Messaging 3.1 to the MAS. The improvements in Serviceability include updates to SNMP, Connectivity/Alarming changes, a System Data Collection Tool, and easier installation. It also includes the activation of the maximum 12 Text-To-Speech resources per MAS for all message storage options.
Capacities for use with the Avaya Message Storage Server range from four to 144 ports and up to 20,000 mailboxes and 15,000 hours of storage. Capacities for Microsoft Exchange or IBM Lotus Domino message storage servers range from four to 240 ports.
- Benefits
- Enables quick and effective collaboration across the enterprise, enhancing the productivity of mobile and remote associates through anytime, anywhere access to voice and fax messages.
- Protects investments in current messaging systems by integrating into existing messaging networks.
- Lowers total cost of ownership through server consolidation and IP (H.323 and SIP) integration to the Avaya Communication Manager switch.
- Minimizes training costs and simplifies migration by using popular Telephone User Interfaces, popular desktop clients or standard Internet browsers, and popular administration clients.
- Components
Included Hardware Components
Servers
Modular Messaging - Messaging Application Server, Message Storage Servers, LAN Switch, KVM Switch and Cables
- The Messaging Application Servers and Message Storage Servers are included with the Message Storage Server option. The Message Storage Servers "High Availability" option is required above certain system capacities. Additional Avaya servers with the Microsoft Windows 2003 operating system are optionally available from Avaya to support the Tracing Service (required at certain system capacities). The off-line Access Message Storage and Web Client are optional.
Included Software Components
Modular Messaging Client Access Licenses
- Client Access Licenses (CALs) can be purchased in several ways; variations exist to match any design requirement. Pricing varies according to quantity and other variables. Quantities are based on the Avaya standardized pricing framework. The more seats purchased per order, the less expensive the per-CAL seat price. Other variables include the offer option selected: Unified Mailbox CALs with the Microsoft Exchange, Lotus Domino, or Avaya MSS CALs.
Adjunct Components
Port Cards
- Port cards may be required to support connectivity to the communication system. Several options exist depending on the host system and the protocols it is supporting.
- Functional Attributes
Avaya S3500 Message Server Elements
The Avaya S3500 Message Server family consists of two major elements: the Message Application Server (MAS) and the Message Storage Server (MSS). Sometimes known as the front end and the back end, each Modular Messaging system consists of one or more MAS front ends and a single MSS back end. Multiple MASs are deployed based on the number of messaging sessions/ports required or to enhance system resiliency by providing duplication of services. The Message Application Server is essentially an IP Gateway, providing the Messaging Application software layer (features) and IP Gateway functions (switch integration interface to IP messaging, i.e., transport). All Message Application Server data is transient; both customer data and messages are stored on the Message Store Server. The Message Storage Server stores the customer configuration database and message database.
The Message Application Server and Message Storage Server communicate over an IP link, which is designed to be separate from the customer's LAN/WAN infrastructure. In the event of an IP link failure between the MAS and MSS, the Message Application Server is sustainable and can continue to store up to 5,000 hours of messages per Modular Messaging system. During operation in a sustainable mode, the MAS "pings" the MSS every 30 seconds so that the message store reconciliation begins within 30 seconds of service resumption. With Modular Messaging, during an MSS or link outage, subscribers can access messages on the MAS (recent messages only) while in an off-line mode.
Message Application Server(s)
One or more Message Application Servers are used to provide the following "front-end" IP Gateway functionality, including (but not limited to):
- Telephony ports.
- Switch integration (SWIN).
- Caller and subscriber touchtone user interfaces (TUIs).
- Twelve channels of Multilingual Text-to-Speech (TTS) - Additional TTS channels can be added for email on unified message stores.
- System Automated Attendant.
- Caller applications.
- Voice encoding and decoding.
- Fax receipt and send (not with H.323).
- Notification of new messages, via switch Message Waiting Indicator (MWI) and/or outcalling.
- Tracing Service functionality (diagnostics and reporting). For larger implementations, a separate server (Supplementary Server) may be used for tracing and off-line storage.
- Optional Web Subscriber Options service.
The maximum number of MASs supported by a single Voicemail Domain will depend on message store used (Avaya MSS, Microsoft Exchange, or IBM Lotus Domino). It will also depend on the integration type (analog, QSIG, IP or Digital Set Emulation) and port card circuit density. A total of five MASs can be provisioned for the Avaya Message Storage Server and up to ten MASs can be used with the email message storage servers.
Beyond capacity expansion, additional servers can also be used to enhance the overall availability and therefore provide additional system protection. For example, if a customer configuration consists of 32 Digital Set Emulation (DSE) ports, two Message Application Servers with two 8-port DSE port boards would be required. To increase availability and add further system protection, a third Message Application Server with up to 16 ports might be configured to effectively add 50% greater availability to the system and 100% port redundancy to any of the individual Message Application Servers.
Designated an N+1 configuration, this type of configuration can be used to extend additional protection for hardware without necessarily providing full redundancy for all hardware elements. (Note that the Modular Messaging N+1 configuration is documented and supported for Modular Messaging integrations with Avaya Communication Manager. Other PBXs may be supported, please check your Switch Integration Configuration Notes for details and support availability). Disk storage redundancy is not required because the Message Application Server stores only transient data. A UPS with 30-minute holdover is required to be provided by the customer. Loss of power and power surges are the primary source of disk failures. By including a UPS, it is estimated that disk failures can be reduced by at least 50%.
The Message Application Server is a Microsoft Windows 2003 Server provided by Avaya. Specifications for the Message Application Servers hardware are included in the Hardware Configurations section. For the email message storage servers, either the Avaya S3500 MAS hardware can be used or customers may provide the hardware based on Message Application Server specifications provided by Avaya.
Message Storage Server
The Message Storage Server (MSS) is a RedHat Linux-based system provided by Avaya. The Message Storage Server provides the following functionality:
- Subscriber mailbox storage, including recorded names and greetings.
- Message storage, including multimedia components voice, fax, text and/or binary attachments.
- Message delivery to local mailboxes.
- Message networking for delivery to remote destinations.
- Directory services, including mailbox account information.
Modular Messaging will support one Message Storage Server. System availability is a significant concern for many customers because the Message Storage Server provides data storage for the system. As such, the Message Storage Server is sold with two "availability" options:
"Standard Availability"
- Two 80Gb disks with data (software mirroring).
- For new R4.0 systems, USB modems are the default for remote access to the Avaya S3500 servers. The MSS remote maintenance board (RMB) is discontinued with new system sales, but continues to be used for customers that retain their servers with the upgrade to R4. Avaya Secure Access Control (SAC) is an optional remote access services offer available with new Modular Messaging R4.0 systems or upgrades to Modular Messaging R4.0.
- A read/write DVD (4.5GB) used for system backup and software installation or updates.
- A UPS with 30-minute holdover will be required. (Note: Loss of power and power surges are the primary source of disk failures. Including a UPS is estimated to reduce disk failures by at least 50%.)
"High Availability"
- Four 73GB SCSI disks with hardware RAID Level 5 data redundancy.
- The disk drives are hot swappable.
- For new R4.0 systems, USB modems are the default for remote access to the Avaya S3500 servers. The MSS remote maintenance board (RMB) is discontinued with new system sales, but continues to be used for customers that retain their servers with the upgrade to R4. Avaya Secure Access Control (SAC) is an optional remote access services offer available with new Modular Messaging R4.0 systems or upgrades to Modular Messaging R4.0.
- A read/write DVD (4.5GB) used for system backup and software installation or updates.
- The power supplies and fans are redundant and hot swappable.
- A UPS with 30-minute holdover is required to be provided by the customer.
The Message Storage Server is a Linux-based system provided by Avaya. Port (Line Interface) Boards provide the interface circuitry between the telephone system and the Modular Messaging/Message Application Server. Port boards in a single Modular Messaging system must all be the same type, (e.g., T/R, DSE, T1 or E1). Port boards are not required for the IP integration. The MASs in a single system must support the same type of port board. For Modular Messaging, Dialogic Port Boards will be provisioned. Each has resources for dynamic fax ports; the fax ports can be used on any available Port board port. A single Message Application Server can only support a single board type and cannot simultaneously support multiple types of boards.
Port Boards
Port (Line Interface) Boards provide the interface circuitry between the telephone system and the Modular Messaging/Message Application Server (MAS). Port boards in a single Modular Messaging system must all be the same type, (e.g., T/R, DSE, T1 or E1). Port boards are not required for the IP integration. The MASs in a single system must support the same type of port board. Each has resources for dynamic fax ports; the fax ports can be used on any available Port board port.
Analog Tip/Ring Board
Analog Tip/Ring Boards can be used for Modular Messaging integration to the PBX. Modular Messaging uses Dialogic 4-port and 12-port Tip/Ring (T/R) boards. Each has resources for 4 dynamic fax ports; the fax ports can be used on any available Port board port.
Digital Set Emulation (DSE) Board
When Modular Messaging is used with certain switches (e.g., Avaya DEFINITY® and Nortel) the DSE board provides the switch integration and eight telephony ports. (See the Switch Integrations section below for more information.) Firmware settings on the DSE board indicate the specific switch set to be emulated. The DSE board simultaneously supports fax on two ports.
T1 Board
T1 boards can provide improved operational characteristics over in-band and DSE integrations. For Modular Messaging, the T1 boards will provide common channel signaling (23+1 PRI) for QSIG switch integration. Currently, QSIG is available with Avaya and Siemens switches (controlled introductions available for Nortel). Modular Messaging will not support T1 boards using Channel Associated Signaling (CAS), also known as "robbed-bit signaling." The T1 board simultaneously supports fax on 4 ports.
E1 Board
E1 boards can provide improved operational characteristics over in-band and DSE integrations. For Modular Messaging, the E1 boards will provide common channel signaling (30+2 PRI) for QSIG switch integration. Currently, QSIG is available with Avaya and Siemens switches (controlled introductions available for Nortel and Cisco). Modular Messaging will not support E1 boards using Channel Associated Signaling (CAS), also known as "robbed-bit signaling." The E1 board will support fax on 4 ports simultaneously.
H.323 IP Integration
No boards are required for IP integrations. H.323 uses QSIG over IP for connection to Avaya Communication Manager. Fax support is not currently available. Customers with the S3400 server can support 20 H.323 sessions per server. Customers with the S3500 server can support 30 H.323 sessions per server.
Session Initiation Protocol (SIP) Integration
No boards are required for IP integrations. Standards-based SIP is used for IP connection to Avaya Communication Manager and Avaya SIP Enablement Services. Fax support for SIP is part of Modular Messaging 4.0. Customers with the S3400 server can support 20 SIP sessions per server. Customers with the S3500 server can support 48 SIP sessions per server.
Remote Access
For new R4.0 systems, USB modems are the default for remote access to the Avaya S3500 servers. The MSS remote maintenance board (RMB) is discontinued with new system sales, but continues to be used for customers that retain their servers with the upgrade to R4. Avaya Secure Access Control (SAC) is an optional remote access services offer available with new Modular Messaging R4.0 systems or upgrades to Modular Messaging R4.0.
Local Area Networks (LANs)/Wide Area Networks (WANs)
Two LANs are used for system operation: one for a "private" LAN and the other for organizational LAN/WAN facilities. The "private" LAN is dedicated for traffic between the Message Application Server and the Message Storage Server. This LAN is only used for server-to-server communications in the Modular Messaging environment and does not have to interact with the organizational LAN/WAN facilities in any way. This facility is simply a wire between severs. The "private" LAN insures sufficient bandwidth between the servers in the Modular Messaging message system and addresses security, reliability and availability.
A small, modem-sized Ethernet Layer 2 Switch is included with each system with more than one Message Application Server, which does not require administration and is used as a simple hub to facilitate a plug and play implementation environment for expansion or servicing requirements. The organizational LAN/WAN facilities are used for all other IP-based communications, for networking between messaging systems, client access to message stores, access to other applications, etc. A system with a single Message Application Server will include a LAN cross-over cable instead of the Ethernet switch.
Standards-Based Client Mailbox message access
Standards-Based Client Mailbox message access by POP3 and IMAP4 clients will be supported in the Modular Messaging. Modular Messaging will support basic IMAP4 as well as POP3 access to Modular Messaging message storage servers. This allows message receipt, playback, and deletion through multimedia PCs.
IMAP4 access is recommended; POP3 (because of polling techniques) is not recommended. The capabilities provided with such clients are dependent on the IMAP4 standard and the specific client being utilized. As an example of a standards-based Messaging offering's increased compatibility with other standards-based applications, IMAP4 standards-based clients offer integrated desktop access to Modular Messaging messages that are stored on the Message Storage Server.
Avaya also offers the Modular Messaging Outlook Client to allow Outlook clients to access Modular Messaging voice mail features not covered in the IMAP4 standard, including Greeting Administration and Outcalling Administration. In Modular Messaging, to aid in the response to messages, the Avaya Voice Player will be supported for voice message playback on standards-based clients that do not support IMAP4 message response in a voice mode. For IMAP4 client access, the Modular Messaging sends a copy of the message to the client and the client plays the message using its speaker(s). Customers can reply via the multimedia PC. Coding is dependent on the encoding selected by the system administrator (either GSM at 13Kbps or G.711 at 64Kbps). Use of standards-based clients does not affect the native server for that client and all voice messaging activity takes place at the client, not the native server.
Using Apple Mail as an example of IMAP4 access, Apple Mail clients can be used to access subscriber mailboxes. Within the client, the subscriber creates an IMAP e-mail account for his/her Modular Messaging mailbox. This "account" would be represented on the Apple Mail client as another Inbox folder. Users also include directory access via LDAP in the Apple Address Book application.
Visual Clients supported with Modular Messaging:
- Standards Based Clients are supported for basic IMAP4 Access
- Modular Messaging Outlook Client for MSS Access
- Modular Messaging Outlook client for unified access
- Modular Messaging Lotus Notes Client for MSS Access
- Web Client
For basic IMAP4 access, Microsoft Outlook 2000, 2002, 2003, or 2007, Outlook Express 6.0 and IBM Lotus Notes 5.0, 6.0, and 7.0 have been tested. Other IMAP4 clients can be used and are supported to the IMAP4 level (not the client). Current compatibilities should be validated. Please refer to the Concepts and Planning Guide for verification.
To summarize:
- IMAP4 (versus POP3) is the preferred implementation because of better message synchronization and management.
- Some of the popular clients that Avaya Labs tested for Modular Messaging include: Microsoft Outlook 2000, 2002, 2003, or 2007, Outlook Express 6.0 and IBM Lotus Notes 5.0, 6.0, and 7.0. Please refer to the Concepts and Planning Guide for verification.
- Note: Certain Outlook 2000 implementations with Microsoft Exchange may preclude the use of IMAP4
- Multimedia PC only
- Maximum of 2,500 IMAP4 simultaneous connections with the Avaya S3500 MSS High-Availability option (1000 connections with the Avaya S3500 MSS Standard -availability option or with Avaya S3400 Message Storage Servers)
- Note: Modular Messaging Server based foldering is not supported
- Modular Messaging Add-Ins for Microsoft Outlook and IBM Lotus Notes to improve message create and reply functions; PC/telephony control, voice mail feature administration.
- POP3 (not recommended)
Modular Messaging System Administration
System administration for the Modular Messaging will be required for both the Message Applications and Message Storage Servers as noted below. Both native and standards-based administration facilities are available for the system. The native administrative facilities are primarily used during system set-up and configuration, the standards-based administrative interface is used for migrations, day-to-day moves, adds, and changes (MACs), and enterprise-wide administration for the subscriber mailbox database.
For the Message Application Server, native Microsoft Windows configuration tools are available as the Message Application Server native interface and are used primarily for system set-up and configuration. The system administrative interface for the Message Application Server is provided in English although administrative fields will accept non-English characters. For the Modular Messaging solution, a native web-based LDAP-driven management tool is available. This tool is used primarily for system set-up and configuration, but is capable of most MAC activities as well. The system administrative interface for the MSS is provided in English, although administrative fields will accept non-English characters. For standards-based management, the Avaya Mailbox Manager (provided by Unimax) is an LDAP-driven graphical user interface (GUI) that provides administration for the Modular Messaging subscriber database, technical migrations, and enterprise-wide subscriber administration. This interface is the same administrative interface shipped with all current Avaya messaging platforms.
So, if customers use Mailbox Manager (MBM) today, additional Modular Messaging MBM training would not be required. MBM Administration of subscribers and their associated mailbox attributes includes adds, deletes and changes. MBM provides the ability to manage multiple Avaya messaging systems including:
- Modular Messaging
- Avaya Octel® 250/350
- Avaya Octel® 200/300
- INTUITY® AUDIX® system
For the Modular Messaging, MBM also provides the ability to migrate or move a subscriber from any of these systems to Modular Messaging. MBM provides a single point of management or synchronization for all Avaya messaging platforms and adds a number of benefits over the native administrative interfaces including:
- Mass create/modify/delete (i.e., bulk loads)
- Scheduling
- Reporting: Find, Filter, Sort and Compare
- Synchronization with other databases
- Transaction logging and audits
- Move/Copy/Renumber functions
On an optional basis, customers can work with the Unimax MBM API to create user interfaces for the Web or for help desk users. For technical migrations from Avaya Octel 250/350 to Modular Messaging, MBM allows administrators to select a legacy subscriber, and via menu-driven point and click techniques, simply move them to the target Modular Messaging. Migrations can include: mailbox profiles to Modular Messaging subscriber attributes, Classes of Service (COS) to Modular Messaging Classes of Service, and Individual System Parameters. The technical migration can be conducted as flash-cut, phased-cut, or as day-to-day MAC operations. Migrations are supported from:
- One Avaya Octel messaging system to one Modular Messaging system.
- Many Avaya Octel messaging systems to one Modular Messaging system.
- One Avaya Octel messaging system to many Modular Messaging systems.
With Modular Messaging, MBM does not support migrations for Automated Attendant programming and announcements, personal names and greetings, or stored message migrations. The legacy system could be networked to allow mailbox owners to move any messages to the new Modular Messaging mailbox.
Message Storage Server Administration performed via the Message Storage Server includes: Subscriber administration (see section above) Message Storage Server parameters (e.g., maximum mailbox size, password parameters, etc.) The maximum number of Classes of Service (COS) indicators for the Modular Messaging is 512. The maximum message length for the Modular Messaging is 100 minutes.
Message Application Server Administration done via the Message Application Server includes, but is not limited to:
- Port boards
- Switch integration information
- Maximum concurrent TTS sessions
- Prompt languages
Tracing Service
Tracing Service administration is based on Microsoft Windows software. The Tracing Service captures information related to the operation of Message Application Servers for per-call data collection and reporting purposes. The tracing service maintains connections with all Message Application Servers in the messaging system and receives notification of events from each of them. These events are written to the operation history file. Periodically, these events are consolidated and recorded in the transaction database. A system administrator may use the Reporting Tool to generate reports summarizing voice messaging activity. Tracing Service software comes standard with the system, but may be optionally provisioned. If used, it may run co-resident on one of the Message Application Servers or on the optional Supplementary Server.
Traffic Measurement and Reporting Statistics for resource usage generally fall into two categories: system statistics and subscriber/mailbox statistics. System statistics measure usage of system resources and allow the System Administrator to effectively manage those resources. It also provides information regarding the potential need for additional resources (e.g., more ports). The following statistics are collected, and corresponding reports are available. These reports are available on an hourly and daily basis:
- Incoming Calls
- Outgoing Calls
- Port Usage
- System Usage
- Networking Usage
- Space Usage
- Features
Voice and Fax Messaging
Combined voice and fax messaging capabilities across the enterprise.
Enables enterprise associates to effectively and efficiently communicate through messaging. Allows office, remote and mobile workers to stay connected to important customers, associates and information, enhancing productivity and lowering costs throughout the enterprise.
Avaya one-X Speech®
With Modular Messaging 4.0, one-X Speech® software licenses are included as a standard feature with Modular Messaging, adding value to not only Modular Messaging but to enterprise applications.
Provides key workgroups with seamless access to critical communication tools and business applications throughout the day, no matter where they are – at work, at home, or on the road.
IP Integration with Avaya Communication Manager
Connects Modular Messaging to the Avaya Communication Manager switch using the SIP or H.323 IP-based protocol. (Note - fax is supported with SIP but not H.323).
Provides efficient IP trunking that helps reduce hardware and associated costs when implementing Modular Messaging with Communication Manager.
Unified Messaging with flexible message storage options
Allows voice, email and fax messages to be stored in a single platform of choice - either Microsoft Exchange or IBM Lotus Domino.
- Improves employee productivity by providing a single inbox for accessing all messages
- Helps reduce administration costs through the single message storage and combined administration for both voice mail and email
- Reduces the number of servers to manage
Unified desktop client access to all message types
Provides PC desktop access to messages (voice, fax and email) through the Microsoft Outlook and IBM Lotus Notes client interfaces.
Helps to increases productivity of associates by providing a single interface for accessing all messages. The MS Outlook client is also available in a "restricted" version to address customer’s policy and compliance concerns
Caller Applications
Modular Messaging supports single-digit menus in the form of caller applications. These are separate applications, such as complex auto attendants, listen-only mailboxes, and bulletin boards that can be designed using a Microsoft Windows graphical user interface-based editor tool and deployed across voice mail domains.
Helps improve customer service and eases administrative tasks.
Find Me/Follow Me
The Find Me/Follow Me feature allows users to control where the Modular Messaging directs calls when away from the desk. Modular Messaging supports real-time Find Me capability, instant telephone, pager and other advanced device outcall notification.
Keeps associates in touch can result in improved responsiveness that drives increased customer satisfaction and revenue generation.
Offline Access to Messages
Allows users to gain access to new call answering messages even when Microsoft Exchange, IBM Lotus Domino or the Avaya Message Storage server are unavailable on the network.
Enhances productivity by supporting access.
Choice of Telephone User Interfaces (TUIs)
Modular Messaging includes AUDIX®, Aria® and Serenade® based Telephone User Interfaces (TUIs) for Modular Messaging.
Reduces the amount of training required when rolling out a new messaging system, as well as the frustration that can come from users having to learn a new telephone user interface. This capability is also especially useful for enterprises that have gone through a merger or acquisition and are bringing together users with different TUI experiences. Recent improvements include Multiple Greeting Support, Expanded Multi-lingual capabilities, and Message Ordering support.
E-mail Text-to-Speech from the Telephone User Interface
When used with Microsoft Exchange or IBM Lotus Domino as the message store, users can also access the E-mail Text-to-Speech from the Telephone User Interface.
Provides convenient user access to voice messages when out of the office or away from the PC.
Personal Distribution Lists
Each subscriber has the ability to administer (via subscriber options client, web-based subscriber options, or the TUI) private personal distribution lists. These lists can then be used by that subscriber for sending messages to other subscribers in the enterprise.
Allows each subscriber to create and maintain lists of users who they communicate with most often. Administrators do not have to get involved in any list administration.
TUI selection available as Class of Service (COS) Administration option
TUIs can now be assigned to subscribers on a class of service basis. Intuity® AUDIX® Aria® and Serenade®-based TUIs are currently supported.
Subscribers that are used to a certain TUI can continue to use their TUI of choice, minimizing the need for end user training.
Private Messages
The Avaya Message Storage Server has parameters that an administrator can set for the privacy enforcement level of the server. This will dictate which clients can access mailboxes, which systems can be networked to Modular Messaging, whether subscribers can reply to or forward messages that are marked private.
Provides a greater level of policy control over the security of private messages within the Modular Messaging system.
Local Area Network (LAN) Backup support
System Back-up and restore via the LAN.
Enables network based backup and recovery of System Data, Messages, Greetings and/or Recorded Names.
TTY/TDD support
TTY/TDD support that fully complies with US government Section 508 and Section 255 requirements.
Provides message accessibility for disabled callers and hearing-impaired employees and callers—and one mailbox for voice and TTY.
Web access to messages
Browser based message management and access when using the Avaya Message Store.
Avaya Modular Messaging Web Client enables subscribers to use a Web browser to access their Modular Messaging voice and fax messages. Also available in a "restricted" versions to address customer's policy and compliance concerns.
Web based Subscriber Options
A web-based interface for users to manage their mailbox configuration settings, including greetings, passwords, schedules, mobility options, notification rules, languages, time zone and personal distribution lists.
Provides convenient Web browser access to mailbox settings without requiring deployment of additional software to the desktop. Avaya recently added Restricted Web Subscriber Options (WSO) to help improve compliancy with regulatory requirements.
- Technical Specifications
For comprehensive details on the technical specifications and requirements of Avaya Modular Messaging, please refer to the Avaya Modular Messaging Concepts and Planning Guide available for download at support.avaya.com.
Message Application Server
Message Application Server Hardware Specifications
Detailed specifications can be found in the Modular Messaging Customer Environment document on support.avaya.com.
Message Storage Server
"Standard Availability" vs. "High Availability" Hardware Specifications and Capacity Considerations
The technical specifications and capacities for the Message Storage Server vary depending on the redundancy option implemented. Standard availability configuration has stricter requirements than the High availability option. Details can be found in the Modular Messaging Customer Environment document found at support.avaya.com.
- Requirements
Software Requirements
Modular Messaging Software Requirements
Several documents are available to assist in the planning, design, and implementation of Modular Messaging Release 4, including the Modular Messaging Concepts and Planning Guide and the Modular Messaging Customer Environment document. These can be found on support.avaya.com, along with other supporting documents that provide detailed software requirements.
Regulatory Requirements
Regulatory Requirements
Meets type-approved criteria for every country in which it is sold. This includes, but is not limited to:
- FCC Parts 15 and 68
- UL 60950
- Canadian Standards Association
- European Conformance (CE) mark
- CE Declaration of Conformity
- RoHS
Security Requirements
Customer Responsibilities
Security is an important facet of the customer's responsibilities. The customer has the primary role in keeping the system secure. Administrative procedures on the part of the customer must be planned and enforced to meet the customer's expectations of a secure system. A Modular Messaging system provides logins for the customer's use in completing their ongoing administration. There is a login for on-site installation and maintenance, another one for initialization of features, etc., and one for remote maintenance. These logins must be protected.
Digital networking provides an additional level of security. The digitized voice mail messages that are transmitted between machines make it almost impossible for someone to tap the line and understand the message content. The customer must administer and monitor data ports and the ASG software to meet their needs; not administering data ports, may result in possible delays in Services' ability to respond to an alarm/trouble in a timely manner. The system administration login is active when the product ships from the factory. The customer must take an active role in preventing access to the long distance network and toll fraud. The customer should be provided with information and advice concerning toll fraud prevention.
- CAUTION:Each system ships from the factory with two Services logins active. None of the customer's logins will be active. The on-site installer immediately after the system comes up is expected to change all of the Services logins then notify the SSO of the new passwords. The installer also assigns a password to the customer logins, then notifies the customer of the new passwords, and encourages the customer to change them immediately to passwords of their choosing.
- Interoperability
Interoperability with Non-Avaya Products
PBX Integrations
Modular Messaging integrates with a variety of Avaya and Non-Avaya PBXs. The list of supported PBXs/integration types can be found on support.avaya.com.
Platform Interoperability
Modular Messaging integrates with a list of certain PBXs using several types of integration protocols, e.g. Analog/RS232, Digital Set Emulation (DSE), QSIG. The PBXs need to meet Avaya's specific requirements for MM integration protocol methods. The integration must meet Avaya's integration validation requirements before it is generally available.
Compatibility Issues
Integration Controlled Introduction Process
If an integration type is not found on support.avaya.com, a request may be made by following the Avaya Switch Integration Certification Process located on support.avaya.com.
- Security
Security Issues
For details on security of Avaya Modular Messaging, please refer to the Avaya Modular Messaging Concepts and Planning Guide available for download at support.avaya.com. For more information about system security, see "Modular Messaging and Security" on the Avaya Modular Messaging Documentation media, also available for access and download at support.avaya.com.
[edit] External Links
[edit] Where to Buy
[edit] Discussion Board
| |
