AvayaAuraMessagingOverviewandPlanning 601

Avaya Aura Messaging Overview and Planning
6.0 CID: 145423 December 2010
2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya generally makes available to users of its products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on its Hardware and Software (Product(s)). Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avayas standard warranty language, as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the Avaya Support Web site: http://support.avaya.com. Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE (AVAYA). Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a
different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Software means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. Hardware means the standard hardware originally sold by Avaya and ultimately utilized by End User. License types Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server. CPU License (CP). End User may install and use each copy of the Software on a number of Servers up to the number indicated by Avaya provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya's prior consent and payment of an upgrade fee. Shrinkwrap License (SR). Customer may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software (Shrinkwrap License). (see Third-party Components for more information). Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or Hardware provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements (Third Party Components), which may contain terms that expand or limit rights to use certain portions of the Product (Third Party Terms). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://support.avaya.com/Copyright. Preventing Toll Fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services.
December 2010
Avaya Toll Fraud Intervention If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: http://support.avaya.com. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Trademarks The trademarks, logos and service marks (Marks) displayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation and Product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya and one-X are registered trademarks and Avaya Aura is a trademark of Avaya, Inc. All non-Avaya trademarks are the property of their respective owners, and Linux is a registered trademark of Linus Torvalds. Downloading Documentation For the most current versions of Documentation, see the Avaya Support Web site: http://support.avaya.com. Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your Product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://support.avaya.com.
December 2010
December 2010
Contents Chapter 1: Introduction.............................................................................................................7

Avaya Aura Messaging overview...................................................................................................................7 Benefits of Messaging.......................................................................................................................................7 Accessibility and mobility..........................................................................................................................8 Flexibility...................................................................................................................................................9 Compatibility.............................................................................................................................................9 Scalability...............................................................................................................................................10 Security...................................................................................................................................................10 Resilience...............................................................................................................................................10 Remote alarming and serviceability........................................................................................................11 Interoperability........................................................................................................................................12 Multilingual support.................................................................................................................................13 Messaging documentation..............................................................................................................................13
Chapter 2: Features.................................................................................................................17
Overview.........................................................................................................................................................17 Tools for getting messages.............................................................................................................................17 Telephone...............................................................................................................................................17 PC...........................................................................................................................................................18 Features for getting message notification.......................................................................................................20 Message Waiting Indicator.....................................................................................................................20 Notify Me................................................................................................................................................20 Features for sending messages......................................................................................................................21 Speech recognition for addressing.........................................................................................................21 Personal Distribution Lists......................................................................................................................21 Enhanced List Application......................................................................................................................22 System broadcast message...................................................................................................................22 Features for the caller.....................................................................................................................................22 Greetings................................................................................................................................................23 Auto Attendant........................................................................................................................................23 Attendant................................................................................................................................................24 Reach Me...............................................................................................................................................24 User Preferences............................................................................................................................................25 Text conversion...............................................................................................................................................25 Text to Speech................................................................................................................................................26 Message Privacy.............................................................................................................................................26 User Management...........................................................................................................................................26 Tools for managing the system.......................................................................................................................27 System Management Interface...............................................................................................................27 Role-Based Access Control....................................................................................................................27 Tools for managing caller applications............................................................................................................28 Caller Applications..................................................................................................................................28 Caller Applications Editor.......................................................................................................................28 Fax support.....................................................................................................................................................28
Chapter 3: Messaging Solution Architecture........................................................................31

About Avaya Aura.........................................................................................................................................31 Avaya Aura components..............................................................................................................................32
December 2010
System Platform.....................................................................................................................................32 System Manager....................................................................................................................................34 Messaging solution overview..........................................................................................................................34 Hardware................................................................................................................................................34 Messaging Software Components..........................................................................................................34 Network topology design.................................................................................................................................37 Decentralized topology...........................................................................................................................38 Centralized topology...............................................................................................................................38
Chapter 4: Planning for Messaging.......................................................................................41

Switch integration............................................................................................................................................41 Traffic flow.......................................................................................................................................................41 Licensing.........................................................................................................................................................43 System design and data collection..................................................................................................................43 Capacity planning............................................................................................................................................44 Preparing for Messaging.................................................................................................................................45 Environmental requirements...................................................................................................................45 Hardware requirements..........................................................................................................................46 Software requirements...........................................................................................................................48 Security requirements.............................................................................................................................49 Preparing your telephony server.....................................................................................................................50 Telephony overview................................................................................................................................50 Resource management..........................................................................................................................51 Systems with multiple sites.....................................................................................................................51
Index.........................................................................................................................................53
December 2010
Chapter 1: Introduction
Avaya Aura Messaging overview

Avaya Aura Messaging, also referred to as Messaging, is Avayas next generation messaging product. Messaging is flexible, scalable, resilient, and easy to deploy on standard Linux-based servers. Messaging is an enterprise-class messaging system targeted for flexible deployment options in single site and multisite environments. Messaging enables quick and effective communication and collaboration across an enterprise, to enhance employee productivity. Using a variety of features and capabilities that the solution offers, employees can receive and respond to calls and contacts from customers, partners, and coworkers faster and more efficiently. Messaging can improve your business by enabling employees to work faster and make better decisions while lowering acquisition and operating costs, with unique and powerful messaging capabilities that deliver tangible benefits: Allowing important calls to get to the right person, at the right time Alerting employees to critical new messages Providing fast and easy access to all messages Lowering the cost of acquisition, implementation, and ownership of the Messaging systems through standards-based interfaces that allow easy integration with the existing networks, administrative systems, and security processes Providing multiple configuration choices for scalability to enable system consolidation significantly lowering total cost of ownership (TCO) while offering new business continuity options
Benefits of Messaging
The core strengths of Messaging are compatibility, interoperability, scalability, and resilience, combined with flexibility, and easy availability. Together, these features improve how your
December 2010
Introduction
organization responds to customers, enhances collaboration, and lowers the cost of ownership. Messaging provides the following benefits to customers: Compatibility: Messaging allows a direct migration from Octel Aria systems, and allows you to preserve important user data from the existing systems, in a familiar menu structure. Interoperability: Messaging interoperates with several Avaya Aura products as well as various third-party products including AudioCodes gateways and third-party fax solutions. Scalability: Messaging provides a scalable solution that ranges from an easy-to-deploy single server to a fully scalable multi-server configuration with dedicated application servers and storage servers. Resilience: Messaging delivers high availability and disaster recovery options ranging from an N+1 configuration for application servers to locally survivable application servers. Flexibility: With organizations migrating from traditional telephony to IP telephony (IPT), business environments are constantly changing. Messaging offers a flexible architecture designed to fit a wide variety of customer environments. It is ideal for enterprises with telephony environments that are in transition. Remote alarming and serviceability: Messaging uses Secure Access Link (SAL 1.5) to provide remote alarming and serviceability. End-user features: Messaging enables users to combine notification features, such as MWI, Reach Me, and Notify Me. It offers voice recognition for addressing messages, Internet Message Access Protocol 4 (IMAP4) access to voice messages, a clientless Outlook toolbar, a browser application for managing user settings, and text conversion of voice messages. Multilingual support: All end-user features are available in multiple languages.
Accessibility and mobility

