Upgrading Avaya Aura® Messaging for Single Server Systems
Release 6.3.2 Issue 1 December 2014 © 2014 Avaya Inc. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED All Rights Reserved. SERVICE. YOUR USE OF THE HOSTED SERVICE SHALL BE Notice LIMITED BY THE NUMBER AND TYPE OF LICENSES PURCHASED UNDER YOUR CONTRACT FOR THE HOSTED While reasonable efforts have been made to ensure that the SERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTED information in this document is complete and accurate at the time of SERVICES IF APPLICABLE, YOU MAY HAVE THE OPPORTUNITY printing, Avaya assumes no liability for any errors. Avaya reserves TO USE FLEX LICENSES, WHICH WILL BE INVOICED the right to make changes and corrections to the information in this ACCORDING TO ACTUAL USAGE ABOVE THE CONTRACT document without the obligation to notify any person or organization LICENSE LEVEL. CONTACT AVAYA OR AVAYA’S CHANNEL of such changes. PARTNER FOR MORE INFORMATION ABOUT THE LICENSES Documentation disclaimer FOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITY OF ANY FLEX LICENSES (IF APPLICABLE), PRICING AND “Documentation” means information published by Avaya in varying BILLING INFORMATION, AND OTHER IMPORTANT mediums which may include product information, operating INFORMATION REGARDING THE HOSTED SERVICE. instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. Licenses Documentation does not include marketing materials. Avaya shall not THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA be responsible for any modifications, additions, or deletions to the WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR original published version of documentation unless such SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE modifications, additions, or deletions were performed by Avaya. End APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR User agrees to indemnify and hold harmless Avaya, Avaya's agents, INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., servants and employees against all claims, lawsuits, demands and ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS judgments arising out of, or in connection with, subsequent APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH modifications, additions or deletions to this documentation, to the AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS extent made by End User. OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES Link disclaimer NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA Avaya is not responsible for the contents or reliability of any linked AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA websites referenced within this site or documentation provided by RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU Avaya. Avaya is not responsible for the accuracy of any information, AND ANYONE ELSE USING OR SELLING THE SOFTWARE statement or content provided on these sites and does not WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR necessarily endorse the products, services, or information described USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, or offered within them. Avaya does not guarantee that these links will YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM work all the time and has no control over the availability of the linked YOU ARE INSTALLING, DOWNLOADING OR USING THE pages. SOFTWARE (HEREINAFTER REFERRED TO Warranty INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING Avaya provides a limited warranty on Avaya hardware and software. CONTRACT BETWEEN YOU AND AVAYA INC. OR THE Refer to your sales agreement to establish the terms of the limited APPLICABLE AVAYA AFFILIATE (“AVAYA”). warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product while under warranty is Avaya grants You a license within the scope of the license types available to Avaya customers and other parties through the Avaya described below, with the exception of Heritage Nortel Software, for Support website: http://support.avaya.com or such successor site as which the scope of the license is detailed below. Where the order designated by Avaya. Please note that if You acquired the product(s) documentation does not expressly identify a license type, the from an authorized Avaya Channel Partner outside of the United applicable license will be a Designated System License. The States and Canada, the warranty is provided to You by said Avaya applicable number of licenses and units of capacity for which the Channel Partner and not by Avaya. license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other “Hosted Service” means a hosted service subscription that You materials available to You. “Software” means computer programs in acquire from either Avaya or an authorized Avaya Channel Partner object code, provided by Avaya or an Avaya Channel Partner, (as applicable) and which is described further in Hosted SAS or other whether as stand-alone products, pre-installed on hardware products, service description documentation regarding the applicable hosted and any upgrades, updates, patches, bug fixes, or modified versions service. If You purchase a Hosted Service subscription, the foregoing thereto. “Designated Processor” means a single stand-alone limited warranty may not apply but You may be entitled to support computing device. “Server” means a Designated Processor that services in connection with the Hosted Service as described further hosts a software application to be accessed by multiple users. in your service description documents for the applicable Hosted “Instance” means a single copy of the Software executing at a Service. Contact Avaya or Avaya Channel Partner (as applicable) for particular time: (i) on one physical machine; or (ii) on one deployed more information. software virtual machine (“VM”) or similar deployment. Hosted Service Licence types THE FOLLOWING APPLIES IF YOU PURCHASE A HOSTED Designated System(s) License (DS). End User may install and use SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA each copy or an Instance of the Software only on a number of CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE Designated Processors up to the number indicated in the order. FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA Avaya may require the Designated Processor(s) to be identified in WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO UNDER the order by type, serial number, feature key, Instance, location or THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH other specific designation, or to be provided by End User to Avaya SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE through electronic means established by Avaya specifically for this APPLICABLE TO ANYONE WHO ACCESSES OR USES THE purpose. HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON Concurrent User License (CU). End User may install and use the BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE Software on multiple Designated Processors or one or more Servers, DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY so long as only the licensed number of Units are accessing and using AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF the Software at any given time. A “Unit” means the unit on which YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A Avaya, at its sole discretion, bases the pricing of its licenses and can COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT be, without limitation, an agent, port or user, an e-mail or voice mail YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE account in the name of a person or corporate function (e.g., TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR webmaster or helpdesk), or a directory entry in the administrative IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server the Avaya Support website: http://support.avaya.com or such or an Instance of the Software. successor site as designated by Avaya. Suspected security vulnerabilities with Avaya products should be reported to Avaya by Named User License (NU). You may: (i) install and use the Software sending mail to: [email protected]. on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server Downloading Documentation so long as only authorized Named Users access and use the Software. “Named User”, means a user or device that has been For the most current versions of Documentation, see the Avaya expressly authorized by Avaya to access and use the Software. At Support website: http://support.avaya.com, or such successor site as Avaya’s sole discretion, a “Named User” may be, without limitation, designated by Avaya. designated by name, corporate function (e.g., webmaster or Contact Avaya Support 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 See the Avaya Support website: http://support.avaya.com for product utilized by the Software that permits one user to interface with the or Hosted Service notices and articles, or to report a problem with Software. your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: Shrinkwrap License (SR). You may install and use the Software in http://support.avaya.com (or such successor site as designated by accordance with the terms and conditions of the applicable license Avaya), scroll to the bottom of the page, and select Contact Avaya agreements, such as “shrinkwrap” or “clickthrough” license Support. accompanying or applicable to the Software (“Shrinkwrap License”). Trademarks Copyright The trademarks, logos and service marks (“Marks”) displayed in this Except where expressly stated otherwise, no use should be made of site, the Documentation, Hosted Service(s), and product(s) provided materials on this site, the Documentation, Software, Hosted Service, by Avaya are the registered or unregistered Marks of Avaya, its or hardware provided by Avaya. All content on this site, the affiliates, or other third parties. Users are not permitted to use such documentation, Hosted Service, and the product provided by Avaya Marks without prior written consent from Avaya or such third party including the selection, arrangement and design of the content is which may own the Mark. Nothing contained in this site, the owned either by Avaya or its licensors and is protected by copyright Documentation, Hosted Service(s) and product(s) should be and other intellectual property laws including the sui generis rights construed as granting, by implication, estoppel, or otherwise, any relating to the protection of databases. You may not modify, copy, license or right in and to the Marks without the express written reproduce, republish, upload, post, transmit or distribute in any way permission of Avaya or the applicable third party. any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, Avaya is a registered trademark of Avaya Inc. transmission, dissemination, storage, and or use without the express All non-Avaya trademarks are the property of their respective owners. written consent of Avaya can be a criminal, as well as a civil offense Linux® is the registered trademark of Linus Torvalds in the U.S. and under the applicable law. other countries. Virtualization Each product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered. Third Party Components “Third Party Components” mean certain software programs or portions thereof included in the Software or Hosted Service 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”). As required, 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 products, Documentation or on Avaya’s website at: http:// support.avaya.com/Copyright or such successor site as designated by Avaya. 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 Contents
Chapter 1: Introduction...... 7 Purpose...... 7 Intended audience...... 7 Document changes since last issue...... 7 Related resources...... 7 Documentation...... 7 Training...... 10 Viewing Avaya Mentor videos...... 10 Support...... 11 Chapter 2: Upgrade overview and considerations...... 12 Messaging upgrades...... 12 Preupgrade requirements...... 12 Preupgrade data gathering...... 15 Messaging templates overview...... 17 Messaging upgrade paths...... 17 Chapter 3: Pre-upgrade tasks...... 20 Prerequisites...... 20 Verifying the version of System Platform...... 21 Checking the RAID battery status...... 22 Viewing current alarms...... 22 Current Alarms field descriptions...... 23 Recording the telephony integration data...... 24 Recording the dial plan configuration data...... 24 Recording the operator (live attendant) properties...... 25 Recording the installed language packs...... 25 Recording server roles and the AxC address...... 25 Recording the system topology...... 26 Cdom and SAL Gateway address assignments...... 26 Overview...... 26 Reassigning Cdom and SAL Gateway IP addresses remotely...... 27 Reassigning Cdom and SAL Gateway IP addresses onsite...... 29 Chapter 4: Upgrade tasks...... 31 Overview...... 31 Upgrade process...... 31 Backing up System Platform...... 32 Logging in to System Platform Web Console...... 32 Backing up System Platform...... 32 Backup field descriptions...... 33 Backing up Messaging...... 34
4 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Contents
Backing up the system...... 34 Backup Now field descriptions...... 35 Upgrading System Platform...... 36 Upgrading System Platform...... 36 Platform upgrade field descriptions...... 38 Verifying the System Platform upgrade...... 39 Checking SAL Gateway...... 40 Upgrading Messaging...... 41 Upgrading the Messaging system...... 41 Search Local and Remote Template field descriptions...... 42 Installing patches...... 43 Patch installation overview...... 43 Installing patches...... 44 Search Local and Remote Patch field descriptions...... 45 Patch Detail field descriptions...... 47 Verifying the patch installation...... 47 Patch List field descriptions...... 48 Chapter 5: Post-upgrade tasks...... 49 Postupgrade configuration...... 49 Installing a license file in WebLM...... 50 Verifying server roles and the AxC address...... 50 Verifying the system topology...... 51 Configuring languages...... 51 Installing language packs...... 51 Languages field descriptions...... 52 Supported languages...... 53 Administering telephony domain...... 54 Telephony administration...... 54 Adding telephony domains...... 54 Telephony Domains field descriptions...... 55 Setting the telephony profile...... 56 Integrating with the telephony server...... 56 Telephony Integration field descriptions...... 57 Migrating the dial plan data...... 59 Setting operator (live attendant) properties...... 59 Administering caller applications...... 60 Caller applications overview...... 60 Caller Applications Editor...... 60 System requirements...... 61 Upgrading Caller Applications Editor...... 61 Logging in to Caller Applications Editor...... 61 Updating a caller application...... 62 Reloading application server cache...... 62
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 5 Comments? [email protected] Contents
Upgrading the voice message form...... 62 Chapter 6: System testing and commissioning...... 65 Basic call answer and Messaging functions verification checklist...... 65
6 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Chapter 1: Introduction
Purpose This document describes how to upgrade and configure a single-server reference configuration for Avaya Aura® Messaging.
Intended audience This document is intended for people who install and configure a verified reference configuration at a customer site.
Document changes since last issue This document replaces Upgrading Avaya Aura® Messaging. The following changes have been made to this document since the last issue: • Added Release 6.3.2 enhancements.
Related resources
Documentation You can download the documents you need from the Avaya Support website at http:// support.avaya.com. In addition to the documentation listed here, you can download a zip file that is a compilation of the Avaya Aura® Messaging documentation library. You can install this library on a computer or on your corporate network. The Avaya Support website also includes the latest information about product compatibility, ports, and Avaya Aura® Messaging releases.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 7 Comments? [email protected] Introduction
Security Title Description Audience Avaya Aura® Messaging Security Discusses security issues to Solution architects, deployment Design consider when designing a engineers, and administrators corporate security strategy. Topics include network security, toll fraud, and recommendations for maintaining a secure system.
Single server configurations Title Description Audience Avaya Aura® Messaging Single Describes the design, capacities, Sales and deployment engineers, Server Reference Configuration interoperability, and limitations of solution architects, and support single-server configurations. personnel Deploying Avaya Aura® Describes an end-to-end Deployment engineers and Messaging for Single Server deployment scenario including all support personnel Systems products that must function together in a single-server configuration.
You might find the following Avaya Aura® documents useful: • Installing and Configuring Avaya Aura® System Platform • Administering Avaya Aura® System Platform • Secure Access Link Gateway Implementation Administration Title Description Audience Administering Avaya Aura® Explains how to use the System Administrators Messaging Management Interface (SMI) to configure your system, use reports and diagnostic tools, manage software and users, and perform routine maintenance tasks. The content is available in two formats: HTML and PDF. Job aid for Administering Avaya Includes routine administration Administrators Aura® Messaging tasks. This job aid is a subset of the administration guide. Avaya Aura® Messaging Alarms Describes system alarms, events, Administrators and support and Events and repair procedures. personnel
8 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Related resources
User functions Title Description Audience Using Avaya Aura® Messaging Explains how to set up and use Users User Preferences and the Messaging toolbar in your email client. The content is available in two formats: HTML and PDF. Using Avaya Aura® Messaging Includes the most common user Users and support personnel Job Aid tasks. This job aid is a subset of the user guide. Avaya Aura® Messaging Quick Describes how to use the Aria Users Reference (Aria) telephone user interface. Avaya Aura® Messaging Quick Describes how to use the Audix® Users Reference (Audix®) telephone user interface. Avaya Aura® Messaging Quick Describes how to use the CallPilot Users Reference (CallPilot®) telephone user interface.
Hardware New installations Title Description Audience Installing the Dell™ PowerEdge™ Describes the components, Deployment engineers and R610 server specifications, and configurations support personnel for this server. Installing the Dell™ PowerEdge™ Describes the components, Deployment engineers and R620 server specifications, and configurations support personnel for this server. Installing the HP ProLiant DL360 Describes the components, Deployment engineers and G7 server specifications, and configurations support personnel for this server. Installing the HP ProLiant DL360p Describes the components, Deployment engineers and G8 server specifications, and configurations support personnel for this server.
Maintenance Title Description Audience Maintaining the Avaya S8800 1U Describes how to add, replace, Deployment engineers and Server for Avaya Aura® Messaging and repair hardware components support personnel for this server. Maintaining and Troubleshooting Describes how to add, replace, Deployment engineers and the Dell™ PowerEdge™ R610 and repair hardware components support personnel server for this server. Also provides
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 9 Comments? [email protected] Introduction
Title Description Audience information about LCD status messages. Maintaining and Troubleshooting Describes how to add, replace, Deployment engineers and the Dell™ PowerEdge™ R620 and repair hardware components support personnel server for this server. Maintaining and Troubleshooting Describes how to add, replace, Deployment engineers and the HP ProLiant DL360 G7 server and repair hardware components support personnel for this server. Maintaining and Troubleshooting Describes how to add, replace, Deployment engineers and the HP ProLiant DL360p G8 and repair hardware components support personnel server for this server.
Training You can get the following Messaging courses at https://www.avaya-learning.com. Enter the course code in the Search field and click Go to search for the course. The course titles might differ from the titles shown.
Course code Course title 2U00230W Avaya UC Messaging — Overview 2U00231W Avaya UC Messaging — Heritage 2U00232W Avaya UC Messaging — Avaya Aura® Messaging 2U00233O Selling Avaya UC Messaging Learning Bytes 3U00141W Designing UC Messaging — Avaya Aura® Messaging 5U00140E Avaya Aura® Messaging Implementation and Support 5U00141E Avaya Aura® Messaging Administration ATI01674VEN Avaya Aura® Messaging — Caller Applications
Viewing Avaya Mentor videos Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya products. About this task Videos are available on the Avaya Support website, listed under the video document type, and on the Avaya-run channel on YouTube.
10 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Support
Procedure • To find videos on the Avaya Support website, go to http://support.avaya.com and perform one of the following actions: - In Search, type Avaya Mentor Videos to see a list of the available videos. - In Search, type the product name. On the Search Results page, select Video in the Content Type column on the left. • To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and perform one of the following actions: - Enter a key word or key words in the Search Channel to search for a specific product or topic. - Scroll down Playlists, and click the name of a topic to see the available list of videos posted on the website. Note: Videos are not available for all products.
Support Go to the Avaya Support website at http://support.avaya.com for the most up-to-date documentation, product notices, and knowledge articles. You can also search for release notes, downloads, and resolutions to issues. Use the online service request system to create a service request. Chat with live agents to get answers to questions, or request an agent to connect you to a support team if an issue requires additional expertise.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 11 Comments? [email protected] Chapter 2: Upgrade overview and considerations
Messaging upgrades This document provides information about the following: • Upgrading Avaya Aura® System Platform. • Upgrading System Platform-based Messaging.
Preupgrade requirements Important: Upgrade the system only during a planned downtime for system maintenance. Best practices For a successful upgrade, implement the following best practices. If you follow best practices, you have a high probability of restoring the initial software release after an upgrade failure. • Identify a server with adequate disk space to store the datasets. The Messaging server backs up Messaging data over the customer LAN to an external ftp server. The network must support a minimum average transfer rate of 1.6 MB per second. The supported backup methods are FTP, SFTP, and SCP. • Get a DVD of the current software release and operating system. • Get the current Service Packs on the application. • Download the required applications on the computer where you want to perform the upgrade. • Get a monitor, a mouse, and the appropriate keyboard to connect to the server. • Get a paper copy of IP addresses, naming information, and worksheets. Software requirements Ensure that the version of System Platform you are running is compatible with Messaging Release 6.3.2. • To obtain information about the supported version, see Avaya Aura® Messaging Release Notes on the Avaya Support website at http://support.avaya.com/Products/P0792.
12 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Preupgrade requirements
• To verify the installed version of System Platform, see Verifying the version of System Platform on page 21. If the software on your system does not match the software components in the release notes, download the needed software before proceeding. After upgrading the System Platform software, update the System Platform software with the latest patches and service packs verified for use with Messaging. You can download the latest patches from the Avaya Support website. For information about the latest patches, see Avaya Aura® Messaging Release Notes on the Avaya Support website, http://support.avaya.com/Products/P0792. For more information on downloading and installing patches and Service Packs, see Installing patches on page 44. License requirements From the Avaya PLDS website, order, download, and install a new Messaging 6.3.2 license file with the Media Encryption feature enabled. After upgrading to Messaging, you must reinstall the new license file and administer telephony integration parameters including transport method, TCP or TLS. If you do not install the new license file, the system cannot use TLS as a transport method. Note: You need a new license file only if you are using TLS/SRTP before upgrading to Messaging 6.3.2. RAID battery status Check the RAID battery status of the server. For more information, see Checking the RAID battery status on page 22. • If you see any of the following alerts, contact Avaya services: O_AVDM10102: RAID battery capacity too low and O_AVDM10101: RAID current setting is write through. • If there are no alerts for RAID battery, continue with the upgrade process. Alarms Ensure that the system does not have any active alarms. • To view current alarms, see Viewing current alarms on page 22. • For the repair procedures for Messaging alarms, see Avaya Aura® Messaging Alarms and Events. • For the repair procedures for System Platform alarms and events, see Administering Avaya Aura® System Platform. Application requirements Install a Secure Shell application, such as PuTTy, on your computer. Browser requirements Install one of the following web browsers on your computer: • Microsoft Internet Explorer 7.x, 8.x, 9.x, or 10.x • Mozilla FireFox 10 and later
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 13 Comments? [email protected] Upgrade overview and considerations
Backup location and access information The Messaging server backs up Messaging data over the customer LAN to an external ftp server. During an upgrade failure, the information stored on the external server is used to restore the system to an operational state. Messaging data backup might easily occupy 50 gigabytes or more. Customers might be unable to support transfers of single files of this size. Hence, in Messaging, the system automatically divides large data backups into 500–MB files before transfer. Each file transfer might complete in about 5 minutes. Consequently, the network must support a minimum average transfer rate of 1.6 MBps. Use one of the following methods for backup: • FTP: A network protocol that provides file transfers over data streams. You must start the FTP server before backing up data. • SFTP: A network protocol that provides file transfers over data streams. The SFTP client is added to all Linux platforms. • SCP: A means of securely transferring computer files between a local and a remote host, or between two remote hosts, using the Secure Shell (SSH) protocol. For more information about backup, see Administering Avaya Aura® Messaging. Disk space Remove large files from home directories under /var/home or /var/home/ftp/pub. A system backup, restore, or upgrade might fail if the disk space that Messaging requires to perform staging is unavailable. The failure occurs because /var/tmp is a staging area for Messaging, and all these directories exist on the same physical partition. Traffic reports Generate traffic reports before you upgrade Messaging. During the upgrade process, the system removes the traffic reports. For more information about traffic reports, see Administering Avaya Aura® Messaging. Outcall notifications During the upgrade process, Messaging does not preserve any pending outcall notifications for users with mailboxes on a Microsoft Exchange message store. MWI options From Messaging Release 6.3, you can configure only the following options for the MWI enabled field on the User Management page. • No: You can use this option to disable the MWI feature. • ByCOS: This option replaces the current default option Yes. Note: If the current option is set to Yes, during the upgrade, the system processes Yes as ByCOS. On the Class of Service page, enable Message Waiting Indicator (MWI) by selecting Set Message Waiting Indicator on user’s desk phone check box.
14 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Preupgrade data gathering
Note: When you upgrade Messaging, the Message Waiting Indicator (MWI) functionality does not change. Cdom and SAL Gateway IP address assignments If you are upgrading to System Platform 6.3 from a version earlier than 6.2, perform one of the following procedures. Choose the procedure depending on the location from where you are performing the upgrade, a remote location or on-site: • Reassigning Cdom and SAL Gateway IP addresses remotely on page 27 • Reassigning Cdom and SAL Gateway IP addresses on-site on page 29 Important: To upgrade from System Platform 6.2 or later, do not perform this procedure. Note: The former Cdom IP address and the new FQDN are assigned during the System Platform upgrade process. For more information, see Chapter 4: Upgrade tasks.
Preupgrade data gathering For a successful upgrade, gather the following data. Language packs • Record the installed language packs that you must reinstall after the upgrade process. For more information, see Recording the installed language packs on page 25. • Download the required language packs from http://support.avaya.com/Products/P0792. Ensure that these language packs are compatible with the software that you are upgrading. For more information about the language packs, see Administering Avaya Aura® Messaging. Dial plan data Record the configured dial plan data in one of the application role servers within a site or cluster. After upgrading to Messaging, move the data from the Dial Rules webpage, the Dial-Out Rules Script, and the Attendant/Operator webpage to the Sites webpage. For more information, see Recording the dial plan configuration data on page 24. The following table includes information about the fields that you must use after the upgrade:
Dial Rules webpage Sites webpage (Postupgrade) Comments (Preupgrade) Country code Country code The country code of the dialing telephone number. Area code / Private number National destination code The beginning sequence of digits that the telephony server processes as a local number other
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 15 Comments? [email protected] Upgrade overview and considerations
Dial Rules webpage Sites webpage (Postupgrade) Comments (Preupgrade) than the one defined for the telephony server. Long-distance prefix National prefix The digits before the area code of the dialing telephone number. International prefix International prefix The digits before the country code of the dialing telephone number. Outside line prefix Outside line prefix The digits required to gain access to the outside line. Number of digits in an extension Subscriber number length within If you are configuring an: the national destination code of • External (Public Network) Dial this site Plan Site, configure the length of Or digits required to call a number within the originating area code Short extension length or a local call in the Subscriber number length (within this site's national destination code) field. • Internal Dial Plan Site, configure the length of extensions for users on this site in the Short extension length field. Number of DID ranges This field is obsolete. Caller ID Internal Number Prefix This field is obsolete. Dial-out rules Use the fields in the Toll-Free and Premium Calls and Local Calls areas to configure the dial-out rules.
Operator (Live Attendant) data Record the configured properties for the operator that you must reenter after the upgrade process. For more information, see Recording the operator (live attendant) properties on page 25. The following table includes information about the fields that you must use after the upgrade:
Attendant / Operator webpage Sites webpage (Postupgrade) Comments (Preupgrade) Schedule type Availability The field that indicates whether the attendant is available. Attendant (operator) extension Operator (live attendant) extension The extension number of the attendant. General delivery mailbox number General mailbox The general mailbox for answering a call if the attendant is unavailable.
16 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Messaging templates overview
Telephony integration data From the Telephony Integration webpage, record the configured connection data that you must reenter after the upgrade process. For more information, see Recording telephony integration data on page 24. After upgrading to Messaging, the Sites webpage remains in a read-only mode because the system cannot find a value for the new field, Telephony Profile Name, on the Sites webpage. To resolve the issue, define the necessary Telephony profiles on the Telephony Domain webpage. When you save the changes to the Telephony Domains page, the system pushes the changes to the application server and overwrites current data.
Messaging templates overview Avaya offers product-specific templates to install different products on System Platform. A template defines the set of applications to be installed on System Platform. Messaging offers the following templates: • Msg_Standard. The Messaging template for the standard server. • Msg_4x146GB_HDD. The Messaging template for the high-capacity storage server. You can upgrade Messaging from one of the following locations. • Avaya Downloads (PLDS): The template files located on the Avaya PLDS website contain all the templates to which your company is entitled. Each line in the list of templates begins with the sold-to number. For more information about the sold-to number, point the mouse to the selected template. • HTTP: You can copy the template files to an http server and install the files on several System Platform servers. • SP Server: You can copy the template files to the /vsp-template directory in Console Domain of the System Platform server. • SP CD/DVD: The template files are located on a CD-ROM or DVD either supplied with the system or created onsite. • SP USB Disk: The template files are located in a USB flash drive connected to the server. The format of the USB flash drive must be ext3. You must decide the location that works best in a specific scenario. For more information, contact an Avaya-certified business partner or an Avaya technician.
Messaging upgrade paths The following table lists all available service packs and patches for a System Platform-based Messaging system, and the upgrade paths available for each version.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 17 Comments? [email protected] Upgrade overview and considerations
Major release Patch or service Direct upgrade to Alternate upgrade path to version pack version Release 6.3.2 Release 6.3.2 6.0 SP 0 Not supported Upgrade to 6.1 SP 3, and then to 6.3.2 6.0.1 SP 0 Not supported Upgrade to 6.1 SP 3, and then to 6.3.2 6.0.1 SP 1 Not supported Upgrade to 6.1 SP 3, and then to 6.3.2 6.0.1 SP 2 Not supported Upgrade to 6.1 SP 3, and then to 6.3.2 6.0.1 SP 3 Not supported Upgrade to 6.1 SP 3, and then to 6.3.2 6.1 SP 0 Not supported Upgrade to 6.1 SP 3, and then to 6.3.2 or Upgrade to 6.2 SP 5, and then to 6.3.2 6.1 SP 1 Not supported Upgrade to 6.1 SP 3, and then to 6.3.2 or Upgrade to 6.2 SP 5, and then to 6.3.2 6.1 SP 2 Not supported Upgrade to 6.1 SP 3, and then to 6.3.2 or Upgrade to 6.2 SP 5, and then to 6.3.2 6.1 SP 3 Supported - 6.2 SP 0 Not supported Upgrade to 6.2 SP 5, and then to 6.3.2 6.2 SP 1 Not supported Upgrade to 6.2 SP 5, and then to 6.3.2 6.2 SP 2 Not supported Upgrade to 6.2 SP 5, and then to 6.3.2 6.2 SP 3 Not supported Upgrade to 6.2 SP 5, and then to 6.3.2 6.2 SP 4 Not supported Upgrade to 6.2 SP 5, and then to 6.3.2 6.2 SP 5 Supported - 6.3 SP 0 Supported - 6.3.1 SP 1 Supported -
18 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Messaging upgrade paths
Note: For more information about upgrading the System Platform-based Messaging system to a Virtualized Environment, see Deploying Avaya Aura® Messaging using VMware® in the Virtualized Environment.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 19 Comments? [email protected] Chapter 3: Pre-upgrade tasks
Prerequisites
No. Tasks References Notes
1 Verify the System See Verifying the version of — Platform version. System Platform on page 21. 2 Order and download a See Deploying Avaya Aura® Perform this task only if you are new Messaging 6.3.2 Messaging for Single using TLS/SRTP before upgrading license file with the Media Server Systems. to Messaging 6.3.2. Encryption feature enabled. 3 Check the RAID battery See Checking the RAID — status of the server. battery status on page 22. 4 Verify that there are no • To view current alarms, — active alarms in the see Viewing current system. alarms on page 22. • To resolve Messaging alarms, see Avaya Aura® Messaging Alarms and Events. • To resolve System Platform alarms and events, see Administering Avaya Aura ® System Platform. 5 Remove large files from — A system backup, restore, or home directories upgrade might fail if the disk space under /var/home that Messaging requires to perform or /var/home/ftp/ staging is unavailable. pub. 6 Record the configured See Recording telephony You must reenter this data after the connection data from the integration data on upgrade process. Telephony Integration page 24. webpage.
20 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Verifying the version of System Platform
No. Tasks References Notes
7 Record the dial plan See Recording the dial plan Perform this task only if you are configuration data. configuration data on upgrading from Messaging page 24. Release 6.0.1 SP3 or 6.1 SP3 to 6.3.2. 8 Record the operator (live See Recording the operator Perform this task only if you are attendant) properties. (live attendant) upgrading from Messaging properties on page 25. Release 6.0.1 SP3 or 6.1 SP3 to 6.3.2. 9 Record the currently See Recording the installed — installed language packs. language packs on page 25. 10 Record server roles and See Recording server roles — the AxC address. and AxC address on page 25. 11 Record the system See Recording the system — topology. topology on page 26. 12 Generate traffic reports. For more information, see During the upgrade process, the Administering Avaya Aura® system removes the traffic reports. Messaging. 13 Reassign Cdom and SAL See Perform this task only if you are Gateway IP addresses. upgrading from a release earlier • Reassigning Cdom and than System Platform Release 6.2. SAL Gateway IP addresses remotely on The former Cdom IP address and page 27. the new FQDN are assigned during the System Platform upgrade • Reassigning Cdom and process. For more information, see SAL Gateway IP Chapter 4: Upgrade process. addresses on-site on page 29.
Verifying the version of System Platform About this task Before you upgrade Messaging, confirm that the version of System Platform you are running is compatible with Messaging Release 6.3.2. To obtain information on the supported version, see Avaya Aura® Messaging Release Notes on the Avaya Support Web site at http:// support.avaya.com/Products/P0792. Procedure 1. Log on to System Platform Web Console. 2. Click Virtual Machine Management > Manage.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 21 Comments? [email protected] Pre-upgrade tasks
3. Verify the version of Domain-0 and cdom. If the software on your system does not match the software components in the release notes, download the needed software before proceeding.
Checking the RAID battery status About this task For a successful upgrade, you must check the RAID battery status of the server before you upgrade Messaging. Important: To check the RAID battery status, the system must be running on System Platform 6.0.3.9.3 or later. If you are running an older version of System Platform, either upgrade to System Platform 6.0.3.9.3 or contact Avaya Services to verify the RAID battery status. Procedure 1. Log on to System Platform Web Console. 2. Click Server Management > Log Viewer. 3. From the Messages heading, click System Logs. 4. From the Log Level heading, click Alert. 5. Click Search. The search result displays System Platform alerts. 6. If you see any of the following alerts, contact Avaya services: • O_AVDM10102: RAID battery capacity too low • O_AVDM10101: RAID current setting is write through 7. If there are no alerts for RAID battery, continue with the upgrade process.
Viewing current alarms Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Server (Maintenance) > Alarms > Current Alarms. 3. Check if there are alarms in the Messaging Alarms section. 4. Resolve if there are any active alarms. • To resolve Messaging alarms, see Avaya Aura® Messaging Alarms and Events.
22 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Current Alarms field descriptions
• To resolve System Platform alarms and events, see Administering Avaya Aura® System Platform.
Current Alarms field descriptions
Field Name Description Product ID A number that uniquely identifies the server. Messaging Product ID A number that uniquely identifies the Messaging product. ID A unique identification number assigned to the alarm. APP The name of the application. Source The abbreviated name of the software module that generated the alarm. • EL: Enhanced List Application • IM: Internet Messaging • LD: LDAP • MT: Maintenance • SM: Station Manager • VM: Messaging • VP: Voice Platform EvtID The event identification number for each alarm. Use the number to identify a particular event from the source that generated the alarm. Lvl The level of the alarm. • MIN • MAJ • WARN Ack The acknowledgement of the alarm by Initialization and Administration System (INADS). Displays a Y (yes) or N (no) to indicate the status. Location The location where the alarm originated. Date A time stamp assigned to the alarm at the time of origination.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 23 Comments? [email protected] Pre-upgrade tasks
Recording the telephony integration data About this task From the Telephony Integration webpage, record the configured connection data that you must reenter after the upgrade process. After upgrading to Messaging, the Sites webpage remains in a read-only mode because the system cannot find a value for the new field, Telephony Profile Name , on the Sites webpage. To resolve the issue, define the necessary Telephony profiles on the Telephony Domain webpage. Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Telephony Settings (Application) > Telephony Integration. 3. Record the following far-end connection data: a. IP address and port number b. Transport method, TCP or TLS
Recording the dial plan configuration data
Important: Perform this task only if you are upgrading from Messaging Release 6.0.1 SP3 or 6.1 SP3 to 6.3.2. About this task Before upgrading the Messaging system, record the current properties of the dial plan, which you must reenter after the upgrade process. Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Server Settings (Application) > Dial Rules. 3. Record the current properties of the dial plan. From Release 6.1 onwards, you can manage these properties from Messaging > Messaging System (Storage) > Sites.
24 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Recording the operator (live attendant) properties
Recording the operator (live attendant) properties
Important: Perform this task only if you are upgrading from Messaging Release 6.0.1 SP3 or 6.1 SP3 to 6.3.2. About this task Before upgrading the Messaging system, record the current properties of the operator (live attendant), which you must reenter after the upgrade process. Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Server Settings (Application) > Attendant/Operator. 3. Record the current properties of the operator. From Release 6.1 onwards, you can manage these properties from Messaging > Messaging System (Storage) > Sites.
Recording the installed language packs About this task Before upgrading the Messaging system, record the currently installed language packs that you must reinstall after the upgrade process. Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Server Settings (Application) > Languages. 3. From the Language Packs: Installed Languages, record the names of all language packs.
Recording server roles and the AxC address About this task Before upgrading the Messaging system, record the current server roles and the AxC address, which you must verify after the upgrade process. Procedure 1. Log on to Messaging System Management Interface.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 25 Comments? [email protected] Pre-upgrade tasks
2. On the Administration menu, click Messaging > Server Settings > Server Role / AxC Address. 3. Record the roles for the server and the AxC address.
Recording the system topology About this task Before upgrading the Messaging system, record the system topology, which you must verify after the upgrade process. Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Messaging System (Storage) > Topology. 3. Record the IP address of the current application server.
Cdom and SAL Gateway address assignments
Overview If you are upgrading to System Platform 6.3 from a version earlier than 6.2, you must complete one of the following procedures. Choose the appropriate procedure depending on whether you are performing the upgrade from a remote location or on-site where the server is located: • Reassigning Cdom and SAL Gateway IP addresses remotely on page 27 • Reassigning Cdom and SAL Gateway IP addresses onsite on page 29 Important: Perform this task only if you are upgrading from a System Platform version earlier than 6.2. If upgrading from System Platform 6.2 or later, this task is not required. Note: This prerequisite does not apply to Avaya Aura solutions that have deployed a remote stand- alone SAL Gateway server. In this case, IP addresses assigned to your system must remain unchanged, because you will not enable the Services Virtual Machine during the platform upgrade process. During an upgrade, the System Platform installation software verifies if your system already uses the local SAL Gateway. If the system is not using the local SAL Gateway,
26 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Cdom and SAL Gateway address assignments
the System Platform installation program automatically installs the Services Virtual Machine in a disabled state, which also disables its embedded SAL Gateway. On both procedures, you must assign a new IP address to the Cdom virtual machine, and then assign the former Cdom IP address to the SAL Gateway. The Avaya customer must provide any site-specific IP address assignments. With System Platform versions 6.2 and later, a new Services Virtual Machine hosts the SAL Gateway unless you have already deployed a remote SAL Gateway server. You do not need to redefine alarm destinations for template applications running on the same server if you assigned both: • The previous Cdom IP address to the embedded SAL Gateway and • A new IP address to the Cdom virtual machine. . You do not have to redefine alarm destinations because the IP address of the SAL Gateway remains unchanged throughout the upgrade process. Completing this process ensures that the SAL Gateway remains in communication with Avaya (or an Avaya Partner) during the upgrade event. The following tables provide an example of Dom0, Cdom, and embedded SAL Gateway address assignments before and after completing the System Platform upgrade prerequisite:
Table 1: Example Dom0, Cdom, and SAL Gateway address allocations before upgrading to System Platform 6.3
Virtual Machine or Application IP Address 1 IP Address 2 Domain 0 (dom0) 192.168.10.100 Console Domain (cdom) 192.168.10.101 (shared) Integrated SAL Gateway (version 1.8)
Table 2: Example Dom0, Cdom, and SAL Gateway address allocations after upgrading to System Platform 6.3
Virtual Machine or IP Address 1 IP Address 2 IP Address 3 Application Domain 0 (dom0) 192.168.10.100 Console Domain (cdom) (Reallocated to Services 192.168.10.102 (New Virtual Machine.) address assignment) Integrated SAL Gateway 192.168.10.101 (version 2.2) on Services Virtual (Reassigned from former Machine (services_vm) cdom virtual machine)
Reassigning Cdom and SAL Gateway IP addresses remotely Perform this task when a System Platform upgrade must be performed from a location remote from the customer site. A Support Engineer at Avaya or an Avaya Partner site must complete this task
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 27 Comments? [email protected] Pre-upgrade tasks
entirely by communication established between an Avaya Remote Server and the server you must upgrade. Before you begin • If you are a customer of Avaya or an Avaya Partner and must upgrade to System Platform version 6.3 from a version earlier than 6.2, go tohttp://support.avaya.com and click on Support Contact Options > Maintenance Support. • Complete the blank fields in the following table. The following steps reference either address “A” or “B”, as appropriate.
Table 3: Cdom IP address assignments (remote procedure)
Current Cdom (avpublic) IP Address: A. New customer-provided IP address for Cdom: B. (The new address for the cdom virtual machine must be on the same IP subnet used by the System Platform Domain 0 virtual machine. Verify using Linux ipcalc or similar tool.) • Support Engineers must have their Token (SecureID) USB device available for additional authentication. About this task Important: If you are upgrading a System Platform High Availability configuration that uses the embedded SAL Gateway, complete Cdom and SAL Gateway IP address reassignments on the primary server only, and only after stopping High Availability. If you later have a High Availability failover event (triggered manually or automatically), the High Availability subsystem enables the Services VM on the standby server. The HA data replication software also automatically propagates the new Cdom and SAL Gateway IP addresses to the standby server. Use of the term target server in this procedure refers to the System Platform server you must upgrade. Procedure 1. Log on to the SAL Remote Server at https://tech1.sal.avaya.com 2. Using the SE ID of VSPU (cdom), open a remote HTTPS SAL session with the Cdom virtual machine on the target server. 3. Log on to the System Platform Web Console, and log in as admin. 4. ClickServer Management > Network Configuration. 5. From the Domain Network Interface panel, under the Console Domain, note the avpublic IP address from Table 3: Cdom IP address assignments (remote procedure) on page 28, field “A”. 6. Enter the new, customer-provided cdom IP address (from Table 3: Cdom IP address assignments (remote procedure) on page 28, field ”B”) into the Console Domain avpublic IP field.
28 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Cdom and SAL Gateway address assignments
7. Click Save. Saving the change you made to the Cdom IP address configuration temporarily severs your secure connection to the target server. However, the server continues to have connectivity and communication with the remote Avaya servers. (Your SAL Gateway 1.8 gracefully manages changes to the server's IP address configuration.) 8. From the SAL Remote Server at https://tech1.sal.avaya.com, request an HTTPS session with the SAL Gateway on the target server. 9. Log on to the SAL Gateway user interface using the VSALGW SE ID: (https://
Reassigning Cdom and SAL Gateway IP addresses onsite Perform this task when a System Platform upgrade can be performed at the customer site. In this case, Avaya or Avaya Partner Support Engineering personnel are available onsite to assist with local (customer network) login to the Web Console for the server that you must upgrade. Before you begin • If you are a customer of Avaya or an Avaya Partner and must upgrade to System Platform version 6.3 from a version earlier than 6.2, go tohttp://support.avaya.com and click on Support Contact Options > Maintenance Support. • Complete the blank fields in the following table. The following steps reference either address “A” or “B”, as appropriate.
Table 4: Cdom IP address assignments (local procedure)
Current Cdom (avpublic) IP Address: A. New customer-provided IP address for Cdom: B. (The new address for the cdom virtual machine must be on the same IP subnet used by the
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 29 Comments? [email protected] Pre-upgrade tasks
System Platform Domain 0 virtual machine. Verify using Linux ipcalc or similar tool.) • Support Engineers must have their Token (SecureID) USB device available for additional authentication. About this task Important: If you are upgrading a System Platform High Availability configuration that uses the embedded SAL Gateway, complete Cdom and SAL Gateway IP address reassignments on the primary server only, and only after stopping High Availability. If you later have a High Availability failover event (triggered manually or automatically), the High Availability subsystem enables the Services VM on the standby server. The HA data replication software also automatically propagates the new Cdom and SAL Gateway IP addresses to the standby server. Procedure 1. Log on to the System Platform Web Console as admin. 2. Select Server Management > Network Configuration. 3. From the Domain Network Interface panel, under the Console Domain, note the avpublic IP address in preceding table, field “A”. 4. Enter the new, customer-provided Cdom IP address (from the preceding table, field ”B”) into the Console Domain avpublic IP field. 5. Click Save. Saving the change you made to the Cdom IP address configuration temporarily severs your secure connection to Cdom on the target server. However, the server continues to have connectivity and communication with the remote Avaya servers. (Your SAL Gateway 1.8 gracefully manages changes to the server's IP address configuration.) 6. Log on to the SAL Gateway user interface using the new Cdom IP address (https://
30 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Chapter 4: Upgrade tasks
Overview You can upgrade the Messaging software for the single-server by: • Connecting the laptop to the services port on the server onsite. • Accessing the server through the corporate network remotely.
Upgrade process
No. Tasks References Notes
1 Back up the System Platform See Backing up System Platform on — configuration information. page 32. 2 Back up Messaging system files See Backing up system files on — and application files. page 34. 3 Upgrade the System Platform See Upgrading System Platform on — software. page 36. 4 Install the latest System Platform See Patch installation overview on — patches. page 43. 5 Upgrade the Messaging software. See Upgrading the Messaging — system on page 41. 6 Install the latest Communication See Patch installation overview on — Manager patches. page 43. 7 Install the latest Messaging See Patch installation overview on — patches. page 43.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 31 Comments? [email protected] Upgrade tasks
Backing up System Platform
Logging in to System Platform Web Console Before you begin • Obtain the IP address of the Console Domain. • Obtain a valid user ID. If you use an Avaya services login that is ASG protected, you must have an ASG tool to generate a response for the challenge that the login page generates. Many ASG tools are available such as Avaya Token Mobile, Avaya Web Mobile, and Site Manager. The first two ASG tools reach the ASG manager servers behind the Avaya firewall. An Avaya Services representative uses Site Manager to pull the keys specific to a site before visiting that site. At the site, the Avaya Services representative uses those keys to generate the response for the challenge that the login page generates. About this task You can gain access to System Platform Web Console from a web browser on your laptop or another computer connected to the same network as the System Platform server. Procedure 1. In the Internet browser, type the URL of System Platform Web Console. For example: https://ipaddress. System Platform Web Console is a secure site. If you see a certificate error, then follow the instructions on your browser to install a valid certificate on your computer. 2. Type a valid user ID. Use the advanced administrator login. 3. Click Continue. 4. Type a valid password. 5. Click Log On.
Backing up System Platform About this task Use this procedure to back up configuration information of System Platform and the Messaging template. Use System Platform Web Console to back up the files. Important: The backup file size can reach 3 GB. Ensure that the location where you are storing the backup file has that much free space. Procedure 1. Log on to System Platform Web Console.
32 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Backing up System Platform
2. Click Server Management > Backup/Restore. 3. Click Backup. 4. On the Backup page, select the Backup Now option to start the backup operation immediately. 5. In the Backup Method field, click where you want to store or send the backup files: • Local: Stores the backup archive file on System Platform in the /vspdata/backup/ archive directory. • SFTP: Stores the backup archive file on the designated SFTP host server as well as on the System Platform server. • Email: Sends the backup archive file to the email address that you specify and stores the file on the System Platform server. Note: Do not use the Email option as the size of backup files is large. 6. Enter other information as appropriate. 7. Click Backup Now.
Backup field descriptions
Field Name Description Backup Method Select a location to send the backup file: • Local: Stores the backup archive file on System Platform in the /vspdata/backup/archive directory. • SFTP: Stores the backup archive file on the designated SFTP host server as well as on the System Platform server. Enter the host name or the IP address, the directory, the user name, and the password for the SFTP server. • Email: Sends the backup archive file to the email address that you specify, as well as stores the file on the System Platform server. Enter the email address and the server address of the recipient. Backup Now Starts the backup operation.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 33 Comments? [email protected] Upgrade tasks
Backing up Messaging
Backing up the system About this task Messaging uses LAN to back up the Messaging data to an external server. The Messaging application data and the server data can be backed up simultaneously or independently. During a system failure, Messaging uses the information stored on the external server to restore the system. Messaging supports the following backup methods: • FTP • SFTP • SCP Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Utilities > Stop Messaging. 3. Click Stop. The system delays the shutdown for three minutes after which the system ends all active calls. The Stop Messaging Software webpage refreshes periodically during the shutdown routine. After the Messaging software stops, the system displays the Stop of Messaging completed message. 4. Click OK. 5. On the Administration menu, click Server (Maintenance) > Data Backup/Restore > Backup Now. 6. On the Backup Now webpage, in the Data Sets area, click Specify Data Sets. Click the following fields: a. Server and System Files b. Security File c. Messaging 7. In the Messaging area, click Messaging Application, Translations, Names, and Messages. 8. In the Backup Method area, click Network Device and then complete the following fields: a. Method b. User Name c. Password
34 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Backing up Messaging
d. Host Name e. Directory 9. If you want to encrypt the backup data, select Encrypt backup using pass phrase and enter a pass phrase using an arbitrary string of 15 to 256 characters. 10. Click Start Backup. For more information, see Backup Now field descriptions on page 35. 11. On the Administration menu, click Messaging > Utilities > Start Messaging. The Start Messaging Software webpage refreshes periodically during the startup process and displays a status message after displaying the Start Messaging information message. After the Messaging software starts successfully, the system displays the Start of Messaging completed message. 12. Click OK.
Backup Now field descriptions
Settings Description Specify Data Sets The data sets that you want to back up. The available options are: • Server and System Files: Back up the variable information to configure the server for a particular installation. • Security File: Back up the variable information to maintain security of the server. • Messaging: Back up one of the following Messaging options: - Messaging Application, Translations and Messages - Messaging Application, Translations, Names, and Messages - Messaging Application, Translations and Names - Messaging Application and Translations - Messaging Application Full Backup A full backup includes security data sets and files that configure both the Linux operating system and the applications. A Full Backup does not include any of the Messaging data sets.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 35 Comments? [email protected] Upgrade tasks
Settings Description Backup Method Method The following methods are available for backup: • SCP: A means of securely transferring computer files between a local and a remote host, or between two remote hosts, using the Secure Shell (SSH) protocol. • FTP: When you choose this option, you must enter the user name, the password, the host name or the IP address, and the directory. The default directory for backup data on the FTP server is /var/home/ ftp. If you want to use the default directory, enter a forward slash (/) in the directory field. You must start the FTP server before backing up data. • SFTP: A network protocol that provides file transfers over data streams. The system adds the SFTP client to all Linux platforms. User Name The user name for storing the backup. Password The password for storing the backup. Host Name The host name of the backup server. Directory The backup is stored on this network directory. Encryption Encrypt backup using pass phrase Defines if you want to encrypt the backup data. The pass phrase can be an arbitrary string of 15 to 256 characters. The pass phrase can contain any characters except the following: single quote ('), ampersand (&), back slash (\), single back quote (`), quote ("), and percent sign (%).
Upgrading System Platform
Upgrading System Platform Procedure 1. Log on to System Platform Web Console. 2. Click Server Management > Platform Upgrade. The system displays the Platform Upgrade page.
36 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Upgrading System Platform
3. In the Upgrade Platform From field, select the medium to search for the System Platform image files for the platform upgrade. The system searches for an upgrade description file that has a .ovf extension. The options are:
Option Action Avaya Downloads Provide SSO Login and SSO Password, and then click Search. (PLDS) HTTP Specify the Platform Upgrade URL, and click Search. If the upgrade files are located in a different server, configure a proxy server depending on your network. Click Configure Proxy to specify a proxy server if required. SP Server Specify the Platform Upgrade URL to download the platform upgrade files located in the /vsp-template directory in Console Domain of the System Platform server, and click Search. SP CD/DVD Click Search. SP USB Disk Click Search.
For more information, see Platform upgrade field descriptions on page 38. 4. Select the VSP description file of the platform upgrade, and then click Select. The system displays the version and additional information for the current and the new platforms, System Domain and Console Domain, on the Platform Upgrade page. 5. Enter the former Console Domain address into the IP address field of the new Services Virtual Machine. Important: During upgrade, the system reboots System Domain and Console Domain followed by Messaging. During the platform upgrade process, all operations on System Platform Web Console are blocked. All links, including menu items, are disabled until the system boots with the new platform for you to commit or rollback the upgrade. 6. On the Platform Upgrade page, click Upgrade. The system displays a dialog box to confirm whether: • The template is qualified for the platform version that you are about to upgrade. • System reboots System Domain and System Platform Web Console after the upgrade. 7. In the dialog box, click OK. The upgrade process starts, and the system displays the Platform Upgrade workflow status page. During the upgrade process, System Domain (Domain-0) and Console Domain are rebooted. Therefore, the Platform Upgrade workflow status page does not show any updates until the system reboots in the new Console Domain. After System Platform Web Console is rebooted, the system automatically redirects you to the login page. The upgrade process takes about 20 minutes.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 37 Comments? [email protected] Upgrade tasks
8. Log on to System Platform Web Console. You can view the time remaining for Auto Rollback of Platform Upgrade on the Commit or Rollback platform upgrade page. You can also check System Platform Web Console to ensure that the upgrade process is running properly. 9. Click I Accept to accept the end user license agreement. 10. When System Platform Web Console prompts to Commit or RollBack the platform upgrade, verify that System Platform is running. For more information, see Verifying System Platform upgrade on page 39. 11. Click Platform Upgrade waiting for user to commit. 12. On the Commit or Rollback platform upgrade page, do one of the following: • Click Commit to continue the upgrade process by committing to the newly upgraded platform. You can commit the upgrade within a 4-hour period. If you do not log in during this period, the system reboots using the previous release of System Platform. If you log in to System Platform Web Console within 4 hours, you can be sure that System Platform is reachable and the timer is cancelled. However, you must still verify and commit the upgrade. • Click Rollback to cancel the upgrade process and return to the previous version of the software. Note: Rolling back the upgrade might impair communication between the AxC and the Application role. Reload User List and Global Address List to connect the Application role with AxC. For more information, see Reloading application server cache on page 62.
Platform upgrade field descriptions
Fields Description Upgrade Platform From The field to select a platform upgrade file from the following options: • Avaya Downloads (PLDS) Use an Avaya SSO login and password to access the Avaya PLDS website. The list on this site contains all the platform upgrade files to which your company is entitled. Each line in the list begins with the sold-to number. Using the sold-to number, you can select the appropriate platform upgrade files for your site. Point the mouse to view more information about the sold-to number. • HTTP To download the platform upgrade files located on an HTTP server, you must enter the Platform Upgrade URL. • SP Server
38 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Upgrading System Platform
Fields Description To download the platform upgrade files located in the /vsp- template directory in the Console Domain of the System Platform server, you must specify the Platform Upgrade URL. You must copy the platform upgrade files in this directory using a file transfer program and change their permissions as follows: chmod 644
Verifying the System Platform upgrade Procedure 1. Log on to System Platform Web Console. 2. On the Commit/Rollback page, verify the following: a. The server successfully booted with the new platform version. b. No image or kernel faults occurred during the upgrade. Otherwise, System Platform automatically rolls back to the previous version and the Rollback Acknowledge page appears. c. No problems occurred in the LDAP storage. 3. Click Virtual Machine Management > Manage. Verify that the Domain–0 and Console Domain (cdom) versions are identical to the version of your System Platform upgrade. 4. Click Server Management > System Configuration. Verify the accuracy of the system configuration information. This action performs a quick check for accuracy of system configuration information carried forward during the platform upgrade.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 39 Comments? [email protected] Upgrade tasks
5. Click Server Management > Date/Time Configuration. Verify that the Date and time are correct as configured. This action performs a quick sanity check on the NTP protocol, date, and time configuration. 6. Click Server Management > Backup/Restore > Restore. If the backup is successful, you can see the latest backup information. 7. Click Server Management > Network Configuration. Verify that all network configuration values are correctly configured. 8. Click Server Management > License management, and start the WebLM License Manager. Log in to the WebLM portal to verify that all template virtual machine license files are valid.
Checking SAL Gateway Before you begin Upgrade the Services virtual machine. For more information, see Upgrading Avaya Aura® System Platform. Procedure 1. Log on to System Platform Web Console. 2. Click Server Management > SAL Gateway Management. 3. On the SAL Gateway Management page, click Enable SAL Gateway. 4. On the SAL Gateway Management page, click the Launch SAL Gateway Management Portal link. The system displays the SAL Gateway page in a new window. 5. On the SAL Gateway page, enter the authorized user ID and password to log in. 6. In the navigation pane of SAL Gateway page, click Administration > Service Control & Status. The system displays the Gateway Service Control window. 7. On the Gateway Service Control page, click Check Health for the Gateway. The system checks the SAL Gateway operation and communication with Avaya remote servers. Next steps • Update System Platform with the latest approved patches and service packs before upgrading the Messaging system. Ensure that these patches and service packs are verified for use with Messaging. You can download the latest patches from the Avaya support website at http:// support.avaya.com/Products/P0792. For information on the latest patches, see Avaya Aura® Messaging Release Notes on the Avaya Support website at http://support.avaya.com/Products/P0792.
40 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Upgrading Messaging
• Upgrade the Messaging system.
Upgrading Messaging
Upgrading the Messaging system Before you begin • Upgrade System Platform. • Upgrade the Services virtual machine. For more information, see Upgrading Avaya Aura® System Platform. • Update System Platform with the latest approved patches and service packs. Ensure that these patches and service packs are verified for use with Messaging. Procedure 1. Log on to System Platform Web Console. 2. Click Virtual Machine Management > Template. The system displays the Search Local and Remote Template page. 3. Click Upgrade. 4. In the Install Template From field, select the medium to search for the Messaging image files. The following table lists the available options:
Option Action Avaya Downloads Provide SSO Login and SSO Password and then click Search. (PLDS) HTTP Specify the Template Location, and click Search. Depending on your network, click Configure Proxy to specify a proxy server if the template files are located on a different server. SP Server Specify the Template Location and click Search. SP CD/DVD Click Search. SP USB Disk Click Search.
For more information, see Search Local and Remote Template field descriptions on page 42. 5. In the Select Template list, select the template that matches the current system configuration. 6. Click Select. 7. On the Template Details page, click Upgrade.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 41 Comments? [email protected] Upgrade tasks
The system displays the Template Network Configuration page with the network configuration information that you entered while installing System Platform. 8. Verify the network configuration, and click Save to continue. The system displays the Template Details page with the system properties that you entered while installing Messaging. 9. Verify the system properties. a. MSG IPv4 Address: The IPv4 address of the Messaging virtual machine b. MSG Hostname: The host name that must be the Fully Qualified Domain Name (FQDN) of the Messaging virtual machine 10. Click Upgrade. The Template Installation page displays the progress of the template installation. 11. When System Platform Web Console prompts to Commit or RollBack the installation: a. Validate that the system plays a greeting for the user. From an outside number, dial the external Pilot number and connect to the extension of any user. b. Validate that the user data is intact after the upgrade. On the Administration menu, click Messaging > Reports (Storage) > Users. The report displays a list of local users in the Messaging system. Click a user, and validate the data. 12. On the Template Installation page, do one of the following: • If the system passes all verification checks, click Commit Installation to complete the upgrade process. • If the system fails verification checks, click Rollback Installation to cancel the upgrade process and return to the previous version of the software. Next steps Install the patches.
Search Local and Remote Template field descriptions
Field name Descriptions Install Template From The location from where you can search for a template. The available locations are: • Avaya Downloads (PLDS) To download the template files located on Avaya PLDS website, you must enter an Avaya SSO login and password to access this site. The list on this site contains all the templates to which your company is entitled. Each line in the list begins with the sold-to number. Using the sold-to number, you can select the appropriate template for your site. To view more information about the sold-to number, hold the mouse pointer over the selection.
42 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Installing patches
Field name Descriptions • HTTP To download the template files located on an HTTP server, you must enter the template location information. • SP Server To download the template files located in the /vsp-template file system in the Console Domain of the System Platform server, you must specify the template location for the server. • SP CD/DVD To download the template files located on a CD-ROM or DVD in the CD/DVD drive on the System Platform server. • SP USB Disk To download the template files located on a USB flash drive connected to the server, format the USB flash drive as ext3. SSO Login The login ID to log on to Single Sign On. The system activates this field only when you select the Avaya Downloads (PLDS) option to search for a template. SSO Password The password for Single Sign On. The system activates this field only when you select the Avaya Downloads (PLDS) option to search for a template. Template Location The URL of the server where the template files are located. The system activates this field only when you select the HTTP or SP Server option to search for a template.
Installing patches
Patch installation overview A Service Pack provides product updates and bug fixes. When a Service Pack is available on the Avaya Support website, the supporting information clearly states the issues addressed in the Service Pack. Even if the system does not have problems, implement the Service Packs to keep the systems up-to-date and minimize the likelihood of future issues. A patch provides critical security, performance, and stability fixes or updates. A Service Pack is a bundle of updates, fixes, enhancements, and previously released patches. In this document, the word patches refers to both patches and Service Packs. You can install, download, and manage the patches from System Platform Web Console.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 43 Comments? [email protected] Upgrade tasks
You must install the following patches in addition to the currently installed software: • Communication Manager: Messaging uses the Communication Manager platform that requires software updates. • Messaging You must install the following patches when available: • Security • Kernel Important: Install kernel updates only during a planned downtime for system maintenance. To download the latest patches and to obtain the necessary information, see Avaya Aura® Messaging Release Notes on the Avaya Support website at http://support.avaya.com/Products/ P0792. Important: Before you apply a patch, back up the system. When you install the latest patch, the installation program automatically uninstalls the previous patch. So, if you remove a patch, the system does not reinstall the previous patch or revert the system to the previous state, that is, the state before the patch was installed. To revert the system to the previous state, you must reinstall the previous patch. For more information, see Administering Avaya Aura® Messaging.
Caution: The patch installation process affects the availability of the Messaging service.
Installing patches Before you begin Ensure that the Messaging system is running. Procedure 1. Log on to System Platform Web Console. 2. Click Server Management > Patch Management > Download/Upload. The system displays the Search Local and Remote Patch page. 3. From the Choose Media drop-down list, select the medium to search for a patch. The following table lists the available options.
Option Action Avaya Downloads (PLDS) Provide SSO Login and SSO Password, and then click Search.
44 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Installing patches
Option Action Note: This option is not available for Avaya Services. HTTP Specify Patch URL, and click Search. If the patches are located on a different server, you might have to configure a proxy server depending on your network. Click Configure Proxy to specify a proxy server if required. SP Server Specify Patch URL, and click Search. Note: This option is not available for Avaya Services. SP CD/DVD Click Search. SP USB Disk Click Search. Local File System Click Add to locate the patch file on your computer and then click Upload.
For more information, see Search Local and Remote Patch field descriptions on page 45. The system displays the Select Patches page. 4. From the Select Patches list, select the patch that you want to download. 5. Click Select. 6. On the Patch Detail page, click Install. For more information, see Patch Detail field descriptions on page 47. The Patch Detail page displays the progress of the patch installation. Next steps Verify the patch installation.
Search Local and Remote Patch field descriptions
Field name Description Supported Patch File Extensions The patch that you select for installing. Ensure that the patch matches the extensions in the following list. For example, *.tar.gz,*.tar.bz,*.gz,*.bz,*.zip,*.tar,*.jar,*.rpm,*.patch. Choose Media The media options from where you can search for a patch. The available options are: • Avaya Downloads (PLDS) To download the patch files located on Avaya PLDS website, you must enter an Avaya SSO login and password to access this site. The list on this site contains all the templates that your company is entitled to. Each line in the list begins with the sold-to number. Use
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 45 Comments? [email protected] Upgrade tasks
Field name Description the sold-to number to select the appropriate template for your site. For more information about a sold-to number, hold the mouse pointer over the number. • HTTP To download the patch files located on an HTTP server, you must enter the patch location information. • SP Server: To download the patch files located in the /vsp-template directory in Console Domain of the System Platform server, you must specify the patch location for the server.
Tip: When you move files from a laptop to the System Platform server, you might encounter some errors, as System Domain (Dom–0) and Console Domain support only SCP. Most laptops do not support SCP. To enable SCP, download the following two programs: - Pscp.exe - WinSCP For detailed procedures on how to download the programs, search the Internet. • SP CD/DVD To download the patch files located on a CD-ROM or DVD in the CD/DVD drive on the System Platform server. • SP USB Disk To download the patch files located on a USB flash drive connected to the server. • Local File System To download the patch files located in a local file system. SSO Login The login ID to log on to Single Sign On. The system activates this field only when you select the Avaya Downloads (PLDS) option to search for a patch. SSO Password The password for Single Sign On. The system activates this field only when you select the Avaya Downloads (PLDS) option to search for a patch. Patch URL The URL of the server where the template files are located. The system activates this field only when you select the HTTP or SP Server option to search for a patch.
46 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Installing patches
Patch Detail field descriptions
Name Description ID The file name of the patch file. Version The version of the patch file. Product ID The name of the virtual machine. Description The short description of the patch file. Detail The name of the virtual machine to which the patch is applicable. This field is not applicable for Messaging patches. Dependency The dependency that the patch file might have on any other file. This field is not applicable for Messaging patches. Applicable for The software load for which the patch is applicable. This field is not applicable for Messaging patches. Service effecting when The action, if any, that causes the selected patch to restart the Messaging services. Restart this console when The conditions or circumstances when the System Platform Web Console must be restarted. This field is not applicable for Messaging patches. Disable sanity when The circumstance when the condition is set to disable. This field is not applicable for Messaging patches. Status The status to show whether the patch is available for installation or already installed. Patch File The path where the patch is cached on the Console Domain.
Verifying the patch installation Procedure 1. Click Server Management > Patch Management > Manage. The system displays the Patch List page. 2. Verify that the system displays the Messaging and Communication Manager patches that you installed under the msg heading and the status of the patch is Active. For more information, see Patch List field descriptions on page 48.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 47 Comments? [email protected] Upgrade tasks
Patch List field descriptions The Patch List page displays the patches on the System Platform server for installation or removal. To view the details of the patch file, click the file name.
Name Description System Platform Lists the patches available for System Platform. Solution Template Lists the patches available for the respective solution templates. msg Lists the patches available for Messaging. Patch ID Lists the file name of a patch. Description Provides information about a patch. For example, the field describes a patch available for System Platform as SP patch. Status Shows the status of a patch. The possible values of Status are Active and Not Installed. Service Affecting Shows if installing the patch causes the Messaging virtual machine to reboot.
48 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Chapter 5: Post-upgrade tasks
Postupgrade configuration
No. Tasks References Notes
1 Install a new Messaging See Installing a license file in Perform this task only if you 6.3.2 license file with the WebLM on page 50. are using TLS/SRTP before Media Encryption feature upgrading to Messaging enabled. 6.3.2. 2 Verify server roles and the See Verifying server roles and — AxC address. AxC address on page 50. 3 Verify the system topology. See Verifying the system — topology on page 51. 4 Configure languages. See Installing language — pack on page 51. 5 Add telephony domains. See Adding telephony — domain on page 54. 6 Set the telephony profiles. See Setting the telephony — profile on page 56. 7 Integrate with the telephony See Integrating with the — server. telephony server on page 56. 8 Migrate the dial plan data. See Migrating dial plan Perform this task only if you data on page 59. are upgrading from Messaging Release 6.0.1 SP3 or 6.1 SP3 to 6.3.2. 9 Set operator (live attendant) See Setting operator (live Perform this task only if you properties. attendant) properties on are upgrading from page 59. Messaging Release 6.0.1 SP3 or 6.1 SP3 to 6.3.2. 10 Administer caller See Caller applications — applications. overview on page 60. 11 Reload the application See Reloading application — server cache. server cache on page 62. 12 Upgrade the voice message See Upgrading the voice This procedure is form. message form on page 62. applicable only if you are
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 49 Comments? [email protected] Post-upgrade tasks
No. Tasks References Notes
using Exchange server as a storage server.
Installing a license file in WebLM Before you begin Obtain the license file from Avaya PLDS website at https://plds.avaya.com. Procedure 1. Log on to WebLM License Manager. 2. In the left navigation pane, click Install license. 3. On the Install license page, enter the license file path. You can also click Browse to select the license file. 4. Click Install to install the license file. WebLM displays a message on successful installation of the license file. The installation of the license file can fail for various reasons, such as: • When WebLM finds an invalid digital signature on the license file. If you get such an error, request PLDS to redeliver the license file. • The current capacity use exceeds the capacity in the installed license. Result After you install the license file, WebLM License Manager screen displays the installed license on the License Products screen. Ensure that Media Encryption feature is enabled.
Verifying server roles and the AxC address Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Server Settings > Server Role / AxC Address. 3. Verify the server roles and the AxC address and check that: a. The correct server role is selected in the Roles for this server drop-down list. b. The correct IP address is entered in the AxC Address section.
50 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Verifying the system topology
4. Make the required changes if the server roles and the AxC IP address are incorrect. Note: • If you change the server roles, you must restart Messaging and log in to Messaging System Management Interface again. • If you change the AxC IP address, ensure that the server at the IP address that you administer is an operational storage and AxC server.
Verifying the system topology Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Messaging System (Storage) > Topology. 3. Verify the topology and check that: a. The correct application server is listed. b. The sites are active on the correct server.
Configuring languages
Installing language packs About this task After upgrading the Messaging system, you must reinstall the language packs. You can download additional language packs from https://plds.avaya.com. The following system features use the languages that you select: • User Preferences • Telephony user interface (TUI) • Auto Attendant • Name playback Multiple languages for the Messaging pilot number and auto attendant are available only after you reinstall the language packs.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 51 Comments? [email protected] Post-upgrade tasks
Caution: Ensure that these language packs are compatible with the software that you upgraded. For information about the language packs, see Avaya Aura® Messaging Release Notes on Avaya Support website at http://support.avaya.com/Products/P0792. Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Server Settings (Application) > Languages. 3. In the Add Language Pack field, click Browse... and navigate to the location of the language packs that you want to add to this application server. 4. Click Upload. Note: When you add a language pack, the system drops all active calls. Additionally, the Messaging system is unavailable for a few minutes. 5. Enter appropriate information in the fields. For more information, see Languages field descriptions on page 52. 6. Click Apply.
Languages field descriptions
Name Description Language Packs: Installed Languages Name The list of language packs that you installed. User Selectable The language for User Preferences and TUI. If you install multiple languages, users can select their preferred language. Language Settings System Language The system uses the value in this field as a backup language setting in case the application server cannot obtain the site configuration from the storage server. The system uses the site language configuration to determine the language that the caller or the user hears. Default Subscriber UI Language The language of the user interface. The system uses the value in this field as a backup language setting in case the application server
52 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Configuring languages
Name Description cannot obtain the site configuration from the storage server. If you install multiple languages, users can select their preferred language. Language Packs Current Application software release The version number of the Messaging system. Add Language Pack Navigate to the location of the language packs that you want to add to this application server and upload the packs. Delete Language Pack Select and delete a language pack from the drop- down list of installed language packs. You cannot delete a language pack if the language: • Is selected by a local or remote user in User Preferences. • Is administered for a Messaging access number. • Is administered for Auto Attendant. • Is administered as System Language or Default Subscribe UI Language on the Languages webpage.
Supported languages The following table lists the languages that Messaging supports for voice messaging forms. Download the forms from http://
Language File name Arabic AvayaVoiceMessage_ar-SA.fdm Chinese-Peoples Republic of China AvayaVoiceMessage_zh-CN.fdm Chinese-Hong Kong AvayaVoiceMessage_zh-HK.fdm Dutch AvayaVoiceMessage_nl-NL.fdm English-US AvayaVoiceMessage_en-US.fdm English-UK AvayaVoiceMessage_en-UK.fdm French AvayaVoiceMessage_fr-FR.fdm French-Canadian AvayaVoiceMessage_fr-CA.fdm German AvayaVoiceMessage_de-DE.fdm Hebrew AvayaVoiceMessage_he-IL.fdm Italian AvayaVoiceMessage_it-IT.fdm
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 53 Comments? [email protected] Post-upgrade tasks
Language File name Japanese AvayaVoiceMessage_ja-JP.fdm Korean AvayaVoiceMessage_ko-KR.fdm Polish AvayaVoiceMessage_pl-PL.fdm Portuguese-Brazilian AvayaVoiceMessage_pt-BR.fdm Russian AvayaVoiceMessage_ru-RU.fdm Spanish AvayaVoiceMessage_es-ES.fdm Spanish-Latin American AvayaVoiceMessage_es-XL.fdm Swedish AvayaVoiceMessage_sv-SE.fdm Turkish AvayaVoiceMessage_tr-TR.fdm
Administering telephony domain
Telephony administration After upgrading to Messaging, the Sites webpage remains in a read-only mode because the system cannot find a value for the new field, Telephony Profile Name, on the Sites webpage. To resolve the issue, define the necessary Telephony profiles on the Telephony Domain webpage. When you save the changes to the Telephony Domains page, the system pushes the changes to the applications server and overwrites current data.
Adding telephony domains Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Telephony Settings > Telephony Domains. 3. Enter the appropriate information in the fields. For more information, see Telephony Domains field descriptions on page 55. 4. Click Save. The system displays a dialog box to confirm that system restart might require to push the configuration changes. Note: When you save the changes, the system pushes the changes to the application server and overwrites current data.
54 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Administering telephony domain
5. Click OK. The system displays a dialog box to confirm that system configuration modified successfully.
Telephony Domains field descriptions Administer the telephony domain parameters that Messaging uses. Far-end Domains Name Description Far-end Domains The number of far-end SIP domains. SMI displays the number of rows that are equal to the number of far-end SIP domains that you select from the drop-down list. You can add a maximum of 500 SIP domains. Delete The check box to delete a far-end domain row. Select the check box for the far-end domain row to delete. Telephony Profile Name The name for the telephony profile that represents a gateway ID and SIP domain of the application server. The name can contain alphanumeric characters along with a dash (-), underscore (_), and period (.). Gateway ID The ID of the far-end connection gateway. Messaging SIP Domain The name of the Messaging SIP domain. Far-end SIP Domain The name of the far-end connection SIP domain.
Far-end Connections Name Description Far-end Connections The number of connections to the far-end SIP proxy servers. SMI displays the number of rows that are equal to the number of far-end SIP domains that you select from the drop-down list. You can add a maximum of 25 far-end connections. Delete The check box to delete a far-end connection row. Select the check box for the far-end connection row to delete. Gateway ID The ID of the far-end connection gateway. IP The IP address of the far-end connection. Transport The transport method that the telephony server uses for SIP signaling. The transport method of the
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 55 Comments? [email protected] Post-upgrade tasks
Name Description application server and the telephony server must match. The types of transport methods are: • TCP: Not encrypted. Use port 5060. This is the default value. • TLS: Encrypted. Use port 5061. Port The port number of the far-end connection. The default value is 5060. Monitor Interval The option to administer monitoring of a far-end connection in minutes. The default value is 0 minutes. If you set the value to 0, Messaging does not monitor the far-end connection.
Setting the telephony profile Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Messaging System (Storage) > Sites. 3. From the Telephony Profile Name drop-down list, select the appropriate telephony profile name. 4. Restart Messaging.
Integrating with the telephony server Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Telephony Settings (Application) > Telephony Integration. 3. Enter the appropriate information in the fields. For more information about administering the telephony integration parameters, see Telephony Integration field descriptions on page 57. 4. Click Save. 5. Restart the telephony processes by clicking one of the following: • Restart Immediate to restart the telephony processes immediately. • Restart Camp-on to wait for all calls to end and restart the telephony processes.
56 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Administering telephony domain
Telephony Integration field descriptions BASIC CONFIGURATION Name Description Switch Integration Type The type of switch integration that Messaging uses. The SIP SPECIFIC CONFIGURATION section is available only for SIP integration. IP Address Version The version of the IP address.
SIP SPECIFIC CONFIGURATION SMI displays the following section only if you click SIP from the Switch Integration Type field. On the Telephony Integration page, you have read-only access to these fields. You can administer these fields on the Telephone Domains page.
Name Description Far-end Domains The number of far-end SIP domains. SMI displays the number of rows that are equal to the number of far-end SIP domains that you select from the drop-down list. You can add maximum 500 SIP domains. SIP Domain The domain names of the application server and the far-end connection. For example, sip.example.com. • Telephony Profile Name: The name of the telephony profile that represents a gateway ID and SIP domain of the application server. • Gateway ID: The ID of the far-end connection gateway. • Messaging SIP domain: The name of the Messaging SIP domain. • Far-end domain: The name of the far-end connection SIP domain. Far-end Connections The number of connections to the far-end SIP proxy servers. SMI displays the number of rows that are equal to the number of far-end SIP domains that you select from the drop-down list. You can add maximum 25 far-end connections. Connection The connection details of a far-end connection that includes: • Gateway ID: The ID of the far-end connection gateway. • IP: The IP address of the connection.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 57 Comments? [email protected] Post-upgrade tasks
Name Description • TCP or TLS: The transport method that the telephony server uses for SIP signaling. The transport method of the application server and the telephony server must match. The types of transport methods are: - TCP: Not encrypted. - TLS: Encrypted. • Port: - TCP: 5060 - TLS: 5061 • Monitor interval Messaging Address The IP address of the near-end application server. This address is always a read-only field. • IP: Use the IP address of the server. • TCP Port: Use port 5060. • TLS Port: Use port 5061. Messaging Ports The maximum number of active calls to or from a user. • Call Answer Ports: The range of the ports, which is from 2 to 100. • Maximum: The maximum number of ports that Messaging uses. • Transfer Ports: The maximum number of transfer ports that Messaging uses. Switch Trunks The number of trunk members for Messaging on the telephony server. • Total: The total number of trunks administered. Messaging requires at least one more port than the number of ports that you administer in Call Answer Ports. • Maximum: The telephony server supports maximum 120 trunk members. The trunk members, in addition to the call answer ports, are for features such as the transfer feature, which require more switch trunks. If the telephony server specifies the maximum number of trunks, the number in the Switch Trunks field must match the number on the telephony server.
58 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Migrating the dial plan data
Migrating the dial plan data
Important: Perform this task only if you are upgrading from Messaging Release 6.0.1 SP3 or 6.1 SP3 to 6.3.2. About this task After upgrading the Messaging system, you must reenter the dial plan data properties. Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Messaging System (Storage) > Sites. 3. Enter the appropriate information in the following fields: a. Site External (Public Network) Dial Plan b. Site Internal Dial Plan c. Toll-Free and Premium Calls d. Local Calls 4. Click Save. 5. Restart Messaging.
Setting operator (live attendant) properties
Important: Perform this task only if you are upgrading from Messaging Release 6.0.1 SP3 or 6.1 SP3 to 6.3.2. About this task After upgrading the Messaging system, you must reenter the operator (live attendant) properties. The properties of a Site automatically propagate to the active application servers of that site. Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Messaging System (Storage) > Sites. 3. Reenter the values in the Operator (Live Attendant) section. The following table maps the properties of Release 6.0.1 to Release 6.1 and 6.2:
Release 6.01 Release 6.1/6.2 Schedule type Availability
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 59 Comments? [email protected] Post-upgrade tasks
Release 6.01 Release 6.1/6.2 Attendant (operator) extension Operator (live attendant) extension General delivery mailbox number General mailbox 4. Click Save.
Administering caller applications
Caller applications overview Caller applications enhance the TUI with custom menus and prompts that guide callers to the appropriate recipient. A caller application contains all custom menus and prompts associated with a unique mailbox. When you create a caller application, you associate the caller application with a site. The storage server for that site deploys the caller application to each application server in the cluster. You can use the Microsoft Management Console (MMC) to import and export caller applications as XML data to other storage servers in a multisite environment. Because Messaging stores each caller application as an LDAP Contact in a central mailbox, the system backs up caller applications each time that you back up the message store. Caller Application contains three types of information: • Application management data • Application structure • Application prompts Application prompts occupy the largest amount of space. The maximum size of a Caller Application must be equal to or higher than the amount of space that the application prompts occupy. Important: Caller applications require all servers to run the same Messaging release. Running different Messaging releases in servers might affect the functioning of some features.
Caller Applications Editor
Use Caller Applications Editor to create custom menus and to configure caller application properties. In the Messaging environment, caller applications perform the same functions as Automated
60 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Administering caller applications
Attendants. Caller Applications Editor runs as a plug-in within the MMC. You can gain access to information about MMC through the MMC Help menu.
System requirements • A computer that is running one of the following operating systems: - Windows Server 2003 - Windows Server 2008 - Windows XP - Windows Vista - Windows 7 32–bit - Windows 7 64–bit • The following software from the Microsoft Download Center: - MMC 3.0 - .NET 3.5 or later • Administrative permissions on the computer.
Upgrading Caller Applications Editor Procedure 1. In your browser, type the following URL: https://
Logging in to Caller Applications Editor Before you begin • All required software is loaded on your computer. • Note the IP address or DNS of the storage server. • Note the password for Caller Applications Editor. The default password is caadmin01. Procedure 1. Click Start > All Programs > Avaya Connector > Avaya AxC CallerApps. 2. Enter the following information in the Connect to Messaging AxC fields: • AxC address: The IP address or DNS of the storage server.
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 61 Comments? [email protected] Post-upgrade tasks
• Password: The password for Caller Applications Editor. 3. Click OK. Caller Applications Editor displays the IP address of the AxC connector in the title bar and the navigation pane.
Updating a caller application Procedure 1. In Caller Applications Editor, open the Properties dialog box for the caller application. 2. Click Ok.
Reloading application server cache Procedure 1. Log on to Messaging System Management Interface. 2. On the Administration menu, click Messaging > Advanced (Application) > System Operations. 3. In Reload Caches, click Reload next to the following fields: a. User List b. Global Address List c. System Greeting The system displays the Operation in progress dialog box. When the system completes the reload operation, the dialog box disappears. 4. Click Synchronize to synchronize the ADCS.
Upgrading the voice message form Before you begin Ensure that you have: • A System Folder on the Exchange server that contains one Organizational Forms Library for each language in a multilingual deployment. • An account with client permissions for administering the Organizational Forms Library. • Completed either of the following: - Configured the avayamsg A or CNAME record in DNS.
62 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Upgrading the voice message form
- Recorded the host name or IP address of a Messaging server. About this task You must upgrade the voice message form on a computer that runs Outlook. This procedure is applicable only if you are using Exchange server as a storage server. Procedure 1. Log in with the user account with client permissions that you created in the EFORMS REGISTRY. 2. On a web browser: a. Type
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 63 Comments? [email protected] Post-upgrade tasks
If you are deploying multiple languages, repeat Step 8 through Step 14 for each language form. 13. Click Close. 14. Click OK three times to exit. When a user opens a voice message, the appropriate voice messaging form downloads automatically.
64 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Chapter 6: System testing and commissioning
Basic call answer and Messaging functions verification checklist Before you begin: • Administer telephony domains. • Migrate dial plan data. Tasks Steps Result and validation Basic call answer Perform the following: Observe the following: Test 1 • Caller hears the personal greeting. • From the extension of User 2, call the direct extension number • The system plays the greeting of User 1 and let the call roll for User 1. over to the voice mail. • MWI changes to On for User 1. • Leave a message. Note user • Email notification delivery, text details and the date and the time message notification delivery, when the message is sent. and subject line. • Hangup. - Voice Message from User 2 Test 2 (ext#here)) for first call. • From an outside number, dial - Voice Message from the external Pilot number and (external#here) for second connect to User 1 extension. call. • Leave a message. Note the This validates: outside number and the date • Basic Call Answering and time when the message is sent. • Basic MWI functionality • Hang up. • Email notifications For more information, see Using • Text message notifications Avaya Aura® Messaging. • Subject line matching
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 65 Comments? [email protected] System testing and commissioning
Tasks Steps Result and validation Basic messaging Perform the following: Observe the following: • From the extension of User 1, • User 1 has two messages in the call the internal pilot number. inbox with the appropriate time. • Provide the password to log in to • MWI updates to Off for User 1. the system. This validates: • Listen to both messages. Do not • Message retrieval through TUI. delete the messages. • MWI updates. • Observe whether MWI turns Off. • Subject line matching. For more information, see Using Avaya Aura® Messaging.
66 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected] Index
A security ...... 8 single server systems ...... 8 accessing user functions ...... 9 Caller Applications Editor ...... 61 document changes ...... 7 adding telephony domains ...... 54 application server cache E reloading ...... 62 Exchange server ...... 62 attended backup ...... 34 F B field descriptions backing up backup screen ...... 35 system ...... 34 current alarms ...... 23 System Platform ...... 32 language packs ...... 52 Backup page telephony domain ...... 55 field descriptions ...... 33 telephony integration ...... 57 backup screen field descriptions ...... 35 I C installing ...... 44 Caller Applications Editor ...... 61 Caller Applications ...... 60 language ...... 51 system requirements ...... 61 IP address updating ...... 62 assignments for Cdom and SAL Gateway ...... 26 Caller Applications Editor ...... 60 installing ...... 61 logging in ...... 61 L Cdom and SAL Gateway language IP address assignments ...... 26 installing ...... 51 checking voice messaging forms ...... 53 RAID battery status ...... 22 language packs SAL Gateway ...... 40 field descriptions ...... 52 checklist recording ...... 25 Messaging configuration ...... 65 license file postupgrade configuration ...... 49 installing ...... 50 CNAME ...... 62 logging in current alarm to Caller Applications Editor ...... 61 viewing ...... 22 current alarms field descriptions ...... 23 M
Messaging ...... 41 D upgrade ...... 41 upgrade paths ...... 17 data gathering ...... 15 Messaging template ...... 17 dial plan data migrating migrating ...... 59 dial plan data ...... 59 DNS record ...... 62 documentation ...... 7 administration ...... 8 O hardware ...... 9 overview ...... 8 operator properties
December 2014 Upgrading Avaya Aura® Messaging for Single Server Systems 67 Comments? [email protected] Index
operator properties (continued) System Platform setting ...... 59 upgrading ...... 36 Organizational Forms Library ...... 62 System Platform upgrade overview verifying ...... 39 single-server configuration ...... 31 System Platform Web Console logging ...... 32 system requirements P Caller Applications ...... 61 patch detail field descriptions ...... 47 T patches ...... 44 installing ...... 44 telephony patch installation ...... 43, 47 administration ...... 54 Patch List page integration ...... 56 field descriptions ...... 48 telephony domain platform upgrade page field descriptions ...... 55 field descriptions ...... 38 telephony integration port field descriptions ...... 57 UDP range ...... 57 telephony server prerequisite integration ...... 56 assigning new IP addresses to Cdom VM and embedded training courses ...... 10 SAL Gateway on-site ...... 29 assigning new IP addresses to the Cdom VM and embedded SAL Gateway remotely ...... 27 U prerequisites ...... 20 UDP port ...... 57 preupgrade upgrade requirements ...... 12 paths ...... 17 upgrade paths ...... 17 R upgrade process ...... 31 upgrading ...... 41 recording System Platform ...... 36 AxC address ...... 25 voice message form ...... 62 language packs ...... 25 operator properties ...... 24, 25 server roles ...... 25 V system topology ...... 26 validating telephony integration data ...... 24 Messaging configuration ...... 65 reloading verify ...... 47 application server cache ...... 62 verifying ...... 47 AxC address ...... 50 S server roles ...... 50 System Platform upgrade ...... 39 search local and remote patch system platform version ...... 21 field descriptions ...... 45 system topology ...... 51 Search Local and Remote Template page videos ...... 10 field descriptions ...... 42 Virtual Machine Management page server field descriptions ...... 38, 42 Exchange ...... 62 voice message form SIP proxy ...... 56 upgrading ...... 62 telephony ...... 56 voice messaging form setting languages supported ...... 53 operator properties ...... 59 telephony profile ...... 56 support ...... 11 system backing up files ...... 34
68 Upgrading Avaya Aura® Messaging for Single Server Systems December 2014 Comments? [email protected]