Avaya Multimedia Messaging Release

Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not 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. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's gents, 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 the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. 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 through the Avaya Support Website: http://www.avaya.com/support License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE http://support.avaya.com/licenseinfo/ ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s) Named User License (NU). Customer 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 Avaya Multimedia Messaging 3.2 Release Notes (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 Product that permits one user to interface with the Product. 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, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://support.avaya.com/thirdpartylicense/ 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 Trademarks Avaya, the Avaya logo, and COMPAS are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. 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 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 Support Web site: http://www.avaya.com/support Release Notes 2

Table of Contents Change History... 4 Introduction... 4 Installation... 5 Product compatibility... 5 Recommended Minimum Load Line-up Requirements for Avaya Core... 5 Product Release Matrix... 5 Fresh Install (AMM 3.2.0.0.372)... 5 Upgrade (AMM 3.0.0.1.180 to 3.2.0.0.372)... 5 What's new... 7 Release 3.2.0.0... 7 Release 3.0.0.1 (3.0 SP1)... 8 Release 3.0.0.0... 8 Fixes... 9 Release 3.2... 9 Known issues and workarounds... 11 Release 3.2... 11 Documentation... 12 Documentation errata... 12 Avaya Multimedia Messaging Reference Configuration Document... 12 VMWare deployment models... 13 Contacting support... 13 Contact Support Checklist... 13 Contact Support Tasks... 13 Appendix A: Acronyms... 14

Change History Date Description 9/22/2017 Add 3.2.0.1 7/14/2017 SVVM-7915 issue added to the Known Issues and Workaround section. 7/10/2017 July GA update for Avaya Multimedia Messaging Release 3.2. Introduction This document provides late-breaking information to supplement the Avaya Multimedia Messaging 3.2 software and documentation. For updated documentation, product support notices, and service pack information, go to the Avaya Support site at http://support.avaya.com. Please refer to the latest Avaya Aura 7.1 Release Notes for information specific to the Avaya Aura feature and service packs. Release Notes 4

Installation Note Starting this SP Aura 6.x is no longer supported Product compatibility For the latest and most accurate compatibility information go to: https://support.avaya.com/compatibilitymatrix/index.aspx. Recommended Minimum Load Line-up Requirements for Avaya Core The following releases are recommended for the best experience. For supported earlier releases consult the compatibility matrix referenced above Component Release Avaya Aura System Manager 7.0.1.2 Build 44 7.1.0.0 Build 1125193 Software Update Revision No: 7.1.0.0 Build 116662 Avaya Aura Session Manager 7.0.1.2 Build 701230 + patch 7.1.0.0 Build 710028 Avaya Aura Presence Server 7.0.1.0 Build 864 7.1.0.0 Build 600 Product Release Matrix The following table lists the release build numbers of the Avaya Equinox clients and required infrastructure servers. Client/Server Release Build Number Date Available Avaya Equinox for Windows 3.2.2.1 29 September 2017 Avaya Equinox for MacOS 3.2.2.4 29 September 2017 Avaya Equinox for Android 3.2.2.1 29 September 2017 Avaya Equinox for ios 3.2.2.4 15 September 2017 Avaya Multimedia Messaging 3.2.0.0 Build 381 29 September 2017 Avaya Aura Device Services 7.1.0.0 Build 374 29 September 2017 Avaya Aura Web Gateway 3.2.0.1 Build 1 21 August 2017 Fresh Install (AMM 3.2.0.1.381) Upgrade PS to the latest 7.1 load Deploy 3.2.0.0.372 OVA (note this is the 3.2 OVA, there is no 3.2 SP1 OVA) Run the 3.2.0.1.381 AMM binary Upgrade (AMM 3.2.0.0.372 to 3.2.0.1.381) Migrate PS to the latest 7.1 load Release Notes 5

Take backup Upgrade the AMM node(s) binary to 3.2.0.1.381 Upgrade (AMM 3.0.0.1.185 to 3.2.0.1.381) Migrate PS to the latest 7.1 load Take backup Upgrade the AMM node(s) binary to 3.2.0.1.381 Release Notes 6