A key component of business agility is the ability to contact the right person at the right time, and this includes both your employees as well as customers. Increased mobility recognizes that companies invest in different devices and modes of communication. Messaging facilitates a quick and easy way to improve communication within an organization. This includes connecting employees, enabling them to collaborate efficiently, and streamlining business processes. Users can access their messages over a telephone using the TUI or Avaya one-X Speech, or by using an IMAP4 based e-mail client, like Microsoft Outlook.
December 2010
One-number connectivity
Reach Me allows callers to the business line to reach you on your cell phones, remote or virtual office, from that single number. This is especially useful when you are away from the office. One number connectivity preserves your corporate identity irrespective of the access method
Flexibility
Messaging works in a wide variety of topologies in centralized and decentralized environments. The flexible architecture of Messaging is designed to fit a wide variety of customer environments. Messaging is a scalable solution ranging from an easy-to-deploy single server with application and storage roles combined on a single virtual machine to a fully scalable multi-server configuration with dedicated application servers and storage servers.
Compatibility
Messaging is compatible with the existing infrastructure of the customers. Messaging is costeffective as customers are not required to replace everything in the network. Messaging provides compatibility with: Internet Browsers: Microsoft Internet Explorer 7.0 and 8.0, Mozilla Firefox v3.5, or Safari v4. Messaging toolbar support for Microsoft Outlook 2003, 2007, and 2010. IMAP4 based e-mail clients. Messaging maintains the familiar menu structure and the relevant features of the Octel Aria TUI. Messaging allows a direct migration from Octel Aria systems and allows you to preserve important user data from the existing systems. For more information, contact Avaya Partners, ATAC or Sales Engineer representative.
Industry standards
Messaging supports the following industry standards: IMAP4 and POP3 client access to messages SMTP/MIME for sending and receiving messages LDAP Session Initiation Protocol
December 2010
Introduction
Scalability
The Messaging architecture achieves high scalability as it fits and grows with various telephony deployment sizes, ranging from small branch office PBXs to larger campus-wide PBXs. It is designed to work with large scale installations over large, global IP networks with varying levels of network quality. For example, in a scalable deployment of the Messaging system, multiple sites can contain multiple application servers, connected to a dedicated storage server.
Security
Messaging offers the capability to minimize the possibility of telecommunications toll fraud on the Messaging system. It offers safeguards that make it harder for unauthorized users to penetrate the Messaging system. Messaging users have the option of marking their voice messages Private. Voice messages marked as Private can only be accessed from the telephone, and cannot be forwarded. Messaging also provides users with options for a secure implementation through support for various secure protocols. Secure connections through firewalls: Messaging supports connection through a thirdparty, external, VOIP-aware firewall. Secure server connections: Avaya certificates secure the connection between Messaging and other products through the HTTPS protocol.
Resilience
The Messaging solution is very resilient as it can remain functional even with major failures in the environment or its own components.
N+1 Redundancy
The application servers do not maintain data that is unique to a single application server. Messaging provides N+1 redundancy: a single application server can be added to the Messaging application server cluster to provide redundancy for any of the existing application servers in the same cluster.
Offline handling
To deal with outages in the data network the application server can operate in offline mode. In offline mode, the application server continues to provide call answering for existing users, and
10
December 2010
callers cannot tell that there is no connectivity with the storage server. Messaging users can still use the TUI and access messages that were received in the past three days as well as any new call answering messages that were received since the outage. Individual user-touser messages sent while offline can be retrieved as well. Offline handling in the Messaging system is session-based. It only applies to those users who are affected by the outages in the data network. The Messaging system is capable of handling outages because the application server maintain a cache of relevant data, such as: directory information (both user directory and user personal distribution lists) user greetings and recorded names voice messages The cache is a hybrid single or distributed cache. Some data, for example, directory data, is cached on each single application server, while other data, for example, voice messages, is stored in a cache that is distributed among the application servers in a cluster.
Disaster recovery
The application servers can be clustered over a WAN to provide disaster recovery capabilities. This is often done to match a clustered-over-WAN IP-PBX configuration. In a typical deployment, half of the cluster application servers are co-located with the corresponding half of the distributed IP-PBX in one geographical location. The other half of the cluster is colocated with the other half of the IP-PBX in a different location. For more information, see Clustering on page 37.
Remote alarming and serviceability

Messaging uses SAL to provide remote alarming and serviceability.
Secure Access Link

System Platform includes Secure Access Link (SAL) gateway to manage service delivery, including alarming and remote access. SAL gateway is a software application that: Facilitates remote access to support personnel and tools that are needed to access supported devices Collects and sends alarm information to a Secure Access Concentrator Core Server, on behalf of the managed devices Provides a UI to configure its interfaces to managed devices, Concentrator Remote and Core Servers, and other settings SAL requires a customer-to-Avaya upload bandwidth of at least 90 KBps (720 Kbps) with a round-trip latency no greater than 150 ms.
December 2010
11
Introduction
During the installation of System Platform, you must register the system, which consists of System Platform, the solution templates, and SAL gateway, and configure SAL for the customer network. Important: For Avaya to provide support, Avaya Partners or their customers must ensure that SAL is registered and configured properly. Avaya support will be delayed or not possible if SAL is not properly implemented. To deliver remote services, Avaya Partners must provide their own business-to-business connection, which may be a virtual private network or other IP-based connectivity. Administrators can launch the SAL gateway management portal from within System Platform.
Interoperability
The key benefits of Messaging includes interoperability with several Avaya Aura products. Messaging also provides interoperability with various third-party products including AudioCodes gateways and third-party fax servers.
Interoperability with Avaya products

Messaging interoperates with the Avaya Aura solution, which is a rich, highly interoperable set of SIP components. The Messaging solution interoperates with: SIP Enablement Services proxy: to provide SIP connectivity. Session Manager: to provide SIP connectivity. Communication Manager: to provide SIP connectivity. Message Networking Release 5.2: for simplified administration, directory management, and performance. ProVision: a provisioning tool used to collect user information for the Messaging system. It sends the collected data to the storage server through an LDAP connection.
Interoperability with third-party products

Messaging interoperates with the following third-party products: AudioCodes gateways Fax servers
12
December 2010
Messaging documentation
AudioCodes gateways
Messaging uses SIP for switch integration with mixed PBX environments. AudioCodes Mediant 1000 gateway allows the Messaging system to work with switches that are not supported by the SIP Enablement Services and Session Manager, mainly those from third-party vendors. Additional documentation for AudioCodes gateways is available at http:// www.audiocodes.com/support.
Third-party fax servers

Messaging interoperates with a customer-provided, third-party fax server to provide fax capabilities. The customer provides the hardware and software required for the third-party fax server. For fax support, Messaging requires that a third-party fax server be installed and configured. Often an organization already has a fax server installed with which the Messaging system can integrate. Instructions to install and configure the fax server are specific to the particular brand of fax server that belongs to the user.
Multilingual support
Messaging supports the following languages for this release. Languages, other than English (US), are available once the language pack is installed. Brazilian Portuguese Canadian French with French GUI English (UK) with English (US) GUI English (US) German Latin American Spanish
The following table describes the documentation provided with Messaging: All documentation is available from the Avaya Support Web site:http://www.avaya.com/ support.
Title Planning Description Audience
December 2010
13
Introduction
Title Avaya Aura Messaging Overview and Planning
Description
Audience
This guide provides information about the Planner, concepts underlying Messaging. Topics Administrator, include Messaging features, Technician components, addressing, telephony, deployment options, and planning data. This document discusses the multilayer Planner, security philosophy of Avaya, network Administrator, security integration, and toll fraud Technician security resources. This document also discusses security issues that customers must consider before designing and implementing a corporate security strategy into their Avaya enterprise. It also provides information on recommendations for maintaining and monitoring security in an Avaya enterprise.
Avaya Aura Messaging Security Design
System installation Implementing Avaya Aura Messaging This document describes how to install Technician the S8800 hardware and Messaging software components. Topics include installation prerequisites, site planning and preparation, and installing the S8800 hardware, Avaya Aura System Platform, Secure Access Link (SAL), and Messaging.
Maintenance Maintaining the Avaya Aura S8800 1U Server This guide illustrates S8800 support for Avaya Aura Messaging. The server is available in a 1U model with various hardware components. The guide describes the procedure required for multiple maintenance tasks. Technician
Administration Administering Avaya Aura Messaging This document provides information on Administrator how to administer the Messaging system. The topics include Messaging administration, server administration, managing software, and using diagnostic tools. These online help topics provide Administrator information on administering the application server and the storage server.
Help for Administrators
End user
14
December 2010
Title Using Avaya Aura Messaging
Description This document describes common end- User user tasks, such as initial setup and using the User Preferences and Messaging toolbar. This document describes how to perform User common tasks and use Messaging features through the telephone. These topics provide information on using the Outlook toolbar. These topics provide information on administering Messaging from the User Preferences. User User
Audience
Avaya Aura Messaging Quick Reference Outlook toolbar Online Help User Preferences Online Help Additional resources Documentation library
This documentation set for Messaging All includes administration, implementation, general reference, and user information.
December 2010
15
Introduction
16
December 2010
Chapter 2: Features
Overview
Messaging provides a set of features, such as one-number connectivity, speech recognition for addressing, PDL, ELA, and system broadcast messages, that helps users and callers while sending and receiving messages. Messaging also provides several message notification features that helps users to be reached at any time and location.
Tools for getting messages

