Avaya Session Border Controller for Enterprise GA Release Notes

Transcription

1 Avaya Session Border Controller for Enterprise GA Release Notes Release Issue 2 December

2 2017 Avaya Inc. All Rights Reserved. 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: 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 ("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 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

3 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: 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 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: 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: 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 in the United States. For additional support telephone numbers, see the Avaya Support Web site: 3

4 Contents OVERVIEW... 5 DOCUMENTATION... 5 BUILD DOWNLOAD LOCATION... 5 NEW FEATURES AND ENHANCEMENTS... 6 UPGRADE PATH... 8 LIST OF KNOWN ISSUES WITH WORKAROUNDS... 9 LIST OF FIXED ISSUES LIST OF KNOWN ISSUES Change history Issue Date Summary of changes 2 12 December 2017 Replacement of corrupted image file (SBCE ) 4

5 Overview This document provides information about the new features/enhancements in ASBCE Release Documentation 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 Deploying Avaya Session Border Controller on AWS Build Download Location File Name PLDS ID MD5SUM Remarks pre7.2fp1_upgrade.tar.gz Pre-upgrade patch, for SBCE f25e60ae42e0a733b58cfc804de installation on 7.2 GA Hardware ASBCE s sbce iso ISO image for fresh install SBCE f8fe3a095afdfbec9d6f32cc7e1d9a on hardware sbce iso.asc SBCE f4e2b7cc9b969f8ebc12c30fee97fad4 Signature file for ISO sbce ova OVA for fresh Installation SBCE d4fb9eaf75e83252a4db0f441a76fcb on VMWare sbce ova.asc SBCE aef3800f179f4158bc Signature file for ova sbce cc0f59ed01f8431eff7a5f tar.gz SBCE cc0f59ed01f8431eff7a5f Upgrade package for upgrade from release 5

6 sbce cc0f59ed01f8431eff7a5f tar.gz.asc sbce qcow2 sbce qcow2.asc sbce _db9a0df49bac816e8 a7d98216f30ecca.img AVAYA-SBCE-MIBP_v112.mib SBCE SBCE SBCE SBCE SBCE ea4ad6eaf3c983ea1605b12102bfbb 3e9cc1a098c40b6fabbfae318924c6e8 5db cd6a12d72b6280c231b0c4 db9a0df49bac816e8a7d98216f30ecca e562fb234eab733f cf86dc310 Signature files to be used for upgrade from release KVM image for fresh installation Signature file for aws ova Image file for creating USB Installer for fresh install on hardware MIB File for ASBCE7.2.1 NEW FEATURES AND ENHANCEMENTS RTCP MONITORING SUBTYPE 4 & 5 RTCP Monitoring tool obtains data metrics from the Avaya IP telephony network by collecting RTCP packets that are sent by Avaya endpoints, such as IP phones, IP Media Processor Boards and Media Gateways. These RTCP packets contain data about the performance of sessions running between the endpoints, including QoS measurements such as; network latency, jitter and loss which can be reported for each leg of a call. In Trunk call scenario, ASBCE receives RTCP streams from trunk which does not have any Avaya specific control information inbuilt like Avaya Endpoints. In order for RTCP monitoring tool to receive this RTCP data, the ASBCE will generate a copy of RTCP Mon packet with sub-type 4 and sub-type 5. RTCP Monitor server details can be provisioned through GUI of ASBCE. ASBCE sends the reporting data to the configured RTCP Monitor server. Intercepting the S/RTCP from trunk at edge of the enterprise network Converting RTCP to RTCP Mon format including sub-type 4 and sub-type 5 Configuration of RTCP Monitoring tool IP address from GUI Decryption of the SRTCP and send forked RTCP MEDIA TUNNELING ENHANCEMENTS The Media Tunneling Feature provides uniform client messaging and signaling from team engagement and customer engagement client SDKs. Media tunneling provides uninterrupted services when, A direct media connection path is unavailable between clients and the enterprise infrastructure because of network topology The corporate firewall of the remote customer enterprise blocks any incoming UDP traffic. ASBCE supports Media Tunneling from 7.2 version and below enhancements are supported from 7.2 FP1 version. 6

7 SHA2: - ASBCE 7.2 supports only SHA-1, which matches only SHA-1 fingerprint derived from peer-certificate to authenticate media streams. Starting with release, ASBCE supports SHA-2 fingerprint derived from peer-certificate to authenticate media streams. RTCP Buffering : -In network congestion situations, ASCBE shall not drop RTCP packets on reaching congestion threshold and buffer it. ASBCE will buffer up to 8 RTCP packets and once the congestion gets reduced, it will relay the buffered packets. Configurable TCP buffer size for audio and video -Supports the option to modify and tune TCP buffer size for audio and video. TCP buffer size can be configured from 500 KB to 1000 KB using ASBCE GUI. WEBRTC IMPROVEMENTS Avaya SBCE supports incoming calls from WebRTC-enabled web browsers to an internal Avaya Aura network with SIP at the core. For example, a consumer can call an Avaya Aura network by using a WebRTC-enabled browser from an external network. This WebRTC call is possible if the organization discloses its website to real-time multimedia calls and enabled the browser with APIs for real-time multimedia communication. The signaling and media traverse the border edge of the enterprise network that contains the firewall and Avaya SBCE in DMZ 7.2 FP1 supports, Symmetric NAT -Supports symmetric NAT with port change binding the peer address with only IP address received in a Channel Bind Support for Multiple IP Addresses from the WebRTC clients. - Supports Channel Bind for multiple Peer IP addresses in same Allocation Context and same Turn client address. NUTANIX SUPPORT 7.2 FP1 adds support for ASBCE to be deployed on Nutanix AHV Hypervisor. LOGS COLLECTION FROM GUI ASBCE 7.2 FP1 supports collecting the logs from EMS GUI. User can collect the logs from ASBCE for specific date and time. Note: Refer to ASBCE documentation available for more information. 7

8 Upgrade Path For SBCE/EMS which is on pre-7.2 version, needs to be upgraded to ( ) version and then upgrade to ASBCE release. Supported Upgrade path is as below: ASBCE ( ) ASBCE 7.2.1( ) For ASBCE upgrade procedure, please refer to Upgrading Avaya Session Border Controller for Enterprise document. Pre-requisite for upgrading hardware ASBCE s on 7.2 GA version to version: Before upgrading ASBCE to version, we must install the pre-upgrade patch on all hardware ASBCE s that are on 7.2 GA version and then upgrade to version. Download the Pre-upgrade patch from PLDS using PLDS id: SBCE Note: This patch must be installed on both EMS and SBC's Below is the patch installation procedure: 1. Make sure /home/ipcs folder has at least 1GB space to copy the pre-upgrade patch. If there is less space than 1GB, clear files in /home/ipcs while logged in as root user. To check disk space availability for /home/ipcs folder run below command: df h To clear the /home/ipcs folder run below command: rm rf /home/ipcs/* 2. Upload the patch to ASBCE using winscp over port Login to the CLI of Avaya EMS and SBCE by using ipcs user login. 4. Switch user to root. su root 5. Verify md5sum of the patch. It has to be 99677f25e60ae42e0a733b58cfc804de. md5sum pre7.2fp1_upgrade.tar.gz 6. Create /usr/local/ipcs/patch directory. mkdir /usr/local/ipcs/patch 7. Move the patch to /usr/local/ipcs/patch directory. mv /home/ipcs/pre7.2fp1_upgrade.tar.gz /usr/local/ipcs/patch 8

9 8. Navigate to /usr/local/ipcs/patch directory. cd /usr/local/ipcs/patch 9. Extract the patch. tar zxvf pre7.2fp1_upgrade.tar.gz C /usr/local/ipcs/patch 10. Install the patch. sh install.sh 11. Reboot the ASBCE. After successfully installing the pre-upgrade patch, please proceed with upgrade of EMS and SBCE s to version. Note: Once the patch installation is successfully completed, make sure to remove all the contents of pre-upgrade patch from /usr/local/ipcs/patch/ directory. (rm rf /usr/local/ipcs/patch/*) List of known issues with workarounds S.No Issue Summary Workaround 1 Cannot view ASBCE license allocations when local WebLM is used. Blank white page appears when user clicks on Installed Products in local WebLM server. This issue is caused due to accessing Faulty URL. To address this issue, replace the faulty URL appearing in the browser address bar with a correct URL and access the page to view the ASBCE license allocations. For correct URL, remove the part of the Faulty URL starting from pipe symbol i.e. {standard.product.name}. Faulty URL: llocations.xhtml?product=session_border_contr oller_e_ae&id=weblm.pagesidebar.main.menu.lic ensedproducts {standard.product.name} Correct URL: llocations.xhtml?product=session_border_contr oller_e_ae&id=weblm.pagesidebar.main.menu.lic ensedproducts 2 Sometimes EMS GUI layout is not correct after upgrade To address this issue, administrator needs to run the below command on EMS using root login. 9

10 is completed 3 Sigma script fails to modify private IP in Contact Header of response 301 Moved Permanently 4 Web application redirection to a partial URL defaults the port in the redirection URL to either 80 or 443. sh /usr/local/ipcs/icu/scripts/set_permissions_nginx.sh This issue is caused when regex_replace is used for replacing the IP in Contact header. In order to resolve the issue, instead of regex_replace function in the script, delete the Contact header first and then add Contact header. This issue is caused if the web application redirects to a partial URL. In such scenario the port defaults to the web protocol (HTTP=80, HTTPS=443). If the web application redirects to a full URL as shown below, then the requested custom port is maintained i.e by NGINX. Example: To address this issue, edit header Proxy_set_header in /usr/local/nginx/conf/proxy.conf file as below and restart nginx-data service: Proxy_set_header Host $http_host; 5 ASBCE cannot obtain licenses from WebLM server. 6 Local WebLM server in EMS does not provide the Server Properties/host ID By default it would be as below: Proxy_set_header Host $host; Please refer to below KB article for fixing this issue. SOLN Login to EMS as root user and run following : 1. setfacl -m u:tomcat:rwx /etc/hosts 2. cd /usr/local/weblm/server/scripts 3. Run below commands:./manage-weblm.py d./manage-weblm.py e List of fixed issues Key Summary AURORA Edit Domain DoS in multi-sbc platform and SBC went to "sync" mode AURORA AURORA AURORA AURORA AURORA AURORA CFD: When a call runs into this URI Rule, SBCE stops working and restarts /var size is growing due to pg_committs CFD: SBCE is not able to use elliptical ciphers alarm "Database replication log usage more than 1GB" but it is a false alarm no audio path for External user when REINVITE for display update comes to SBC. CLONE - CFD:SBC is changing the contact header uri scheme of re-invite, service provider responding with error saying unsupported URI scheme 10

11 AURORA /var partition gets 100%,there are no inodes available on SBCE AURORA AURORA AURORA AURORA CLONE - CFD: SBC is not able to use the correct authentication, when duplicate server is configured CFD: only in 7.2 GA load : Not able to change password for ipcs or root if ASG is enabled in 7.1 SP2 or 7.2 SBC Error message should be change when local WebLM license is not loaded(product id not found) CFD :TH changes are not taking effect in DB unless application restart in SBC AURORA Upgrade failed to 7.2 in SBCE, if Secondary EMS is Down. AURORA Snapshot cannot be taken if one of the SBCE in multi SBCE deployment is down. AURORA CFD: SBC has crashed on 7.0sp2 load AURORA ssyndi restart, couldn't route the call. application restart resumes the service. AURORA CFD: SBC is not responding to in-dialog options message AURORA CFD: No free media ports on 7.1sp1+ hot fix AURORA CFD: After DHCP expire, SBC is not able to update offered ip address AURORA "nosuchobject" displayed under SIP Summary (SIP Statistics) AURORA multiple SSYNDI crash for remote worker deployment AURORA Refer Handling: SBCE sends 491 request pending for re-invites AURORA SBCE Refer handling issue: sbce sends unhold invite after 200OK AURORA Application restart required to include if we include cloned sigma profile in SBC. AURORA sync issue while going to edit the mapping profile AURORA CFD: Upgrade failed from 7.1sp1 to 7.1sp2 AURORA CFD: Log server is restarting on Primary SBCE, AURORA CFD: Customer not able to modify the sigma script AURORA Global Data missing after upgrade from 7.0 Sp1 to 7.1 GA. AURORA EMS GUI doesn't load any data/pages if lower node-id SBCE is down AURORA SBCE fails to send INVITE for REFER handling when 2 out of 3 servers configured in routing profile with round robin are down. 11

12 AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA-6875 HA SBCE's went into SYNC state, after deleting snapshot server from GUI Sigma script size limitation from GUI is 4096 KB while DB has a limitation of 8 KB Cloning a sigma profile with name of consisting of 32 characters(max) restricts the name to 20 characters. TLS profile changes from GUI are not pushed to RP(nginx) ssl_conf file License state flipping on both primary and secondary EMS from "Ok" to "Grace period Active" when license installed on local WebLM CFD: SBC is not able to use the correct authentication, when duplicate server is configured Scrubber anomaly detected for all register messages Postgres on Secondary SBCE going down as xlog consuming disk space Factory reset on secondary EMS doesn't clean database CFD : nginx process is not starting if server profile created with more than one CA certificates selected for peer verification SBCE HA pair newly added got stuck at sync with EMS, clicking the sync link doesn't resolve the issue. CFD: log server restarting List of known issues Key AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA AURORA Summary No Media on Trunk to RW Transcoded call with Off Boarding AMS- double failover scenario Equinox Media Server/MCU answers Media with incorrect order in HTTP Tunnel call via SBCE TIME Zone not in Sync after configuring NTP server IP address in EMS with DUAL STACK configuration Calls fail from Skype For Business (SFB) to Aura Equinox when MKI is enabled in media rules which is applied to SFB server flow. Prognosis fail to parse subtype 4 and subtype 5 RTCP data In RW-RW call, user experience noise after Hold/ Resume, if SBCE handles SRTP interworking with one leg of call as Dual stack and other as Non-ANAT. Removal of group line in Answer, if Offer received with group and with only one audio token "Bad request" received in response to SIP INFO messages sent by SBC for DTMF MDA-IPv6 - Noise on resuming the bridged call Collecting the logs of size greater than 5 GB using Log Collection feature on GUI has failed without proper error message. Can't change the SNMP trap profile associated with SNMP user. PSTN call to SBC is dropped due to wrong PRACK sent by SBC to SM. SFB integration issue: one way audio after 15 mins when RTP is enabled on media rules 12

13 AURORA AURORA AURORA AURORA AURORA Link failure alarms are not clearing after reboot Call drops after hold for audio transcoding call between G729AB and G711A codecs GUI Statistics doesn t show value for Active Turn channel session for WebRTC calls SNMP Traps are not getting generated when any of the EMS process fails IPv6 addresses do not work if management and data interfaces are configured with dual_stack address. 13