Avaya Session Border Controller for Enterprise 7.0 Release Notes

Avaya Session Border Controller for Enterprise 7.0 Release Notes Release 7.0 Issue 2 July 2016 1

Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site: http://support.avaya.com License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE http://support.avaya.com/licenseinfo/ ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s) Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server. 2

Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://support.avaya.com/thirdpartylicense/ Preventing toll fraud "Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: http://support.avaya.com Trademarks Avaya and the Avaya logo are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: http://support.avaya.com Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Support Web site: http://support.avaya.com 3

Table of Contents Overview... 5 Documentation... 5 New features and enhancements... 6 SIPREC... 6 End to End Security... 6 Avaya SBCE support for Serviceability Agent... 6 Support for IP Office trunk from a dynamic IP address... 7 Reuse of connection established by IP Office for delivering calls... 7 Secure Client Enablement Services proxy... 7 Support for using non-unique IP address for multiple data interfaces on Avaya SBCE... 7 Support for integrated Dell Remote Access Card and integrated Lights-Out... 7 Media encryption by using AES-256... 7 Unsupported hardware for this release... 7 List of known issues and workarounds... 8 4

Overview This document provides information about the new features/enhancements in ASBCE Release 7.0, and the known issues for this release. Documentation The latest documentation for 7.0 is available on support.avaya.com. No. Title Link 1. Avaya Session Border Controller for Enterprise Overview and Specification 2. Deploying Avaya Session Border Controller for Enterprise 3. Deploying Avaya Session Border Controller in Virtualized Environment 4. Upgrading Avaya Session Border Controller for Enterprise 5. Administering Avaya Session Border Controller for Enterprise 6. Troubleshooting and Maintaining Avaya Session Border Controller for Enterprise 7. Avaya SBCE 7.0 Security Configuration and Best Practices Guide https://downloads.avaya.com/css/p8/documents/101013691 https://downloads.avaya.com/css/p8/documents/101013756 https://downloads.avaya.com/css/p8/documents/101013935 https://downloads.avaya.com/css/p8/documents/101014042 https://downloads.avaya.com/css/p8/documents/101014037 https://downloads.avaya.com/css/p8/documents/101014063 https://downloads.avaya.com/css/p8/documents/101014066 5

New features and enhancements Following new features and enhancements are added in this release. SIPREC Avaya SBCE enhances its functionality to deliver SIP call recording with support for the SIPREC standard using the ASBCE as the recording client for call flows that traverse the ASBCE. With the SIPREC-based recording solution, Avaya SBCE supports full-time session recording. Every communication session connected to the SIP recoding device by using Avaya SBCE can be recorded. The Avaya SBCE SIPREC recording is fully tested and aligned with Avaya s Work Force Optimization solution leveraging the Avaya Call Recorder. Other third party session recording devices that align with the SIPREC standard may be tested through Avaya s DevConnect process. SIPREC-based recording invokes two sessions on ASBCE, one for the call session and one for the replicated session to the call recording device. Avaya SBCE supports a SIP-based media recording (SIPREC) solution with the following components: Avaya SBCE as the SIP Recording Client (SRC) Avaya Contact Recorder as the SIP Recording Server (SRS) Application Enablement Services for CTI integration Contact Center Application Servers such as Avaya Aura Contact Center and Call Center Elite Media anchor points such as Avaya Aura Media Server or Communication Manager Media Gateway You must have a SIP trunk on Avaya SBCE to ensure that SIPREC functions correctly. SIPREC is not supported if you use overlapped IPs in the Avaya SBCE deployment. End to End Security Avaya endpoints can display an end-to-end secure indicator for calls that use the secure protocols TLS and SRTP. Avaya SBCE provides a Securable field on the Server Configuration page to indicate whether the server is securable. Avaya SBCE uses the Av-Secure-Indicator header to determine whether the trunk or call server is using secure protocols, and sets appropriate values for the header. To use this feature, you must have Avaya Aura 7.0. Avaya SBCE support for Serviceability Agent Avaya SBCE contains Serviceability Agent which monitors faults on the system. Serviceability Agent sends SNMPv2c and SNMPv3 notifications to configured destinations through the net-snmp master agent. With the support for Serviceability Agent, you can use Avaya SBCE to: Manage SNMPv3 users Manage SNMP trap destinations Create, edit, and view SNMP trap profiles 6