What's new Avaya Multimedia Messaging provides a powerful tool to interact with other users over IM and efficiently handle multiple IM conversations with individuals or groups. Avaya Multimedia Messaging offers users more effective handling of IM between a user s desktop and mobile devices, support for more meaningful workflows for team messaging, and ability to quickly and easily record and send rich multimedia messages for more effective communications. The following lists the enhancements in Avaya Multimedia Messaging 3.2 and is cumulative since the last major release showing the most recent release first and oldest release last. Release 3.2.0.1 (3.2 SP1) Aura 6.x is no longer supported with the release of this service pack. Aura 7.x is required. Bug fixes SVVM-7969: If SMGR CA is sub-ca, then replication is not working for AADS connected with this SMGR SVVM-8062: AMM using chain certificate does not send chain to client Note to leverage SMGR sub-ca functionality, SMGR needs to be configured as a sub-ca and the AMM certificates need to regenerated Release 3.2.0.0 Presence Server 7.1 Federation Relay Microsoft Lync and Skype for Business federation now requires Presence Services Release 7.1.The Avaya Multimedia Messaging relay entity will no longer be used for IM and Presence message signaling. Read Receipt Support for Read Message and Read Attachment notifications on Avaya Multimedia Messaging clients. Note: Read Receipts are not supported for federated notifications on Avaya Multimedia Messaging. System Layer Commands The sys command line alias has been introduced to facilitate the discovery and use of system layer commands. New partitioning version 2.0 A new file system structure or partitioning scheme, called partitioning version 2.0, has been introduced to the OVAs for this release. The partitioning scheme created by OVAs from previous releases is called partitioning version 1.0. Both partitioning version 1.0 and 2.0 are supported in this release. Release Notes 7

