AE Services 6.1 Super Patch 2 Release Notes

Transcription

1 AE Services 6.1 Super Patch Release Notes March 14, 011 Virtual Appliance, Bundled Server, and Software Only File Name: 61_0_SuperPatch_.zip File Size: 107 MB (11 1, ,887 Bytes) MD5 Checksum: 1f51de048b768453c4073b11c9ba841 c9ba841 What is fixed in this Patch? This patch contains the following update to Cert Management: Issue AES84158: Replaced the WebLM pkcs1 file which will expire on March 1, 011. Added the new Avaya SIP CA certificate which was used to sign the new WebLM server certificate. Note ote: Please refer to PSN311 for more general information on the WebLM Root Certificate Expiration Issue. The following issues have been resolved for the DMCC Service: Issue AES848919: SIP stack changes: New parameters have been added to the /opt/mvap/user-configuration.properties file: 1. cmapi.nist_ssl_socket_backoff: The interval of time in milliseconds between server attempts to establish an outbound TLS socket connection after a timeout.. cmapi.nist_ssl_socket_retry: The server will attempt to re-establish an outbound TLS socket connection multiple times after a failure occurs if set to true. 3. cmapi.nist_ssl_socket_timeout: The interval of time in milliseconds that the server waits for a TLS socket connection to be established. Issue AES8597: The DMCC Service SIP stack now sends a SIP 481 response to a re-invite or an INFO request if a dialog does not exist for the request. AE Services 6.1 Super Patch Release Notes 1

2 Issue AES849831: Previously, an attempt to register an extension via Device & Media Call Control (DMCC) would sometimes fail, with the server logs indicating that the registration failed due to an "ICV authentication error". This would cause DMCC to mark the gatekeeper (CLAN or Processor Ethernet IP address that was used) as unavailable. Thus, any further attempts to register using that gatekeeper would be blocked. It is now guaranteed that, if an ICV authentication error occurs, the gatekeeper is not marked as unavailable. Issue AES8563: ARQ Timer Cancellation When a DMCC endpoint is initially registered, if the client application sends two or more switchhook requests (on/off-hook) before CM can connect the Q931 signaling channel, then the endpoint may not register correctly. This MR ensures that the registration will complete successfully under these circumstances. Issue AES78553: Previously, if a user browsed to Status Status and Control DMCC Service Summary, in the AE Services Management Console, the screen was unable to display clients connected via TR-87. Issue AES85840: Previously, a client application specified both a telecommuter extension and an RTP IP address in the same RegisterDevice request. However, these two parameters are considered contradictory in nature, and are flagged as an error in later releases of AE Services. However, AE Services releases prior to R4..3 did not flag this combination as an error. Thus the application that used to work with AE Services prior to R4..3, no longer worked correctly with later releases. This patch ensures that such applications can still work with later releases of AE Services. Issue AES856673: Previously, when 'Bridged alert appearance' was enabled, the exception rules with stations were ignored. The following issues have been resolved for the SNMP Service ervice: Issue AES85887: Previously, notification was not issued after installing or upgrading to AE Services 6.1. AE Services 6.1 Super Patch Release Notes

3 The following issues have been resolved for the TSAPI Service: Issue AES855956: Previously, there was a TDI memory leak in the TSAPI Service. The G3PD may leak TSDI buffers when processing ASAI REDIRECTED events. Eventually, the TSAPI Service will activate flow control and will not accept any more requests. What AE Services rpm/s is updated by AE Services 6.1 Super Patch? aesvcs-callcontrol i386.rpm aesvcs-certmgmt-config noarch.rpm aesvcs-platform noarch.rpm aesvcs-tomcat-config noarch.rpm aesvcs-watchdog-config noarch.rpm Are there e new features or enhancements included in AE Services 6.1 Super Patch? n/a What must application suppliers do to be compatible with AE Services 6.1 Super Patch? (recompile, re-link, etc.) Super Patch is fully compatible with AE Services 6.1.x Clients and SDKs. Is applying this patch service affecting? The Application Enablement Server will be out of service for 0 to 30 minutes while the patch is being applied. With which Application Enablement Services release(s) is Super Patch compatible? AE Services 6.1. Is AE Services 6.1 Super Patch cumulative? n/a. Can AE Services 6.1 Super Patch be installed on Application Enablement Services 3.x, 4.x, or 5.x servers? No. AE Services 6.1 Super Patch is supported with AE Services 6.1 only. AE Services 6.1 Super Patch Release Notes 3

4 What are the CM requirements for Application Enablement Services 6.1 Super Patch? AE Services 6.1 Super Patch supports CM 4.x or later. Note: certain functionality on AES 6.1 requires CM versions later than CM 5.x Is there any specific action to be carried out when used with an AACC? Yes, in the case of AACC HA Deployments, settings need to be changed as follows: 1. Start a console session on the AE Server (locally, via service port, or remotely, using e.g. putty) Login as sroot or root Uncomment and set the properties in /opt/mvap/conf/user-configuration.properties as listed below: ######################################################################### # # cmapi.nist_ssl_socket_retry: The server will attempt to re-establish an # outbound TLS socket connection multiple times after a failure occurs if # set to true. # # cmapi.nist_ssl_socket_timeout: The interval of time in milliseconds # that the server waits for a TLS socket connection to be established. # ######################################################################### cmapi.nist_ssl_socket_retry=false cmapi.nist_ssl_socket_timeout=1000. Log into the AE Services Management Console using a browser. Set the parameter Network TCPSettings TCP Retransmission Count to How do I install l the patch? AE Services 6.1 Super Patch Release Notes 4