You can access Messaging voice messages through your desk phone, mobile phone and computer. Messaging is compatible with several products like: Avaya one-X Speech Avaya one-X Mobile Avaya one-X Communicator Microsoft Outlook Any IMAP4 or POP3 based e-mail client
Telephone
The Messaging system can be integrated in to the existing PBX environment so that users can use their desk phone, mobile, or any telephone to access the system in the following manners: Using the Voicemail or Messages button Dialing the Messaging System Pilot Number Dialing the office main number For more information, see Using Avaya Aura Messaging. You can also get access to the Messaging voice messages using Avaya one- X Speech or Avaya one-X Mobile.
December 2010
17
Features
Avaya one-X Speech

Avaya one-X Speech is a complementary Avaya product providing an US English speech user interface. Speech recognition and Text to Speech (TTS) technology allows mobile professionals to gain access to their business computer resources from any telephone. Avaya one-X Speech: Provides access to voice mail messages, call answering, and follow-me or hold-mycalls filtering Provides e-mail reading capabilities Provides speech access and voice control of voice and corporate e-mail messages Enables users to create and access private messages Enables users to launch telephone calls, either single-party or multi-party conference calls, all from a single session For more information, see the Avaya one-X Speech client product documentation (Site Preparation Guide, Installation Guide, and Wallet Card) available at http://www.avaya.com/ support.
Avaya one-X Mobile

Avaya one-X Mobile provides a graphical interface for accessing the Messaging voice messages. You can use Avaya one-X Mobile to both see and hear voice messages on your mobile phone. You do not need to dial into the system because messages are automatically downloaded to the handset in the form of sound files. As all messages are visible in a list with sender name and duration, you do not have to sort through for the important messages. For more information, see the Avaya one-X Mobile product documentation available at http:// www.avaya.com/support.
PC
You can get access to the Messaging voice messages on a PC using Avaya one-X Communicator or Microsoft Outlook , or from any IMAP4 or POP3 based e-mail client.
Avaya one-X Communicator

Avaya one-X Communicator provides desktop access to your voice messages from a single, intuitive user interface.
18
December 2010
Tools for getting messages
You can use Avaya one-X Communicator to perform the following actions: Listen to voice mail Delete voice mail Call a voice mail Add a number from voice mail to personal contact Add a number from voice mail to Favorites Mark a voice mail as read or unread
IMAP4 or POP3 based e-mail client

Users can set up an IMAP/SMTP e-mail account in an IMAP4 or POP3 based e-mail client to access voice messages.
Microsoft Outlook
The Avaya Voice Message form adds a dedicated toolbar to Microsoft Outlook. This toolbar allows you to play voice messages and call the sender from within Outlook. You can use Microsoft Outlook to add the Avaya Voice Message forms to the forms folders on your Exchange server. When you open a voice message from Outlook, the body of the message contains the Messaging toolbar for voice messages. The Messaging toolbar has the following features: Play on PC Play on Phone Voice Reply - to reply to the message with another voice message Voice Forward - to forward the message as a voice message with an introduction Call Sender User Preferences Help - to access online help Because the form is associated with the message class, any Outlook client connected to Exchange automatically uses this form when displaying a Messaging voice message. The Messaging toolbar is only available for voice messages shown in your Avaya Aura Messaging IMAP4 Inbox in Outlook. If you set up your User Preferences to receive a Notify Me e-mail copy of each voice message, the copies will appear in your main Outlook Inbox. These copies will not show the Messaging toolbar.
December 2010
19
Features
The Messaging toolbar is not available in Outlook Web Access. For more information, see Outlook toolbar GUI Online Help and Using Avaya Aura Messaging, available on the Avaya Aura Messaging Documentation Library.
Features for getting message notification

Messaging provides message notifications in the form of lighting the Message Waiting Indicator (MWI) on the desk phone, sending a text message to a mobile phone, or placing a call to a telephone.
Message Waiting Indicator

You can use the MWI feature for alerts when you receive messages that meet your specified criteria. You can configure MWI to get alerts by a lamp indicator on the telephone. When you receive a voice message, the MWI light turns on. The MWI lamp on your desk phone is lit as long as one or more voice messages in your Messaging Inbox are marked as Unread. It is turned off when all voice messages in your Inbox are marked as Read.
Notify Me
Notify Me is a feature that sends you a notification when you receive a new voice message. You can be notified by: Text message to your mobile phone or page notification to your pager Phone call to a telephone or mobile phone E-mail copy
Text message or page notification

When your mailbox receives a new message, Messaging sends a text message to the email address or sends a page to the numeric pager specified by you for notification. You can configure Notify Me to send notifications only when a caller marks a voice message as High Importance.
Phone call to a telephone or mobile phone

Administrators can configure Notify Me to send a notification through a phone call to a telephone or mobile phone on a Class of Service (CoS) basis. You can configure the phone call notification settings in User Preferences with an option to turn on or off the notification through the TUI. When you enable notification to send a phone call, a call is made to the designated phone to alert you that you have received a new voice message.
20
December 2010
Features for sending messages
You can determine whether you want to be notified of all new messages or only important messages.
E-mail copy
You can configure the Email Copies feature on the Notify Me Web page of your User Preferences. You can configure Notify Me to receive an e-mail message with a copy of each voice message. You can also decide to include the recording of the voice message in the email messages.
Features for sending messages

Messaging provides various features that simplify sending a message. These features includes speech recognition for addressing, Personal Distribution Lists and Enhanced List Applications, and system broadcast messages.
Speech recognition for addressing

Messaging provides speech recognition for addressing. Users can say a name of a recipient or distribution list to address a message, instead of having to memorize a mailbox number or having to spell a name on the keyboard.
Personal Distribution Lists

A Personal Distribution List (PDL) is a labeled collection of users (recipients) that a user may create and save for later use. Messages that are addressed to the list are sent to all the recipients (list members) within the list. Users who frequently send messages to the same group of people can create PDLs for the groups. For example, if a user frequently sends messages to 10 members of the Sales team, the user can create a PDL labeled Sales that has the addresses of those 10 Sales team members. When the user sends a message to the PDL Sales, the message is sent to all 10 members of the Sales team. Unlike an ELA, a PDL is created and managed by a user rather than a system administrator. A PDL is personal; only the owner of the list can view and use the list. A PDL is not available to other users. Mailbox number or network address can be used for adding members to the PDLs. Mailbox number is used for a local user, while Network address is the mailbox number for a remote user. You can have both local and remote users in PDLs.
December 2010
21
Features
Enhanced List Application

