Product Support Notice
© 2017 Avaya Inc. All Rights Reserved.
PSN # PSN004956u
Original publication date: 16-Mar-17. This is Issue #02, published date: 10-Apr-17. Severity/ Medium Urgency
When convenient
risk level
Name of problem
Avaya Session Border Controller for Enterprise (ASBCE) 7.1 SP2
Products affected
ASBCE 7.1
Description
ASBCE 7.1 SP2 addresses below issues.
Defect ID
AURORA-10201
AURORA-10162
AURORA-10213
AURORA-10134
Summary
Inbound & Outbound T38 fax calls failing, SBCE c=line in reINVITE & 200OK on external interface contains
internal IP address (G430 MGW IP address)
ASBCE not handling T.38 Fax correctly
SBCE not passing on 200 OK for hold re-INVITE
SSYNDI is crashing for Refer handling
SBC crash, cause outage due to video call come in from Service Provider
AURORA-10847
Tilera SBC in HA fall into synchronizing state after applying hotfix in 7.1Sp1
AURORA-10507
ASG fails to work with 7.1 SP1
AURORA-10035
SSYNDI restarting when there is no response from SP for Re-INVITE during call transfer.
AURORA-10843
SBC Changing SIPS to Sip in Request URI after installing Hotfix sbce-7.1.0.1-07-12090-hotfix-12222016
AURORA-10374
SBCE failed to send response for subsequent UPDATE with SDP in early dialog state.
AURORA-10004
AURORA-10920
SBC offer CM crypto Key toward Asteric after CM refreshed the session
SBC crash due to retransmissed 200OK during a call transfer
AURORA-10133
SBC Lync Integration, fails when edge pool fqdn resolves to multiple edge servers
AURORA-10214
Application Relay services do not function properly when FQDN is used
AURORA-10152
CLONE - One of the HA pair went into "sync" state after adding sigma script to servers
AURORA-10197
AURORA-10292
AURORA-10852
Common data restore for multi SBCE's setup does not work
CSeq being out of sync in registration.
Nginx upstream cert validation issue
AURORA-10454
Alarms having same description causing issue in creating rule at SRAM for tooling
AURORA-10370
Trans-expire configured in server inter-working in not honored by SBCE
AURORA-10632
AURORA-10464
AURORA-10250
AURORA-10422
AURORA-10619
Support skype for business certified yealink phones for SFB-Aura deployment
TOPOLOGY Hidings breaks if the TH profile name is changed
SBC failover, due to crash due to call transfer with 408 Request Timeout
No free media port available on SBCE
Hold support for RFC3264, cannot remove "c=0.0.0.0" inside audio session
AURORA-10881
Enable the non-repudiatoin in the Generate CSR->Key Usage Extension by default in the GUI
AURORA-10908
SSYNDI crash if TLS client profile has certificate as none
AURORA-10420
When there is update with SDP in early dialog that causes no talk path
AURORA-10095
Application relay with listening protocol as TLS and connect protocol as TCP not working
AURORA-10203
AURORA-11203
SBC is changing the contact header uri scheme of re-invite, service provider responding with error saying
unsupported URI scheme
Intermittently SBCE not passing 180 ringing to SP trunk
AURORA-11084
Remote worker status not available in GUI>Status>User Registrations
AURORA-10320
Resolution
To address these issues, download the 7.1 SP2 release notes from Support site and download the files mentioned in the Download files
section. Follow the instructions provided in release notes to upgrade the ASBCE. Below are the details of the 7.1 SP2 upgrade file.



File name
md5sum
PLDS Download ID
:
:
:
sbce-7.1.0.2-01-13249-6c1b52581902475a32f56e4bd27af195.tar.gz
6c1b52581902475a32f56e4bd27af195
SBCE0000076
Note: For more information on other files not mentioned above but necessary for upgrade, refer to 7.1 SP2 Release notes.
https://downloads.avaya.com/css/P8/documents/101036944
Make sure to perform the upgrade during a maintenance window to avoid service disruption.
Workaround or alternative remediation
n/a
Remarks
Read 7.1 SP2 Release Notes for information on Prerequisites for upgrade, files to be downloaded, Upgrade / Rollback instructions and
Known issues.
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
n/a
Patch install instructions
n/a
Verification
n/a
Failure
n/a
Patch uninstall instructions
n/a
Service-interrupting?
Yes
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
© 2017 Avaya Inc. All Rights Reserved.
Page 2
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.
BusinessPartner Notes
Additional information for BusinessPartners
NOTE:
WebLM Notice;
NEW Installs:
You must have a WebLM server in order to install R6.3. The Business Partner MUST generate the licenses through PLDS or KRS.
Upgrades:
You must have a WebLM server in order to upgrade to R6.3 from previous releases. The Business Partner MUST regenerate the
licenses via PLDS and KRS.
© 2017 Avaya Inc. All Rights Reserved.
Page 3