Support for IP Office trunk from a dynamic IP address Avaya SBCE supports an IP Office trunk originating from dynamic IP addresses. Reuse of connection established by IP Office for delivering calls Avaya SBCE reuses the TLS connection from IP Office for SIP signaling towards the IP Office. The routing profile towards the Remote Branch Office must use a routing entry that matches the server configuration for the Remote Branch Office. For Remote Branch Office routing entries, the transport must be TLS and the Port field must be empty. Secure Client Enablement Services proxy To provide CES services to Avaya one-x Mobile clients outside the enterprise network, Avaya SBCE provides a secure proxy that must be deployed in the enterprise DMZ. Avaya SBCE checks all traffic from Avaya one-x Mobile clients outside the enterprise network to the CES server. Support for using non-unique IP address for multiple data interfaces on Avaya SBCE Avaya SBCE supports the use of the same IP address on multiple data interfaces in Avaya SBCE. With support for using the same IP address more than one time, more than one user can use the same IP address to connect to Avaya SBCE. Support for integrated Dell Remote Access Card and integrated Lights-Out Avaya SBCE supports integrated Dell Remote Access Card (idrac) on Dell R630 and HP integrated Lights-Out (ilo) on HP DL360 G9. Media encryption by using AES-256 Release 7.0 onwards, Avaya SBCE supports media encryption by using AES-256. To provision this feature, Avaya SBCE supports the following crypto suites: AES_256_CM_HMAC_SHA1_32 AES_256_CM_HMAC_SHA1_80 For information about new features for Release 7.0, see Avaya Session Border Controller for Enterprise Overview and Specifications and Administering Avaya Session Border Controller for Enterprise. From Release 7.0, a single ova file is available to deploy EMS and Avaya SBCE. For information about deploying Avaya SBCE, see Deploying Avaya Session Border Controller for Enterprise and Deploying Avaya Session Border Controller in Virtualized Environment. For information about upgrading to Release 7.0, see Upgrading Avaya Session Border Controller for Enterprise. Unsupported hardware for this release Avaya SBCE does not support upgrades to Release 7.0 on Amax and HP DL360 G7 servers. The system displays a message regarding unsupported hardware on the EMS web administration page and the log file /archive/log/upgrade.log. Any attempt for fresh installation will show a message on the VGA or SERIAL console regarding unsupported hardware. For information about supported hardware and 7

recommendations for migrating from Amax and HP DL360 G7 servers, see Upgrading Avaya Session Border Controller for Enterprise. For upgrade failure on an HP ProLiant 360 G7 server that is being used as a standalone server, the server is set to UPGRADING state. In order to set the server back to COMMISSIONED mode, run the following command on the SSH session: /usr/local/solid/bin/solsql x returnerroronexit a e "update global_nodes set STATE='COMMISSIONED' where node_id=1" "tcp 127.0.0.1 1320" savon savon List of known issues and workarounds 1. Roll back from Release 7.0 to Release 6.3.1 or earlier: The EMS GUI does not display after rolling back from Release 7.0 to Release 6.3.1 or earlier. You must run a patch after rolling back to Release 6.3.1 or earlier: a) Download the patch file sbc700-rollback-patcha8f30e5b192e0b0bdd5a94aa1d6eb416.tar from PLDS. b) Type mkdir -p /archive/ sbc700-rollback-patch. c) Go to /archive/temp/sbc700-rollback-patch and type tar xf sbc700- rollback-patch-a8f30e5b192e0b0bdd5a94aa1d6eb416.tar. d) Type cd /archive/temp/ sbc700-rollback-patch. e) Type./install.sh. f) Verify that the patch has been installed. 2. Configuration for interoperability with Avaya Multimedia Messaging: The timeout value set for Avaya Multimedia Messaging and Avaya SBCE are different. Therefore, when users log in to Avaya Communicator through Avaya SBCE, they lose service periodically. To support long polling used in Avaya Multimedia Messaging, you must run a script that sets the timeout value: a) Download the patch file sbc700-nginx-patch-661df0673c597c707a297ac095646bda.tar from PLDS. b) Type mkdir /archive/cespatchdir. c) Type cd /archive/cespatchdir. d) Type tar xf sbc700-nginx-patch- 661df0673c597c707a297ac095646bda.tar. e) Type./sbce-patch.sh -i sbc700-nginx-patch- 661df0673c597c707a297ac095646bda.tar.bz2. f) Type./sbce-patch.sh l. g) Verify that the patch has been installed. 3. Preferred Primary feature: Do not use the preferred primary feature while enabling High Availability. 8

