Product Support Notice Patch Notes
Total Page:16
File Type:pdf, Size:1020Kb
Product Support Notice © 2017 Avaya Inc. All Rights Reserved. PSN # PSN005034u Original publication date: 12 July 2017 This is Issue #01, published date: 12 July Severity/ Medium Urgency When convenient 2017. risk level Name of problem ASBCE 7.2 GA has problems with detection of dtmf/SIP INFO, simplified contact dialing, and re-invite filtering for MOBX- CS1k Integration. Products affected Avaya Session Border Controller for Enterprise (ASBCE) 7.2 GA (7.2.0.0-18-13712) Description This patch (sbce-7.2.0.0-18-13712-hotfix-06272017.tar.gz) addresses the following issues in Release 7.2 GA: Issue ID Issue Description AURORA-11725 Unable to detect dtmf/SIP INFO. AURORA-11796 Simplified contact dialing does not work. AURORA-11760 Re-invite filtering does not work. Resolution Install the sbce-7.2.0.0-18-13712-hotfix-06272017.tar.gz patch on EMS, SBCE, and Standalone SBCE, that is, EMS+SBCE only. This is a cumulative patch and contains all the fixes provided in patch sbce-7.2.0.0-18-13712- hotfix-06012017.tar. This patch can either be installed over 7.2 GA (7.2.0.0-18-13712) version or on top of patch sbce-7.2.0.0-18-13712-hotfix-06012017.tar. File name : sbce-7.2.0.0-18-13712-hotfix-06272017.tar.gz md5sum : 21c2744f34c9c9f8b254f6aa229ff9a3 PLDS Download ID : SBCE0000091 Make sure that you install the patch during a maintenance window to avoid service disruption. Workaround or alternative remediation n/a Remarks Patch Notes The information in this section concerns the patch, if any, recommended in the Resolution above. Backup before applying the patch Take a backup of ASBCE and save it on an external storage. Download Download the patch from https://plds.avaya.com Download ID: SBCE0000091 Patch install instructions Service-interrupting? Y The patch must be installed on a 7.2 GA version of ASBCE. Install the patch on EMS and SBCE. Note: For HA SBCE, install the patch first on a secondary SBCE and perform failover. Later, install the patch on a new secondary SBCE. Note: Make sure that you install the patch during a maintenance window to avoid service disruption. 1. Copy the patch file to the /home/ipcs directory on all SBCEs using any SFTP client, for example, WINSCP. 2. Log in to the CLI of SBCE as user ipcs. 3. Switch user to root by running the command: su – root 4. Change directory to /home/ipcs by running the command: cd /home/ipcs 5. Verify that md5sum of the patch file matches the md5sum on PLDS, that is, 21c2744f34c9c9f8b254f6aa229ff9a3 md5sum sbce-7.2.0.0-18-13712-hotfix-06272017.tar.gz 6. In the /usr/local/ipcs/ directory, create a directory called Patch. mkdir /usr/local/ipcs/patch 7. Copy the patch to /usr/local/ipcs/patch/ cp sbce-7.2.0.0-18-13712-hotfix-06272017.tar.gz /usr/local/ipcs/patch/ 8. Change the directory to /usr/local/ipcs/patch/. cd /usr/local/ipcs/patch/ 9. Untar the patch file: tar –zxvf sbce-7.2.0.0-18-13712-hotfix-06272017.tar.gz –C /usr/local/ipcs/patch/ 10. Stop the application by running the command: /etc/init.d/ipcs-init stop 11. Run the install_hotfix.sh script: sh install_hotfix.sh 12. After the script is run successfully, reboot SBCE. /sbin/reboot 13. Check the output of the ipcs-version command. The application version and the GUI Module version should be 7.2.0.0-13761 Follow the same procedure to install the patch on other SBCE instances. Verification n/a Failure n/a Patch uninstall instructions Service-interrupting? Y Note: For HA SBCEs, uninstall the patch first on a secondary SBCE and perform the failover. Later, uninstall the patch on a new secondary SBCE. Uninstall the patch on EMS and SBCE. Note: Make sure that you uninstall the patch during a maintenance window to avoid service disruption. 1. Log in to the CLI of SBCE as user ipcs. 2. Switch user to root: su – root 3. Change the directory to /usr/local/ipcs/patch/. cd /usr/local/ipcs/patch/ 4. Untar the patch file if required or if the folder is empty: tar –zxvf sbce-7.2.0.0-18-13712-hotfix-06272017.tar.gz –C /usr/local/ipcs/patch/ 5. Stop the application by running the command: /etc/init.d/ipcs-init stop 6. Uninstall the patch: sh remove_hotfix.sh 7. After the script is run successfully, reboot the SBCE: /sbin/reboot 8. Check the output of the ipcs-version command. The application version and PCF Module version should be 7.2.0.0-18-13712. Follow the same procedure to uninstall the patch on other ASBCE instances. Security Notes The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks N/A Avaya Security Vulnerability Classification Not Susceptible Mitigation N/A If you require further information or assistance please contact your Authorized Service Provider, or visit support.avaya.com. There you can access more product information, chat with an Agent, or open an online Service Request. Support is provided per your warranty or service contract terms unless otherwise specified in the Avaya support Terms of Use. Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED “AS IS”. AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS “AVAYA”), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS’ SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA. All trademarks identified by ® or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. .