Release Notes for Avaya Aura Communication Manager Messaging R6.3.100 VMware vappliance Software with SP5 (for CMM 6.03.0.141.0) Release Notes Issue 1, 10-August-2015 2011-2015 Avaya Inc. All rights reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya generally makes available to users of its products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on its hardware and Software ( Product(s) ). Refer to your sales agreement to establish the terms of the limited warranty. In addition, 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 website: http://www.avaya.com/support Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Software means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products or pre-installed on hardware products, and any upgrades, updates, bug fixes, or modified versions thereto. 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 ANAUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA R ESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERSTO 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 you a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. 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 you. 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. License type(s) 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. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or hardware provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Virtualization Each Product has its own ordering code. Note that each instance of a Product must be separately licensed and ordered. Instance means one unique copy of the Software. For example, if the end user customer or Business Partner would like to install 2 instances of the same type of Products, then 2 Products of that type must be ordered. Third-party components Third Party Components mean certain software programs or portions thereof included in the Software that may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). Information regarding distributed Linux OS source code (for those Products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the Documentation or on Avaya s website at: http://support.avaya.com/thirdpartylicense/. You agree to the Third Party Terms for any such Third Party Components. Note to Service Provider
The Product or Hosted Service may use Third Party Components subject to Third Party Terms that do not allow hosting and require a Service Provider to be independently licensed for such purpose. It is your responsibility to obtain such licensing. 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 Toll Fraud intervention If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: http://www.avaya.com/support. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation and Product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners, and Linux is a registered trademark of Linus Torvalds. Downloading documents For the most current versions of documentation, see the Avaya Support website: http://www.avaya.com/support Contact Avaya Support See the Avaya Support website: http://support.avaya.com for product notices and articles, or to report a problem with your Avaya product. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: http://support.avaya.com, scroll to the bottom of the page, and select Contact Avaya Support.
Table of Contents Release Notes for Communication Manager Messaging R6.3.100 VMware vappliance Software... 1 Table of Contents... 4 Release Notes... 1 Document History... 1 Deploying the Avaya Aura Communication Manager Messaging 6.3.100 software release... 1 New Installation... 1 Upgrades... 2 Software reference lists... 3 Hardware compatibility... 3 Interoperability and requirements... 3 Fixed issues... 4 Known issues and workarounds... 6
Release Notes These Release Notes support the deployment and documentation for Avaya Aura Communication Manager Messaging Federal Markets R6.3.100 Document History Issue Date Description 10-August- Issue 1 is the initial Release Notes to support the deployment of Release 6.3.100. 1 2015 Deploying the Avaya Aura Communication Manager Messaging 6.3.100 software release New Installation Installation of the Messaging 6.3.100 release software, from its associated templates or VMware OVA, is described in the Deploying Avaya Aura Communication Manager Messaging documents. In addition, installation will also require Service Packs per the software reference list provided below. For new installations, please refer to one of the following guides, depending on your configuration. Then complete the initial administration chapters in the Administering Avaya Aura Communication Manager Messaging guide. Deploying Avaya Aura Communication Manager Messaging using VMware in the Virtualized Environment Implementing Avaya Aura Communication Manager Messaging Please read the PCN s for each of the Service Packs to familiarize oneself with the nuances of each Service Pack since some might involve reboots and commit steps. Also wait until messaging is completely up after each install before proceeding with the next Service Pack install. 10-August-2015 Page 1
Upgrades To upgrade from earlier releases of Avaya Aura Communication Manager Messaging, please refer to one of the following guides, depending on your configuration: Deploying Communication Manager Messaging using VMware in the Virtualized Environment NOTE: Before beginning an upgrade, or any such installation or maintenance task, it is important to have a current backup of the system. NOTE: If the version of your currently installed Messaging software is not listed above, you will need to upgrade to one of the latest release versions listed above prior to upgrading or migrating to Avaya Aura Communication Manager Messaging 6.3.100. Upgrade Paths You can directly upgrade to Messaging 6.3.100 from the following Messaging releases: System Platform to VMware CMM 6.3 FP4 or later VMware to VMware CMM 6.3 FP4 or later NOTE: If the version of your currently installed Messaging software is not listed above, you will need to upgrade to one of the latest release versions listed above prior to upgrading or migrating to Avaya Aura Communication Manager Messaging 6.3.100. 10-August-2015 Page 2
Software reference lists Avaya Aura Communication Manager Messaging VMware Offer (Install in this order below!) VMware vsphere File Name PLDS File ID PCN / PSN ESXi 5.0, 5.1 or 5.5 Avaya Aura Communication Manager Messaging Avaya Aura Communication Manager Messaging 6.3.100 VMware vappliance OVA Avaya Aura Communication Manager 6.3 VMware Tools Service Pack 5 Avaya Aura Communication Manager 6.3 Kernel Service Pack 4 Avaya Aura Communication Manager 6.3 Security Service Pack 6 Avaya Aura Communication Manager 6.3.111 (Service Pack 111) Avaya Aura Communication Manager Messaging 6.3.100 Service Pack 5 (Load 141 Service Pack) (not applicable) File Name CMM-06.03.0.141.0-e51-2.ova CMM63000078 VMWT-2.6.18-400.AV2-5.5-005.tar CMM63000079 PCN 1923S KERNEL-2.6.18-400.AV2.tar CMM63000080 PCN 1922S PLAT-rhel5.3-3019.tar CMM63000072 PCN 1921S 03.0.141.0-22460.tar CMM63000082 PCN 1798S CMM-03.0.141.0-0505.tar CMM63000076 Hardware compatibility For hardware platform information, refer to the Deploying Communication Manager Messaging using VMware in the Virtualized Environment document. Interoperability and requirements See the Avaya Compatibility Matrix application for full Avaya product compatibility information. 10-August-2015 Page 3
Fixed issues in SP5 (for CMM 6.03.0.141.0) Notes: 1. SP5 is all inclusive of prior Service Packs SP1 to SP4. 2. This Service Pack cannot be installed with CMM 6.03.0.124.0. DESCRIPTION MSG-14550 MSG-18644 MSG-18773 MSG-18888 MSG-18915 MSG-19042 MSG-19147 MSG-19625 MSG-19802 MSG-19917 MSG-19073 MSG-20044 MSG-20062 MSG-20114 MSG-20200 MSG-20257 MSG-20366 SMI allows changing mailbox number to its secondary extension, which is invalid. Various Voice-Name audit issues, which need to be corrected during the audits. SMI auto-attendant: no error when editing automated attendant menu to transfer to an invalid variable length extension. AE_SYSERR when changing a primary and secondary extensions to the same value, which is not a valid error. IMAP Status does not correctly reflect number of currently running client sessions. imapd does not handle all IPv6 co-resident addresses correctly. mm audit mishandles valid audio formats. Eliminate Adata core due to invalid XML forwarding rules. Messages not forwarded due to incoming mailbox rules. ldap_full_upd status from MN is not handled properly. Ldap FEs shouldn't return empty umrecordedname attribute value. TUI: Subscriber Admin Menu: No option to: "Disable Message Delivery" unless Call- Answer-Disabled is also enabled If PIN is too small and the Minimum time between PIN changes is not yet passed, TUI forces a change of PIN, but Adata rejects change and TUI says "This call experiencing difficulties" Transfers Stop Working Every Few Days. Restart Messaging to Fix. Automatic Forwarding of outside Call Answer Messages uses an invalid 'Mail From' address. Eliminate SSL vulnerability for IMAP4, POP3 and LDAP. Removing networked machine, run network data audit to tombstone subscribers, and weekly audit to remove on AAM, subscribers removed on MN; also fixes removal of remote subscribers by other means. 10-August-2015 Page 4
MSG-20506 MSG-20524 MSG-20565 MSG-20739 MSG-20804 MSG-20850 MSG-20875 MSG-20917 MSG-21043 MSG-21094 MSG-21189 MSG-21356 MSG-21539 MSG-21620 Can not disable standard LDAP port. postfix can lose Certificate Chain File on postfix restart Outlook 2010: Address Book: searching for users only works using 'Advanced Find', Regular: 'Search' Fails with 'Unknown Error' Can not add an email address to an ELA list After shutting down abnormally, LDAP may come up in a corrupt state. SMTP Log Summary report only gives 4 dates to select from. From: address malformed on an auto-forwarded message from an ELA list. "Can't bind to Unix Socket: No such file or directory" error message on console during startup/shutdown Messaging setting incorrect SIP domain in P-AI header for MWI NOTIFY message Generated Mime versions of Priority Call Answer Messages do not have any Priority Headers. Imapd SSL_write() errors are handled incorrectly. Message Core fails to start when FIPS mode is enabled on JITC CMM-FM. TUI disconnects with "This Call Experiencing Difficulties". Restore fails due to multiple copies of the OcTime LDAP attribute. 10-August-2015 Page 5
Known issues and workarounds The following is a list of known issues with this release. Reference Number Issue Description Workaround 10-August-2015 Page 6