4. Configuration for using FQDN for the Presence Server Address in Subscriber flow (Remote Worker): In Release 6.3.1, 6.3.2, 6.3.3, and 7.0, Avaya SBCE does not rewrite the Presence Subscription URI if Remote Workers use FQDN instead of the external Avaya SBCE IP address. This change is required to support the Adhoc Presence feature, with which endpoints detect the Presence Server by LDAP. Presence service to the Remote Workers does not work if the private FQDN used to reach Avaya SBCE is not resolvable in the enterprise network. To fix this problem, you can: a) Configure Split DNS to make the private FQDN resolvable within the enterprise network. b) Create a Regular Expression in Avaya Aura Session Manager for Presence, and use the Regular Expression in the Routing Policy for the Presence Server. 5. Upgrades from 6.3.6: Upgrade to Release 7.0 is not supported from 6.3 SP5 and 6.3 SP6 build. If there is a requirement to upgrade to 7.0 release, it is recommended that the upgrade be done from 6.3 SP3 build or earlier builds of 6.3.x. The following table summarizes the known issues in this release: Key AURORA-6565 AURORA-6537 AURORA-6502 AURORA-6440 AURORA-5043 AURORA-3503 AURORA-1389 AURORA-6141 AURORA-5391 AURORA-5080 Summary Avaya SBCE Routing Profiles page don t display the correct priority order for the Next Hop Address which is configured Editing existing signaling IP for Avaya SBCE is not taking effect after application restart Encrypted SRTCP : Getting White Noise after doing Hold from Trunk Cannot generate CSR with SIP URI in SAN AMM server gets disconnected ~ every 30 seconds when user logged in AC iphone client through Avaya SBCE VMWare snapshot SBC HA state changes from Primary to secondary & vice versa In HA, enabling preferred primary option for Avaya SBCE is not working Boot from local drive and Rescue installed system options are not working when USB is plugged in (HP G9) Blind Call transfer failed when transfer is initiated from Trunk user, where trunk server does not add record-route header Default CPU Reservation is missing from OVAs AURORA-5043 Avaya SBCE: AMM server getting disconnected ~ every 30 seconds when user logged 9

Key Summary in AC iphone client through SBC AURORA-5280 HA Active calls media failover issues at the upgrade time AURORA-6852 Recording tone is played again on performing hold/resume after Avaya SBCE failover AURORA-5460 SIPREC: VDN calls in alerting state gets stuck on CTI monitors page on ACR GUI AURORA-5796 Avaya SBCE is not sending probation notify to Remote Worker endpoint In case of SM manual failback AURORA-2817 Sigma script cannot modify the connection info in the SDP AURORA-2969 CFD: Avaya SBCE fails to Anchor 200K PRACK message when we recieve PRACK with SDP from Service Provider Migration from 6.2.x looks like it is allowed in GUI. AURORA-6360 AURORA-6501 Note: Migration from 6.2.1 is not allowed in GUI though it looks like it is upgrading. PRACK with cseq no less than the cseq no of Previous PRACK transaction being dropped AURORA-6743 Active calls stats do not show calls when the calls do not have SDP (delayed sdp). AURORA-6866 Audit log does not show details of changes made in GUI for some things. AURORA-6903 Under Avaya SBCE failover conditions, SBC statistics viewer shows "no active calls" AURORA-5244 Avaya SBCE unable to handle 302 response when contact have remote phone user AURORA-2671 Call Transfer fails with refer handling enabled on trunk, transfer initiated from remote user to trunk, where trunk is in proxy mode Related product support notice (PSN) is available at: http://downloads.avaya.com/css/p8/documents/101015817 10