Enhanced List Application (ELA) is a messaging tool that greatly expands the capability of the Messaging system to deliver messages to a large number of recipients. ELA associates one mailbox to a list of members, so that when users want to send a message to the whole list, they can send a message to the list mailbox instead. When a new message is delivered into the list mailbox, known as the shadow mailbox, the ELA software distributes the message to the members of the list. ELA members can be local or remote users, thus providing extreme flexibility. For example, administrators can set up an ELA list for a suggestion box that messages addressed to this list are distributed to the Messaging mailboxes of a set of users. An ELA mailbox is like any other mailbox, allowing such operations as recording a name and a greeting for the list and allowing call answer messages to be distributed through ELA. Like any other mailbox, an ELA mailbox has a mailbox number, a numeric address, and a Messaging e-mail address. A numeric address enables subscribers to address messages to any local or remote recipient in an organization. The numeric address allows a subscriber to send a message to any recipient from the TUI without having to know the geographic location of the recipient. The directory makes all numeric addresses available to all locations within the organization. A numeric address is same as the Mailbox Number.
System broadcast message

The system broadcast message allows a group of users, based on CoS, to send a message or an announcement to all users of a given cluster of application servers. The system broadcast message is presented only when users use the TUI on one of the application servers. The system broadcast message is not available in the IMAP4 mailbox of a user and no notifications are sent. Only one system broadcast message can be active at a time. Since the system broadcast message typically presents information that relates to system administration for a cluster, the system broadcast message is presented even when the application server is offline.
Features for the caller

Messaging provides various features that ease message receiving and helps the users and callers to remain in contact efficiently. These features includes the personal attendant, auto attendant and basic speech based auto attendant, and Reach Me.
22
December 2010
Features for the caller
Greetings
Messaging supports the following types of greetings: Personal greeting Extended Absence Greeting
Personal greeting
You can use the personal greeting to greet all callers that reach your mailboxes. Your personal greeting is played to callers when your phone is busy or you do not answer a call. You can have just one personal greeting used for both busy and no answer or you can also have a separate greeting for busy and for no answer. The number of greetings may be restricted by CoS. If you do not record a personal greeting, then a system greeting will be used. This system greeting will include the name you have recorded. If you have not recorded a name, then the system will use TTS to speak the directory name for you.
Extended Absence Greeting

You can use the Extended Absence Greeting (EAG) to inform a caller that you are away from the office and have infrequent or no access to your messages. Callers cannot dial-through an EAG. Administrators can choose through CoS whether to allow callers to leave messages after an EAG or not.
Auto Attendant
Each user in a Messaging system is associated with a single site. For each site, an Auto Attendant pilot number can be defined to access the Auto Attendant. By default, Auto Attendant of a site contains all the users associated with the site. Administrators can add other sites to a given Auto Attendant of a site. In this case, all users associated with the other sites are reachable through the Auto Attendant of the site. This requires a uniform dialing plan and implies voice traffic between those two sites. Mailbox users and Caller Applications can be included in the Auto Attendant. The Auto Attendant includes shortlist handling for spell mode. If an entered name matches multiple names in the directory, then a shortlist is presented to the caller to choose from.
Basic Speech Auto Attendant

Messaging includes Basic Speech Auto Attendant, allowing callers to reach users listed in the Auto Attendant directory by saying their names instead of entering an extension.
December 2010
23
Features
The Basic Speech Auto Attendant recognizes: Combination of First Name and Last Name Common Name Pronounceable Name If the confidence level of the speech recognition result is below a certain threshold, the Basic Speech Auto Attendant asks the caller to confirm the recognized name. The confirmation dialog will speak a TTS version of the name and ask the caller if this was the intended name. If the recognized name in the Basic Speech Auto Attendant matches multiple names in the directory, then a shortlist is presented to the caller to choose from. The Basic Speech Auto Attendant requires an additional seat license for each user or caller application that is included in that Auto Attendant. This seat license is required only once for an entry, even if that entry appears in multiple sites' Auto Attendants.
Attendant
The Messaging system often directs incoming calls to an attendant. Attendant forwarding settings define where calls are forwarded when a caller presses zero while listening to your voice messaging greeting. You can configure the attendant schedule, main extension, and general delivery voice mailbox. Messaging supports following types of attendants: System attendant: Callers are routed to the system attendant (operator). Personal attendant: Callers are routed to a phone number, defined for the personal attendant. This phone number can be internal (typically a phone extension) or external (any phone number formatting is acceptable). If a caller presses 0 to reach the operator, the caller is transferred to this extension. For example, extension 4200. When the system attendant or personal attendant does not answer incoming calls, callers reach the general delivery mailbox number. Typically, this is a shared mailbox accessible by all attendants. A typical greeting for this mailbox is: There is no one available at this time.
Reach Me
Reach Me is a feature that redirects unanswered calls to a list of telephone numbers specified by the user. With Reach Me, you can set up schedules with an associated list of telephone numbers for forwarding unanswered calls. Reach Me is implemented only for calls that are not answered even after the extension rings. Reach Me is not implemented for calls that are not answered because the extension is busy. When unanswered calls are directed to Messaging, the system checks to see if Reach Me is enabled, and, if so, whether the call has arrived within the active schedule. If the call has arrived
24
December 2010
User Preferences
within the active schedule, Messaging asks callers if they want to leave a message or have the system try to locate the user. Reach Me manages how your incoming calls are forwarded based on the following: Caller priority: You can define different call handling for priority callers and other callers. Priority callers are all the voice messaging users in the internal directory of the Messaging system. Call screening: Callers are prompted to record their name before a call is forwarded. When the user receives the forwarded call, the recorded name is played and the user can accept or reject the call. If rejected, the caller is told that the user is unavailable and is routed to the Messaging mailbox of the user. Forwarding numbers: Calls can be forwarded to up to three Reach Me numbers in an attempt to reach the user. These numbers are called sequentially. The Messaging system will try to reach you using all your Reach Me numbers before forwarding a call to your Messaging mailbox. Schedule: Calls can be forwarded during certain hours and on certain days defined by the user.
User Preferences
You can use User Preferences to modify your mailbox settings from a Web browser. You can modify all or some of your mailbox settings, depending on how the mailbox is configured by the administrator. The system administrator can apply restrictions to User Preferences to customize or restrict the user interface, allowing user access to some or all of the tasks available from User Preferences. Administrators can restrict features through CoS.
Text conversion
Speech to Text converts Messaging voicemail messages to text and delivers them through email or text message. This increases personal productivity by converting downtime associated with voicemail retrieval, playback and taking notes into productive time. Simply read voice mails as e-mails, wherever you are, and at a glance see who called, when they called, and what they said. Note: Speech to Text will be delivered as a post GA feature. For more information on the availability of the Speech to Text feature, contact your ATAC or Sales Engineer representative.
December 2010
25
Features
Text to Speech
Messaging provides licensed speech synthesis software so that users can hear the envelope and subject information of messages and text names over the telephone through a computergenerated voice. TTS is also used for name confirmation when a recorded name is unavailable. TTS does not read out contents of a text message that might have been sent.
Message Privacy
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 TUI and from GUI clients. It also includes the restrictions that these clients and interfaces impose on the recipients of private messages. The support that GUI clients provide is subject to the enforced privacy parameters. Enforcement of message privacy This includes privacy parameters that administrators can configure using the System Management Interface on application server and storage server. System administrators can set the levels of privacy support and privacy enforcement. These administered levels also determine the behavior of UI and clients, with respect to privacy.
User Management
Following is the list of important operations that you can perform using the User Management: Add an user View, modify and delete an existing user Assign and remove permission, roles, groups, address, contacts for users Search for a user A system administrator can only add, modify, and delete the user profiles. A system administrator can also modify User Preferences properties.
26
December 2010
Tools for managing the system
Tools for managing the system

Messaging provides System Management Interface for administration of storage server, application server, and Messaging features.
System Management Interface