5 Before beginning the installation of the Patch, check the md5 checksum of the file. Run the following command: md5sum 61_0_SuperPatch_.zip Note: If the MD5 checksum does not match what is stated at the beginning of these Release Notes, do not proceed with the installation of the patch. Download the patch and check the MD5 checksum again. Backup the AE Services database before applying AE Services 6.1 Super Patch. Follow these steps to back up the AE Services database: 1. Log into the AE Services Management Console using a browser.. From the main menu, select Maintenance Server Data Backup. AE Services backs up the database, and displays the Database Backup page, that displays the following message: The backup file can be downloaded from here. 3. Click the "here here" link. A file download dialog box is displayed, that allows you to either open or save the backup file (named as: mvapdbddmmyyyy.tar.gz, where ddmmyyyy is a date stamp). 4. Click Save, and download the backup file to a safe location that the upgrade will not affect. For example, save the file to your local computer or another computer used for storing backups. How do I install Super Patch? A. Patch Installation Instructions for Virtual Appliance Offer (AE Services on System Platform) 1. On the System Platform Webconsole, click on Server Management Patch Management Download/Upload. Choose the source of the patch (PLDS, HTTP, SP server, devices on SP server, or local to your PC). 3. After it has been uploaded to the SP server, click on Manage (from the Patch Management agement menu). Now you ll see the available patch waiting for installation below the caption AES. 4. Once you re ready, click on the PatchID link, finally on the Install button. 5. Follow the on-screen instructions. AE Services 6.1 Super Patch Release Notes 5

6 B. Patch Installation Instructions I for Bundled Server or Software Only systems: 1. Start a console session on the AE Server (locally, via service port, or remotely, using e.g. putty). Login as sroot or root 3. Copy 61_0_SuperPatch_.zip to /tmp directory on the Application Enablement Server 4. Run the following from the command line: cd /tmp update -u --force 61_0_SuperPatch_.zip Note: the option --force is not required if this is the first patch to be installed 5. Follow the on-screen instructions After applying Super Patch, reboot the AE Server ver. On Bundled Server or Software Only systems, this can be done from the command line by running the command shutdown r now On a System Platform, this can be done as follows: 1. On the System Platform Webconsole, click on Virtual Machine Management Manage.. On the Manage Virtual Machines page, click on Application Enablement Services 3. On the Application Enablement Services page, click on Reboot Post Patch Installation verification: 1. Start a console session on the AE Server (locally, via service port, or remotely, using e.g. putty). Login as sroot or root 3. Run the following command to verify the installation of Super Patch : swversion The swversion command should return one of the following ************* Patch Numbers Installed in this system are ************* ==== ==== In case you used swversion -a, the rpms will be listed as well below the patch number: AE Services 6.1 Super Patch Release Notes 6

7 ************* Patch Numbers Installed in this system are ************* ==== aesvcs-callcontrol i386.rpm aesvcs-certmgmt-config noarch.rpm aesvcs-platform noarch.rpm aesvcs-tomcat-config noarch.rpm aesvcs-watchdog-config noarch.rpm ==== Note: Instead of the steps 1-3 as listed above, you can use the same procedure as described at the beginning of this section for AES on System Platform (which does not require a console login). 4. Log into the AE Services Management Console using a browser. 5. From the main menu, click Status. 6. On the Status page, verify that all previously licensed services are running. 7. Validate the server configuration data, as follows: a. From the main menu, click Networking. b. Under AE Service IP (Local IP), verify that the settings are correct. c. Under Network Configure, verify that the settings are correct. d. Under Ports, verify that the settings are correct. 8. Check all of the remaining Management Console pages listed under AE Services and Commun munic ication Manager Interface. Verify that the information is complete and correct. This completes the installation of Super Patch. Use the following procedure only if the AE Server configuration data has changed. 1. From the main menu, select Maintenance Server Data Restore. OAM displays the Restore Database Configuration page. The initial state of the Restore Database page provides you with two basic functions: Text box with the Browse button, which provides the means to select a backup file to use for the Restore process. Alternatively, you can type a fully qualified name of the backup file in the text box. Restore button, that starts the Restore process. Click Browse and locate the AE Services database backup file that you intend to use (For example: mvapdb tar.gz). 3. Click Restore. OAM redisplays the Restore Database Configuration page, with the following message. "A database restore is pending. You must restart the Database Service and the AE Server for the restore to take effect. To restart these services now, click the Restart Services button below." 4. Click Restart Services. AE Services 6.1 Super Patch Release Notes 7

8 AE Services restarts the Database Service and the AE Server, thereby completing the Restore process. How do I remove Super Patch? A. Patch Removal Instructions for Virtual Appliance Offer (AE Services on System Platform) The Patch can be uninstalled as follows: 1. On the System Platform Webconsole, click on Server Management Patch Management Manage. Now you ll see the installed patch as active.. Click on the PatchID link, finally on the Remove button. 3. To also remove the patch file itself, click on the Remove Patch File button (optional). B. Patch Removal Instructions for Bundled Server or Software Only systems: 1. Start a console session on the AE Server (locally, via service port, or remotely, using e.g. putty). Login as sroot or root 3. Run the following from the command line: update -e 4. Follow the on-screen instructions Do I have to perform any additional steps if I am uninstalling the patch? No AE Services 6.1 Super Patch Release Notes 8