Avaya Media Application Server Fundamentals

Release 6.6 NN44474-101, Document Revision: 01.03 August 20, 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 Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree 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(s) 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 this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s 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://www.avaya.com/support. Please note that if you acquired the product 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, AND 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

2

Avaya Media Application Server Fundamentals

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 Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. 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. Database License (DL). End User may install and use each copy of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicate with no more than a single instance of the same database. 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 Named User License (NU). End User may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. “Named User,” means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a “Named User” may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as “shrinkwrap” or “clickwrap” license accompanying or applicable to the Software (“Shrinkwrap License”). The text of the Shrinkwrap License will be available from Avaya upon End User’s request (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(s) and Product(s) provided by Avaya. All content on this site, the documentation(s) and the product(s) 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. 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.

August 20, 2010

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://www.avaya.com/support/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. Avaya 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://www.avaya.com/support/. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: [email protected]. Trademarks The trademarks, logos and service marks (“Marks”) displayed in this site, the documentation(s) 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(s) 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 is a registered trademark of Avaya Inc. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: http://www.avaya.com/support 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://www.avaya.com/ support

Avaya Media Application Server Fundamentals

August 20, 2010

3

4

Avaya Media Application Server Fundamentals

August 20, 2010

Contents Chapter 1: New in this release.................................................................................................9 Features............................................................................................................................................................9 Media Application Server platform hardware............................................................................................9 Media Application Server on Linux...........................................................................................................9 Media Application Server dual-stack support.........................................................................................10 Other changes.................................................................................................................................................10

Chapter 2: Introduction...........................................................................................................11 About MAS......................................................................................................................................................11 Related books.................................................................................................................................................12

Chapter 3: Media Application Server Fundamentals...........................................................13 Media Application Server................................................................................................................................13 Network deployment options...........................................................................................................................14 Supported platform..........................................................................................................................................14 License requirements......................................................................................................................................15 Automated installations and upgrades............................................................................................................15 Web-based configuration and management features.....................................................................................15 Packaged application support.........................................................................................................................16 Session Initiation Protocol features.................................................................................................................17 Media processing features..............................................................................................................................17 Audio and video codecs.........................................................................................................................18 Playing and recording audio...................................................................................................................18 Digit collection and relay methods..........................................................................................................19 Conferencing..........................................................................................................................................19 Media security........................................................................................................................................20 Media Quality of Service.........................................................................................................................20 QoS statistics..........................................................................................................................................20 Report generation...........................................................................................................................................20 Content store...................................................................................................................................................21

Chapter 4: Ad Hoc Conferencing...........................................................................................23 Multimedia conferencing.................................................................................................................................23 DivX Multipoint video conferencing feature.....................................................................................................24 Video conference behavior during bridging.....................................................................................................28 Bearer negotiation...........................................................................................................................................28 Accounting records.........................................................................................................................................29

Chapter 5: Announcements....................................................................................................31 Treatment (cause) announcements................................................................................................................32 Branding announcements...............................................................................................................................35 OAMP considerations.....................................................................................................................................38

Chapter 6: Instant Message Chat...........................................................................................39 IM Chat features..............................................................................................................................................39 Public chat room.....................................................................................................................................39 Public chat room with password.............................................................................................................39 Private chat room...................................................................................................................................40 System administrator-created chat rooms..............................................................................................40

Avaya Media Application Server Fundamentals

August 20, 2010

5

User-created chat rooms........................................................................................................................40

Chapter 7: Meet Me Conferencing.........................................................................................41 Chairperson controls.......................................................................................................................................44 Chair Status............................................................................................................................................46 Conference Kill.......................................................................................................................................46 Chairperson Call for Operator without Transfer......................................................................................46 Conference Fast Start............................................................................................................................46 Meet Me conferencing recording............................................................................................................47 Conference IM Chat...............................................................................................................................47 Silent Bridge Audit...........................................................................................................................................47 DivX Multipoint Video Conferencing................................................................................................................48 Video conferencing features...................................................................................................................48 DivX video conference behavior during bridging....................................................................................51 Premium conferencing............................................................................................................................52 Bearer negotiation..................................................................................................................................52 Accounting records.........................................................................................................................................53

Chapter 8: Music on Hold.......................................................................................................55 Chapter 9: Personal Ringback Tones....................................................................................57 Chapter 10: Unified Communications...................................................................................59 Unified Communications (basic).....................................................................................................................59 Unified Communications with Avaya Aura Personal Agent integration...........................................................60 Unified Communications voice mail delivery through e-mail...........................................................................61

Chapter 11: MAS application features...................................................................................63 Multilevel Precedence and Preemption...........................................................................................................63 User Agent Preemption..........................................................................................................................63 Network Preemption...............................................................................................................................63 Preempted party handling......................................................................................................................64 Audible precedence ringback tone.........................................................................................................64 Preemption tone.....................................................................................................................................64 Announcements......................................................................................................................................64 Call scenarios.........................................................................................................................................64

Chapter 12: MAS security.......................................................................................................69 Differentiated Services Code Point marking....................................................................................................69 Public Key Infrastructure.................................................................................................................................70 File system integrity........................................................................................................................................70 Certificate validation........................................................................................................................................70 Certificate verification policy...................................................................................................................71 Certificate extensions.............................................................................................................................71 Login banner...................................................................................................................................................71 Password policy..............................................................................................................................................72 User roles........................................................................................................................................................72 Linux user accounts........................................................................................................................................73 Security logs....................................................................................................................................................74 Linux audit logs...............................................................................................................................................74 Quantum security logs....................................................................................................................................74 EM security logs..............................................................................................................................................75

6

Avaya Media Application Server Fundamentals

August 20, 2010

MAS ports.......................................................................................................................................................75 Management access control and VLAN..........................................................................................................76

Chapter 13: Installation...........................................................................................................77 System requirements......................................................................................................................................77 Installation overview........................................................................................................................................77 Installation work flow.......................................................................................................................................78 Installation configurations................................................................................................................................80 Standalone.............................................................................................................................................80 Uninstall overview...........................................................................................................................................80

Chapter 14: Administration....................................................................................................81 Element Manager overview.............................................................................................................................81 Navigating Element Manager.................................................................................................................82 Interface features....................................................................................................................................83 Basic interface operation........................................................................................................................84 Central authentication, authorization, and auditing................................................................................85 UCM security server roles......................................................................................................................86 RBAC concepts......................................................................................................................................86 Identities.................................................................................................................................................87 Accounts.................................................................................................................................................88 Permissions............................................................................................................................................89 Roles......................................................................................................................................................90 Policies...................................................................................................................................................90 Limit access control views......................................................................................................................91 Certificates..............................................................................................................................................91 Element status and operational controls.........................................................................................................93 Element Status.......................................................................................................................................94 Starting, stopping and restarting.............................................................................................................94 Operational states..................................................................................................................................94 Cluster configuration and status monitoring controls......................................................................................94 Cluster configuration...............................................................................................................................95 Cluster status..........................................................................................................................................95 License management......................................................................................................................................95 Server licensing......................................................................................................................................96 Nodal licensing.......................................................................................................................................96 Signaling configuration....................................................................................................................................97 SIP configuration....................................................................................................................................97 Media configuration.........................................................................................................................................97 Quality of Service...................................................................................................................................97 Audio codecs..........................................................................................................................................98 Video codecs..........................................................................................................................................98 Digit relay (DTMF)..................................................................................................................................99 Media security........................................................................................................................................99 Hysteresis.............................................................................................................................................100 Monitoring and logging global configuration support.....................................................................................100 Monitoring.............................................................................................................................................100 Logging.................................................................................................................................................103 Application management...............................................................................................................................104 Packaged applications..........................................................................................................................105 Reporting.......................................................................................................................................................105 Backup and restore.......................................................................................................................................105

Avaya Media Application Server Fundamentals

August 20, 2010

7

General settings...................................................................................................................................106 Backup tasks........................................................................................................................................106 Restore.................................................................................................................................................106 Backup destination...............................................................................................................................107 History logs...........................................................................................................................................107 Media management......................................................................................................................................107 Advanced settings.........................................................................................................................................108 Disaster recovery..........................................................................................................................................108

Chapter 15: Commissioning.................................................................................................109 Initial security configuration...........................................................................................................................109 MAS configuration.........................................................................................................................................109 License configuration.....................................................................................................................................111 Network management protocol configuration................................................................................................111 SNTP.....................................................................................................................................................111 SNMP...................................................................................................................................................112 SOAP....................................................................................................................................................112 Connection security..............................................................................................................................113 Network configuration....................................................................................................................................113 IP address assignment and traffic classes............................................................................................113 QoS audio and video DSCP settings configuration..............................................................................114 QoS monitoring and alerting configuration....................................................................................................114 SIP configuration...........................................................................................................................................114 Media provisioning.........................................................................................................................................116 Packaged application configuration...............................................................................................................116

Chapter 16: Terminology.......................................................................................................119

8

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 1: New in this release The following section details what's new in Avaya Media Application Server Fundamentals, NN44474-101 for Avaya Media Application Server (MAS) Release 6.6.

Features For information about feature-related changes, see the following sections: • Media Application Server platform hardware on page 9 • Media Application Server on Linux on page 9 • Media Application Server dual-stack support on page 10 For information about all MAS features in this release, see Avaya Aura™ Application Server 5300 Release Delta, NN42040-201.

Media Application Server platform hardware MAS Release 6.6 introduces a new platform hardware: x3550 M2. For more information, see Supported platform on page 14.

Media Application Server on Linux New sections describe the following MAS packaged applications: • Personal Ringback Tones on page 57 • Instant Message Chat on page 39 The following new sections describe new functionality: Digit Collection and Multilevel Precedence and Preemption (MLPP). For more information, see • Digit collection and relay methods on page 19 • Multilevel Precedence and Preemption on page 63 MAS no longer supports the Windows platform. Information about the Windows Performance Monitoring application is removed.

Avaya Media Application Server Fundamentals

August 20, 2010

9

New in this release

Media Application Server dual-stack support MAS Release 6.6 introduces IPv4/IPv6 dual-stack support. For more information about MAS and dual-stack support, see IP address assignment and traffic classes on page 113. For information about Avaya Aura™ Application Server 5300 and dual-stack support, see Avaya Aura™ Application Server 5300 Overview, NN42040-100.

Other changes The following list includes changes that are not feature-related: • Incorporated applicable information from the following document, now retired: Nortel Media Application Server Overview - Services and Features, NN44471-112. • The Multimedia PC Client is renamed to Avaya Aura™ AS 5300 UC Client. Revision history

10

August 2010

Standard 01.03. This document is issued to support Avaya Media Application Server Release 6.6 for Avaya Aura™ Application Server 5300 Release 2.0. Editorial changes were made.

May 2010

Standard 01.02. This document is issued to support Avaya Media Application Server Release 6.6 for Avaya Aura™ Application Server 5300 Release 2.0. Editorial changes were made.

April 2010

Standard 01.01. This document is issued to support Avaya Media Application Server Release 6.6 for Avaya Aura™ Application Server 5300 Release 2.0. This document contains the information previously contained in the following documents, now retired: Nortel Media Application Server Fundamentals, NN44471-111 and Nortel Media Application MAS Overview - Services and Features, NN44471-112.

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 2: Introduction This document describes the fundamental topics for Avaya Media Application Server (MAS). Navigation • Media Application Server Fundamentals on page 13 • Ad Hoc Conferencing on page 23 • Announcements on page 31 • Instant Message Chat on page 39 • Meet Me Conferencing on page 41 • Music on Hold on page 55 • Personal Ringback Tones on page 57 • Unified Communications on page 59 • MAS application features on page 63 • Installation on page 77 • Administration on page 81 • Commissioning on page 109 • Terminology on page 119

About MAS The MAS provides a robust, scalable software platform for hosting multimedia applications. The MAS platform supports generic multimedia processing using standard open protocols. Not all the MAS packaged applications described in this book apply to all systems. The MAS supports various services, depending on your system configuration. For more information about supported MAS packaged applications, see Avaya Media Application Server Planning and Engineering, NN44474-200.

Avaya Media Application Server Fundamentals

August 20, 2010

11

Introduction

Related books The following books provide more information about the MAS: • Avaya Media Application Server Documentation Roadmap, NN44474-100 • Avaya Media Application Server Meet Me Conferencing Quick Reference, NN44474-102 • Avaya Media Application Server Unified Communications Quick Reference, NN44474-103 • Avaya Media Application Server Planning and Engineering, NN44474-200 • Avaya Media Application Server Commissioning, NN44474-301 • Avaya Media Application Server Administration and Security, NN44474-600 • Avaya Media Application Server Troubleshooting and Fault Management, NN44474-700 • Avaya Media Application Server Operational Measurements Reference, NN44474-701 • Avaya Media Application Server Alarms and Logs Reference, NN44474-702 • 102.1.1 AS5300 Server Installation • 102.1.5 AS5300 x3550 M2 Installation • 102.1.6 AS5300 MAS Platform and Application Installation • 102.2.7 AS5300 MAS Release Upgrade • 103.2.2 AS5300 MR And Patch • 103.2.7 AS5300 MAS Backup And Restore • 105.1.3 AS5300 Security Hardening • 106.2.99 AS5300 Symantec AntiVirus Installation

12

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 3: Media Application Server Fundamentals This chapter provides an overview of what you need to know to work with the Avaya Media Application Server (MAS). Navigation • Media Application Server on page 13 • Network deployment options on page 14 • Supported platform on page 14 • License requirements on page 15 • Automated installations and upgrades on page 15 • Web-based configuration and management features on page 15 • Packaged application support on page 16 • Session Initiation Protocol features on page 17 • Media processing features on page 17 • Report generation on page 20 • Content store on page 21

Media Application Server MAS is a software-based, media processing server. The host servers process media using software. The MAS architecture facilitates unique scalability for all core functions of the platform, including signaling, application execution, content management, and media processing. MAS interworks with Avaya Aura™ Application Server 5300 to provide multimedia applications. To support some applications, certain information is configured on both the MAS and the Avaya Aura Application Server 5300.

Avaya Media Application Server Fundamentals

August 20, 2010

13

Media Application Server Fundamentals

Network deployment options You can configure your network as a stand-alone system or as a cluster of multiple servers. Configure the following aspects of your network from the appropriate pages in Element Manager (EM): • cluster configuration (primary, secondary, standard): see Cluster configuration and status monitoring controls on page 94 • SIP configuration (general settings, domains and accounts, nodes and routes): see SIP configuration on page 97 All nodes within a cluster must operate on the same operating system and MAS release.

Supported platform You can install MAS on both Avaya- and customer-provided hardware. Avaya provides a mapvichecker.exe tool to confirm that your platform meets the minimum requirements. Avaya recommends that you use the following platforms: • for existing systems: IBM x3550 (dual quad-core Intel XEON 5140 2.33 GHz, 2 GB RAM, SCSI HD) running Red Hat Enterprise Linux version 5.2 • for new systems (MAS 6.6): IBM x3550 M2 running on Red Hat Enterprise Linux version 5.4 (mandatory). Important: MAS does not support the Windows platform. Avaya-supplied hardware includes a hardened version of Red Hat Enterprise Linux. The system requires Gigabit Ethernet (GbE) (recommended) or 100 MB full-duplex network connectivity. For new systems, RHEL version 5.4 provides a number of additional IPv6 compliancy capabilities for use by MAS. These new systems require AudioCodes and Integrated Access Devices (IAD) version 5.8. For MAS packaged applications, you must use a Nodal License Key, which you provision through the EM. See Avaya Media Application Server Commissioning, NN44474-301 for details about licensing configuration.

14

Avaya Media Application Server Fundamentals

August 20, 2010

License requirements

For more information about hardware requirements, see Avaya Media Application Server Planning and Engineering, NN44474-200.

License requirements The system determines your maximum number of simultaneous active sessions by the number of licenses you purchase. Applications cannot function if you install them without the proper licensing. MAS supports a nodal licensing model. When the MAS is commissioned, an administrator provisions it with a license key. In a redundant MAS configuration, you must provision each MAS node with a unique license. The license key specifies how many ports are licensed for each supported application.

Automated installations and upgrades You can install MAS by using either command line interface (CLI) mode using Secure Shell (SSH), or silent install mode (which is automated). In both cases, installation requires minimal user input. You can perform minor upgrades to the MAS platform and the installed applications by running a newer installer (MAS and applications) over the existing installation. You can upgrade the platform without reinstalling the applications. The upgrade is fully automated and the system preserves all configuration data.

Web-based configuration and management features EM is a Web-based administration tool that you use to configure and manage the MAS. Use EM to control the following elements: • licensing configuration • system operational state management • alarm and event log viewer • alarm and event log configuration and filtering • cluster configuration • backup and restore

Avaya Media Application Server Fundamentals

August 20, 2010

15

Media Application Server Fundamentals

• Simple Network Management Protocol (SNMP) and SysLog support • network multi-netting and traffic classes • debug tracing • Web services configuration • gateway configuration • media management • monitoring of - advanced features (including Component Status, Advanced Protocols, Troubleshooting Archive Generator, and Security Logs) - active sessions - operational measurements - session detail records - protocols For more information about Element Manager, see Avaya Media Application Server Commissioning, NN44474-301 and the Element Manager help.

Packaged application support Packaged applications are off-the-shelf applications. You can manage and configure these applications using Element Manager (EM). A packaged application is installed and configured using a custom installer. The installer adds application configuration data and translations to the MAS. As part of the installation process you must configure license keys for all packaged applications. Use the EM to view installed packaged applications, the version, and operational state. Within the EM, packaged applications are located under Products and Applications, Custom Applications. The following MAS packaged applications, also known as MAS Services, are available: • Ad Hoc Conferencing: Use Ad Hoc Conferencing to join multiple participants in a multimedia conference call. You can initiate a conference call from any client. After you select the Join button, the calls transfer to the conference server. The conference originator can leave the conference without interrupting the call. The conference server terminates the call when only one participant remains. For more information about Ad Hoc Conferencing, see Ad Hoc Conferencing on page 23. • Announcements: The Announcements application plays both cause and treatment, and branding recordings. For more information about the Announcements application, see Announcements on page 31.

16

Avaya Media Application Server Fundamentals

August 20, 2010

Session Initiation Protocol features

• IM Chat: The Chat application provides messaging in a chat room, which consists of a single window. For more information about the Chat service, see Instant Message Chat on page 39. • Meet Me Conferencing: The Meet Me Conferencing application provides reservationless audio and video conferencing on the MAS platform. You can use Meet Me Conferencing for private conferencing at any time. For more information about Meet Me conferencing, see Meet Me Conferencing on page 41. • Music on Hold: The Music on Hold application plays music while a caller is on hold. For more information about Music on Hold, seeMusic on Hold on page 55. • Personal Ringback Tones: With the Personal Ringback Tones application, subscribers can select custom audio that the system plays to incoming callers instead of traditional ringback tones. For more information about Personal Ringback Tones, see Personal Ringback Tones on page 57. • Unified Communications: The Unified Communications application provides integrated access to voice mail messages from a preferred client device, such as a personal computer (PC), a Voice over IP (VoIP) telephone, a wireless telephone, or a traditional circuit switched telephone. Optionally, users can configure the system to e-mail voice messages to their e-mail client for playback. For more information about Unified Communications, see Unified Communications on page 59.

Session Initiation Protocol features The MAS platform supports Session Initiation Protocol (SIP) for call and session signaling. SIP provides a standard means to establish sessions, negotiate capabilities, invoke applications, and exchange data with MAS. The MAS platform uses SIP Transport Layer Security (TLS) to secure SIP signaling. MAS manages a list of trusted network sources, and routes signaling from nontrusted sources to a network proxy for authentication. MAS supports a SIP trunking mode for the reuse of connections to and from network proxies for subsequent calls to reduce the overhead of TLS signaling. SIP routes define all SIP proxy and SIP registrar servers with which a MAS node can communicate. MAS uses SIP routes designated as a SIP proxy server to route outbound SIP requests for outbound traffic load sharing and failover. MAS registers applications with all configured SIP registrars. Registration is optional based on your MAS configuration and digest authentication support.

Media processing features MAS supports text, audio, and video for most multimedia processing features. The system can stream audio and video in a variety of codecs and formats, fully synchronized from the server,

Avaya Media Application Server Fundamentals

August 20, 2010

17

Media Application Server Fundamentals

unbuffered, and in real time. The system can deliver text through both instant messaging and Web push methods.

Audio and video codecs MAS supports the following audio codecs: • ITU-T G.711 A-Law and Mu-Law • ITU-T G.729a • EVRC • AMR MAS supports the following video codecs: • NNVC (DivX-4) • H.263+, H.263++ MAS can transcode to and from the following audio formats: • Linear 16-bit PCM, 8 kHz Mono • Linear 8-bit PCM, 8 kHz Mono • G.711 A-Law • G.711 Mu-Law • G.729 • EVRC

Playing and recording audio MAS can stream media files (also called prompts or announcements) in all supported codecs. These files are not limited to audio. You can control media playback using the following VCR controls: • pause: suspend the request • resume: continue the request • adjust positive: skip ahead a specific number of milliseconds within the request • adjust negative: skip backward a specific number of milliseconds within the request • stop: cancel the request

18

Avaya Media Application Server Fundamentals

August 20, 2010

Media processing features

The MAS caches media files locally and transcodes them into temporary files. For subsequent requests of the same media file, the MAS uses the transcoded file and creates a packet for the file without further processing. Files that surpass a configurable hit rate are pulled into memory in the post-transcoded form and packets are created directly. An uncached file that is not eligible for caching, is transcoded in real time.

Digit collection and relay methods MAS supports the most popular SIP INFO digits, and RFC2833 and RFC4733, for digit relays. SIP INFO, RFC2833, and RFC4733 are fully configurable, including preference rank. The Linux digit collection application explicitly uses the MAS to enable digit collection. This MAS feature provides generic digit collection for the Application Server 5300. The MAS platform negotiates to SIP INFO or RFC2833 DTMF digit collection. If the MAS platform negotiates INFO digits, then it also accepts in-band tones. The MAS digit collection operates during the call. MAS digit collection has the following areas of concern: • provisioning: When you install the application, it provides a default digit map (4 to 10 digits with a terminating number sign [#]) and tone on the MAS. The system uses a digit map to define digit screening behavior. The system plays the default tone after it receives the digit collection SIP invite message, and before it collects digits. An administrator can provision the MAS with custom digit maps through the Provisioning Client. Map provisioning conforms to standard MAS paradigms. The system stores all content in a two-level hierarchy; the system contains all content items in a namespace followed by a content group. • digit collection: The system invokes digit collection by using a standard SIP INVITE with parameters that specify how to perform the digit collection.

Conferencing MAS supports multimedia conferencing for audio and video streams in large and small conferences. The conferencing algorithm uses mixing, which means that you can hear up to four parties simultaneously. Each channel runs a voice activity detector (to determine speech versus background noise), an automatic gain control algorithm, and a dynamic jitter buffer with compaction and packet loss concealment.

Avaya Media Application Server Fundamentals

August 20, 2010

19

Media Application Server Fundamentals

Media security The MAS secures media streams with cryptographic protection based on RFC3711 (The Secure Real-Time Transport Protocol [SRTP]). SRTP is an RTP (RFC3550) profile with symmetrical data encryption that provides the following security services: encryption, message integrity, and replay protection.

Media Quality of Service MAS services support Differentiated Service (DiffServ) packet marking on outgoing RealTime Transport Protocol (RTP) streams. The MAS framework assigns the DiffServ Control Point (DSCP) to expedited forwarding (EF), which is a widely supported indicator for Quality of Service (QoS)-enabled networks. QoS-enabled network routers examine the DSCP information in a packet and provide priority (with respect to routing and handling) to those packets marked with expedited forwarding. Overloaded routers drop generic data packets before they drop DiffServ-marked packets. The MAS service strategy follows RFC2598, which designates the EF bit pattern. The MAS platform uses QoS packet scheduling to reserve 70 percent of all available network bandwidth to voice traffic and gives a higher priority to voice traffic packets, delivering them to the network first. The MAS contains the Telchemy VQMON agent for QoS monitoring.

QoS statistics MAS services receive and generate Real-Time Transport Control Protocol (RTCP) Sender reports. The MAS transmits RTCP packets to each participant, detailing the perceived quality of the session. The system continually monitors R-Factor, jitter, and loss packet for each call. The system logs calls that fall below a configured R-Factor threshold and archives all QoS statistics with session detail records (SDR) for analysis.

Report generation The reporting framework is based on third-party Jasper reports, a flexible solution that can generate complex reports. Administrators can use the reporting framework to generate reports on demand and provide automated report generation based on a configured time schedule.

20

Avaya Media Application Server Fundamentals

August 20, 2010

Content store

The reporting framework supports CSV, HTML, and XML reporting types. The system can deliver scheduled reports through e-mail or File Transfer Protocol (FTP).

Content store MAS contains an onboard content storage feature that provides a reliable, network accessible store for multimedia content. You can configure MAS to replicate data across multiple content stores to provide High Availability and redundancy. The following four MAS package applications require access to the MAS Content Store (CStore): • Meet Me Conferencing • Unified Communications • Music on Hold • Announcements Data associated with these applications reside on a single CStore or mirrored pair of CStores within a pool. A pool can contain any number of routes to MASs; however, only one (two if they are mirrored) has an active CStore.

Avaya Media Application Server Fundamentals

August 20, 2010

21

Media Application Server Fundamentals

22

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 4: Ad Hoc Conferencing The Media Application Server (MAS) Ad Hoc Conferencing service supports both Ad Hoc Conferences and consultative call transfers. The Ad Hoc Conferencing service provides the following basic conferencing capabilities: • multimedia conferencing with support for audio mixing, transcoding for G.711 and G.729 audio codecs, and arbitrarily sized conferences • Bearer negotiation on page 28 • RTCP support. For more information, see QoS statistics on page 20. • QoS support. For more information, see Quality of Service on page 97. • Multilevel Precedence and Preemption on page 63 Navigation • Multimedia conferencing on page 23 • DivX Multipoint video conferencing feature on page 24 • Video conference behavior during bridging on page 28 • Bearer negotiation on page 28 • Accounting records on page 29

Multimedia conferencing The Ad Hoc Conferencing service supports consultative call transfers. In this call transfer scenario, the system creates an ad hoc conference during the consultation phase of the call transfer. The Ad Hoc Conferencing service provides support for SIP REFER-based ad hoc conferencing and audio media stream mixing for the conference. The system tracks and mixes the two most powerful audio streams. To determine the relative energy levels of each audio stream, the system periodically applies Energy Detection algorithms to the received audio streams. The system uses these algorithms to determine the two most powerful audio streams at a given instant. The most powerful audio stream is relayed to the source of the second most powerful audio stream. Likewise, the second most powerful audio stream is relayed to the source of the most powerful audio stream. Additionally, the two most powerful audio streams are mixed for distribution to all other endpoints participating in the conference. The following table shows how the MAS mixes and distributes audio during a three-party conference call.

Avaya Media Application Server Fundamentals

August 20, 2010

23

Ad Hoc Conferencing

Table 1: Audio mixing sample Primary/Secondary

Party A hears

Party B hears

Party C hears

PartyA/PartyC

PartyC

PartyA + PartyC

PartyA

PartyB/PartyA

PartyB

PartyA

PartyA + PartyB

PartyB/PartyC

PartyB + PartyC

PartyC

PartyB

PartyC/PartyA

PartyC

PartyA + PartyC

PartyA

PartyC/PartyB

PartyB + PartyC

PartyC

PartyB

The audio mixing function occurs at 10-millisecond (ms) intervals and operates on 10 ms of audio data. This period enables the audio mixer to support multiple sample sizes (sample sizes that are multiples of 10: 20 ms, 30 ms, 60 ms). Audio conferencing normalizes all received audio streams before processing (audio transcoding). The service performs all audio conference operations on the normalized data. Normalization of the received audio streams enables the Ad Hoc Conferencing service to support parties using different audio codec selections in the same conference. The following table shows details about the supported audio code characteristics of the Ad Hoc Conferencing service. Table 2: Supported audio codecs Audio codec

Interval rates (ms)

Sampling rates (kHz)

G.711 (PCMU)

10, 20, 30, 60

8

G.711 (PCMA)

10, 20, 30, 60

8

G.729a

10, 20, 30, 60

8

The Ad Hoc Conferencing service also supports reception of G.711-encoded silence suppression and comfort noise as defined by RFC3389.

DivX Multipoint video conferencing feature This feature provides video conferencing capabilities to users who participate in an ad hoc conference. Using the DivX video codec, the feature supports all video resolutions available on the Avaya Aura™ AS 5300 UC Client. DivX is the only video codec that the Avaya Media Application Server supports and is installed as part of the Avaya Aura™ AS 5300 UC Client. DivX is a proprietary video codec (based on the MPEG-4 video standard) of DivX Inc. Important: For video conferencing, you must identically license and configure all Avaya Media Application Servers within the same Pooled Entity in a subdomain. In other words, you must

24

Avaya Media Application Server Fundamentals

August 20, 2010

DivX Multipoint video conferencing feature

licence and configure all Avaya Media Application Servers within the same Pooled Entity in a subdomain to either enable video conferencing or disallow video conferencing. The DivX Multipoint Video Conferencing feature provides • switched video delivery, which means that the system transmits a video image of the active speaker to nonactive, video-enabled participants, and a placeholder image to audio-only participants and the active speaker. • video switching hysteresis ensures that the video stream of the active speaker does not switch too often or unintentionally. This mechanism ensures that the video-enabled speaker is the most active speaker for a specific amount of time before it transmits a video image of the speaker to other participants. Video-switching hysteresis delays the change from one active speaker to another. • force-to-chairperson Session Description Protocol negotiation uses the chairperson’s video capabilities determine the video capabilities of the conference participants. Important: All video participants of the conference must use the DivX codec. The chairperson video configuration controls the availability of video and the size of the video frame. The Avaya Media Application Server performs no video transcoding. • support of MAS audio capabilities, to enable video conference participants and the chairperson to use different audio configurations. Important: All parties in the video conference receive the mixed audio stream for the conference regardless of whether they can send video. • mixed client support, both video-enabled and audio-only clients can participate in MAS video conferences. The only supported video clients are the Avaya Aura™ AS 5300 UC Client and Multimedia Web Client. This feature supports all audio clients that the MAS supports. Audio-only clients cannot send or receive video. For the complete list of clients that this feature supports, see Avaya Aura™ Application Server 5300 Overview, NN42040-100. • mixed video frame rates, to enable the chairperson and participants to use different video frame rates. The MAS software attempts to adapt frame delivery to the frame rate of each conference participant. Important: The MAS software uses best-effort adaptation to send as many video frames each second as possible to the limit of each participant’s frame rate. Pauses can occur in delivery if a participant’s frame rate is substantially below that of the active speaker. A flow diagram of the steps involved in setting up a video conference follows.

Avaya Media Application Server Fundamentals

August 20, 2010

25

Ad Hoc Conferencing

Figure 1: Setting up an Ad Hoc video conference

26

Avaya Media Application Server Fundamentals

August 20, 2010

DivX Multipoint video conferencing feature

Figure 2: Setting up an Ad Hoc video conference (continued)

Avaya Media Application Server Fundamentals

August 20, 2010

27

Ad Hoc Conferencing

Video conference behavior during bridging Bridged (chained) video conferences may not behave as expected. If a single dominant speaker is in a bridged video conference, then the active speaker’s video is switched as expected. If no single dominant speaker is in a bridged video conference, unexpected video switching can occur. For example, if two equally active speakers exist (one in each half of a bridged video conference), then a different active speaker is chosen in each half of the bridge. As a result, the active speaker video shown in one half of the bridge is different from the active speaker video shown in the other half. Another bridging issue occurs if the system chooses the bridged leg as the active speaker. In this case, the system displays the placeholder video to every party in the bridged conference. Normally, only the active speaker sees the placeholder video. Important: Do not use Ad Hoc Conferencing to add someone into a Meet Me conference; this causes your conference controls to stop working. The best solution is to ask the person to dial in to the Meet Me bridge to join your conference.

Bearer negotiation You can license the Ad Hoc Conferencing service to support all or some subset of the total media capabilities. The licensed media capabilities are configured (supported codecs, supported formats, supported sampling rates) and used during media negotiations to build requests or responses. Configuration of media capabilities is an integral part of the licensing process. The Ad Hoc Conferencing service provides access to audio and video capabilities, and you can license this service to support G.711, G.729, or both. Clients interact with the Ad Hoc Conferencing service using SIP and negotiate their media capabilities using Session Description Protocol (SDP). When a session begins, the originating client provides information describing the preferred media capabilities in an SDP. This SDP request is delivered to the media negotiator, which analyzes the requested media capabilities and builds a response that provides the best match between the requested media capabilities and the media capabilities available on the Ad Hoc Conferencing service. The Ad Hoc Conferencing service automatically detects the packet time and codec after it receives the first incoming audio packet. In addition, the Ad Hoc Conferencing service can change packet times on an existing audio stream. The Ad Hoc Conferencing service also supports code changes; however, this requires stopping and starting the audio stream by using a call hold and retrieve sequence.

28

Avaya Media Application Server Fundamentals

August 20, 2010

Accounting records

Accounting records To generate accounting records, the Ad Hoc Conferencing service requires data capture to correlate all participants in a conference. Currently, the system uses and fields in the Internet Protocol Detail Records (IPDR) to associate data among the records. The system identifies ad hoc conferences by a conference token. For video conferencing services, the IPDR also captures the video codecs used for each call. The billing service, which captures accounting information resides on the system on which IPDRs are generated. Therefore, the additional data required for conference correlation is sent to the system in SIP INFO messages. For an ad hoc audio conference, the MAS sends the INFO message only once after the conference begins, because that is when it creates the token. All subsequent parties requesting entry into the ad hoc conference already have the token in the message, so the MAS need not send additional INFO messages.

Avaya Media Application Server Fundamentals

August 20, 2010

29

Ad Hoc Conferencing

30

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 5: Announcements Use announcements to inform callers about the status of their call or to identify a company or product for commercial purposes. The Announcements service • supports both cause and treatment, and branding announcements. • supports multiple languages and, if no language identifier is provided, you can define a default announcement. • allows you to play more than one announcement (chaining) and to specify the order in which multiple announcements are played. • allows you to play announcements continuously or for a specified number of times. • allows you to play an announcement during the precall state. • allows you to specify (after an announcement is played) whether the call is terminated or is routed to a number. The routed number can be either the dialed number, a predefined number such as voice mail, or security numbers. • allows you to define announcements at either the domain or subdomain level. • transcodes announcements at run time to the client settings, encoding the digital bit stream using the G.711 or G.729 transmission algorithm. The MAS transmits announcements with packet times of 10, 20, 30, or 60 milliseconds. • supports media files in the Microsoft Wave file format that are encoded as single-channel (mono) linear 16-bit bitstreams using a pulse code modulation (PCM) that is sampled at 8 kHz. • supports the automatic raising and lowering of the amplitude of announcement files to a normalized level. • allows you to define announcements based on individual announcement files, languages, and compression type. • supports the collection of accounting information. • supports both simplex (single Announcement MAS) and duplex architectures (two fully redundant Announcement MAS). • allows you to swap the standard (in-service) announcement files with pre-loaded media files that are in reserve on the MAS. For example, using the Provisioning Client, you can activate holiday or inclement weather announcements. • supports the existence of more than one active Announcement MAS within the same root domain. The AS 5300 Session Manager can always route calls to the available MAS. • is service-package independent.

Avaya Media Application Server Fundamentals

August 20, 2010

31

Announcements

• allows you to use multiple service instances and subdomains (during configuration) to ensure that calls are routed to local servers within a domain. • plays branding announcements that are configured in the domain or subdomain of the terminating party. • complies with the requirements for network announcements as defined by the Internet Engineering Task Force (IETF) draft document. Specifically, this feature supports the SIP URI, as well as the parameters play, early, repeat, and locale. Avaya does not supply default audio files with the Announcements service software. The system administrator must obtain and provision the audio files. Navigation • Treatment (cause) announcements on page 32 • Branding announcements on page 35 • OAMP considerations on page 38

Treatment (cause) announcements These announcements provide the calling parties with an explanation of why their calls cannot be completed immediately. For example, the announcement might inform the caller that all circuits are busy. Treatment (cause) announcements consist of one or more audio messages that you (the administrator) can chain together and for which you can specify a playback order. You decide which audio messages the caller hears for each call failure scenario. Additionally, you can configure messages to loop indefinitely or for a specified duration. After the caller hears the announcement, you can configure the service to terminate the call or to route the call to a predefined number (for example, voice mail or security). The Announcements service is service-package independent, which means the treatment (cause) announcements are also service-package independent. If the following conditions are met, then the caller will hear a treatment: • You configured treatments for a domain (and optionally a subdomain). • You placed the necessary treatment audio files on the MAS. • A problem occurs completing a call, and the AS 5300 Session Manager for the terminating party generates one of the supported SIP cause messages. For a complete list of the Session Initiation Protocol (SIP) cause messages that are supported in the current release of the Announcements service, see Avaya Media Application Server Commissioning, NN44474-301.

32

Avaya Media Application Server Fundamentals

August 20, 2010

Treatment (cause) announcements

The SIP cause messages are triggered by call failure scenarios. For example, when: • A bad request was made. • An unauthorized call is attempted. • Payment is required to complete the call. • A bad extension is used. • The called party is temporarily unavailable. The text included with each SIP cause message summarizes the reason why the call failed (for example, BAD_REQUEST or TEMPORARILY_UNAVAILABLE). The following flow diagram shows the steps to play a treatment to a caller.

Avaya Media Application Server Fundamentals

August 20, 2010

33

Announcements

Figure 3: Flow diagram showing the process for treatment announcements

34

Avaya Media Application Server Fundamentals

August 20, 2010

Branding announcements

Branding announcements Branding announcements allow you to play marketing messages to people who use your network. A branding announcement is played before the call is routed to the called number. Branding announcements consist of one or more audio messages that you (the administrator) can chain together and for which you can specify a playback order. Additionally, you can configure these messages to loop indefinitely or for a specified duration. The Announcements service is service-package independent, which means that branding announcements are also service-package independent. If the following conditions are met, then the caller hears a branding announcement before the call is answered: • You configured branding announcements for a domain (and optionally a subdomain). • You placed the necessary audio files on the MAS. The branding announcement plays to the caller based on the domain or subdomain of the called party. During call setup, the AS 5300 Session Manager determines if the originating and called parties are within • the same subdomain (of a parent domain) • different subdomains (of a parent domain) After the AS 5300 Session Manager determines the relationship of the originator and called parties within the domain and subdomain hierarchy, the AS 5300 Session Manager uses the rules in Table 3: Branding for calls between users within subdomains of a domain on page 35 to determine if a branding announcement should play to the caller. Table 3: Branding for calls between users within subdomains of a domain Domain xyz.com Parent domain xyz.com

Subdomai Subdomai n n a.xyz.com b.xyz.com

Branding for calls between users within a.xyz.c om

Branding for calls between users within b.xyz.com

Branding for calls between users of a.xyz.com and b.xyz.com

True

True

True

True

True

True

False

False

False

False

False

False

False

True

True

True

True

False

True

False

False

False

False

True

False

False

True

False

True

False

Avaya Media Application Server Fundamentals

August 20, 2010

35

Announcements

The conclusions that you can draw from Table 3: Branding for calls between users within subdomains of a domain on page 35 are as follows: • When both the originating and called parties are in the same subdomain, then the rules for that subdomain override the rules for the domain. • When the originating and called parties are in different subdomains, then the rules for the domain override the rules for the subdomains. The following flow diagram shows the steps to play a branding announcement to a caller.

36

Avaya Media Application Server Fundamentals

August 20, 2010

Branding announcements

Figure 4: Flow diagram showing the process for branding announcements

Avaya Media Application Server Fundamentals

August 20, 2010

37

Announcements

OAMP considerations The following Operation, Administration, Management and Provisioning (OAM&P) considerations relate to the Announcements service and the system as a whole. The system uses the Internet Protocol Detail Record (IPDR) format to store accounting information for announcements. If the AS 5300 Session Manager requests a file or folder for playback but a MAS-based application indicates that it cannot find the requested file or folder, the AS 5300 Session Manager creates a log entry. The system increments the Media Controller (annc::AnnouncementServicesUses) operational measurement (OM) each time it plays a treatment or branding announcement. This counter tracks the number of announcements the system plays over a specified period of time. When provisioning audio files for MAS services both on the Avaya Media Application Servers and the Provisioning Manager, the domain administrator must avoid typing mistakes in the audio file names. The system does not automatically check file name validity; therefore, the domain administrator must check the file names. The domain administrator must name audio files the same across all servers in a common resource pool. The administrator must also ensure each server in a resource pool contains a copy of each audio file.

38

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 6: Instant Message Chat The Instant Message (IM) Chat service allows two or more users who have Avaya Aura™ AS 5300 UC Clients or Multimedia Web Clients to send text messages to a chat room, consisting of a single window. Each participant is able to send an instant message to any or all participants within the IM chat room. In addition, the IM Chat service allows users to invite other people to join the chat room, to browse available online chat rooms, or to select a specific chat room to join. A user is able to join multiple chat rooms simultaneously, in which case, each chat room appears in a separate window. Navigation IM Chat features on page 39

IM Chat features This service allows users and administrators to create the following three types of chat rooms: • public • public with password • private In addition to the three general types of chat room, the IM Chat service allows the following groups to create chat rooms: • system administrators • users

Public chat room This chat room is visible in the chat-room list, and users do not need a password to join.

Public chat room with password This chat room is visible in the chat-room list; however, users need a password to join.

Avaya Media Application Server Fundamentals

August 20, 2010

39

Instant Message Chat

Private chat room This chat room is not visible in the chat-room list, and only users who are invited can join.

System administrator-created chat rooms These are predefined chat rooms created by system administrators in advance. These chat rooms always appear in the chat-room list until the administrator removes them.

User-created chat rooms These are chat rooms created by end-user subscribers.

40

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 7: Meet Me Conferencing The Meet Me Conferencing service provides reservationless multimedia conferencing based on the Avaya Media Application Server platform. A subscriber, also known as the chairperson, must have Meet Me in their service package to host a conference call. An Application Administrator uses the operator controls in the Provisioning Client to assign a subscriber's: • service package • access code and chairperson PIN, which the subscriber uses to set up a conference call. An Application Administrator is an administrator with the Applications Management-only role. For more information about operator controls, see Avaya Aura™ Application Server 5300 Using the Provisioning Client, NN42040-112. Navigation • Chairperson controls on page 44 • Silent Bridge Audit on page 47 • DivX Multipoint Video Conferencing on page 48 • Accounting records on page 53 Meet Me Conferencing provides the following basic capabilities: • audio mixing • transcoding for G.711 and G.729 audio codecs • arbitrarily sized conferences • Premium conferencing on page 52 • Bearer negotiation on page 52 • RTCP support. For more information, see QoS statistics on page 20 • QoS support. For more information, see Quality of Service on page 97. • Multilevel Precedence and Preemption on page 63 • Meet Me Conference Reporter, which is accessible through the MAS Element Manager (EM). See Avaya Media Application Server Commissioning, NN44474-301 for details about the EM.

Avaya Media Application Server Fundamentals

August 20, 2010

41

Meet Me Conferencing

In addition, the Meet Me Conferencing service provides the following features: • the ability for an end user, configured with the Meet Me Conferencing service, to set up a multimedia conference anytime, on demand, with no reservation required, for up to a configured number of conferees. • ubiquitous access to Meet Me conference resources through use of a service dial-in number • private chairperson access codes that provide the Meet Me service subscribers secure access to their conference sessions • configurable hold music, advertisements, and informational audio for participants while waiting for the chairperson to start the conference • audio support for callers. For a complete list of supported phones, see Avaya Aura™ Application Server 5300 Overview, NN42040-100. • DivX Multipoint Video Conferencing on page 48 support for callers using the Avaya Aura™ AS 5300 UC Client • the ability for the conference chairperson to initiate an instant message chat room for the conference • audio entry/exit tone indicators to announce the arrival and departure of conference participants • audio emoticon support that provides interactivity options for conference participants. The administrator is responsible for providing the media source files for the audio emoticons. Some examples of audio emoticons that the chairperson or a participant can play are clapping, booing, and laughing. • chairperson prompts that enable the chairperson to - activate the multimedia conference - place all waiting participants into a multiparty multimedia conference session - start/stop an instant message chat session for the conference - mute/unmute all conference participants - enable/disable audio emoticon support - enable/disable audio entry/exit tone indicators • Optional conference-related instant messages that inform the chairperson of various events Table 4: Conference-related instant messages Conference event

Example instant message

The chairperson dials in and enters the chair PIN. Welcome. Participant dials in and is waiting, listening to music.

John Dee is waiting.

Participant stops waiting (hangs up while waiting for the conference to start).

Elvis Rocker has left.

Participant transfers the Meet Me call to another destination.

John Dee transferred to 9724561234.

42

Avaya Media Application Server Fundamentals

August 20, 2010

Conference event

Example instant message

Participant fails to enter the correct conference passcode and is disconnected.

Janet Doe failed to enter the passcode.

Participant joins the conference.

Janet Doe has joined.

Participant hangs up while in conference.

Sandy Hill has left.

• dynamically assigned passcodes that a chairperson can set for a conference. Participants must successfully enter the passcode to join, providing control over who may access the conference. • the ability for conference participants to mute/unmute themselves • Provisioning Client integration, allowing system administrators to configure the following conference attributes: - access code - chairperson PIN - conference behavior options • Personal Agent integration allowing end users to view their specific conference information, which includes - dial-in number - access code - chairperson PIN • monitoring features (accessed using the Provisioning Client) that provide operators with the ability to view active sessions, User Agent data, and Meet Me-specific user lookups by access code • operator controls that you can use to mute, unmute, and terminate specific lines. You access these controls through the Provisioning Client. For more information, see Avaya Aura™ Application Server 5300 Using the Provisioning Client, NN42040-112. • Chairperson controls on page 44 (available to the operator using the TUI or in the administrative Web interface) that provide the chairperson the ability to - enable or disable audio emoticons - play audio emoticons - launch a chat session - enable or disable entry and exit tones - lock or unlock the conference - enable or disable conference continuation on chair exit - count the participants - mute or unmute all participants

Avaya Media Application Server Fundamentals

August 20, 2010

43

Meet Me Conferencing

- immediately release all calls • additional enhancements, including the ability to - start the conference before the chairperson arrives - assume the role of the chair after the chairperson has left - call the operator without transferring out of the conference - allow the chairperson to record the conference audio Some feature behaviors are configured for each individual user, while others are only system wide. For example, instant message generation event is set globally, while chairperson PIN is set for each user. Important: If you are in a Meet Me conference, do not use Ad Hoc Conferencing to join anyone into the Meet Me conference (or your conference controls will no longer work). Ask the person to dial in to the Meet Me bridge to join your conference. The MAS provides the following conference benefits: • Automatic Gain Control (AGC) running on each channel to increase and correct the amplitude of low volume, most often caused by incorrect microphone settings or poor headsets • the capability to mix up to four speakers (participants). Every 50 milliseconds (ms) the system may change the speakers it mixes. Mixing occurs every 10 ms. Basic conferencing mixes only two speakers every 10 ms. • Voice Activity Detection (VAD), which enables the system to make better decisions about which channels to mix. VAD improves the differentiation between voice and background noise. • Quality of Service (QoS) monitoring of all channels for network problems such as packet loss and excessive jitter. QoS also provides packet loss concealment. • Global IP Sound (GIPS), which corrects problems when the system detects excessive packet loss or jitter. This resource helps to maintain a good audio quality experience for participants.

Chairperson controls Meet Me Conferencing service users have their own private conferencing resource available for meetings at any time. A conference owner, the chairperson, provisioned with the service by an administrator, controls use of this personal conference resource. Chairpersons can configure the conference bridge through their Personal Agent, or they can request that the Application Administrator configure the conference bridge through the Provisioning Client. The chairperson provides the meeting details to the desired participants whenever a conference meeting is needed. Participants are given the Meet Me Conferencing service dial-

44

Avaya Media Application Server Fundamentals

August 20, 2010

Chairperson controls

in number, an access code that uniquely identifies the particular conference, and the date and time. You can configure the conference bridge to start in one of the following two ways: • after the chairperson dials in • after the first participant dials in If you configure the conference to start after the chairperson dials in, the system places the participants who dial in early on hold and connects to an audio stream of music, advertisements, or information as configured by the administrator. The system activates the conference only after the chairperson arrives. The administrator can configure whether or not the conference continues after the chairperson leaves. If you configure the conference to start after the first participant dials in, also known as “Fast Start,” the conference starts as soon as the first participant dials in, regardless of whether the first participant is the chairperson. For more information about Fast Start, see Conference Fast Start on page 46. In either configuration, the chairperson has control of the bridge. You can also configure a conference bridge to end in one of the following two ways: • after the chairperson hangs up. Any participants remaining on the bridge hear an announcement that the bridge will end. • after the last participant hangs up. If the chairperson hangs up, any remaining participants can continue to participate in the conference. The chairperson can use the following controls through the administrative Web interface; the Application Administrator can also use these controls through the Text-based User Interface (TUI): • enable or disable audio emoticons • play audio emoticons • launch a chat session • enable or disable entry and exit tones • lock or unlock the conference • enable or disable conference continuation on chair exit • count the participants • start or stop recording • mute all or unmute all participants • immediately release all calls For more information about chairperson controls, see Avaya Media Application Server Meet Me Conferencing Quick Reference, NN44474-102.

Avaya Media Application Server Fundamentals

August 20, 2010

45

Meet Me Conferencing

Chair Status The Chair Status option allows any user to assume the role of the chairperson if no chairperson is present or if a chairperson was present on the call and subsequently left the conference. If the conference has started and the chairperson has not arrived or has left, a user will have the option to press *0 and then enter the conference PIN. The user will be recognized as the conference chairperson and will have the ability to use all available conference chairperson commands. This is allowed anytime a chairperson is not present. If a previous chairperson had started a command such as a chat room and left the conference, a new chairperson would have the ability to stop the chat room. Only one chairperson is allowed at a time (for each conference).

Conference Kill The Conference Kill option allows the chairperson to end the conference immediately by pressing 11. A confirmation prompt is played to prevent the chairperson from unintentionally ending the conference. Upon confirmation by the chairperson, the conference and all participants are informed that the conference will end.

Chairperson Call for Operator without Transfer When the chairperson presses 00 to transfer to an operator, the operator joins the conference as a participant and the chairperson remains in the conference. The operator is then connected to all parties in the conference. If any of the participants press 00, they are transferred to an operator and leave the conference to prevent participants from disturbing conferences with operator questions.

Conference Fast Start Conference Fast Start allows the chairperson to configure the conference to start on the arrival of the first person in the conference (chairperson or participant). Use the Personal Agent to configure Conference Fast Start for each conference. The chairperson must configure a conference to either Fast Start or Traditional. If the chairperson enables Fast Start, the application plays an announcement to indicate the conference has started after the first person arrives and enters the access code.

46

Avaya Media Application Server Fundamentals

August 20, 2010

Silent Bridge Audit

Meet Me conferencing recording The chairperson may record all or part of a conference by pressing *9 (toggles on/off). The system sends the chairperson an e-mail message that contains the conference audio recordings after the chairperson presses *9 to stop audio recording or after the conference ends. Chairpersons specify their e-mail addresses using the Personal Agent. The application segments the audio files into manageable chunks of 30 minutes and sends them out accordingly for longer conferences. Conference participants, including participants that join the conference after the recording starts, hear an announcement indicating the conference is being recorded. Important: The Meet Me conferencing service sends conference audio recordings (as wave files) to the chairperson through e-mail. The audio files are segmented into chunks of up to 30 minutes by default. The administrator can change the recording size through the following configuration parameter: Audio Recording Collection Interval. The maximum size of an audio file attached in an e-mail message is approximately 5 MB. The chairperson’s SMTP server limits e-mail message size. Configure the chairperson’s SMTP server to receive an e-mail message with up to 30 minutes of audio data. For detailed instructions on how to configure Meet Me conferencing recording, see Avaya Aura™ Application Server 5300 Using the Provisioning Client, NN42040-112.

Conference IM Chat The chairperson can start an Instant Message chat room (hosted on the Meet Me conference server) and invite all conference participants (who are using the Avaya Aura™ AS 5300 UC Client) to join. The chat room name is the same as the conference access code. The system terminates the chat room session after either the chairperson ends the chat sessions or the conference ends.

Silent Bridge Audit To prevent users from leaving a conference in an open state (tying up MAS resources), the MAS software automatically detects any conference that has been silent (for a predetermined period of time) and drops the conference.

Avaya Media Application Server Fundamentals

August 20, 2010

47

Meet Me Conferencing

DivX Multipoint Video Conferencing This feature provides DivX video conferencing capabilities to users who participate in a Meet Me conference. Using the DivX video codec, the feature supports all video resolutions available on the Avaya Aura™ AS 5300 UC Client. DivX is the only video codec supported by the Avaya Media Application Server and is installed as part of the Avaya Aura™ AS 5300 UC Client. DivX is a proprietary video codec produced by DivXNetworks, Inc., and is based on the MPEG-4 video standard. Important: For video conferencing, you must identically license and configure all Avaya Media Application Servers within the same Pooled Entity in a subdomain. In other words, you must licence and configure all Avaya Media Application Servers within the same Pooled Entity in a subdomain to either enable video conferencing or disallow video conferencing.

Video conferencing features The DivX Multipoint Video Conferencing feature provides • switched video delivery: a video image of the active speaker is transmitted to nonactive, video-enabled participants, and placeholder video is transmitted to audio-only participants as well as to the active speaker. • video-switching hysteresis: a mechanism to ensure that the video stream of the active speaker does not switch too often or unintentionally. This is done by ensuring that the video-enabled speaker is the most active speaker for a specific amount of time before actually transmitting a video image of the speaker to other participants. Video-switching hysteresis delays the change from one active speaker to another. • force-to-chairperson Session Description Protocol negotiation, which means that the chairperson’s video capabilities determine the video capabilities of the conference participants All video participants of the conference must use the DivX codec. The chairperson’s video capabilities dictate whether there will be video and determine the size of the video frame. The Avaya Media Application Server does not perform any video transcoding. • support for all existing audio capabilities of the Avaya Media Application Server: video conference participants are not forced to adopt the chairperson’s audio capabilities. All parties in the video conference receive the mixed audio stream for the conference whether or not they can send video. • mixed client support: both video-enabled and audio-only clients are allowed to participate in MAS video conferences. The only supported video client is the Avaya Aura™ AS 5300 UC Client. This feature supports all audio clients supported by the MAS. Audio-only clients

48

Avaya Media Application Server Fundamentals

August 20, 2010

DivX Multipoint Video Conferencing

are not able to send or receive video. The complete list of clients supported by this feature can be found in Avaya Aura™ Application Server 5300 Overview, NN42040-100. • support for mixed video frame rates: video frame rates are not forced to match the chairperson’s frame rate. The MAS software attempts to adapt frame delivery to the frame rate of each conference participant. The MAS software uses best-effort adaptation to send as many video frames each second as possible up to the limit of each participant’s frame rate. There may be pauses in delivery if a participant’s frame rate is substantially below that of the active speaker. The following figures present a flow diagram of the steps involved in setting up a video conference.

Avaya Media Application Server Fundamentals

August 20, 2010

49

Meet Me Conferencing

Figure 5: Setting up a Meet Me DivX video conference

50

Avaya Media Application Server Fundamentals

August 20, 2010

DivX Multipoint Video Conferencing

Figure 6: Setting up a Meet Me DivX video conference (continued)

DivX video conference behavior during bridging Bridged (chained) DivX video conferences may not behave as expected. If there is a single dominant speaker in a bridged video conference, then the active speaker’s video is switched

Avaya Media Application Server Fundamentals

August 20, 2010

51

Meet Me Conferencing

as expected. If there is no single dominant speaker, there may be unexpected video switching. For example, if there are two equally active speakers (one in each half of a bridged video conference), then a different active speaker is chosen in each half of the bridge. As a result, the active speaker video shown in one half of the bridge is different from the active speaker video shown in the other half. Another bridging issue occurs when the bridged leg is chosen as the active speaker. In this case, every party in the bridged conference receives the placeholder video. Normally, the placeholder video should only be seen by the active speaker.

Premium conferencing Premium conferencing provides an improvement over basic conferencing through the use of several key technologies. Premium conferencing is designed to better handle network conditions often associated with DSL or Cable modem access networks. This includes packet loss conditions and extreme variances in jitter. In addition, the system performs better active speaker analysis to avoid mixing channels that contain noise instead of speech. The system is also capable of mixing more channels simultaneously than basic conferencing, which improves the perceived conference experience. Both basic conferencing and premium conferencing can coexist and run simultaneously on the same Avaya Media Application Server. Premium conferencing adds the following enhancements over basic conferencing: • Automatic Gain Control (AGC) runs on each channel to increase/correct the amplitude of low-volume channels typical of incorrect microphone settings or poor headsets. • A maximum of three speakers can be mixed for each 10-millisecond (ms) interval (basic conferencing mixes two speakers every 10 ms). • Voice Activity Detection (VAD) enables the system to make better decisions about which channels to mix by better differentiating between voice and background noise. • History is recorded for each channel to avoid switching too rapidly or between speaking pauses. • All channels are monitored for Quality of Service (QoS) issues, including networkrelated problems such as packet loss and excessive jitter. Packet loss concealment processing is applied to these channels dynamically, to help reduce the effects of these conditions on perceived QoS. These premium conferencing enhancements require additional server resources but offer a conference experience that is superior to basic Meet Me conferencing.

Bearer negotiation The Meet Me Conferencing service can be licensed to support all, or a subset, of its total media capabilities. The licensed media capabilities are configured (supported codecs, supported

52

Avaya Media Application Server Fundamentals

August 20, 2010

Accounting records

formats, supported sampling rates) and used during media negotiations when building requests or responses. Configuration of media capabilities is an integral part of the licensing process. The Meet Me Conferencing service provides access to audio capabilities and can be licensed to support G.711, G.729, or both. Clients interact with the Meet Me Conferencing service using SIP and negotiate their media capabilities using Session Description Protocol (SDP). When a session is initiated, the originating client provides information describing its preferred media capabilities in an SDP. This SDP request is delivered to the media negotiator, which analyzes the requested media capabilities and builds a response that provides the best match between the requested media capabilities and the media capabilities available on the Meet Me Conferencing service. The Meet Me Conferencing service automatically detects the packet time and codec when the first incoming audio packet is received. In addition, the Meet Me Conferencing service supports changing of packet times on an existing audio stream. Code changes are also supported; however, this requires that the audio stream be stopped and restarted by using a call hold/retrieve sequence.

Accounting records The Meet Me Conferencing service requires data capture to allow correlation of all participants in a conference for the purpose of generating accounting records. Currently, the and fields in the Internet Protocol Detail Records (IPDRs) are used to associate data among the records. Meet Me conferences are identified by the chairperson user name (user@domain). For video conferencing services, the IPDR also captures the video codecs used for each call. The billing service responsible for capturing the accounting information resides on the system where IPDRs are generated. Therefore, the additional data required for conference correlation is sent to the system in SIP INFO messages. For a Meet Me conference, an INFO message is sent for each participant upon entry into the Meet Me conference because the system does not have access to the chairperson user name. For the Meet Me service, the additional INFO messages sent to a system have some impact on the system. The system has to process the incoming INFO messages. Also the billing service on the system has to generate the IPDRs based on the information received in the INFO messages.

Avaya Media Application Server Fundamentals

August 20, 2010

53

Meet Me Conferencing

54

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 8: Music on Hold The Music On Hold (MOH) service allows a user, who receives a call and places that call on hold, to play music to the person on hold until the call is retrieved. Music On Hold service • is available for calls on End-User Hold, Transfer Hold, and Call Park Hold • supports continuous music. The music does not restart from the same point for each new call on hold. • allows for chained music files. You can specify more than one music file to be played. • can be configured to operate at the domain or subdomain levels • is enabled through service packages • supports the Microsoft Wave file audio format (single channel [mono] linear 16-bit PCM sampled at 8 kHz) • automatically normalizes the amplitude of the media (music files) to raise or lower the amplitude as soon as the files are placed on the Music On Hold Avaya Media Application Server • does not support external media sources. All media source files must be resident on the Music On Hold Avaya Media Application Server. • generates accounting information consisting of the duration and type of media file that is played • allows an administrator to swap the standard in-service media files with media files that are in reserve on the MAS by means of the Provisioning Client • supports a redundant configuration • supports the streaming of music through a gateway to an on-hold caller who is located on the PSTN or a private branch exchange (PBX) • generates performance data Important: You can disable the Music On Hold service for a user that typically connects to non-Application Server 5300-hosted conferences (time division multiplex, or third-party SIP conferences). The Music On Hold service software is able to detect when an Application Server 5300 user is connected to a Avaya Media Application Server-based conference. If this happens, the Music On Hold service does not play music if a caller is placed on hold by one of the conference participants. However, if an Application Server 5300 user dials into a non-Application Server 5300-hosted conference, such a user may place one of these TDM or third-party SIP conference participants on hold, thus triggering music to be played to the onhold participant (as well as everyone else on the conference bridge). In this case the Music On Hold service does not automatically determine that music should not be played. The purpose of the music is to reassure the person on hold that the call has not been disconnected or dropped.

Avaya Media Application Server Fundamentals

August 20, 2010

55

Music on Hold

To activate this service, the system administrator must provision music folders containing audio files, and configure the MAS to play this music to callers of users at either the domain or subdomain levels. Avaya does not supply any default audio files with the Music On Hold service software. It is the responsibility of the system administrator to obtain and provision the music files. Music On Hold is enabled through the user’s service package. If a user has Music On Hold enabled, and then puts a caller on hold (end-user hold, transfer hold, or call park hold), then the caller on hold hears music. The music that the caller hears is the music that is assigned to the domain or subdomain of the called party. If the user does not have Music On Hold enabled through their service package, and receives and places a call on hold, then the person on hold does not hear music. This is true even if music is assigned to the domain or subdomain of the called party.

56

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 9: Personal Ringback Tones Personal Ringback Tones (PRBT) service, also known as Colorful Ringback Tones (CRBT), enables enduser subscribers to select custom audio to be played to incoming callers instead of traditional ringback tones. Enhancements to several components provide the following capability: • Service Package: Provisioning the PRBT on the service package enables/disables PRBT for the subdomain. • Routable Service: PRBT is created as a routable service. • Logical Entities: A logical entity (pool) is created to include the PRBT routable service. • OPI methods: PRBT can be provisioned using Open Provisioning Interface (OPI) methods or the Provisioning Client. The AS 5300 Session Manager coordinates the PRBT call handling and other advanced call routing services such as SimRing and Sequential Ringing. A call placed to a PRBT subscriber causes the AS 5300 Session Manager to initiate and bridge a connection to the MAS to supply the ringback media. Once the call is answered, the AS 5300 Session Manager removes the MAS from the call path. The MAS PRBT service lets operating companies manage and access the custom ring-tone media. The service is delivered by a pool of servers and is accessed through Routable Services using SIP from the AS 5300 Session Manager. Media content is delivered to each MAS using an automated data synchronization tool called the Data Source Server (DSS). You must install the DSS on a separate, dedicated server, that does not have the MAS platform installed. The DSS serves as the controlling node for synchronization. During synchronization, the DSS: • adds or deletes any media files that you added or deleted on the DSS server • deletes or re-adds any media files that you added or deleted on the MAS The following figure shows the architecture of the PRBT service.

Avaya Media Application Server Fundamentals

August 20, 2010

57

Personal Ringback Tones

Figure 7: PRBT architecture

Important: Audio recordings are protected by national and international copyright laws. Customers who choose the PRBT are solely responsible for procuring all permissions and licenses necessary to use any audio recordings in offering the PRBT feature to end-user subscribers. The Customer agrees to indemnify Avaya for any third-party claims of infringement resulting from the Customer failing to obtain the necessary licenses from the copyright owners.

58

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 10: Unified Communications The Unified Communications service provides users with integrated access to their voice mail messages from a preferred client device, such as a PC, voice over IP (VoIP) phone, wireless phone, or a traditional circuit switched telephone. The following sections describe the services and features that each of these service offerings provides. Navigation • Unified Communications (basic) on page 59 • Unified Communications with Avaya Aura Personal Agent integration on page 60 • Unified Communications voice mail delivery through e-mail on page 61

Unified Communications (basic) The Unified Communications offering provides a basic set of integrated multimedia messaging functionality for subscribers hosted by the Avaya Aura™ Application Server 5300 solution. Subscribers are provided access to a TUI in order to retrieve messages and perform simple mailbox administration. The following key capabilities are included at the basic server level: • play • compose • delete/restore • reply to sender of message (call back) • Personal Identification Number (PIN) modification • message status announcements after logon to the mailbox • operator assistance • navigate between messages (next, previous) • skip backward/forward during a message • remote voice message retrieval from hard and soft clients (for a complete list of clients see Avaya Aura™ Application Server 5300 Overview, NN42040-100 • PIN authentication • multiple greetings support • greeting recording, selection, and activation

Avaya Media Application Server Fundamentals

August 20, 2010

59

Unified Communications

• audio codec support for IP clients: G.729 and G.711 (Mu-Law and A-Law) • greeting interruption for message deposits • allowance for callers to delete (cancel) and re-record messages before message deposit in a mailbox One single mailbox may be used by these many telephony devices and the messages deposited in this common mailbox may optionally be mailed to a user’s e-mail client, offering another convenient access option for voice mail message playback. Users manage their account through a traditional Telephony User Interface (TUI) or through the Web-based Avaya Aura™ Personal Agent (PA), which may be optionally configured for the user.

Unified Communications with Avaya Aura Personal Agent integration In addition to receiving basic voice mail services, subscribers may have the added benefit of using the Personal Agent as a Web-based interface for mailbox configuration and management. The integrated Unified Communications Personal Agent service increment includes the following additional functionality and an alternative user configuration interface: • PIN modification • the ability to reset PIN lockout state resulting from consecutive failed logon attempts from a TUI • greeting selection and activation • custom destinations: configuration for transfer out of voice mail to specific DNs or custom operator (for example, press 1 for operator; press 2, for secretary) • automatic identification for subscribers that are calling from a known device or a device that an Avaya Aura™ Application Server 5300 client is logged onto (for a complete list of clients, see Avaya Aura™ Application Server 5300 Overview, NN42040-100). Automatic identification is an administrator-controlled option enabled through the user’s service package. There are two ways you can use automatic identification: - when calling from a client

Figure 8: Calling from a client

60

Avaya Media Application Server Fundamentals

August 20, 2010

Unified Communications voice mail delivery through e-mail

- when using the customizable option. With this option you can enter up to three different PSTN or ESN numbers. The customizable option only lets you enter valid PSTN or ESN digits and not a user name. In other words, the numbers listed in the Alias field of a user in the Provisioning Client or in the Aliases field in the Personal Agent, Preferences- Personal- Contact Info will not work. You would list a user’s PSTN number as an Alias number for that user, so you would not enter that number as an address to be auto-identified. You would use auto-identification for the "my client" the user is logged in as.

Figure 9: Using the customizable option

• configuration to limit the maximum length of a message that someone may deposit • custom use of greetings for each caller and/or time of day

Unified Communications voice mail delivery through e-mail Subscribers may be provisioned to simultaneously receive deposited voice messages through their e-mail clients. The messages that are deposited in a subscriber’s mailbox are compressed into an audio file and forwarded to the subscriber’s e-mail address or another e-mail address as specified in the user’s Unified Communications preferences in the Personal Agent. Voice mail messages are encoded using the GSM codec and attached to an e-mail sent to the subscriber’s e-mail account using simple mail transfer protocol (SMTP). If the SMTP request fails, it is re-attempted several times, at one-minute intervals. Users can listen to and store their messages on their computer, since they are delivered to their inbox as a file attachment. Even when the e-mail deliver option is enabled, the MAS keeps a copy of the voice mail message on the network for efficient access from phone clients. The e-mail clients and the network storage are, however, loosely synchronized using hypertext transfer protocol (HTTP) indications generated by the e-mail client. Synchronization will work with any HTML-enabled e-mail client. When a message is viewed in the e-mail client, it sends HTTP requests to render the e-mail body and to notify the Unified Communications service that the message has been read. The MAS will deactivate the Message Waiting Indicator (MWI) on the subscriber’s client phone devices when the last new message is viewed.

Avaya Media Application Server Fundamentals

August 20, 2010

61

Unified Communications

62

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 11: MAS application features This section describes the key Avaya Media Application Server (MAS) application features. Navigation • Multilevel Precedence and Preemption on page 63 • MAS security on page 69

Multilevel Precedence and Preemption The Multilevel Precedence and Preemption (MLPP) service provides the ability to specify the precedence level of each call that is placed. Calls are processed based on their precedence level within the same MLPP service domain. Navigation • User Agent Preemption on page 63 • Network Preemption on page 63 • Preempted party handling on page 64 • Audible precedence ringback tone on page 64 • Preemption tone on page 64 • Announcements on page 64 • Call scenarios on page 64

User Agent Preemption User Agent Preemption (UA Preemption) preempts a call session on a call endpoint based on an incoming session of higher precedence than any active sessions, and when no other sessions can be presented. UA Preemption occurs when there are no other call appearances that the client can use to present the new arriving Precedence call to the user.

Network Preemption Network Preemption preempts within the network, resulting from active call sessions reaching the provisioned bandwidth limit or call count. A SIP signaling appliance, such as a call server or

Avaya Media Application Server Fundamentals

August 20, 2010

63

MAS application features

gateway, performs preemption when it has a new call with a high Precedence based on the provisioned budget.

Preempted party handling After a decision to preempt a member of an Ad Hoc or Meet Me conference has been made, the preemption tone plays for the preempted party for a period of 3 seconds. The session ends , the internal resource (license and conference limit count) release, and a SIP BYE message occurs with a cause and reason code. Because the feature deals only with preemption due to resource limitation, the only cause used is Reserved Resources Preempted.

Audible precedence ringback tone A precedence ringback tone plays to alert the user that the calling party has made a precedence call. This tone only plays after it is confirmed by the server through a 180 response. If a 183 with SDP response is received, the incoming audio stream plays instead of the local ringback notification.

Preemption tone When a member of an Ad Hoc or Meet Me session is preempted, the preemption tone plays. The device speaker broadcasts the tone.

Announcements One announcement is applicable in the MAS MLPP arena: Blocked Precedence Announcement (BPA). This announcement plays to the calling party if a priority call is attempted and cannot complete because parties of equal or greater priority are actively using MAS conferences. In this case, the MAS sends a return code and only applies a BPA when requested.

Call scenarios Conference max is the maximum number of parties provisioned for a given conference. Conference max also refers to the current number of parties on a locked conference. Resource max is when all MAS resources have reached the engineered limit.

64

Avaya Media Application Server Fundamentals

August 20, 2010

Multilevel Precedence and Preemption

Table 5: Meet Me call scenarios Scenario

Result

Synopsis

A Priority call is made to a Meet Me conference with Resources available.

The Priority call joins the Meet Me Conference.

This is a normal case.

A higher priority call is made to a conference with no additional resources, which include a lower priority caller.

The higher priority call joins the Meet Me Conference, lower priority caller is preempted and both the parties hear a preemption tone.

To allow a priority call to enter a conference, the system determines which party to preempt by searching for the lowest priority call within the conferees. The preempted party can be any one of the conference members, even the chairperson or the current speaker. Both the calling and preempted parties hear the preemption tone. The preempted party drops and the calling party session joins into the conference.

A Priority call is made to a Meet Me conference where the called conference is at resource maximum and no lower Priority calls exist.

The priority call receives the BPA announcement.

To allow for a priority call to enter the conference, a search for a lower priority party is made, and fails. The calling party will receive the BPA announcement. The original INVITE receives the reason Blocked Precedence.

A Priority call is made to a Meet Me conference that is not at resource maximum, but the MAS is at Resource maximum and a lower Priority call exists on the MAS.

The Priority call is added to the Meet Me Conference, Calling party and the preempted party receive preemption tones.

To allow for a priority call to enter the conference, a check to identify lowest priority level in the MAS is made in no particular order. If a low priority call is found, that call is chosen as the Preempted party. This may include the chair, the current speaker, the chair for a different conference or the speaker from a different conference.

A priority call is made to a Meet Me conference where MAS reached Resource maximum and no lower Priority call exists.

The Priority call receives the To allow for a priority call to BPA announcement. enter the conference, a search for a lower priority party is made, and fails. The calling party will receive the

Avaya Media Application Server Fundamentals

August 20, 2010

65

MAS application features

Scenario

Result

Synopsis BPA announcement. The original INVITE receives the reason, Blocked Precedence.

Table 6: Ad Hoc call scenarios Scenario

66

Result

Synopsis

Priority call A calls party B. A, B and C are joined in an Party A then calls party C and Ad Hoc conference. connects party B and Party C using the Join button.

The priority level of party A will be assigned to B and the priority level of party B will be assigned to C. Party A, Party B and Party C become the same priority level, matching the priority of Party A.

Priority call A calls party B, who in turn calls party Z. Party A will join the conference at resource maximum. All parties have the same precedence level.

Party A will join the Conference but when B attempts to join in the conference, it returns to one on one communication with Z.

To allow for a priority call to enter the conference, a search for a lower priority party is made, and fails. All parties are brought in with priority 3 therefore the last party Z has no one to preempt. B and Z do not join the Ad Hoc conference but remain in communication with each other.

Priority call A calls party B. Party B calls and joins up to Conference resource maximum. Party B calls party Z.

Party B will join Conference maximum parties but when parties B and Z join in the conference, another party in the conference drops.

To allow for a priority call to enter the conference, a search for a lower priority party is made. All parties are brought in with priority 3. When B adds Z at priority 4, a party at priority 3 is removed. This may include the chair or current speaker party. The preempted party receives preemption tones.

Priority call A calls party B. Party B calls and joins the conference with only one empty spot remaining but resource maximum is reached. Party B calls party Z.

Party B joins Conference maximum parties but when parties B and Z join in the conference, another party in the MAS drops.

To allow for a priority call to enter the conference, a search for a lower priority party is made All parties are brought in with priority 3. When B adds Z at priority 3, a party at priority 1 or 2 is removed from another Ad Hoc session. The preempted

Avaya Media Application Server Fundamentals

August 20, 2010

Multilevel Precedence and Preemption

Scenario

Result

Synopsis party receives preemption tones.

Priority call A calls party B. Party B calls and joins the conference with one empty spot remaining, but Resource maximum is reached. Party B calls party Z.

Party B will join in up Conference maximum parties but when B/Z joins in the conference, another party in the MAS drops.

Avaya Media Application Server Fundamentals

To allow for a priority call to enter the conference, a search for a lower priority party is made. All parties are brought in with priority 3. When B adds Z at priority 4, a party at priority 3 is removed either in this Ad Hoc session or another. The preempted party receives preemption tones.

August 20, 2010

67

MAS application features

68

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 12: MAS security The Avaya Media Application Server (MAS) has several external communication interfaces that must be secured. This is done through Information Assurance (IA) operations that protect and defend information by ensuring the following: • availability: reliability, level of data importance, timely delivery • integrity: data cannot be created, changed, or deleted without appropriate authorization • authentication: ensuring users or objects are genuine • confidentiality: information or processes accessed by only users who have been authorized • nonrepudiation: the act of disclaiming responsibility for a message Navigation • Differentiated Services Code Point marking on page 69 • Public Key Infrastructure on page 70 • File system integrity on page 70 • Certificate validation on page 70 • Login banner on page 71 • Password policy on page 72 • User roles on page 72 • Linux user accounts on page 73 • Security logs on page 74 • MAS ports on page 75 • Management access control and VLAN on page 76

Differentiated Services Code Point marking IP Packet headers can contain Differentiated Service Code Point (DSCP) marking that allow network routers and border controllers to filter and prioritize IP Packet transmission based on their DSCP values. DSCP values can be configured for all traffic classes.

Avaya Media Application Server Fundamentals

August 20, 2010

69

MAS security

The following transaction types have a configurable value within the range 0-63: • signaling • media flows • OAMP/Cluster transactions

Public Key Infrastructure MAS integration with the Public Key Infrastructure (PKI) is enhanced to meet the IA requirements. These requirements include • support for the Online Certificate Status Protocol (OCSP) • validation of key usage certificate extensions • communication with PKI using HTTP and HTTPS protocols • security logging enhancements

File system integrity For security reasons, you can use the following two tools to monitor the MAS file system: • Fcheck: provides the ability to create a snapshot/baseline of file checksums of various directories on the system • Audit daemon: provides the security daemon feature for Red Hat Linux. If you configure a DoD deployment, you are required to use the audit daemon. The system stores audit logs in /var/log/audit. You must configure these tools to cover MAS files and folders.

Certificate validation During the establishment of a TLS connection, certificates are exchanged and validated by the endpoints. Validation also requires that the certificate revocation status is checked.

70

Avaya Media Application Server Fundamentals

August 20, 2010

Login banner

Two methods for certificate validation exist: • Certificate Revocation List (CRL): The CRL is a list of certificates that have been revoked by a Certificate Authority (CA). The CA publishes this list regularly, and the list can be manually or automatically retrieved. MAS supports manual CRL retrieval. • Online Certificate Status Protocol (OCSP): An online query protocol provides a realtime certificate revocation status. This method eliminates the window of opportunity introduced by CRL publishing time frames. An OCSP Responder stores the list of revoked certificates for the CA. The OCSP responses are encrypted and signed to prevent tampering with the query results.

Certificate verification policy MAS uses the following rules during the certificate verification process: • Check for a manually configured CRL. The verification process ends if the CRL has not expired. • If the OCSP Responder is in the certificate and OCSP is enabled in the MAS security configuration, perform the OCSP query. The verification process ends when a response is received.

Certificate extensions Certificate extensions are additional attributes in an X.509v3 certificate. An extension can be marked as either critical or noncritical. All included critical extensions must be validated. Any unrecognized critical extensions are rejected and result in certificate verification failure. MAS validates all extensions included in the certificate regardless of criticality. The new extensions which the PKI currently marks as critical are: • Key Usage: Indicates the purpose for which the CA intended the key to be used. The application must ensure certificate use is consistent with the key usage indicated. • Basic Constraints: Indicates whether it is a CA or end-entity certificate. For an intermediate certificate, the CA component of the extension must be present and configured to true. If the extension is not present, then the certificate is considered an end-entity certificate and cannot be used to verify certificate signatures.

Login banner The Linux server platform supports the display of warning banners before log in (pre-login banner) and after log in (post-login banner) when accessing the server command line. Both

Avaya Media Application Server Fundamentals

August 20, 2010

71

MAS security

banners are optional and contain default values after the system is installed. After installation, the customer can modify these files. The default pre-login and post-login text is "Authorized users only. All activity may be monitored and reported." The server backup procedure backs up the pre-login and post-login banners, in case the customer has customized them. If a system restore is required, the server restore procedure restores the banners. The MAS Element Manager (EM) also contains a login banner. The banner can contain a message up to 2500 characters long.

Password policy Each server manages password complexity and if any value is manually changed on one server, it must also be manually changed on all other servers to keep them in synchronized. No automatic password complexity synchronization exists between servers. For Linux user passwords, MAS uses the existing SIP core policy implementation with no special customizations or requirements. MAS EM ensures that all user passwords comply with the following policies: • cannot contain User Account Name or the User Name Description • cannot contain, repeat, or reverse the associated user id • passwords cannot contain three of the same characters used consecutively • password reuse • minimum length • minimum number of lowercase characters • minimum number of uppercase characters • minimum number of digits • minimum number of special characters • minimum password age • maximum password age

User roles When a user is added to the system, the administrator assigns the user to one or more of the following roles. The user can perform the functions associated with that role. Access rights to

72

Avaya Media Application Server Fundamentals

August 20, 2010

Linux user accounts

the local file system are based upon the assigned user role. The user roles apply to Linux as well as EM user accounts, however these accounts are independent of each other. The following user roles are defined for the MAS: • System Security Administrator: equivalent to a System Administrator with additional security responsibilities which include: - maintain the operating system configuration - maintain the hardware and network configuration - maintain the security configuration, including IPsec and IPTables configuration - perform backup and restore of all elements on the system including any MAS application-specific data - perform user management such as add, delete, modify users - perform certificate management. • Security Auditor: manages the security log files, and can read security logs and back them up to a remote server • Application Administrator: can install, configure, and administer the MAS platform and packaged application software. These administrators cannot access Security logs or policy settings. • Backup Administrator: responsible for performing system backups. This role allows a user to strictly perform backups without being able to do anything else on the server. Important: The MAS does not include a Database Administrator role, because MySQL is embedded into the platform software and not directly accessible by administrators.

Linux user accounts MAS supports the ability to have preconfigured or individual Linux user accounts. Preconfigured accounts are configured during installation. • Individual Linux user accounts: allow for full accountability and monitoring of individual actions. If this option is chosen during server installation, the customer must create the individual user accounts after installation is complete. • Linux preconfigured user accounts: each preconfigured account has its own password that is processed by the password complexity profile. These accounts are shared, there is no action accountability at the individual user level for these accounts.

Avaya Media Application Server Fundamentals

August 20, 2010

73

MAS security

Security logs The ability to track what occurs on a system and by who, greatly increases the ability to analyze a system if a security breach occurs. Security logs contain minimum information such as User id, Timestamp, Local Server Address, Remote Host Address, and Description of Security Event. MAS supports the following categories of security logs: • Linux audit logs • Quantum security logs • EM security logs

Linux audit logs Linux servers use the audit daemon kernel module. This module starts automatically on server boot up and is always running. Audit daemon tracks all system events such as logons, file access, file handling and network access.

Quantum security logs The Quantum Security logs are accessible by only SSA or SA user roles and are generated for the following events: • change in security policy • change in certificate configuration • successful login attempt • failed login attempt • logout or session termination • session or user timeout • security logs archived • security logs cleared • unauthorized attempts to access system security resources • changes made in a user’s security profile and attributes

74

Avaya Media Application Server Fundamentals

August 20, 2010

EM security logs

• changes made in access rights associated with resources • changes made in system security configuration • disabling a user

EM security logs The EM Security logs are accessible by only SSA or SA user roles and are generated for the following events: • software stop or start • system operational state change (lock, pending-lock, unlock) • configuration data change • backup or restore maintenance operation

MAS ports All Avaya Media Application Server ports have a hidden signature to provide basic protection against rogue clients. The MAS terminates any attempt to connect to any MAS ports by rogue clients without the proper signature before any malicious activity takes place. Before taking any action, MAS services validate all command-type messaging that clients send. If validation fails, the MAS discards the command. The MAS encrypts all IM Chat messages using shared secret key encryption. To successfully connect to a MAS service, the AS 5300 Session Manager must first authenticate and register a user with the AS 5300 Session Manager. No additional authentication takes place directly between a client and a MAS service. The Avaya Media Application Server (MAS) services offer the security protection provided by the Linux operating system. You can configure the port range used by the Avaya Media Application Server software. However, by default, the services use port 5060/5061 for SIP messaging and 53500-beyond (in increments of four for each participant media type) for RTP/ RTCP/SRTP. Table 7: MAS IP ports Application

Use

Port

SIP

session signaling

5060 UDP and TCP 5061 TLS

RTP/RTCP SRTP

media channels

53500-beyond (in groups of four for each media flow)

Avaya Media Application Server Fundamentals

August 20, 2010

75

MAS security

Application

Use

Port

Terminal Services

remote console

3389 TCP

Multimedia conductor

platform connectivity

4004 TCP

IVR media processor

platform connectivity

4001 TCP

External Session API (ESA) platform connectivity

4005 TCP

Conference media processor

platform connectivity

7080 TCP

Multimedia content store

platform connectivity

52005 TCP

Stream Source

music streaming

19999 TCP

RTFT

transfer protocol

52007 TCP

Web Collaboration and Application Sharing

HTTP/S signaling

80/443 TCP

During or after installation, you can configure the AS 5300 Session Manager from which the Avaya Media Application Server accepts SIP INVITEs.

Management access control and VLAN Administrative access to the Linux platform is through the SSH client. Administrative access to the MAS is through HTTPS using the EM administrative user accounts. These clients allow for separate virtual channels. The system restricts management access control to a limited number of authorized IP addresses. The number of IP addresses must be equal to or less than the number of network administrators. Administrators require a valid user account and password to access the MAS. The system uses a timeout feature, set to 15 minutes, to disconnect idle connections. If the system detects three consecutive failed logon attempts for a user account, it removes availability for the account for 15 minutes. The system uses a virtual local area network (VLAN) to separate SSH client and EM administrative user accounts from other traffic. The system creates a virtual adapter for each VLAN you add.

76

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 13: Installation This chapter explains Avaya Media Application Server installation fundamentals. For step-by-step information about how to install the MAS platform, see 102.1.5 AS5300 x3550 M2 Installation and 102.1.6 AS5300 MAS Platform and Application Installation. Navigation • System requirements on page 77 • Installation overview on page 77 • Installation work flow on page 78 • Installation configurations on page 80 • Uninstall overview on page 80

System requirements You can install the MAS platform software on Commercial off-the-shelf (COTS) servers or blades. You can use a Platform Vendor Independence (PVI) to confirm if your platform will work with MAS. The system requires Gigabit Ethernet (GbE) (recommended) or 100 MB full-duplex network connectivity. For new systems, RHEL v5.4 provides a number of additional IPv6 compliancy capabilities for use by MAS. These new systems require AudioCodes and Integrated Access Devices (IAD) release version 5.8.

Installation overview The following are high-level procedures you need to complete to install Avaya Media Application Server (MAS). • Perform the following MAS pre-installation steps: - Record the network configuration. - Verify the MAS package contents.

Avaya Media Application Server Fundamentals

August 20, 2010

77

Installation

- Download the latest Avaya documentation to the administrative computer. • Install the selected hardware. • Install the MAS platform software. You can install the MAS platform software using any of the following methods: - silent console mode: no user interaction is involved - interactive console mode: installation is completed through console command lines using SSH Install the selected MAS packaged application software. For more information about MAS pre-installation and installation procedures, see 102.1.5 AS5300 x3550 M2 Installation and 102.1.6 AS5300 MAS Platform and Application Installation.

Installation work flow The installation of the Avaya Media Application Server follows a linear process. The only variations are based on whether or not you use Avaya hardware. If you use non-Avaya hardware, use the Platform Vendor Independent (PVI) installation procedures.

78

Avaya Media Application Server Fundamentals

August 20, 2010

Installation work flow

Figure 10: Installation work flow

Avaya Media Application Server Fundamentals

August 20, 2010

79

Installation

Installation configurations Installation can be made in standalone or cluster configurations. Once installed, you can configure servers as primary, secondary, and standard. • primary: This server hosts the content store and licensing. • secondary: This server acts as a backup for the primary server. • standard: These servers provide improved performance and scalability for the system. The MAS system uses a multiprocess, multithreaded architecture that takes advantage of multiple processor core and hardware platforms. The server achieves scalability across multiple computers by replicating the entire system.

Standalone You can deploy MAS in a standalone configuration where it has no external dependencies and all network related resources are configured on a single MAS node. A standalone configuration includes only a primary server to configure. No secondary or standard servers require configuration.

Uninstall overview You can uninstall the MAS platform software so that your configuration data is either removed or left intact. The configuration data should be removed if you want a clean install of MAS. Otherwise, the configuration data can be left intact.

80

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 14: Administration This chapter explains Avaya Media Application Server Administration fundamentals. For step-by-step information about MAS platform Administration, see Avaya Media Application Server Administration and Security, NN44474-600. Navigation • Element Manager overview on page 81 • Element status and operational controls on page 93 • Cluster configuration and status monitoring controls on page 94 • License management on page 95 • Signaling configuration on page 97 • Media configuration on page 97 • Monitoring and logging global configuration support on page 100 • Application management on page 104 • Reporting on page 105 • Backup and restore on page 105 • Media management on page 107 • Advanced settings on page 108 • Disaster recovery on page 108

Element Manager overview This section explains Element Manager (EM) fundamentals. For step-by-step information about EM, see Avaya Media Application Server Commissioning, NN44474-301 and the Element Manager help. EM is a Web-based administration tool used to facilitate operation, administration, and maintenance (OAM) for the MAS applications, servers, and cluster. The EM provides the following functions: • provisioning of nodal license keys for each MAS based on the MAC addresses of the server • view/modify configuration parameters for the MAS platform and packaged applications

Avaya Media Application Server Fundamentals

August 20, 2010

81

Administration

• backup/restore of system and service data • monitoring of alarms, logs, and active sessions • performance monitoring and operational measurements • software state management and control • media management

Navigating Element Manager The EM layout includes a branding banner, task selection pane, breadcrumbs area, and a content area as illustrated in the following figure.

Figure 11: Element Manager interface

Management activities are performed in the content area of the page. The displayed content is dependent on the selected top-level framework or system element context and the task selection within this context. The welcome page appears first after logon. It contains a welcome message, the versions of MAS installed, and a message to assist the administrator to begin. The top of the content area includes the hostname and management IP address of the component being managed. Element Manager divides properties into categories, to which you can navigate from the menu pane. Each category appears on a separate page. Categories are

82

Avaya Media Application Server Fundamentals

August 20, 2010

Element Manager overview

further divided into subcategories, which appear as sections on the category page. You can jump to a section within the page with the shortcut links at the top of the configuration table. The branding banner area contains the image of the Avaya logo. In addition to indicating what application you are in (for example, EM), the branding banner provides a context sensitive Help link and a Logout link. Click the Help link to open context sensitive help in a new browser. The Logout link logs you off of EM and returns you to the Login page. You can perform task selection and element navigation using the three following elements on the EM screen: • menu pane • Network navigation • breadcrumbs These three components are central to the work flows that the administrator performs for routine OAM activities. You can initiate work flows from the menu pane. The menu pane displays a menu of tasks that the administrator can perform in the content area. With the exception of the network tasks, the scope of OAM activities the administrator can perform is limited to the current element to which the administrator is logged on to. To facilitate the management of multiple elements in the network, You can view elements in the network with the network navigator component and navigate to them individually to perform OAM tasks. Finally, the administrator can find the information about the element currently being managed and the task currently being performed with the ability to navigate “up” the hierarchy of management screens in the breadcrumb area.

Interface features Initiate all tasks from the menu pane on the left side of the screen. The items listed in the menu pane are grouped into two sections. The top section of the menu pane contains a link to network-wide services that can affect the operation of all network elements or network-wide entities such as Network, User Services, Security, and Tools. The lower section contains tasks related to the operation, administration, and maintenance of the network element to which the administrator is logged on. The element-level section is further divided into task groupings. The highest-level groupings include System Status, Cluster Configuration, System Configuration, Products and Applications, Licensing, and Tools. Each task group contains a set of related tasks. Tasks that an administrator must perform for MAS platform and packaged application administration, operations, and maintenance appear in the lower section of the menu pane. These are grouped into six categories: • System Status: The administrator can view current and historical information pertaining to the status of the system with system status tasks. These tasks include element status, cluster status, alarm viewing, event log viewing, and monitoring. The monitoring task includes active session monitoring, performance, operational measurements, and

Avaya Media Application Server Fundamentals

August 20, 2010

83

Administration

protocol monitoring. The component status and advanced protocols are advanced functionality therefore; they are categorized as advanced monitoring tasks. • Cluster Configuration: The administrator can access the server designation and replication settings. • System Configuration: The administrator can view and modify the MAS platform configuration. Configuration categories include server profiles, network settings, signaling protocols, media processing, application interpreters, monitoring settings, session detail records, logging settings, debug tracing, engineering parameters, element manager settings, SIP/TDM gateway, routing and CTI, external host, and e-mail. • Licensing: The administrator can configure the nodal license keys and the nodal license utilization threshold. • Tools: The administrator can view what software and versions of the software are installed using the software inventory tool, perform a backup of system and customer data with the back up and restore tool, generate reports of archived OMs using the reports tool, manage media files using the media management tool, view session detail records using the session detail records browser, and view logs using the log capture tool.

Basic interface operation You can expand categories or higher-level tasks to reveal subtasks in the menu pane by clicking on the expansion point that appears to the left of the category or task label. If an item contains subitems, a plus (+) symbol appears before it. Click the + to expand the item, displaying its contents below it. Click the minus (-) symbol before the label to collapse expanded items. The expansion state of subtasks is maintained when their parent is collapsed. For items that contain no subitems, the expansion point appears as a minus symbol. Click the item label in the menu pane to select and launch the following associated task in the content area: • Task Category: If the category is collapsed, then it will expand after you click it. An information screen for the task is displayed in the content area. This screen shows a highlevel description of the category of tasks and a brief description for each task in the category. Task names appear as hyperlinks. Clicking the task name launches the task, and is equivalent to selecting the task from the menu pane. • Task: The task is launched in the content area. You can start a task in a new browser window by using the right-click menu of the Web browser. You should right-click on the task to be performed and choose the option to open the page in a new window. A new browser window appears with a banner area, menu pane, and task selected in the content area. You can scroll each section of the menu pane independently. Vertical scroll bars appear in a section when its contents cannot be displayed without vertical clipping. Horizontal scroll bars can also appear when the contents of the menu pane sections cannot be displayed without

84

Avaya Media Application Server Fundamentals

August 20, 2010

Element Manager overview

horizontal clipping. You can use the vertical line separating the menu pane and the content and breadcrumb areas to resize the menu pane horizontally. Some configuration items are designed to enable or disable certain features on the page. When a feature is disabled by the administrator, any configuration settings relevant to that feature appear grayed out on the screen. Use Save to save the changes to the platform. No changes are made to the platform configuration until you click Save. Before the configuration is stored in the MAS database, the administrator input is validated. If any errors are detected during validation, the configuration is not saved, and the page is redisplayed with error messages. The administrator needs to correct these errors and click Save to save the changes. After the changes have been saved, the administrator returns to the parent of the current page, which is often the previous page. If you decide not to save the changes made to the configuration, click Cancel to cancel any changes to be made to the configuration. A click of the cancel button returns you to the parent of the current page (usually the previous screen) without saving any changes to the configuration. Restore Defaults is used to restore every configuration parameter on the screen to its default value. After a click of Restore Default, every field displays its default value. Click Save to save the default values to the platform. If any error is detected on the page, an error message is displayed, describing the problem in general. Text describing the error in detail (if applicable) appears to the right or below the fields in question in red. The administrator must correct the errors before resaving the page. Invalid data is never saved.

Central authentication, authorization, and auditing The MAS system incorporates central authentication, authorization, and auditing. Authentication is the process through which the Unified Communications Management (UCM) determines if a user can gain access to the elements in your MAS system. Central authentication eliminates the need to have user IDs and passwords for each product or server. Instead, you can log on to the UCM security framework using a single user ID and password (also known as single sign-on) to gain access to any application or server for which the administrator has permissions. Authorization (also known as access control) is the process of determining and enforcing assigned privileges for an authenticated user. To provide central authorization, UCM uses the Role Based Access Control (RBAC) model. With this model, users see only what you authorize them to see based on their assigned roles and permissions. Auditing is the process by which UCM methodically measures the security of the MAS system. To provide central auditing, UCM uses audit logging features. The UCM framework logging feature records user activity, usage patterns, and authorization violations. The logs collect information such as denials, approvals, and code exceptions. Only security administrators can view log information on the Logs page in UCM.

Avaya Media Application Server Fundamentals

August 20, 2010

85

Administration

UCM security server roles You must configure each UCM security server in a UCM network to the Primary role. Important: UCM server roles are different from the roles used in MAS clustering. Each UCM network must have one Primary security server. The designated UCM Primary security server stores all administrator identities, authorization data, and security configuration data. The system must contact and query the Primary security server for all authentication, authorization, audit logging, and certificate management.

RBAC concepts The Unified Communications Management (UCM) security framework uses the Role Based Access Control (RBAC) model to determine a user's authorization. In this model, each user is identified through a unique identity, and each identity can have one or more user accounts for different elements. To configure access rights for user accounts, the security administrator assigns permissions to roles, and then assigns these roles to users. The following figure is an example of the MAS RBAC model.

86

Avaya Media Application Server Fundamentals

August 20, 2010

Element Manager overview

Figure 12: Example of the MAS RBAC model

Identities In the MAS RBAC model, security administrators must assign a unique digital identity to each user in a company. This identity contains a user's credentials and authorization rights. All identities are stored in security services, and this information is used by servers or products on the network.

Avaya Media Application Server Fundamentals

August 20, 2010

87

Administration

Each identity can have different user accounts for different managed elements. Security administrators can manage these identities to create, read, update, or delete user accounts. You can manage identities on the Administrative Users page in UCM. To navigate to the Administrative Users page, click User Services, Administrative Users in the navigation pane.

Accounts The UCM security framework supports the following types of user accounts: • local account • built-in account • emergency account • external account

Built-in accounts UCM has one built-in account that security administrators must use to log on to the system after installation. This built-in account is called nortelmasadmin, and it has the following builtin roles: • NetworkAdministrator • PowerUser • SecurityAdministrator Important: With the built-in admin account, security administrators can add, delete, and edit managed elements; however, they cannot directly access the management applications of the managed elements. Avaya recommends that security administrators create new accounts and assign roles to those accounts for access to the managed elements based on their specific security policy requirements. Security administrators can also use the built-in account as an emergency account. For more information about emergency accounts, see Emergency accounts on page 88.

Emergency accounts The default emergency account is the account you use when you log on to the EM for the first time before you configure security (UCM). You also use emergency accounts to access Element Manager (EM) on a local system if the primary security server is down or cannot be reached. To create a custom emergency account, you use the emUser tool, which is installed by the MAS platform installer.

88

Avaya Media Application Server Fundamentals

August 20, 2010

Element Manager overview

For information about creating emergency accounts, see Avaya Media Application Server Administration and Security, NN44474-600.

Local accounts You can set up local accounts for administrators who are authenticated locally in Unified Communications Management (UCM). To set up a local account, you must create a local user identity and password. The UCM security framework stores data entry and password information for a local user account in persistent storage. You can manage local user identities on the Administrative Users page in UCM. To navigate to the Administrative Users page, click User Services, Administrative Users in the navigation pane.

External accounts You can set up external accounts to allow Unified Communications Management (UCM) to authenticate administrators with external authentication. A MAS performs external authentication through Lightweight Directory Access Protocol (LDAP), Remote Authentication Dial In User Service (RADIUS), or Kerberos. Administrators can configure only one external authentication authority of each type (that is, LDAP, RADIUS, and Kerberos). You can configure external accounts in UCM on the External Identity Repositories page. To navigate to the External Identity Repositories page, click User Services, External Authentication. An external user has a shadow entry inside the persistent repository of the UCM security framework. The security framework uses the shadow entry to assign roles to the external user. Important: The security administrator role is not available for external LDAP users. Users cannot initialize or change passwords for external users through UCM. The external authentication authorities store the external account passwords.

Permissions Permissions specify which management functions a user can perform on an element. Security administrators assign permissions to roles, and then assign these roles to users. You can map permissions to a role on the Roles page in UCM. To navigate to the Roles page, click Security, Roles in the navigation pane. For information about mapping permissions, see Avaya Media Application Server Administration and Security, NN44474-600.

Avaya Media Application Server Fundamentals

August 20, 2010

89

Administration

Roles Roles define a set of management functions a user can perform on an element. Security administrators assign roles to users. You can map roles to users on the Roles page in UCM. To navigate to the Roles page, click Security, Roles. The MAS publishes a set of default roles into Unified Communications Management (UCM). You can assign default roles to administrators, or you can create custom roles. For information about assigning roles or creating custom roles, see Avaya Media Application Server Administration and Security, NN44474-600.

Policies In the UCM security framework, users can configure policies for passwords, security, and the sign sign-on cookie domain. You can configure policies on the Policies page in UCM. To navigate to the Policies page, click Security, Policies.

Password aging policy The security administrator can specify the number of days for the following password aging parameters: • password expiration period • password expiration warning • minimum password age

Password history policy UCM uses the password history policy to verify that a password is new. The security administrator can define the number of previously used passwords to reject. The default value of passwords to block is 6.

Password strength policy Security administrators can configure the password strength policy to define specific parameters for passwords. If a password does not meet the required parameters, the system rejects the password. Security administrators can specify if the password must contain a specific number of lower case, upper case, numeric, or special characters. An example of a special character is an exclamation mark (!). Passwords must have a minimum of eight alphanumeric characters.

90

Avaya Media Application Server Fundamentals

August 20, 2010

Element Manager overview

Password lockout policy The password lockout policy allows you to specify the following: • a limit for the number of times that a user can attempt to access UCM • the number of minutes between consecutive invalid logon attempts • the number of minutes to lock out users after they reach the maximum number of failed logon attempts A user is locked out of the UCM framework when the specified number of logon attempts is reached. By default, the user is locked out after 5 failed attempts.

MAS login warning banner Security administrators can change the text for the login warning banner that appears when you log on to Unified Communications Management (UCM).

Single sign-on cookie domain When the primary security servers are configured in different domains, users can change the single sign-on (SSO) cookie domain to ensure that the domains match. You must match the primary and backup SSO cookie domains to ensure that you can log on to one application or server on the MAS, and then navigate to another application or server and remain authenticated.

Limit access control views In the RBAC model, a user's role determines their permissions and the tasks available to them. By default, Element Manager (EM) hides or grays out unauthorized tasks in the menu pane and content area.

Certificates Unified Communications Management (UCM) uses certificates for secure communication between a Web browser and a Web server. Certificates are used for the following: • Web interfacing using Secure Sockets Layer (SSL) • Session Initiation Protocol (SIP) signaling using Transport Layer Security (TLS)

Avaya Media Application Server Fundamentals

August 20, 2010

91

Administration

UCM manages certificates using the X.509 standard for Web SSL, which ensures that certificates are issued by a Certificate Authority (CA) that binds a public key to a particular distinguished name. You can manage certificates on the Certificate Management page in UCM. To navigate to the Certificate Management page, click Security, Certificates in the navigation pane. The UCM certificate management interface supports the following: • add, replace, and list stored certificates • add, remove, and replace certificate association with a distinguish name • add, remove, and list trusted certificate authorities • display of a list of currently revoked certificates

Certificate authorities A Certificate Authority (CA) is a trusted entity that issues, renews, and revokes certificates. You can use UCM to install certificates from both its private CA or public CAs. The UCM security framework uses only one private CA to sign internally generated certificates. Once UCM generates the private CA, you cannot change it. Therefore, during installation you must enter configuration information for the private CA on the primary security server. For more information, see Avaya Method of Procedure (MOP) documentation. A public CA is either an existing internal CA of the customer organization (for example, the CA from the customer’s Information Technology [IT] department) or an outside commercial CA (for example, Verisign or Thawte).

Certificate types UCM certificate management supports three types of certificates: • certificates signed by the private CA hosted on the UCM primary security server: The MAS creates a private CA during the installation of the UCM primary security server. You can use the private CA to issue certificates to remote devices in the same security domain. When the UCM primary security server issues a certificate and distributes it to a remote device, the remote device automatically adds the root certificate of the private CA to its trusted certificate list. As a result, devices that use certificates issued by the same private CA always trust each other. • certificates signed by a public CA: You can use the UCM X.509 Certificate Management page to generate a Certificate Signing Request (CSR) from a target device, and then send the CSR to a public CA to obtain a certificate response, which contains an X.509 certificate. You can use the UCM Certificate Management page to process the certificate response returned from a public CA, and thereby, distribute the X.509 certificate to the target device. To access the Certificate Management page, click Security, Certificates. • self-signed certificates: A CA does not issue a self-signed certificate; self-signed certificates issue themselves. This type of certificate does not provide any authentication,

92

Avaya Media Application Server Fundamentals

August 20, 2010

Element status and operational controls

and is vulnerable to a man-in-the-middle attack. Avaya recommends that you avoid using self-signed certificates.

SIP TLS When UCM distributes the SIP TLS certificates that are signed by the private CA to the Network Routing Service or SIP Gateway, the private CA is automatically added to the trusted CA list of the Network Routing Service or SIP Gateway. Therefore, if all the Network Routing Service and SIP Gateway elements use certificates signed by the private CA, UCM automatically configures mutual authentication for SIP TLS among them.

Web SSL During the primary security service installation, the private CA issues a Web SSL certificate that is installed as part of the primary security service. Use the Web SSL certificate for the UCM Web server and the LDAP server. The security administrator must configure the Web SSL certificate for the primary security server by using the UCM Certificates link.

Certificate revocation lists A certificate revocation list (CRL) is a list of certificates that are revoked and should not be trusted. You can use the MAS system to revoke certificates that you issued previously, to get a list of revoked certificates, and to update the CRL. You can manage CRLs on the Certificate Management page by clicking the Private Certificate Authority tab and navigating to the Certificate Revocation List (CRL) Details pane.

Element status and operational controls The Element Status page is available from the System Status menu in EM. It shows the following information about the element: • element name • UUID • server address • service status • operational state

Avaya Media Application Server Fundamentals

August 20, 2010

93

Administration

• element status • alarm description

Element Status The Element Status shows the most severe alarm reported for the selected element. For example, an element with Critical and Minor active alarms has an overall status of Critical. An element with no alarms has a status of Normal. Click an element name to view alarm details for the selected element.

Starting, stopping and restarting Use the Start, Stop, and Restart buttons to change the Service Status of the Avaya Media Application Server respectively.

Operational states Use the More Actions drop-down to change the operational state of the element to one of the following: • More Actions • Lock • Pending Lock

Cluster configuration and status monitoring controls A cluster is a collection of MAS nodes that work closely together and essentially can be viewed as one. You must configure the hierarchy within the cluster before you can configure the system. This activity should be done shortly after installation.

94

Avaya Media Application Server Fundamentals

August 20, 2010

License management

Cluster configuration In Server Designation, you define your primary server and all secondary servers. The local server starts with the Primary role by default. When defining your servers, you must provide the following information: • replication account user name and password • role (primary, secondary, or standard) • server address • server UUID From the Replication Settings page you can enable or disable the SDR, OM and Configuration Replications. Advanced Settings are automatically configured based on your Server Designations. You should not change these settings.

Cluster status The Cluster Status page is available from the System Status menu in EM. It shows the following information about all elements in the cluster: • element name • UUID • element role information • most severe alarm status • description for an existing alarm, if any

License management You can use the Licensing section of Element Manager to configure licensing information. The following list items describe the relevant task areas within the licensing section, each with its own subset of tasks: • Licensing Configuration: Use this section to add or replace nodal license keys. • License Utilization Threshold: Use this section to set the threshold for license usage, which is expressed as a percentage of all licenses in use. Once this threshold is reached, a notification alarm is generated. The default threshold value is 85%.

Avaya Media Application Server Fundamentals

August 20, 2010

95

Administration

Server licensing In server licensing mode, a cluster shares licenses that float across all its MAS nodes. To set up server licensing, you must use a Redundant License Servers cluster licensing configuration. In this configuration, you install license servers on the two MAS nodes in the cluster designated as the cluster primary and secondary nodes. Cluster primary and secondary license servers operate in the three following states: • Starting up: During the license server startup process, the license server is in startingup state, and it does not respond to any license requests. • Active: The server that is serving license requests is in the active state. • Standby: The idle server is in the standby state. Each license server broadcasts a message to its local subnet to detect its redundant partner. It correspondingly sets itself to the active, or standby state, depending on the state of the other server. If both servers are in starting up state, the one with the larger IP address becomes active and the other becomes standby. The larger IP address is defined to be the larger of the two integers representing the Internet standard dot notation addresses. When a server is in the active state, it responds to license requests from clients and expects health check messages from the standby server. It also broadcasts a message every 80 seconds to detect if there is any other active server is in the subnet. When a server is in standby state, it does not respond to license requests. It opens a TCP/ IP connection to the active server and sends out health check messages periodically. If the active server goes down, the standby server switches to the active state until the previously active server is restarted and becomes active. During the license server startup process, the license server is in the starting-up state, and it does not respond to any license requests. After initialization, the license server changes to the standalone state and starts to serve license requests. You can view the license server state information on the License Server Status page in Element Manager. To navigate to the License Server Status page, click Licensing, License Server Status in the navigation pane.

Nodal licensing In Nodal licensing mode, licenses are bound to a particular MAS platform and are not shared across MAS nodes. In this node-locked configuration, you must configure each MAS node with its own license key. For example, if your MAS cluster contains five MAS platforms, you need five different licenses keys. Without a valid license key, you can install the MAS platform and packaged applications; however, the system rejects incoming sessions.

96

Avaya Media Application Server Fundamentals

August 20, 2010

Signaling configuration

Signaling configuration You can configure the SIP settings from the Signaling Protocols pages.

SIP configuration You can configure the following from the SIP settings pages: • General Settings • Domains and Accounts • Nodes and Routes

Media configuration This section outlines the media configuration support of the MAS.

Quality of Service MAS supports Differentiated Services (DiffServ) packet marking on outgoing Real-Time Transport Protocol (RTP) streams. The system sets the DiffServ Control Point (DSCP) to expedited forwarding (EF), which is a widely supported indicator for Quality of Service (QoS)enabled networks carrying real-time audio and video data. Network routers that are QoSenabled examine the type of service bits in the IP header and provide priority (with respect to routing and handling) to those packets marked with expedited forwarding. In addition to marking packets, MAS uses high resolution, interrupt-driven timers to drive RTP packetization at precise intervals. MAS follows RFC2598, which designates the EF bit pattern. MAS uses flow specifications for each codec to identify packet delivery characteristics to the operating system, enabling it to prioritize (internally) packets destined to and from the network interface card (NIC). The framework ensures that QoS marked packets sent from MAS media processors are not dropped or delayed in their delivery to the wire. MAS can reserve a percentage of NIC bandwidth for its media processors. This ensures that management and signaling does not affect the quality of the audio or video streams in use on the platform. The use of flow specifications also offers some denial of service protection as the transport layers discard packets (instead of attempting to process them) that do not conform to the flow specification. MAS contains the Telchemy VQMON agent for QoS monitoring and RTCP-XR support. RFactor, jitter, and packet loss are continually monitored for each call. Calls that fall below a

Avaya Media Application Server Fundamentals

August 20, 2010

97

Administration

configured R-Factor threshold are logged. All QoS statistics are archived with session detail records (SDR) for analysis. To configure QoS monitoring and streaming settings, use the System Configuration, Media, General Settings page in Element Manager.

Audio codecs To configure audio codec settings, use the System Configuration, Media, Audio Codecs page in Element Manager. You can complete the following configuration tasks for audio codecs: • enable or disable audio codecs. The following audio codecs are supported: - G.711 Mu-Law - G.711 A-Law - G.729a - EVRC-0 - AMR • configure the preferred order of enabled codecs for negotiation (Session Description Protocol [SDP] answer) or default SDP (SDP offer). • enable packet time (ptime) for each codec • configure the default ptime for each codec • configure transmission characteristics EVRC-0 and AMR codecs

Video codecs To configure video codec settings, use the System Configuration, Media, Video Codecs page in Element Manager. You can configure the following video codec settings: • enable or disable video codecs. The following video codecs are supported: - H.263 - H.263+ - H.263++ - NNVC (Nortel Networks Video Codec) Important: H.263 uses the Video Fast Update (VFU) capability to allow clients to ask for IntraFrames on the fly, improving the ability to perform video switching. H.263 uses a SIP INFO message to carry the VFU request, so use of H.263 imposes additional SIP

98

Avaya Media Application Server Fundamentals

August 20, 2010

Media configuration

traffic on the system, in the amount of one SIP message in and out of the MAS per video switch operation. • configure the preferred order of enabled codecs for negotiation (SDP answer) or default SDP (SDP offer) • enable frame rates for each codec • configure the default frame rate for each codec • configure the preferred format for each codec • configure the Annex profile for each codec (if required)

Digit relay (DTMF) To configure digit relay, use the System Configuration, Media, Digit Relay (DTMF) page in Element Manager. You can configure the following digit relay properties: • enable or disable the dual-tone multi-frequency (DTMF) relay method. The following DTMF relay methods are supported: - INFO digits - RFC2833/4733 • configure the preferred order of enabled DTMF relay methods for negotiation (SDP answer) or default SDP (SDP offer). • configure the RFC2833 payload type. Avaya recommends that you select the default payload type, which is determined dynamically. However, some clients require a fixed payload type.

Media security To configure media security settings, use the System Configuration, Media, Media Security page in Element Manager. Secure SIP signaling is provided by employing SIP Transport Layer Security (TLS), which is supported by the Radvision stack. In addition, the MAS manages a list of trusted network elements and rejects (redirect to network proxy) any signaling requests from nontrusted nodes. Media security provides the ability for the MAS to secure media streams with cryptographic protection based on RFC3711 (The Secure Real-Time Transport Protocol [SRTP]). SRTP is an RTP (RFC3550) profile with symmetrical data encryption that provides the following security services: encryption, message integrity, and replay protection. Secure RTCP (SRTCP) provides the same security services to RTCP as SRTP does to RTP. SRTP message authentication protects the RTCP fields that keep track of membership, provide feedback to

Avaya Media Application Server Fundamentals

August 20, 2010

99

Administration

RTP sends, or maintain packet sequence counters. M5T SRTP stack is used to deliver the media security feature. SRTP/SRTCP uses a master key and a master salt to derive a session encryption key, session authentication key, and a session salt key for media encryption. The master keys are exchanged and negotiated through Session Description Protocol (SDP) with key management protocol extension. Several key management protocol extensions are defined for SRTP. RFC4568 (Session Description Protocol Security Descriptions for Media Streams) is supported in this release.

Hysteresis To configure hysteresis, use the Advanced Settings, Media Processing page in Element Manager. You can configure the video hysteresis for each server. You can override the default value for the video switching hysteresis for a conference server by configuring the Video switching hysteresis parameter with a custom value. You specify this value in milliseconds (ms). Take care when setting custom values for Video switching hysteresis, as inappropriate settings can create an unpleasant user experience. For example, too small a value may lead to the video switching too often, as the video switching becomes more sensitive to background noise. Likewise, too large a value may lead to a noticeable lag in switching to a new active speaker's video.

Monitoring and logging global configuration support This section outlines the monitoring and logging global configuration support of the MAS.

Monitoring This section outlines the monitoring global configuration support for the MAS.

Event logs An event log is a historical view of events that occurred on the system. Event logs have the following severity levels: • Alert • Critical • Major

100

Avaya Media Application Server Fundamentals

August 20, 2010

Monitoring and logging global configuration support

• Minor • Emergency • Error • Warning • Info • Debug • Indeterminate • Notice You can enable and configure Event log throttling for an event so that only the most recent event log and contents are buffered. The most recent log is generated when the Throttle Check Interval property is exceeded along with an instance count for that event. Log throttling prevents the event logs from being flooded with recurring events. Events logs are sent to the local Linux server. However, you can optionally configure event logs to be delivered as SNMP traps and be delivered to SysLog destinations. The system automatically archives and rotates the logs as needed. To view event logs in Element Manager, choose System Status, Event Logs. You can filter event logs by identifier, date, severity, and class. The following table describes the fields that are displayed for each event log. Table 8: Event log fields Field

Description

Id

Identifier assigned to the event log.

Severity

The severity type of the event log (alert, critical, major, minor, emergency, error, warning, info, debug, indeterminate, and notice). In addition, a colored icon represents the log severity type. Red indicates an error event log, yellow indicates a warning event log, and white indicates informational event log.

Date and Time

The timestamp of when the event is logged. The date and time when the event is last reported. By default, the table is sorted so the most recent event appears at the top of the table.

Class

The class of the event. Available classes include Audit, Configuration, Data, Fault, Information, Maintenance, Metrics, Security, and State.

Description

A description of the event log. To view further details about the event log, click the option button beside the applicable event ID. The details appear in the bottom portion of the page.

Avaya Media Application Server Fundamentals

August 20, 2010

101

Administration

Operational measurements The MAS supports the following types of operational measurements: • counters, which record and monitor activity on the system and increase incrementally. They notify the administrator of incremental states, such as the total number of failed transfers or the total number of successful incoming instant messages. A counter can increment in chunks of any size. Counters reset automatically after a component restarts. • gauges, which provide real-time information about the system and can incrementally increase or decrease. Administrators look to gauges for the current status of measurements that can fluctuate, such as the number of active calls or the number of active IVR connections. You can view counters and gauges through the Element Manager. Selected operational measurements are archived to the local platform archive database and are stored in the Statistics table. Archived operational measurements are typically processed or analyzed later using the historical reports in Reporter. Archived operational measurements can be replicated to the primary and secondary node in a cluster so that operational measurements can be consolidated for cluster-wide historical reports. Operational measurements written to the Statistics table can be viewed in Element Manager (System Status, Monitoring, Operational Measurements), and the following table shows how information is displayed. Table 9: Selected operational measurements details Field name

102

Description

Category

Category or type of operational measurement.

Name

Operational measurement counter or gauge name.

Current Value

Current value of the operational measurement.

Previous Value

Value recorded during last interval.

Previous Interval Low Water Mark

Low value recorded during last interval.

Previous Interval High Water Mark

High value recorded during last interval.

Interval Value

Value of interval time.

Previous Interval Duration (s)

Interval duration. The default is 900 s. (15 minutes).

Avaya Media Application Server Fundamentals

August 20, 2010

Monitoring and logging global configuration support

Logging This section outlines the logging global configuration support for the MAS.

System diagnostics You can place the system in diagnostic mode for logging by selecting the Enable System Diagnostic Mode check box on the System Configuration, Logging page in Element Manager. Important: Enabling the system diagnostic mode can cause system performance degradation.

SysLog SysLog is a standard for forwarding log messages in an IP network. The MAS platform optionally supports SysLog over User Datagram Protocol (UDP) for the delivery of logs and alarm history to one or more SysLog server destinations. To enable or disable SysLog delivery, use the SYSLOG Delivery of Logs property (on the System Configuration, Logging page in Element Manager). To configure one or more SysLog server destinations, use the SYSLOG Destination Server List property (on the System Configuration, Logging page in Element Manager). You can enter the IP address of the SysLog server.

Session logging Configure the following SDR properties under the System Configuration, Logging section of Element Manager: • Session Detail Record Archiving: This check box enables or disables the archiving of session detail records. The default is enabled. • Session Detail Record Archive Minimum Record Age (Days): Session detail records older than configured days are removed when cleanup is initiated. The default is 90 days. • Session Detail Record Archive: The maximum number of session detail records before cleanup is initiated. The default is 1500 MB. Approximately 5k of storage is required for each SDR. The MAS creates a Session Detail Record (SDR) for each individual session that originates from or terminates to the platform. An SDR includes detailed information about each session, which you can use for tracking and billing purposes. The platform archives all SDR to the local platform database. These archived records are used by the platform to generate reports. The platform ensures that the archive does not grow too large by deleting old records based on the configuration. You can view records in either real-

Avaya Media Application Server Fundamentals

August 20, 2010

103

Administration

time or in historical reports. Archived SDRs can be replicated to the primary and secondary node in a cluster so that SDRs can be consolidated for cluster-wide historical reports.

Operational measurements logs The platform archives selected operational measurements to the local platform database. The platform uses these archived operational measurements to generate reports. The platform ensures that the archive does not grow too large by deleting old records based on the configuration. Configure the following operational measurements properties under the System Configuration, Logging, OMs section of Element Manager: • Archive Operational Measurements: This check box enables or disables the archiving of operational measurements. The default is enabled. • Operational Measurement Archive Minimum Record Age: Operational Measurements older than the configured number of days are removed when cleanup is initiated. • Operational Measurement Archive Cleanup Threshold Size: The amount of archived operational measurements data to store before cleanup is initiated. • Operational Measurement Reset Interval: The interval in minutes when operational measurements are archived and reset. A value of 0 disables the reset feature. The default is every 15 minutes.

Debug logging You can find the following settings related to debug logging in the System Configuration, Logging, Debug section of Element Manager. You can enable or disable Platform debug logging using Element Manager; a restart of the platform is not required. The system stores Debug logs in the directory \common \logs, where is the directory in which the system installs software. The default directory is D:\Program Files\Nortel\Multimedia_Applications. The system also creates trace files for each platform component.

Application management Packaged applications can be deployed on the MAS using an installer.

104

Avaya Media Application Server Fundamentals

August 20, 2010

Reporting

Packaged applications A packaged application is installed using its own installer. The installer may add application configuration data and translations to the MAS. As part of the installation process you need to configure license keys for all packaged applications. Packaged applications can only be installed after the MAS platform has been installed and configured. Use the EM to view information about the installed packaged applications (version and operational state) and configure various parameters of the application. Packaged applications are found under Applications, Packaged Applications.

Reporting To configure reporting settings, use the Tools, Reports page in Element Manager. MAS includes a report generation framework and third-party reporting framework based on Jasper reports.

Backup and restore It is important to back up your data to ensure that you can restore your original data if it is lost. You can perform backup and restore tasks on the Backup and Restore page in Element Manager (EM). To navigate to the Backup and Restore page, click Tools, Backup and Restore. This page includes the following task categories: • General settings • Backup Tasks • Restore • Backup Destinations • History Log For more information about backing up and restoring MAS data, see 103.2.7 AS5300 MAS Backup And Restore.

Avaya Media Application Server Fundamentals

August 20, 2010

105

Administration

General settings When you backup or restore your data, all actions are logged in a log file. You can set the value of "Store history and log files up to" parameter to define the duration for store history. The log file refreshes after the defined duration, that is, after this duration, the history will not be stored in the log file.

Backup tasks To back up your data, you must first define a backup task and then specify a schedule. A backup task specifies what to back up and where to store the backup data. You can manage backup tasks on the Backup Tasks page in Element Manager. To navigate to the Backup Tasks page, click Tools, Backup and Restore, Backup Tasks. On the Backup Tasks page, you can add a new backup task, and edit or delete an existing backup task. After you create a backup task, you must specify a backup schedule. You can run backup tasks manually or schedule the backup tasks to run immediately, once, daily, weekly, or monthly. You can also use the Backup Tasks page to schedule multiple tasks. Each task runs at the next specified start time. The Backup Tasks page shows you when the next scheduled backup is supposed to occur, as well as details about the schedule frequency and the backup destination.

Restore You can choose the backup source that you want to restore on the Restore page in Element Manager (EM). To navigate to the Restore page, click Tools, Backup and Restore, Restore in the navigation pane. The backup source can be the following: • the default backup destination, which is the local folder on the MAS Server where backups are stored • an uploaded backup file, which is located either on your computer or in a folder on the network The Restore page shows details about the backup, such as the name of the task, the type of backup, and the date when the back up last occurred. Important: Note that the restore process may take a while, during which time EM is offline and closes the connection to all users until the process is complete. It is the administrator’s responsibility to inform users when the system is back up and running. During the restore, the system cannot take calls. If a restore is completed without errors, the backup file is deleted; otherwise, the backup file remains on the server.

106

Avaya Media Application Server Fundamentals

August 20, 2010

Media management

Backup destination The Backup Destination specifies the location of the backup file.

History logs The backup/restore history log shows the status of backup or restore tasks and assists you in resolving errors. You can view the history log on the History Log page in Element Manager (EM). To navigate to the History Log page, click Tools, Backup and Restore, History Log. The history log shows the task name, type, and status; the time when the task is performed; the time to complete the task; and the size of the backup data. On the History Log page, you can export the log file in HTML format to a local folder of your choice. To customize the history log, you can do the following: • Use the View list to filter your tasks. The options are show all tasks, backup tasks only, or restore tasks only. The default is all tasks. • Use the Refresh Interval list to select the refresh interval for the history log. The default value is set at 30 seconds. • Click a header link to sort the list in ascending or descending order.

Media management On the Media Management page, you can manage media files of many formats, including sound, video, .xml, plain text, or zipped files. To navigate to the Media Management page, log on to Element Manager (EM) and click Tools, Media Management in the navigation pane. You can perform the following actions on media files: • upload • rename • copy • move • search • download • delete

Avaya Media Application Server Fundamentals

August 20, 2010

107

Administration

In EM, you can organize media into content namespaces and content groups. Use content namespaces to divide media into logical containers. Use content groups to subdivide the media in a content namespace into logical groups. You can initially provision a content namespace by using one .zip file for the whole content namespace or by creating one content group at a time. After the media file is uploaded, EM displays it in a tree view. The root of the tree is the content namespace and individual content groups appear below it with + or - icons before their names. EM displays the namespace, and the content groups in the left pane, and the media files contained in the selected content group in the right pane. The media file list includes the file name, content type, and size of the file; the time initially created; the time last modified; and the version information. You can browse content namespaces and add, rename, or delete content groups.

Advanced settings Access the Advanced Settings page from Cluster Configuration, Advanced Settings. These values are automatically configured based on changes made on the Server Designation page.

Disaster recovery You can recover the primary server to restore critical operations if you experience a disaster situation. To ensure successful recovery, you must implement a disaster recovery plan when you configure a Avaya Media Application Server (MAS). To plan for disaster recovery, follow these best practices: • Designate the secondary server in a different location than the primary server to protect the secondary server from natural or user-induced disasters that affect the primary server. • Create an off-site location to protect the backup system from natural or user-induced disasters that affect the primary system. • Create a full backup task to ensure successful recovery of all data if a disaster situation occurs. • Define a daily backup schedule to ensure successful recovery of up-to-date data if there is a disaster situation. If you experience a disaster situation, you must restore the primary server to reestablish critical operations. This operation involves installing the MAS software on a primary MAS server. Then, you must restore the latest full backup. For more information about Disaster recovery procedures, see Avaya Media Application Server Troubleshooting and Fault Management, NN44474-700.

108

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 15: Commissioning This chapter explains Avaya Media Application Server commissioning fundamentals. For step-by-step information about how to commission the MAS platform, see Avaya Media Application Server Commissioning, NN44474-301. Navigation • Initial security configuration on page 109 • MAS configuration on page 109 • License configuration on page 111 • Network management protocol configuration on page 111 • Network configuration on page 113 • QoS monitoring and alerting configuration on page 114 • SIP configuration on page 114 • Media provisioning on page 116 • Packaged application configuration on page 116

Initial security configuration The MAS configures the initial login and emergency account details upon installation. This information is required for you to access your servers and complete the security configuration. Use your User ID and Password for your installed operating system to access Unified Communications Management (UCM) the first time. You are required to change these once you have accessed your Primary server.

MAS configuration You can configure the MAS as a standalone system or in cluster configuration. A standalone configuration includes only a primary server to configure. No secondary or standard servers require configuration.

Avaya Media Application Server Fundamentals

August 20, 2010

109

Commissioning

For a cluster configuration, you must configure a primary server, which hosts the content store and licensing. By default on the Server Designation page, the system always lists the Local Server (localhost) as the first server on the page and you cannot remove it. The role is set to Primary; however, the you can change the role of the local server.

Figure 13: MAS cluster configuration work flow

110

Avaya Media Application Server Fundamentals

August 20, 2010

License configuration

License configuration Configure your nodal licenses and set the nodal license utilization threshold.

Figure 14: License configuration procedures

Network management protocol configuration This section outlines the network management protocol configuration support of the MAS.

SNTP Add the IP address or hostname of the Simple Network Time Protocol (SNTP) server in the SNTP Source Server field in Element Manager. The SNTP Source Server is used to synchronize the clocks of all nodes in the cluster.

Avaya Media Application Server Fundamentals

August 20, 2010

111

Commissioning

SNMP The MAS platform provides Simple Network Management Protocol (SNMP), which is a network management standard widely used in TCP/IP networks. SNMP is used to manage information between network devices. SNMP uses SNMP network management clients (running anywhere in the network) to provide a method of managing network devices running SNMP agents. After the SNMP service is enabled on the MAS, the system can request logs and events for reporting and troubleshooting purposes. SNMP supports outgoing traps for logs and alarms to remote SNMP-based Network Management Stations (NMS). In addition, NMS can query alarm table and audit services. Traps use the Avaya Reliable MIB format to support active and cleared alarm notifications as well as informational log messages. In Element Manager (EM), you can configure SNMP on the System Configuration, Network Settings page to activate the delivery of alarms and logs using SNMP traps. You can enable or disable the sending of traps when the system raises or clears alarms, or when the system generates event logs. Enable the SNMP service for proper configuration of SNMP. If an SNMP Management server IP address and SNMP Community String are provisioned in the MAS EM, only traps generated by a Avaya Media Application Server service will be sent to the designated Management Server IP address. The MAS platform supports SNMP v2. SNMP uses community names to authenticate messages. The community name is similar to a password that is shared by the SNMP NMS and the MAS SNMP agent. The community name must be the same value on both the NMS and the MAS SNMP agent. The MAS SNMP agent supports queries on the ActiveAlarm table and audits for resynchronization with the management server. These queries are either Get requests on specific fields or GetNext requests for table traversal.

SOAP The Simple Object Access Protocol (SOAP) is used to exchange Extensible Markup Language (XML) messages over a network. The MAS platform provides a set of Web services, which can be used to manage, monitor, configure, or access a set of services or resources provided by the platform. The SOAP server acts as a mini-embedded Web server and exposes the following MAS Web services: application APIs, content store APIs, and Management APIs. You can access these Web services by using SOAP-formatted XML messages over HTTP 1.1 transport. To enable the MAS Web services, you must configure the trusted nodes that are allowed to send requests to the MAS Web services. In Element Manager, trusted nodes are configured on the System Configuration, Network Settings page. First, select the Enable Trusted SOAP

112

Avaya Media Application Server Fundamentals

August 20, 2010

Network configuration

Nodes check box and then enter one or more hostnames or IP addresses in the Trusted Nodes field. You must separate multiple entries in the Trust Nodes field with a semicolon.

Connection security To configure connection security in Element Manager, see the System Configuration, Network Settings page. You can configure the following properties: • Always Approve HTTPS Certificate • Enable TCP TLS Transport • TCP TLS Enable Cipher AES 128 SHA • TCP TLS Enable Cipher AES 256 SHA • TCP TLS Enable Cipher NULL SHA • TCP TLS Session Renegotiation Enable • TCP TLS Session Renegotiation Timer Important: You can enable and select multiple ciphers in order of strength.

Network configuration This section outlines the network configuration of the MAS.

IP address assignment and traffic classes You can assign the IP address for the available traffic classes in EM on the System Configuration, General Settings page. The traffic classes include: • signaling • IPv4 media • IPv6 media • cluster • OAM

Avaya Media Application Server Fundamentals

August 20, 2010

113

Commissioning

You can set MAS to work in IPv4-only mode by selecting None in the Media IPv6 list. You can also assign the preferred media setting (IPv6 or IPv4) in EM on the System Configuration, General Settings page. Select the Prefer IPv6 for Media check box to place IPv6 first in the SDP ANAT field of SIP messages. If you deselect the Prefer IPv6 for Media check box, then the system places IPv4 first in the SDP ANAT field of SIP messages. If the Media IPv6 list is set to None, the IPv6 Preferred check box is disabled.

QoS audio and video DSCP settings configuration Configure Quality of Service (QoS) settings for streaming in EM on the System Configuration, Media, General Settings page. Options include: • Audio QoS • QoS Maximum Bandwidth Per H.263 Video Flow • QoS Maximum Bandwidth Per NNVC Video Flow • Video QoS

QoS monitoring and alerting configuration Configure Quality of Service (QoS) settings for media on the System Configuration, Media, General Settings page. Options include: • Enable QoS monitoring • Alert interval in milliseconds • Critical R Threshold • Maximum Alerts • Refresh Interval in seconds • Warning R Threshold in percentages

SIP configuration SIP provides a standard means to establish sessions, negotiate capabilities, invoke applications, and exchange data with the MAS.

114

Avaya Media Application Server Fundamentals

August 20, 2010

SIP configuration

The following work flow shows the process for configuring your MAS SIP signaling.

Figure 15: SIP configuration work flow

Avaya Media Application Server Fundamentals

August 20, 2010

115

Commissioning

Media provisioning Media provisioning involves creating media content namespaces and media files for the MAS. The system uses these media files for Announcements and Music on Hold packaged applications. The following work flow shows the process for provisioning media files to the MAS.

Figure 16: Media provisioning tasks

Packaged application configuration You must configure any packaged applications you purchase for your deployment to ensure that users can access and use packaged applications according to business requirements. Not all the MAS packaged applications described in this book are applicable to all systems. The MAS supports different services, depending on your system configuration. For more

116

Avaya Media Application Server Fundamentals

August 20, 2010

Packaged application configuration

information about supported MAS packaged applications, see Avaya Media Application Server Planning and Engineering, NN44474-200.

Avaya Media Application Server Fundamentals

August 20, 2010

117

Commissioning

118

Avaya Media Application Server Fundamentals

August 20, 2010

Chapter 16: Terminology The following table describes common terminology associated with the Avaya Media Application Server (MAS) . Term

Description

3DES

Triple Data Encryption Standard.

AA

Application Administrator

Ad Hoc Conferencing

MAS service. Use Ad Hoc Conferencing to join together multiple participants in a multimedia conference call.

AES

Advanced Encryption Standard

AIN

Advanced Intelligent Network

AGC

automatic gain control

AIS

Alarm Indication Signal

ALI

Automatic location information (for 911 service)

AM

Accounting Manager

Announcements

MAS service. The Announcements application plays both cause and treatment, and branding recordings.

API

Application Programming Interface

ARP

Address Resolution Protocol

AS 5300 Session Manager

Avaya Aura™ Application Server 5300 component that handles SIP sessions and applications, and provides the core services that enable communication between SIP clients.

ASU

Automatic software upgrade

ATM

Asynchronous transfer mode

Avaya Aura™ AS 5300 UC Client

A standalone, SIP-enabled user agent that operates on a PC and provides telephone services, multimedia communications, communication management, and automatic software updates.

Avaya Aura™ AS 5300 Web Client

A lighter version of the Avaya Aura™ AS 5300 UC Client

Avaya Media Application Server Fundamentals

August 20, 2010

119

Terminology

Term

Description

AVP

Audio Video Profile

BA

Backup Administrator

Backup

A copy of data. The copy is preserved in case the system the data was copied from fails, is damaged, or changes to an undesired state.

BBUA

Back-to-Back User Agent

BCT

Blade Center Telecom

BIOS

Binary Input/Output System

BPA

Blocked Precedence Announcement

BPT

Bulk Provisioning Tool

CA

Certificate Authority

CAC

Carrier Access Code

CD

Compact Disc

CDMA

Code Division Multiple Access

Certificates

A security tool used to identify secure packages of data over a network

CFB

Call Forwarding Busy

CFD

Call Forwarding Default

CFNA

Call Forwarding No Answer

CFP

Call Forward Prefix

CFU

Call Forwarding Unconditional

CFW

call forward

CLI

Command Line Interface

Cluster

A collection of servers on the MAS

CNID

Calling Number Identification Delivery

CNIR

Calling Number Identification Restriction

CODEC

Coder Decoder. The CODEC is used for transmitting media files over a network.

COM

Component Object Model

Commercial-Off-The-Shelf

See COTS.

Conferencing

A means of including more than two people in an audio or video interaction.

ConfMP

Conference Media Processor

120

Avaya Media Application Server Fundamentals

August 20, 2010

Term

Description

COS

Class of Service

COTS

Commercial-Off-The-Shelf. Generic purchased hardware that can be used in a wide variety of installations.

Counters

A measurement tool to record the number of times an event occurs.

CPL

call processing language

CPU

Central Processing Unit

CRBT

Colorful Ringback Tones

CRL

Certificate Revocation List

CRM

customer records management

CS 1000

Communication Server 1000

CS 2000

Communication Server 2000

CSR

Certificate Signing Request

CStore

Content Store

CSV

comma-separated value

CTI

Computer telephony integration

CTP

Call Transfer Prefix

CUSTGRP

customer group name

CUSTID

customer identifier

DACD

dial access code

DBA

Database Administrator

DC

direct current

DHCP

dynamic host configuration protocol

Differentiated Services

See DiffServ.

DiffServ

Differentiated Services. A computer network architecture designed to manage and provide Quality of Service over a network.

DivX CODEC

video conferencing

DMS-100

Digital Multiplex System-100

DN

Directory Number; distinguished name

DND

Do Not Disturb

DNPIC

Directory Number Primary Inter-Exchange Carrier

Avaya Media Application Server Fundamentals

August 20, 2010

121

Terminology

Term

Description

DNS

domain name server

DoD

Department of Defense

DoS

Denial of Service

DP

Developer Program

DSCP

Differentiated Service Control Point

DSL

Digital Subscriber Line

DSP

digital signal processor

DSS

Data Source Server

DTGW

Direct to Gateway

DTMF

Dual-tone multi-frequency. A signaling technology used for signaling over a telephone network.

DTX

Discontinuous Transmission

Dual-tone multi-frequency

See DTMF.

Dual CLI

dual calling line ID

E911

Enhanced 911

EA

Equal Access

EBIP

enhanced breaker interface panel

EF

expedited forwarding

Element Manager

See EM.

EM

Element Manager. A Web-based tool used for configuring and managing MAS and its components.

ERC

Express Routing Code

ERL

emergency response location

ESA

External Session API

ESD

electronic software delivery; Electrostatic Discharge

ESM

Ethernet Switch Module

ESN

Electronic Switched Network

Event

An incident that is either recorded or causes other actions to occur.

EWSG

Embedded Web Services Gateway

Extensible Markup Language

See XML.

122

Avaya Media Application Server Fundamentals

August 20, 2010

Term

Description

FAC

Feature Activation Code

File Transfer Protocol

See FTP.

FIPS

Federal Information Processing Standards

FPM

Fault Performance Manager

FPS

frames per second

FQDN

Fully Qualified Domain Name

FSI

file system integrity

FTP

File Transfer Protocol. A network protocol used for transmitting files over a network.

Gauge

A tool for providing real-time information about the system.

GbE

Gigabit Ethernet

GbESM

Gigabit Ethernet Switching Module

Graphical User Interface

See GUI

GSTN

General Switched Telephone Network

GUI

Graphical User Interface. A visual interface used for interacting with a computer system.

H.263

CODEC Video Point-to-point

HD

Hard disk

HDLC

high-level data link control

HSC

hot swap controller

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol Secure

IAD

Integrated Access Device

ICM

Incoming Call Memory

IETF

Internet Engineering Task Force

IIS

Internet Information Services

IKE

Internet Key Exchange

IM

instant messaging

IM Chat

MAS service. The Chat application allows users to instant message to a chat room, consisting of a single window.

IMS

Internet Protocol Multimedia Subsystem

Avaya Media Application Server Fundamentals

August 20, 2010

123

Terminology

Term

Description

IN

Intelligent Network

INAP

International Network Application Protocol

Instant Message Chat

See IM Chat.

I/O

input/output

IP

Internet Protocol

IPCM

Internet Protocol Client Manager

IPDR

Internet Protocol Detail Record

IPMI

Intelligent Platform Management Interface

ISDN

Integrated Services Digital Network

ISM

Internet Service Manager

ISSG

Intelligent Network SIP Signaling Gateway

ISUP

Integrated Services Digital Network User Part

IVR

interactive voice response

IvrMP

interactive voice response Media Processor

JDBC

Java database connectivity

JNLP

Java Network Launching Protocol

JRE

Java Runtime Environment

JVM

Java Virtual Machine

KRS

Keycode Retrieval System

KVM

keyboard/video/mouse

LAN

local area network

LDAP .

Lightweight Directory Access Protocol. An application protocol for working with directory services over a network

License

An identification showing the number of users can be active for a piece of software.

Lightweight Directory Access Protocol

See LDAP.

LINEATTR

line attributes index

Logging

An action for recording actions in a log.

LOM

Lights-out Management

LTGRP

logical terminal group

LTID

logical terminal ID

124

Avaya Media Application Server Fundamentals

August 20, 2010

Term

Description

LTNUM

logical terminal number

MAC address

Media Access Control address

MADN

Multiple Appearance Directory Number

MAP

Mobile Application Part

MAS

Media Application Server. A software based, media processing server. All media processing is performed in software on the host CPUs. The MAS architecture facilitates unique scalability for all core functions of the platform, including signaling, application execution, content management and media processing.

MCP

Multimedia Communications Portfolio

MCS

Multimedia Communication System

MCT

Malicious Call Trace

Media Application Server

See MAS.

Meet Me Conferencing

MAS service. The Meet Me Conferencing application provides reservationless audio and video conferencing on the MAS platform. You can use Meet Me Conferencing for private conferencing at any time

MGCF

Media Gateway Control Function

MIB

management information base

MLPP

Multilevel Precedence and Preemption

MO

managed object

MOH

Music on Hold (MAS service). With this feature, MAS can play music while a caller is on hold.

MOP

method of procedure

MOTD

message of the day

MPCP

Media Portal Control Protocol

MR

Maintenance Release

MSAG

master street address guide

Music on Hold

See MOH.

MVNO

Mobile Virtual Network Operators

MWI

message waiting indicator/indication

NAPT

network address port translation/translator

Avaya Media Application Server Fundamentals

August 20, 2010

125

Terminology

Term

Description

NAT

network address translation/translator

NCL

Network Call Logs

NE

Network Element

NEBS

Network Equipment Building Standards

NED

network element daemon

NEI

network element instance

NGSS

Next Generation Session Server

NIC

network interface card; network interface controller

NML

Network Management Layer

NN

network number

NSD

Network Service Description

NTP

Network Time Protocol

OAM

Operation, Administration and Maintenance

OAM and P; OAM&P; OAMP

operations, administration, maintenance, and provisioning

OCM

origination call manager; originating call model

OCSP

Online Certificate Status Protocol

OEM

Oracle Enterprise Manager

OFCENG

Office Engineering

OM

operational measurement

OMA

Open Mobile Alliance

OMI

Open Management Interface

ONT

Online Network Terminal

OPI

Open Provisioning Interface

OS

Operating System

OSA

Open Security Architecture

OSN

on-site notification

OSS

operations support system

PA

Personal Agent

PAD

preferred audio device

PBX

private branch exchange

126

Avaya Media Application Server Fundamentals

August 20, 2010

Term

Description

PC

personal computer

PCM

pulse code modulation

PCMM

Packet Cable Multimedia

Permissions

A security tool that identifies what actions can be performed by a given role.

Personal Agent

An interface where users configure the services that they have been assigned. Specifically, this refers to the Avaya Aura™ Application Server 5300 Personal Agent.

Personal Ringback Tones

See PRBT.

PJM

Persistence Job Manager

PKCS

Public-Key Cryptography Standards

PKI

Public Key Infrastructure

Platform Vendor Independence

See PVI.

PM

performance measurement

PN

presentation number

PNG

portable network graphic

Policies

Security rules that govern the behavior and actions of a computer system. These rules tell the computer what actions to take in the case of certain events, independent of human intervention.

PPND

Public/Private Name and Number Display

PRACK

persistent acknowledge messages

PRBT

Personal Ringback Tones (MAS service). This application enables subscribers to select custom audio that the system plays to incoming callers instead of traditional ringback tones. Also known as Colorful Ringback Tones (CRBT).

PRI

primary rate interface

Provisioning Client

An interface that provides administrators access the Avaya Aura™ Application Server 5300 Provisioning Manager.

Provisioning Manager

A software component on the Avaya Aura™ Application Server 5300.

PSAP

Public Safety Access Point

PSI

Public Service Identifier

Avaya Media Application Server Fundamentals

August 20, 2010

127

Terminology

Term

Description

PSTN

public switched telephone network

PTimes

packet times

PVI

Platform Vendor Independence. A tool for determining if hardware or software is compatible with MAS.

QFE

Quick Fix Engineering. A tool for implementing small changes to MAS.

QoS

Quality of Service. A means of controlling priorities between applications for access to resources.

Quality of Service

See QoS.

Quick Fix Engineering .

See QFE

RADIUS

Remote Authentication Dial In User Service. A protocol for managing large networks.

RBAC

Role Based Access Control. A means of restricting access to a network or parts of a network based on assigned roles.

Real-Time Transport Protocol

See RTP.

Remote Authentication Dial In User Service

See RADIUS.

Restore

An action of copying backed up data to a system.

RFC

Request for Comment

RFCP .

Redirect For Calling Party

RoHS

Reduction of Hazard Substances

Role Based Access Control

See RBAC.

Roles

An identified role in a system that can be assigned permissions.

RPS

Regional Patching System Administrator

RRI

Remove Redirect Information

RSA

Rivest-Shamir-Adleman

RSS

Really Simple Syndication

RTCP

Real-Time Transport Control Protocol

RTF

Rich Text Format

RTP

Real-Time Transport Protocol. A protocol for transmitting audio and video over a network.

SA

System Administrator; Security Auditor

128

Avaya Media Application Server Fundamentals

August 20, 2010

Term

Description

SC

Service Consumer; Session Controller

SCA

selective call acceptance

SCP

Signaling Control Point

SCRJ

selective call rejection

SDP

Session Description Protocol. A protocol for describing initialization parameters of streamed media.

SDR

session detail record

SE

Service Element

Session Description Protocol

See SDP

Session Initiation Protocol

See SIP.

SFTP

SSH File Transfer Protocol

SHA

Secure Hash Algorithm

Simple Network Management Protocol

See SNMP.

Simple Object Access Protocol

See SOAP.

SimRing

Simultaneous Ring

SIP

Session Initiation Protocol. A protocol for creating and removing communication sessions over a network.

SIP-T

Session Initiation Protocol - Telephony

SM

System Management

SMDI

simple message desk interface

SMTP

Simple mail transfer protocol

SNMP

Simple Network Management Protocol. A protocol for monitoring devices attached to a network.

SNTP

Simple Network Time Protocol

SOAP

Simple Object Access Protocol. A protocol for transmitting and receiving XML messages over a network.

SOPI

Subscriber Open Provisioning Interface

SQL

structured query language

SRTCP

Secure Real-Time Transport Control Protocol

SRTP

Secure Real-Time Transport Protocol

SS

Service Session

Avaya Media Application Server Fundamentals

August 20, 2010

129

Terminology

Term

Description

SS7

Signaling System 7

SSA

System Security Administrator

SSH

Secure Shell

SSL

Secure Socket Layer

SSO

single sign-on

Standalone

An installation of a single server with MAS.

STD

format standard format

SUBGRP

subgroup number

TAT

Termination Attempt Trigger

TCM

terminating call model

TCP

Transmission Control Protocol

TCP/IP

Transmission Control Protocol/Internet Protocol

TDM

Time Division Multiplexing. A means of simultaneously transferring two or more signals or bit streams over one communication channel.

TFTP

Trivial File Transfer Protocol

TG

Transformation Gateway

Time Division Multiplexing

See TDM.

TLS

Transport Layer Security. A technology for providing secure communications over a network.

Transport Layer Security

See TLS.

TRKGRP

trunk group

TSAC

Terminal Services Advanced Client

TUI

Text-based User Interface

UA

User agent

UC

Unified Communications

UCM

Unified Communications Management or Unified Communications Manager. A framework for providing security when using Element Manager.

UCOMM

Unified Communications (MAS service). The Unified Communications application provides users with integrated access to their voice mail messages from a preferred client device, such as a PC, VoIP telephone, wireless telephone, or a traditional circuit switched telephone. Optionally,

130

Avaya Media Application Server Fundamentals

August 20, 2010

Term

Description users can set the system to e-mail voice messages to their e-mail client for playback.

UDP

Universal Datagram Protocol

UE

usage entry; usage event

UFTP

UNIStim File Transfer Protocol

UI

User Interface

UM

unified messaging

UMTS

Universal Mobile Telecommunication System/ Service

Unified Communications

See UCOMM.

Unified Communications Management

See UCM.

UNIStim

Unified Network Internet Protocol Stimulus Protocol

URI

Uniform Resource Identifier

URL

uniform resource locator

USB

universal serial bus

USP

Universal Signaling Point

UTC

Universal Time Coordinated

UUID

Universally Unique Identifier

VAD

Voice Activity Detection

VFU

Video Fast Update

VLAN

Virtual Local Area Network

VoD

Video on Demand

VoIP

Voice over Internet Protocol

VPD

Vital Product Data

VPN

virtual private network

VRDN

Virtual Router Distribution Node

VXML

Voice Extensible Markup Language

WAN

wide area network

WebDAV

Web Distributed Authoring and Versioning

Web service

A technology which supports interaction between computers on a network.

WSDL

Web service definition language

Avaya Media Application Server Fundamentals

August 20, 2010

131

Terminology

Term

Description

XLARTSEL

translation route selector

XML

EXtensible Markup Language. A specification for creating customizable mark up languages.

132

Avaya Media Application Server Fundamentals

August 20, 2010