The System Management Interface (SMI) is the single point of access into your Messaging system and the license server. You can open SMI from any standard Web browser from anywhere within the firewall of your organization. SMI has three interfaces: The licensing administration interface to view the status of the server license. The messaging administration interface to gain access to administration, diagnostic, and reporting tools to set up, manage, and maintain your Messaging system. In addition to monitoring system status, you can also use the messaging administration interface to administer: - Server roles, trusted and hosted servers, sites, and topology - Features like Auto Attendant and call transfer - IMAP and SMTP - Users and class of service The server administration interface to configure, maintain, and troubleshoot Messaging servers.
Role-Based Access Control

Role-Based Access Control (RBAC) gives customers the ability to control privileges on the application server based on the customer-defined roles. RBAC is used to create roles to allow or restrict access to the System Management Interface Web pages as desired. The Web Access Mask Web page allows you to restrict individual logins. Messaging provides some default access masks and names, such as System Profile, Customer Super User Profile, and Customer Non-Super User Profile. Using SMI, you can also create a new web access mask profile and enable access as desired. For more information, see Avaya Aura Messaging Administration Guide.
December 2010
27
Features
Tools for managing caller applications

Caller Applications
Caller Applications are a collection of menus and prompts that allow administrators to extend the Messaging caller interface. Using Caller Applications, administrators can extend the Automated Attendant depending on the requirements of the organization. The basic functions that a Caller Application provides include: Transferring callers to a specified mailbox Defining business hour and off-hour schedules for the organization, as applicable Defining Holiday schedules for the organization, as applicable Configuring prompts by uploading voice-based prompts if required by the caller menus, or entering Text-to-Speech prompts Defining call menus in support of business hours, off-hours, and holiday schedules The Caller Applications Editor creates Caller Applications.
Caller Applications Editor

Caller Applications Editor is a software application that consists of Microsoft Management Console (MMC) snap-ins and extensions. The Caller Applications Editor creates Caller Applications. Caller Applications are, upon creation, automatically deployed to the storage server and to the relevant application servers. Caller Applications Editor can only run on a Microsoft Windows platform that can communicate with the AxC to deploy the created Caller Applications.
Fax support
If your company has integrated a fax server with Messaging, faxes can be redirected to the fax server, which then typically delivers the fax to your e-mail inbox. The actual fax handling options within your e-mail depend on your companys fax server features.
28
December 2010
Fax support
Note: When calling the Messaging system, fax messages are not available through the telephone user interface. The following are the requirements for third-party fax server interoperability with Messaging: The fax server must be integrated with the mail system as an e-mail connector or an email gateway for fax. The fax server must support DTMF detection and collection.
December 2010
29
Features
30
December 2010
Chapter 3: Messaging Solution Architecture
About Avaya Aura

Avaya Aura, Avaya's next generation core communications architecture, represents a new approach to business communications that radically simplifies complex multi-vendor, multimodal, multi-location networks and creates a truly unified architecture. Avaya Aura simplifies complex communications networks, reduces infrastructure costs and quickly delivers voice, video, messaging, presence, Web applications and more to employees anywhere. It adds powerful new capabilities to Communication Manager, including session management that enables multi-vendor hardware and software to communicate across the enterprise network. Avaya Aura orchestrates a wide array of communications applications and systems by decoupling applications from the network. As a result, services can be deployed to users depending on what they need rather than by where they work or the capabilities of the system to which they are connected. Avaya Aura supports single cross-enterprise dial plans and centralized administration, reducing operating costs and speeding up rollouts of new applications. New aggregated presence features and the inclusion of Avaya one-X Unified Communications interfaces allow businesses to take full advantage of unified communications application and solutions.
Additional documentation is available at http://support.avaya.com.
December 2010
31
Messaging Solution Architecture
Avaya Aura components

Avaya Aura core communications services are provided by the following components: Avaya Aura Communication Manager, is the open, highly-reliable and extensible IP Telephony foundation on which Avaya delivers Intelligent Communications to enterprises large and small. Avaya Aura SIP Enablement Services, delivers rich communications, collaboration, mobility, and application integration capabilities to the enterprise. This centrally managed application provides customers with a smooth migration path into SIP-based communications with support for SIP trunking, SIP stations, Presence and Instant Messaging, and SIP-based applications. Avaya Aura Messaging, provides a solid messaging platform. Messaging is a part of the Avaya Aura architecture, but it can also be used in other environments. For more information, see Avaya Aura Messaging overview on page 7. Avaya Aura Session Manager, is a SIP routing and integration tool and the core component of the Avaya Aura solution. Session Manager integrates all of the SIP entities across the entire enterprise network within a company. It offers a new perspective on enterprise communication where individual locations are no longer managed as separate units within the enterprise. Each location, branch, and application is viewed and managed as part of the overall enterprise. Avaya Aura System Manager, a common management framework that optimizes centralized management functions for provisioning, operations and fault/performance monitoring. For more information, see System Manager on page 34. Avaya Aura System Platform, a technology that allows you to consolidate applications in a single server, decreasing your hardware footprint, cooling and energy costs. Because of this consolidation, you may need fewer servers for the same configuration than with other competitors. All messaging systems are installed on System Platform. For more information, see System Platform on page 32. Additional documentation is available at http://support.avaya.com.
System Platform
System Platform is a generic virtual server software platform that provides a common set of features and services. This set of features and services allows preinstalled and configured virtual applications, called solution templates, to reside on a single physical server. System Platform is Xen-based and includes the following:
32
December 2010
Avaya Aura components
Base CentOS Linux system running the Xen Hypervisor (Dom0) Web-based management console for installing and managing templates Virtual machine for System Platform system utilities System Platform features include: SAL to handle alarming and remote access A consistent upgrade method for all patches and products in the solution template Security that conforms to Avaya product security standards A Web License Manager (WebLM) server to manage product licenses A Network Time Protocol (NTP) clock synchronized to a customer-provided NTP server
Virtual Machines
System Platform includes CentOS as the base operating system, the Xen Hypervisor, and a virtual machine (CDOM) that is used to manage the platform. System Platform includes the following: System Domain (Dom0): In addition to exporting virtualized instances of CPU, memory, network, and block devices, Xen displays a control interface to manage how these resources are shared between the running domains. Access to the control interface is restricted to a specially privileged virtual machine, known as domain 0 or System Domain. Console Domain: Console domain is a virtual machine, which is a part of System Platform and has many platform elements, such as: - Common logging and alarming - Remote access - System Platform Web Console - Upgrades and patches - WatchDog - Licensing
Template
All messaging systems are installed on System Platform using a template. Avaya offers product-specific templates to install different products on System Platform. A template is a definition of a set of one or more applications to be installed on System Platform. Messaging offers the following templates: Msg_Standard.ovf. The Messaging template for the standard server (3 x 146GB 10K RPM disks with RAID5). Msg_4x146GB_HDD.ovf. The Messaging template for the high capacity storage server (4 x 146GB 15K RPM disks with RAID5). For more information on templates, see Implementing Avaya Aura Messaging.
December 2010
33
System Manager
Avaya Aura System Manager takes a solution-level approach to network administration. IT departments can use System Manager to incorporate new components and applications under a common management umbrella over time, managing all the elements of Avaya Aura together as a system. System Manager centralizes provisioning, maintenance, and troubleshooting to simplify and reduce management complexity and solution servicing. System Manager provides a common management framework that: Reduces the complexity of operations for distributed multisite networks with multiple control points inherent in SIP Increases the value of convergence through tight integration with the enterprise IT infrastructure
Messaging solution overview

Messaging is a voice messaging system that consist of hardware and software components. The following topics provide more information on the hardware used and the software components used in Messaging.
Hardware
Messaging is installed on System Platform running on an Avaya S8800 server. Messaging offers two types of servers, depending on the mailbox capacity, as listed below: Standard Server High Storage Capacity Server For more information, see Implementing Avaya Aura Messaging.
Messaging Software Components