Release 3.0.0.1 (3.0 SP1) Bug fixes SVVM-7373: cleanamm not working on 6 node cluster - cassandra errors causing node mastership to keep switching SVVM-7385: Backup operation failed with Build 3345 SVVM-7492: Zero participants in conversation with latest PS loads SVVM-7498: Considerable increase in writes to sdb partition during AMM traffic SVVM-7527: SIP subscription refresh not happening in lyncim resulting in possible roster updates to fail ACS-3997: DRS batches timeout in sync Release 3.0.0.0 Enhancements Increased scalability in a larger enterprise community (Up to 38K users across 6 nodes (Resilience deployment 5+1) Chat-state notifications ("istyping" indications) Event notifications on escalation to call AMM-AMM intra-enterprise federation (aka Multi-Custer federation) AMM federation with APS 7.0.1 AMM intra-enterprise federation with Lync 2010 / 2013 & Skype for Business 2015 AMM to Lync / Skype for Business inter-enterprise federation AMM federation can support AMM messaging with Avaya Presence Server (XMPP/HTTPS REST) IM users AMM messaging with Lync / Skype for Business IM users. Not supported in this release AMM user configuration with AMM messaging to both Avaya Presence Server and Lync users is not supported. AMM Multi-cluster federation with Avaya Presence Server and Lync / Skype for Business Release Notes 8

Fixes The following fixes are cumulative since the last major/minor release showing the most recent release first and oldest release. Release 3.2 ID Summary Found in Release Fixed in Release SVVM- 7295 Clients cannot retrieve media files after data restore. There is an issue with backup directories being created with invalid permissions causing back-ups to fail. 3.0.0 3.0.0.1 SVVM- 7373 Workaround: Manually create the backup directories and ensure permissions allow back-ups to be written (775). cleanamm not working on a six node cluster. Cassandra errors causing node mastership to keep switching. This occurs when trying to handle expired conversation when the number of conversations in the system is very high. This can be mitigated by enabling the "Configure Auto-Discard for Closed Conversation" option in the Storage Management section of the UI, and selecting a reasonable value for the number of days. This will prevent closed conversations from remaining in the system longer than they are needed. Such mitigation should be considered if the customer expects more than 500k conversations before upgrading to SP1. 3.0.0 3.0.0.1 SVVM- 7385 This issue will be addressed in SP1. Customers with large deployments are advised to wait for SP1 There is an issue with back-up directories being created with invalid permissions causing back-ups to fail. 3.0.0, 3.0.0.1 3.0.0.1 SVVM- 7397 Workaround: Manually create the backup directories and ensure permissions allow back-ups to be written (775). notify_master and notify_backup are not updated after build-to-build upgrade preventing alarms from being logged on the virtual IP switch over. 3.0.0, 3.0.0.1 3.0.0.1 Workaround: If you are upgrading from a previous version of AMM 3.0.0, you must run the configuration script on the _backup_ node for your virtual IP: /opt/avaya/multimediamessaging/3.0.0.0.3345/cas/3.0.0.0.3345/bin/configurea MM.sh Navigate to Cluster Configuration, open the Virtual IP configuration menu, and click Apply. Release Notes 9

SVVM- 7458 Click Apply again to restart the services. This will allow alarms to be raised and cleared on virtual IP switch over. This does not need to be run on the Virtual IP _master_ (though it is harmless to do so). This does not need to be executed or new installs, or installs migrated directly from a 2.1 version. AMM stopped working for users, and unable to login from the GUI. File system full 100%. 3.0.0.1 3.0.0.1 Release Notes 10

Known issues and workarounds Avaya Multimedia Messaging 3.2 Release Notes The following issues are cumulative since the last major/minor release showing the most recent release first and oldest release. Release 3.2 ID Summary Found in Release SVVM-7662 When running 'glusterinstall.sh <node1> <node2> <node3>' on node1 to create a 3-node 3.0.0.1 GlusterFS, node3 was successfully added (probe peer) but gluster on node1 hasn't picked up on it just yet. Creating cs_volume involving bricks from node3 fails. Workaround: > sudo rm -rf /media/data/content_store/brick* on each node. > Run glusterinstall.sh SVVM-7773 Until SMGR 7.1.1 (GA August 18th) is released two AMM alarms will appear as indeterminate on SMGR: 3.2.0 SVVM-7851 "OP_AMM-00094 - AMM Server Node Licenses Unavailable Alarm raised(major)" "OP_AMM-00096 AMM Server Node Licenses Threshold Reached(Minor)" If indeterminate alarms appear tor AMM, please investigate AMM server logs but not the issues above would not reflect dynamic service impacting issues. When running the binary installer, always set Configure Gluster to N in the Advanced Configuration menu. GlusterFS setup is performed at the tail end of a fresh install: 3.2.0 Run the binary installer on all nodes first. From one node, run glusterinstall to create the content store volume. To add a node to GlusterFS: Run the binary installer on the new node. From an existing node, run glusteradd to add the new node to the content store volume. Re-balance the volume as soon as practical. SVVM-7874 Please refer to the AMM deployment guide for details The documentation introduces the term 'signing authority certificate' that may cause confusion. This term is synonymous with Certificate Authority (CA). The use of a different term is not intended to imply any different functionality or usage. Release Notes 11 3.2.0

SVVM-7915 Avaya Multimedia Messaging is not able to communicate with Microsoft Lync or Skype for Business (S4B) systems that are federated to other Lync or S4B systems that AMM is directly federated with. Documentation For example: AMM <-> Lync/S4B SystemA <-> Lync/S4B SystemB AMM would not be able to communicate with SystemB. Presence Server Federation Relay would try to directly talk to SystemB and would not use SystemA as an intermediary. This issue will be addressed by PSNG-4194 scheduled for Avaya Aura Release 7.1.2. For Avaya Multimedia Messaging 3.2, the following documents have been updated on the support site: Guide Avaya Multimedia Messaging Reference Configuration Deploying Avaya Multimedia Messaging Administering Avaya Multimedia Messaging Links https://downloads.avaya.com/css/p8/documents/101041354 https://downloads.avaya.com/css/p8/documents/101041351 https://downloads.avaya.com/css/p8/documents/101041355 Documentation errata Avaya Multimedia Messaging Reference Configuration Document # Documentation errata 1 Virtual machine and physical server deployment specifications table should be updated to: Specification 500 users 1000 users 10,000 users vcpus (@ 2.9GHz) 8 8 32 Memory 8GB 8GB 32GB Storage reservation 0.5TB 1TB 5TB Release Notes 12

VMWare deployment models Avaya Multimedia Messaging 3.2 Release Notes Specification 500 users 1000 users 10,000 users vcpus (@ 2.9GHz) 8 8 32 Memory 8GB 8GB 32GB Storage reservation 0.5TB 1TB 5TB Contacting support Contact Support Checklist If you are having trouble with the Avaya Multimedia Messaging server, you should: 1. Set log level to debug. 2. Retry the action. Carefully follow the instructions in written or online documentation. 3. Check the documentation that came with your hardware for maintenance or hardware-related problems. 4. Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation available. If you continue to have a problem, contact Avaya Technical Support: 1. Log in to the Avaya Technical Support Web site https://support.avaya.com. 2. Contact Avaya Technical Support at one of the telephone numbers in the Support Directory listings on the Avaya support Web site. Avaya Global Services Escalation Management provides the means to escalate urgent service issues. For more information, see the Escalation Contacts listings on the Avaya Web site. Contact Support Tasks You may be asked to email one or more files to Technical Support for analysis of your application and its environment. Release Notes 13

Appendix A: Acronyms AAC AADS AMM ASBCE BLA CM FP MDA POM PS SM SMGR SP SRTP TOM TLS Avaya Aura Conferencing Avaya Aura Device Services Avaya Multimedia Messaging Avaya Session Border Controller for Enterprise Bridged Line Appearance Avaya Aura Communication Manager Feature Pack Multiple Device Access Presentation Only Mode Avaya Aura Presence Services Avaya Aura Session Manager Avaya Aura System Manager Service Pack Secure Real-Time Transport Protocol Top of Mind Transport Layer Security Release Notes 14