Servers
Server overview The flexible architecture of Avaya Aura Messaging allows you to customize your messaging system to fit your business needs. When you first set up your Messaging system, you assign
34
December 2010
Messaging solution overview
your servers a role. As your business changes and grows, you can add new servers and reassign the roles of existing servers. Server roles The Messaging system is designed to play two distinct functions, or roles. These roles are: Storage role Application role These roles are independent of the server on which they reside. The Messaging architecture allows you to change the role of the server. For example, you can change a single-server system into a two-server system in which: The original server continues to play both roles and the second server plays the application role, or The original server plays the storage role and the second server plays the application role Storage role: The storage role persistently stores: Voice messages Directory data in an LDAP directory (users contacts, distribution lists, caller applications) The storage role also supports non-voice interaction with users, including: IMAP4 and POP3 access to voice messages SMTP routing of voice messages, text-message notifications, and e-mail copies AxC connectivity to: - The LDAP directory - The message store for monitoring Message Waiting Indicator (MWI) and Notify Me (text message notifications, telephone call notification, and e-mail copies) - User Preferences Application role: The application role supports real-time telephony interaction with users and callers, including: Integration with your telephony system, for voice and MWI A telephone user interface (TUI) for users and callers, including Auto Attendant and Caller Applications Local caching for the offline handling of user directory data, greetings, recorded names, and voice messages Connection to the AxC connector for access to the storage role
December 2010
35
Server types Server types refer to the functionality of the server. All servers share the same software and the same System Management Interface (SMI). The type of an Avaya Aura Messaging server depends on the role it assumes. Server types are: Single server. A server that combines the application and storage roles. Dedicated storage server (also called a storage server). A server that is identical to a single server except that only the storage role has been enabled. Dedicated application server (also called an application server). A server that is identical to a single server except that only the application role has been enabled. You can change the server type as your messaging needs change. For example, if your company needs to expand its messaging system to accommodate new users, you can add a second server to your single-server configuration. You can then assign the storage role to one server and the application role to the other server. You can continue to add more servers as your business grows. Network topology Your Avaya Aura Messaging system can consist of the following topologies: A single-server topology in which one server plays both the application and storage roles. A front-end/back-end topology in which roles are split between servers. The application role is the front end; the storage role is the back end. You can design your system so that it contains a mix of the above topologies. For example, one single server might play both storage and application roles for the site in which it is located. It might also play the storage role for a remote dedicated application server. Single server In the single-server topology, the application and storage roles are active on the same server. The application role integrates with the telephony server.
36
December 2010
Network topology design
Front-end/Back-end In front-end/back-end topologies, the front end plays the application role and the back end plays the storage role. Dedicated application servers communicate with the telephony server and the AxC that resides on the storage server. You can design your system so that the location of the front-end application servers is remote from the back-end storage server. This flexibility allows you choose either decentralized or centralized system topologies for your organization. Clustering You can combine up to three application servers to form a cluster. You can add an additional N+1 server for redundancy (for a total of 4 servers in the cluster) as long as the active traffic does not exceed 300 ports. Each cluster connects to one storage server and supports the same telephony server. Clustering application servers allows you to: Increase the system's capacity so it can support more users. Every application server you add to the cluster increases the number of available ports. Provide redundancy for any application server in the same cluster. Application servers within a cluster are configured identically and are, therefore, interchangeable.

Your messaging network topology is determined by the way your organization has identified its sites. Typical network topologies include sites with: Decentralized application roles Centralized application roles Small organizations typically require an easy-to-deploy single-server topology that is ready to grow as the organization's needs expand. Large organizations can use the examples discussed in Network topology on page 36 as building blocks for their enterprise-wide network architecture, including: Conforming to an existing network topology Fitting into centralized data centers Supporting local survivability networks Meeting high availability requirements Supporting disaster recovery requirements
December 2010
37
Decentralized topology
A decentralized topology exists when application servers are located with the sites they support. This topology typically consists of one location that includes a dedicated application server and a dedicated storage server. Remote locations have a dedicated application server but no storage server. The following image is an example of a topology with two sites, Atlanta and Boston. But you can create a decentralized topology of more than two sites.
In this example, there are three application servers; two in Atlanta and one in Boston. Each communicates with their local switch. However, they all communicate with the dedicated storage server that is located in Atlanta.
Centralized topology
A centralized topology exists when not all application servers in a network are located with the site they support. A centralized topology can include either of the following network topologies: All application servers are located at the same location and support several sites The application servers are divided among a small number of locations that support a large number of sites The following image is an example of a centralized topology in which all application servers are located at the same site.
38
December 2010
In this example, the second telephony server in Atlanta uses SIP trunks to connect the Messaging system to the telephony servers in Atlanta and Boston. You administer SIP trunks as part of a trunk group on the telephony server. SIP connectivity is typically accomplished by one of the following: Avaya Aura SIP Enablement Services proxy Avaya Aura Session Manager AudioCodes gateway. You need one AudioCodes gateway for each application server. Note: See your account representative for a complete list of products that provide SIP connectivity. This topology accommodates telephony servers with either uniform or mixed dialing plans.
December 2010
39
40
December 2010
Chapter 4: Planning for Messaging
Switch integration
Switch integration is achieved when a call is presented to a voice port and information about the call is supplied to the Messaging system. This information includes the nature of the call, called party information, and the calling party number.
Session Initiation Protocol

Messaging supports only SIP integration. SIP is an important technology for establishing realtime audio and multimedia calls in a converged IP network environment. With SIP, the switch and the application servers are connected to the local area network (LAN). All exchange of information, such as call information, signaling information, and voice data, happens by means of voice channels through the LAN. Messaging system is connected to the switch, using the SES proxy or Avaya Session Manager, through SIP trunks. The SIP trunks are administered as part of a trunk group on the switch. Messaging supports SIP Integrations without the need for a Session Enablement Server or Session Manager. Consult your ATAC or Sales Engineer representative for these types of integration. Messaging interoperates with AudioCodes gateway to work with switches and integrations that are not supported.
Traffic flow
Your IT infrastructure needs to allow network traffic to move freely to and from the messaging system. Use the following table to determine whether your network can accommodate network traffic for Avaya Aura Messaging. The table shows: The protocol used by the components The port associated with each component
IN X OUT X Service Name FTP Protocol TCP 21 Port Notes Used to upload software updates (optional)
December 2010
41
Planning for Messaging
IN X X X
OUT X X X X
Service Name SSH TELNET SMTP DNS HTTP POP3 NTP SNMP SNMPTRAP LDAP HTTPS SMTPS syslog LDAPS POP3S hp-sshd h248message
Protocol TCP TCP TCP UDP TCP TCP TCP UDP UDP TCP TCP TCP UDP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP 22 23 25 53 80 110 123 161 162 389 443 465 514 636 995
Port
Notes
Disabled by default
X X
X X X
Redirects to HTTPS by default
X X X X X
X X X X X X
X X X X X X X X X X
X X
2222 2945 5022 5060 5061 8081 8083 55000 1024 65534
Avaya proprietary use secure remote access
X X X X X X X
secure-sat SIP SIP TLS ADCSJAX ADCSFETCH msgmgr N/A
Avaya proprietary use secure remote access
Avaya proprietary use cluster communications Avaya proprietary use cluster communications Avaya proprietary use legacy mail access API Used by several protocols to reach clients, including RTP/ SRTP Used by several protocols to reach
N/A
UDP
1024 65534
42
December 2010
Licensing
IN
OUT
Service Name
Protocol
Port
Notes clients, including RTP/ SRTP
N/A
ICMP
Used for "ping" support
Licensing
Avaya controls the use and access of some Messaging features through licenses, which the customer must purchase, including the number of Messaging enabled mailboxes the customer wants to use. Messaging uses WebLM as its standard licensing mechanism. Messaging features are tied to the WebLM server, and any client of that server can acquire and use a licensed feature. Messaging requires a WebLM hosted license. Messaging uses an enterprise license that allows the same license to be shared with multiple Messaging systems within an organization, if desired. The number of seat licenses is shared between all the Messaging systems associated with that license. The license file controls the number of user mailboxes. The license is created based upon the Host ID of the WebLM server. The user count can only be changed via PLDS either by purchasing additional seats or by moving seats between licenses. If more than one Messaging system exists in an enterprise, then the licensing model should be planned before obtaining the required license through PLDS.
System design and data collection

In preparation for a Messaging implementation, customers are required to provide specific information related to their voice and data network. During the system planning phase and prior to installation, customers are required to complete this information. Consultation with a Messaging Software Specialist is highly recommended. Information customers should be prepared to provide includes: Unique host names for all Messaging servers Corporate IP addresses, subnet-mask and default gateway information Corporate networks domains, DNS, NTP and SNMP information PBX/Call server type Message Networking and SMTP protocol information
December 2010
43
Desired system feature functionality, including classes of service, mailbox size, message length, time zones and telephone user interface (TUI) Caller Application (Auto-Attendants), Enhanced Lists / Broadcast (System Distribution Lists)
Capacity planning
Server models
Two server models are available: A standard server Serves as either: - Single server (application + storage server) - Application only server, or - Storage only server A high capacity storage server Serves as a storage only server to support a large number of mailboxes.
Capacity examples
Role: Hardware: Standard Server Application + Storage (Single Server) 100 ports = 6,200 users @ 62 users/ port 8,000 mailboxes @ 20 mins/mailbox (G. 711) 5,500 mailboxes @ 30 mins/mailbox (G. 711) Application Only (dedicated application server) 100 ports = 6,200 users @ 62 users/ port For a single site, up to 3 application servers can be clustered for a max port size of 300 ports. An additional application server can be added to a cluster for N+1 redundancy as long as active traffic is not exceeding 300 ports. Storage Only (dedicated storage server) 8,000 mailboxes @ 20 mins/mailbox (G. 711) 5,500 mailboxes @ 30 mins/mailbox (G. 711)
High Storage Capacity Server
Same as above. (Not Not applicable. typical use this configuration can be
20,000 mailboxes @ 20 mins/mailbox (G. 711)
44
December 2010
Preparing for Messaging
Role: Hardware:
Application + Storage (Single Server) used if this server is expected to become a dedicated storage only server in the future.)
Application Only (dedicated application server)
Storage Only (dedicated storage server) 13,500 mailboxes @ 30 mins/mailbox (G. 711)

Environmental requirements
Safety instructions
Use the following safety guidelines to ensure your own personal safety and to help protect your system and working environment from potential damage. Observe the following precautions for rack stability and safety. Also refer to the rack installation documentation accompanying the rack for specific caution statements and procedures. Systems are considered to be components in a rack. Thus, component refers to any system as well as to various peripherals or supporting hardware. Danger: Before installing systems in a rack, install front and side stabilizers on stand-alone racks or the front stabilizer on racks that are joined to other racks. Failure to install stabilizers before installing systems in a rack could cause the rack to tip over, potentially resulting in bodily injury. After installing components in a rack, never pull more than one component out of the rack on its slide assemblies at one time. The weight of more than one extended component could cause the rack to tip over and may result in serious injury. Use caution when pressing the component rail release latches and sliding a component into or out of a rack because the slide rails can pinch your fingers. Note: Your system is safety-certified as a free-standing unit and as a component for use in a rack cabinet using the customer rack kit. It is your responsibility to ensure that the final
December 2010
45
combination of system and rack complies with all applicable safety standards and local electric code requirements. System rack kits are intended to be installed in a rack by trained service technicians. Important: Two or more people are required to install components that are 2U or larger in a rack cabinet. Always load the rack from the bottom up, and load the heaviest item in the rack first. Make sure that the rack is level and stable before extending a component from the rack. Do not overload the AC supply branch circuit that provides power to the rack. The total rack load should not exceed 80 percent of the branch circuit rating. Ensure that proper airflow is provided to components in the rack: - Do not block any air vents. Usually 15 cm (6 in.) of space provides proper airflow. - Install the server only in a rack cabinet with perforated doors. - Do not leave open spaces above or below an installed server in your rack cabinet. To help prevent damage to server components, always install a blank filler panel to cover the open space and to help ensure proper air circulation. Do not step on or stand on any component when servicing other components in a rack. Do not place any object on top of rack-mounted components.
Clearance requirements
Install the server in a rack that meets the following requirements: Minimum depth of 70 mm (2.76 inches) between the front mounting flange and inside of the front door if the server is installed in a cabinet. Minimum depth of 157 mm (6.18 inches) between the rear mounting flange and inside of the rear door if the server is installed in a cabinet. Minimum depth of 718 mm (28.27 inches) and maximum depth of 762 mm (30 inches) between the front and rear mounting flanges to support the use of the cablemanagement arm.
Hardware requirements
Avaya-provided equipment
Avaya provides the following equipment: Server and power cord Slide rails
46
December 2010
Cable management arm assembly Cable management arm stop bracket Cable management arm mounting bracket Cable management support arm Two 1032 screws Four M6 screws Five small cable ties One large cable tie Other hardware as ordered, such as uninterruptible power source (UPS).
Customer-provided equipment
The customer must provide the following equipment: Standard 19-inch four-post equipment rack that is properly installed and solidly secured. The rack must meet the following standards: - American National Standards Institute and Electronic Industries Association standard ANSI/EIA-310D-92. - International Electrotechnical Commission standard IEC 297 - Deutsche Industrie Norm standard DIN 41494 Screws that come with the racks for installing the rails #2 cross-point (Phillips) screwdriver or 3/8 inch flathead screwdriver USB keyboard, USB mouse, and monitor must be available on the site for advanced installation or troubleshooting. Power from a nonswitched electrical outlet Access to the network
Server specifications
Messaging supports the S8800 1U server. These servers arrive at your site with all appropriate components and memory. You do not need to add anything to the servers on site. The following table lists the specification of the S8800 1U server.
Component Chassis Processor Speed 1U E5520 Quad-core 2.26 Ghz processor Standard Server High Capacity Storage Server 1U E5520 Quad-core 2.26 Ghz processor
December 2010
47
Component Number of Processors System Memory Ethernet Ports RAID Type Disk Standard Power Supply 1
Standard Server 1
High Capacity Storage Server
12 GB 2 RAID 5
12 GB 2 RAID 5
3 x 146Gb 10k rpm SAS hard 4 x 146Gb 15k rpm SAS hard disk drives disk drives Dual power supplies Dual power supplies
Software requirements
Required software for Messaging
The following table lists the Web browser requirements for the Messaging system.
Software System Platform Supported versions Internet Explorer 7 Mozilla Firefox 2 Mozilla Firefox 3 Internet Explorer 7 Internet Explorer 8 Mozilla Firefox 3.5 Safari 4
User Preferences System Management Interface
The following table lists the software requirements for the Messaging system.
Software System Platform Messaging 6.0.0.0.11 6.0 Supported versions
The following table lists the supported versions of Microsoft Outlook.

Software Microsoft Outlook 2003 2007 2010 Supported versions
48
December 2010
Supported versions of Avaya products

The following table lists the supported versions of the Avaya products.
Software Avaya Aura SIP Enablement Services, Avaya Aura Session Manager, Message Networking Avaya one-X Speech Avaya one-X Mobile Avaya one-X Communicator 5.2.1 6.0 5.2 5.2 5.2 6.0 5.2 6.0 Supported versions
Supported versions of third-party software

Avaya supports use of the documented software versions with the current release of this product. These software versions are the minimum versions required by Avaya. This release does not support operating systems, databases, Web servers, switches, or other software platforms that are not documented here, unless stated otherwise in a Product Support Notice. Avaya will support subsequent updates and service packs that are released to provide corrections to a bug, defect, or problem for the documented software versions, so long as those updates and service packs: Are guaranteed by the manufacturer to be backwards compatible with the supported version. Do not include changes to core functionality or new features. Avaya recommends that you test all updates and service packs subsequent to the supported versions in a development environment before applying them to a production environment.
Security requirements
Before implementing a Messaging system, ensure that the customer security staff reviews and approves the Messaging deployment. This means that customers should engage the expertise of their security staff early in the implementation process. The security staff must consider how they will incorporate the Messaging system into their routine maintenance of virus protection, patches, and service packs. For more information about system security, see the Messaging and Security section of the Messaging documentation library.
December 2010
49
Additional security information

Additional security information and documentation about all Avaya products is available at the Avaya Security Advisories Web site (http://support.avaya.com/security). For example, you can find information about the following: Avaya Product Security Vulnerability Response Policy Avaya Security Vulnerability Classification Security advisories for Avaya products Software patches for security issues Reporting a security vulnerability Automatic e-mail notifications of security advisories You can also find additional information about security practices at the National Security Agency Security Configuration Guides Web site (http://www.nsa.gov/snac).
Preparing your telephony server

Telephony overview
Avaya Aura Messaging is a SIP-based messaging system. However, when coupled with a SIP gateway, it supports a wide variety of analog, digital, and H323 telephony servers and telephones. In large organizations with specialized administration roles, the switch and messaging administrators might be different individuals. If this is true for your organization, you may need to coordinate integration activities because some telephony parameters must be identical on the telephony and application servers.
Configuration Notes
This chapter provides general information meant to assist you in making decisions about your integration. Avaya provides Configuration Notes with switch-specfic configuration information. You can download them from the Avaya Support Web site at http://www.avaya.com/support.
50
December 2010
Preparing your telephony server
Resource management
You need to ensure that your telephony server has a sufficient amount of resources dedicated to messaging functionality. Variables for calculating capacity and determining how many SIP trunks to dedicate to Messaging are: The amount of network traffic that flows through your messaging system The number of ports reserved for messaging The types of telephones your organization uses
Messaging ports
The total number of ports that you require determines how many SIP trunks to administer for Messaging.
Call answer ports

Call answer ports handle any incoming call for: One call answer session One voice-mail login session They also handle outgoing calls initiated by the following Messaging features: Reach Me Call Sender Notify Me Some products, like AudioCodes and some older telephony servers, put an explicit limitation on how many call answer ports you can have. System Manager and SES do not.
Transfer ports
Transfer ports are dedicated to outgoing transfer operations for the following Messaging features: Auto Attendant Personal Attendant
Systems with multiple sites

Each Messaging site has a one-to-one relationship with a telephony server. If your organization uses more than one telephony server, then it has a multi-site messaging system and you must repeat administration activities on each telephony server in your telephony network.
December 2010
51
52
December 2010
Index A
accessibility ..................................................................8 additional security information ....................................50 application role ......................................................36, 37 application server topology ...............................................................38 attendant personal attendant ...............................................24 system attendant ..................................................24 AudioCodes ..........................................................39, 51 Auto Attendant ...........................................23, 27, 35, 51 Avaya Aura Session Manager .................................................39 SIP Enablement Services ....................................39 Avaya Aura components .........................................................32 overview ...............................................................31 Avaya one-X Communicator ......................................18 Avaya one-X Mobile ...................................................18 Avaya one-X Speech ..................................................18 AxC .............................................................................37
E
e-mail ..........................................................................35 ELA .............................................................................22 email copies ...............................................................20 Enhanced List Applications ........................................22 equipment Avaya provided ....................................................46 customer provided ...............................................47 extended absence greeting ........................................23
F
fax ...............................................................................28 flexibility ........................................................................9 front-end/back-end ................................................37, 38 centralized topology .............................................38 decentralized topology .........................................38
G
gateway ................................................................39, 41 AudioCodes .........................................................39 greetings .....................................................................23
B
Basic Speech Auto Attendant .....................................23
C
Call Sender .................................................................51 Caller Applications ................................................28, 35 Caller Applications Editor ...........................................28 capacity planning ........................................................44 centralized topology ...................................................38 clearance requirements ..............................................46 clustering ....................................................................37 compatibility .................................................................9 Configuration Notes ....................................................50
H
hardware ....................................................................34
I
IMAP ...........................................................................35 industry standards ........................................................9 interoperability ............................................................12 AudioCodes gateways .........................................12 Avaya products ....................................................12 fax ........................................................................12 third-party products ..............................................12
D
data collection ............................................................43 desk phone .................................................................17 dial plan ......................................................................38 disaster recovery ........................................................11 documentation ............................................................13
L
languages ...................................................................13 LDAP ..........................................................................35 License
December 2010
53
management ........................................................27 licensing .....................................................................43
resilience ....................................................................10
M
message notifications .................................................20 message privacy ........................................................26 message waiting indicator ..........................................20 Message Waiting Indicator .........................................35 Messaging benefits ..................................................................7 overview .................................................................7 software requirements .........................................48 migration ......................................................................9 mobility .........................................................................8 multi-site system centralized ............................................................38 decentralized ........................................................38 MWI ............................................................................20
S
S8800 .........................................................................34 S8800 1U Server ........................................................47 safety instructions .......................................................45 SAL gateway ..............................................................11 scalability ....................................................................10 security ............................................................10, 49, 50 additional information ...........................................50 security requirements .................................................49 server .........................................................27, 3538, 50 centralized ............................................................38 decentralized ........................................................38 front-end/back-end ...............................................37 management ........................................................27 roles .....................................................................35 single server .........................................................36 telephony ........................................................37, 50 types ....................................................................36 server role application ......................................................36, 37 storage .................................................................37 server specifications ...................................................47 serviceability ...............................................................11 Session Initiation Protocol ..........................................41 SIP ..............................................................................41 SMI .............................................................................27 SMTP .........................................................................35 speech recognition .....................................................21 storage role ................................................................37 supported versions .....................................................49 switch ....................................................................37, 51 resources .............................................................51 switch integration ........................................................41 system broadcast message ........................................22 system design ............................................................43 System Management Interface ..................................27 System Manager ........................................................34 System Platform .........................................................32
N
network topology ...............................................................37 network topology ........................................................36 Notify Me .........................................................20, 35, 51
O
offline handling ...........................................................10 one-number connectivity ..............................................9 Outlook .......................................................................19
P
PDL ............................................................................21 Personal Attendant .....................................................51 personal distribution lists ............................................21 personal greeting ........................................................23 ports call answer ...........................................................51 transfer .................................................................51 ProVision ....................................................................12
T
telephony integrating with .....................................................35 telephony server ..............................................37, 50, 51 multiple sites ........................................................51 resources .............................................................51 text conversion ...........................................................25 text notification ...........................................................35
R
RBAC .........................................................................27 Reach Me .............................................................24, 51 redundancy .................................................................10 requirements ..............................................................49
54
December 2010
text to speech .............................................................26 toolbar ........................................................................19 topology centralized ............................................................38 decentralized ........................................................38 front-end/back-end ...............................................37 network ................................................................37 single server .........................................................36 traffic flow ...................................................................41 TTS .............................................................................26 TUI ..............................................................................35
User Preferences ..................................................25, 35
V
voice mail ...................................................................35
W
Web Access Mask ......................................................27
U
User Management ......................................................26
December 2010
55
56
December 2010

AvayaAuraMessagingOverviewandPlanning 601

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AvayaAuraMessagingOverviewandPlanning 601

Uploaded by

Copyright:

Available Formats

Avaya Aura Messaging Overview and Planning

6.0 CID: 145423 December 2010