Click

here
to view and download a PDF of this document.

Table of Contents

SBC 5xx0-7000-SWe Documentation Home page


About SBC Release Notes

This document describes new features, the latest hardware and software requirements, known limitations and other pertinent release information for the latest release of SBC Core.

Please note that all Ribbon bugs reported by customers on a given software release are fixed in the latest release on that software release branch.

To view and download the latest End of Product Sale (EoPS) and other End Of Life (EOL) notices, navigate to the Resource Library on the corporate website (https://ribboncommunications.com/company/get-help/resource-library).

Related Documentation

The SBC Core 07.02.xx documentation is located at the following Wiki space: SBC Core 7.2.x Documentation.

Release Notes Use and Distribution

Ribbon Release Notes are protected under the copyright laws of the United States of America. This work contains proprietary information of Ribbon Communications, Westford, MA-01886, USA. Use, disclosure, or reproduction in any form is strictly prohibited without prior authorization from Ribbon Communications.

Associated Ribbon Bulletins

The following Ribbon Bulletins are referenced in this release note:

  • Warning-18-00028230: Call failure during LSWU when upgrading 5.x release to 6.2.1 or higher (VMWare or KVM) with 10 or more vCPUs configured.
  • Warning-17-00022847: The DNS configuration parameters within the address contexts may cause certain configurations to fail during an upgrade
  • Warning-17-00022689: Duplicate Trunk Group or Zone names can cause unexpected behavior
  • Warning-14-00020748: Verify system and databases are fully in sync prior to Live Software Upgrade (LSWU)
  • Bulletin-18-00028529: The System Security Intrusion Detection AIDE Reports False Positive Alarms

  • Warning-19-00028624: Custom EMA TLS certificate is overwritten with a default self-signed SBC certificate during an upgrade to versions 6.1.x, 6.2.x, 7.1.x, 7.2.x 
  • Warning-19-00028636: SBC SWe Gateway-to-Gateway signaling is disabled in certain SBC SWe versions 
  • Warning-19-00029555: CDR Viewer and Live Monitoring cannot be enabled/disabled
  • Warning-19-00029562: Surrogate Registration may Fail after an Upgrade to SBC version 7.0/7.1/7.2/8.0 if the Surrogate Registration ipPeer has surrogateRegistration hostPart Configured 
  • Warning-17-00022737: Re-installing an SBC from an ISO image and restoring the config. from a tar.gz backup file may cause loss of encrypted config. parameters for certain releases

To view/download Ribbon bulletins, do the following:

  1. Log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login)
  2. Click Bulletins link from the menu bar. 
  3. Enter the bulletin number (last eight numbers) in the search field and press Return.
Note

The WBA section may not include all Warnings, Bulletins and Alerts associated with this release. Before attempting to upgrade to any release, we recommend that you check the Ribbon Support Portal for any newly published WBAs that may include this release in the Affected Versions section.

Problems or Questions

For problems or questions, contact the Global Support Assistance Center:

Ribbon Support Portal: https://ribboncommunications.com/services/ribbon-support-portal

Voice: +1-833-RIBBON1 (1-833-742-2661)

About SBC Core

The SBC Core platforms address the next-generation needs of SIP communications by delivering media transcoding, robust security and advanced call routing in a high-performance, 2RU, and 5RU form-factor devices enabling service providers and enterprises to quickly and securely enhance their network by implementing services like SIP trunking, secure Unified Communications and Voice over IP (VoIP).

For more product information, refer to the section About SBC Core in the main documentation space.

Interoperability

The SBC Core software interoperates with the following:

  • SIP/H.323 compliant IADs and IP-PBXs
  • PSX Policy Server Softswitch via SIP redirects and/or Diameter+ protocol
  • SBC 9000 through SIP call signaling and Networks MCS protocol
  • NetScore collection, analysis, monitoring, and reporting of selected Key Performance Indicators (KPIs) on a near-real time basis

Note

NetScore maintains a list of remote host keys for all nodes from which it collects data. If NetScore is deployed in your network, you will lose connectivity to the SBC whenever the SBC software is reinstalled because the SBC’s host key is updated during the install. Refer to NetScore Release Notes for steps needed to reconnect to the SBC.

H.323-SIP and SIP-H323 Calls

When using H.323-SIP and SIP-H.323 call flows, an additional Re-invite/Update may get generated towards the SIP side. To suppress this, enable the IP Signaling Profile (IPSP) flag Minimize Relaying Of Media Changes From Other Call Leg at the SIP side.

Note

H.323 is not supported on SBC SWe cloud deployments.

Compatibility with Ribbon Products

Tip

When upgrading your network, you must upgrade each product to the most current release to take advantage of the latest features, enhancements, and fixes.

Info

For complete interoperability details between various Ribbon products, including backwards compatibility, refer to Ribbon Product Interoperability.

Refer to SBC Core Portfolio Interoperability Matrix for the latest and minimum compatible product versions supporting the 07.02.01R007 release.

Sample Heat Templates Included in This Release

To instantiate the SBC instances, the following template can be used:

SBC Heat Templates

 Template NameDescription
heatRgNoDhcp.yamlM-SBC/S-SBC Heat template for No DHCP IPv4 or IPv6. This template include instructions to enable port redundancy.

Note:

Example template files are packaged together in .tar.gz and .md5 files separate from the SBC Core application installation and upgrade files:

  • cloudTemplates.tar.gz
  • cloudTemplates.tar.gz.md5

SBC SWe Cloud Requirements for OpenStack

The system hosting the SBC SWe Cloud must meet the below requirements for OpenStack:

Server Hardware Requirements

 

ConfigurationRequirement
Processor

Intel Xeon processors (Nehalem micro-architecture or above) with 6 cores and above (processors should support hyper threading).

Note

Ribbon recommends Westmere (or newer) processors for better SRTP performance. These processors have the AES-NI instruction set for performing cryptographic operations in hardware. 

 RAMMinimum 24 GiB
 Hard DiskMinimum 100 GB
Network Interface Cards (NICs)

Minimum 4 NICs.

Note

Make sure NIC has multi-queue support which enhances network performance by allowing RX and TX queues to scale with the number of CPUs on multi-processor systems.

Note

The PKT ports must be 10 Gbps SR-IOV enabled port.

Note

6 NICs are required for supporting PKT port redundancy.


The system hosting the SBC SWe must meet the following requirements to achieve the performance targets listed: 

S-SBC SWe Requirement

S-SBC SWe Requirements
for 1000 CPS/120K Signaling Sessions 
Notes

32 vCPUs

Due to the workload characteristics, allocate 20 physical cores with two hyper-threaded CPUs from each core to the SBC.

128 GiB RAM

Must be Huge Page memory. The minimum page size is 2048 KiB, but 1048576 is recommended.

100 GB Disk

None

4 vNICs/6 vNICs

Attach MGT0 port to the Management VirtIO Tenant network.

HA port has to be on IPv4 VirtIO Tenant network.

Attach PKT0 and PKT1 ports to SR-IOV and Provider network.

M-SBC SWe Requirement

M-SBC SWe Requirements
for 30K Media Sessions
Notes

20 vCPUs

Due to the workload characteristics, allocate 10 physical cores with two hyper-threaded CPUs from each core and from single NUMA node to the SBC.

32 GiB RAM

Must be Huge Page memory. The minimum page size is 2048 KiB, but 1048576 is recommended.

100 GB Disk

None

4 vNICs/ 6 vNICs

Attach MGT0 port to the Management VirtIO Tenant network.

HA port has to be on IPv4 VirtIO Tenant network.

OpenStack Requirements

The SBC SWe supports the following OpenStack environments:

  • Newton with RHOSP 10 and RHEL 7.4
  • Queens with RHOSP 13 and RHEL 7.5
Note

The SBC SWe Cloud was tested on OpenStack Queens with RHOSP 13 and RHEL 7.5.

SBC SWe Requirements for KVM

The following table lists the server hardware requirements.

KVM Hypervisor Server Hardware Requirements

 
Configuration Requirement
Processor

Intel Xeon processors (Nehalem micro-architecture or above) with 6 cores and above (processors should support hyper threading).

Note

Ribbon recommends using Westmere (or newer) processors for better SRTP performance. These processors have the AES-NI instruction set for performing cryptographic operations in hardware.

Note

The supported CPU Family Number is 6 and CPU Model Number must be newer than 26. Refer to Intel Architecture and Processor Identification document for more information.


 RAMMinimum 24 GB
Hard DiskMinimum 500 GB
Network Interface Cards (NICs)
Minimum 4 NICs.
Note

Make sure NIC has multi-queue support which enhances network performance by allowing RX and TX queues to scale with the number of CPUs on multi-processor systems.

Note

The Intel I350, x540, and 82599 Ethernet adapters are supported for configuring as SR-IOV and DirectPath I/O pass-through devices.


Ports

Number of ports allowed:

  • 1 Management port
  • 1 HA port
  • 2 Media ports

SBC SWe Requirements for VMWare

The following table lists the server hardware requirements:

Server Hardware Requirements

 
 ConfigurationRequirement
Processor

Intel Xeon processors (Nehalem micro-architecture or above) with 6 cores and above (processors should support hyper threading).

Note

Ribbon recommends using Westmere (or newer) processors for better SRTP performance. These processors have the AES-NI instruction set for performing cryptographic operations in hardware.

Note

The supported CPU Family Number is 6 and CPU Model Number must be newer than 26. Refer to Intel Architecture and Processor Identification document for more information.

Note

ESXi 6.5 and later releases require approximately two physical cores to be set aside for hypervisor functionality. Number of VMs which can be hosted on a server needs to be planned accordingly.

 RAMMinimum 24 GB
Hard DiskMinimum 500 GB
Network Interface Cards (NICs)
Minimum 4 NICs, if physical NIC redundancy is not required.

Otherwise, 8 NICs (preferably with SR-IOV capability to support SWe optimizations).

Notes
  • Make sure NIC has multi-queue support which enhances network performance by allowing RX and TX queues to scale with the number of CPUs on multi-processor systems.
  • The Intel I350, x540, and 82599 Ethernet adapters are supported for configuring as SR-IOV and DirectPath I/O pass-through devices. The SR-IOV is supported only with 10 Gbps interfaces (x540/82599).
  • The Enterprise Plus license is required for SR-IOV.
Note

 Intel x710 NICs are also supported on VMware (ESXi versions 6.5 and above) with SR-IOV enabled. x710 NICs are not supported on Direct I/O or KVM. 

Ports

Number of ports allowed:

  • 1 Management port
  • 1 HA port
  • 2 Media ports

 

 

Warning

The SBC SWe software only runs on platforms using Intel processors. Platforms using AMD processors are not supported.

Required Software and Firmware Versions

The following SBC 5000 series (51x0/52x0), SBC 5400 and SBC 7000 software and firmware versions are required for this release. For 5xx0 the BIOS can be installed during app install, whereas for 5400 and 7000 the BIOS is included in the firmware package and is installed during the firmware upgrade. 

Required Software and Firmware Versions

Components

Software/Firmware

Version

SBC Platform

  

SBC 51x0/52x0 BMC

V03.20.00-R000

SBC 51x0/52x0 BIOSV02.06.00
SBC 5400 Firmware

BMC: V03.20.00-R000

BIOS: V1.17.0

SBC 7000 Firmware

BMC: V03.20.00-R000

BIOS: V2.13.0

SBC Application

 


Operating System (OS) Version

V06.02.01-R007
SonusDB

V07.02.01-R007

EMAV07.02.01-R007

SBC Application

V07.02.01-R007

Note

The firmware package of SBC 5400 and 7000 series includes BMC, BIOS, and other binaries. The firmware is upgraded from the BMC.

How to Verify Currently Installed Software/Firmware Versions

Use the EMA to verify the currently installed software and firmware versions.

Log on to the EMA, and from the main screen navigate to Monitoring > Dashboard > System and Software Info.

Software Bundles

The following software release bundles are available for download from the Customer Portal:

  • SBCSWe_7.2
  • SBC5x7x_7.2

Download the appropriate software packages for your desired configuration from the Customer Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) to your PC:

SBC 5000 Series (51x0/52x0) Firmware

  • firmware-5XX0-V03.20.00-R000.img

  • firmware-5XX0-V03.20.00-R000.img.md5

  • bmc5X00_v3.20.0-R0.rom.md5sum

  • bmc5X00_v3.20.0-R0.rom

SBC 5400 Firmware

  • firmware-5400-V03.20.00-R000.img
  • firmware-5400-V03.20.00-R000.img.md5

SBC 7000 Series Firmware

  • firmware-7X00-V03.20.00-R000.img
  • firmware-7X00-V03.20.00-R000.img.md5

Note

Execute the Method Of Procedure (MOP) only for upgrading the FPGA image of an SBC 7000 DSP-LC card when the SBC 7000 DSP-LC FPGA version is 0x14. The MOP can be applied at any version time, with the only restriction being that the BMC firmware version is at least 1.25.0. However, if the SBC application is running version V05.01.00R000 or higher, then the DSPs will be set to disabled and transcoding and transrating calls will fail if the SBC 7000 DSP-LC FPGA version is 0x14. Therefore, it is necessary to upgrade the SBC 7000 DSP-LC FPGA if the version is 0x14, before upgrading the SBC to 5.1.0. However, the MOP can be applied if the application version is higher than 5.1.0. Click Here to view the 550-06210_DSP-LC_FPGA_Upgrade_MOP.

SBC Core Operating System Installation Package

The ConnexIP Operating System installation package for SBC Core:

  • sbc-V07.02.01R007-connexip-os_06.02.01R007_10_amd64.iso
  • sbc-V07.02.01R007-connexip-os_06.02.01R007_10_amd64.iso.md5


Note

 Once the ConnexIP ISO procedure is completed, the SBC application package is automatically uploaded to SBC platforms.

SBC Core Application Package

The SBC Application installation and upgrade package for SBC Core:

  • sbc-V07.02.01R007-connexip-os_06.02.01-R007_10_amd64.qcow2
  • sbc-V07.02.01R007-connexip-os_06.02.01-R007_10_amd64.qcow2.md5
  • sbc-V07.02.01-R007.x86_64.tar.gz
  • sbc-V07.02.01-R007.x86_64.md5
  • sbc-V07.02.01-R007.x86_64.signature

For detailed information on installation and upgrade procedures, refer to SBC Core Software Installation and Upgrade Guide.

Upgrade Notes

Warning

A LSWU on an SBC 7000 should only be performed when the total number of active calls on the system is below 18,000. If the criteria is not met, a double failure during the upgrade may occur, thereby losing all active calls. If such a failure occurs, both active and standby SBC services will go down.  Contact Ribbon Support immediately.

Note

Release 7.2 requires additional user account security practices for SBC SWe deployments in Openstack cloud environments. During upgrade of SBC SWe cloud instances deployed using Heat templates, you must use a template that includes SSH keys or passwords for the admin and linuxadmin accounts. The example Heat templates have been updated to include information on how to specify this type of data in the userdata section of a template.

Note

Once the installation or upgrade completes on the SBC 51x0 and SBC SWe platforms, the copy of the installation package (327777473) is automatically removed from the system.

Note

As an SBC Core password security enhancement, user passwords automatically expire after upgrading to 7.2.x. As a result, users are required to change their passwords upon initial login immediately following the upgrade.

Note

Customers using the Network licensing mode will stay on the Network licensing mode after upgrade to the SBC 7.2.0 Release.

Customers using Legacy mode will stay on the Legacy mode after upgrade to SBC 7.2.0 Release. Once upgraded to SBC 7.2.0 Release, the customer will not be able to set Network License mode.

Note

The SBC 7.2 5xx0 and 7000 platforms may exhibit a 7% degradation of CPU performance relative to earlier releases. This is attributable to the Spectre/Meltdown security patches.

Note

For the procedure specific to SBC SWe upgrades on KVM Hypervisor or VMware to take advantage of performance improvements due to hyper-threading, refer to MOP to increase vCPUs Prior to Upgrading SBC SWe on VMware or KVM Hypervisor

Note

 In NFV environments, the method used for upgrades involves rebuilding the instance, which requires additional disk space on the host. The minimum disk space needed for this operation is listed in the table below.

Disk Space Requirements

Flavor
Extra Space Required (GB)
S-SBC80
M-SBC80
PSX-M360
PSX-S360
PSX-Test360
EMS_SA150

Note

The SBC 51xx and 52xx systems require 24GB of RAM to run 6.x code or higher.

07.02.01R007 Upgrade Information

Warning

Prior to performing an upgrade to release 07.02.01R007, usernames that do not conform to the new SBC user-naming rules must be removed to prevent upgrade failure. Upgrade can proceed successfully after removing all invalid usernames. The following user-naming rules apply:

  • Usernames can begin with A-Z a-z _ only.
  • Usernames cannot start with a period, dash, or digit.
  • Usernames can contain a period(.), dash(-), alphabetic characters, digits, or underscore(_).
  • Usernames cannot consist of digits only.
  • Usernames can contain a maximum of 23 characters.

The following names are not allowed:

tty disk kmem dialout fax voice cdrom floppy tape sudo audio dip src utmp video sasl plugdev staff users nogroup i2c dba operator

Note: Any CLI usernames consisting of digits only, or not conforming to new user naming rules, are removed after performing a restore configuration action in this release 7.2.1R005

Warning

Prior to performing an upgrade to the 7.2 release, the dnsGroups with type mgmt must be specified/updated with the "interface" field. The steps are included in WBA "W-17-00022847". To view the WBA, log on to the Support Portal and click the Bulletins link from the menu bar. Enter the bulletin number (last eight numbers) in the search field and press Return.

If the above MOP is not run, the LSWU process may fail because of duplicate trunk group or zone names.

Warning

Prior to performing an upgrade to 7.2 release, the duplicate trunk groups or zones must be removed. The steps are included in WBA "W-17-00022689". To view the WBA, log on to the Support Portal and click the Bulletins link from the menu bar. Enter the bulletin number (last eight numbers) in the search field and press Return.

If you are upgrading from any SBC version with ePSX configuration to the 07.02.01R007 release, execute the Method of Procedure, MOP to Reconfigure SBC (with ePSX) to External PSX Prior to an Upgrade to 06.00.00R000 Release prior to performing an upgrade. For a list of supported LSWU paths, refer to 327777473.

Support of maddr Post-Upgrade

When upgrading SBC Core to release 5.0.0 (and above) from a pre-4.2.4 release, complete the "Action to take" immediately after the upgrade if either condition that follows is applicable:

  • If you are using the SBC with a Broadsoft system and the SBC is configured for registration access (where the SBC sits between SIP phones and the Broadworks System). Otherwise no new REGISTER will be processed (phones will lose registration).
  • If you are using the SBC with other feature servers that require maddr processing.

Action to take: On the SIP trunk group facing Broadsoft (or other feature server), set the SIP Trunk Group signaling flag, honorMaddrParam, to enabled on the Trunk Group(s) requiring maddr handling. The default is ‘disabled’.

set addressContext <addressContext name> zone <zone name> sipTrunkGroup <TG name> signaling honorMaddrParam <disabled | enabled> 

See the following pages for configuration details:

SBC SWe Pre-Upgrade Requirements

VM CPU resource allocation requirements

Starting with 4.2.4R0 release, CPU resource allocation requirements for SBC SWe VM are strictly enforced contrary to previous releases. You must review and verify these VM settings (including co-hosted VMs) against the documented "VM Configuration Recommendations" on the For VMware page in the Hardware and Software Requirements section before upgrading. If you encounter a problem, correct the CPU reservation settings as specified in step 6 of the "Adjust Resource Allocations" procedure on Creating a New SBC SWe VM Instance with VMXNET3. CPU reservation should be set as “number of vCPUs assigned to VM * physical processor CPU frequency". If VM uses the same number of vCPUs as the number of physical processors on the server, this reservation may not be possible. In this case, reduce the number of vCPUs assigned to VM by one and set the CPU reservation to the appropriate value.

When using the show table system serverSoftwareUpgradeStatus command during the upgrade, the Standby server's LSWU status will always display "Upgrading" even though the upgrade may have failed due to host checker validation. To check if host validation failed for the Standby, check for HostCheck Validation Failed message in the upgrade.out log.

Disable Call Trace feature prior to LSWU/upgrade

As a prerequisite for SWe LSWU/upgrade, disable the Call Trace feature prior to performing the LSWU/upgrade and re-enable it once the LSWU/upgrade is completed.

Manually check for Hostcheck Validation Failed message

Perform the following procedure on the Standby to check for the Hostcheck Validation Failed message in the upgrade.out log.

  1. Log on to ESXi of the Standby SBC SWe.

  2. Check in/opt/sonus/staging/upgrade.out (this log shows the Hostcheck Validation Failed error).

  3. Power off the VM.

  4. Reduce the number of vCPUs assigned to VM by one and set the CPU reservation to the appropriate value.

  5. Power on the VM. The SBC SWe successfully upgrades to the latest version 6.2.0. 

  6. Run the command show table system serverSoftwareUpgradeStatus to confirm the successful upgrade.

  7. Perform similar procedure for LSWU on Active.

Preparing for Upgrade (All Platforms)

Warning

Prior to performing a Live Software Upgrade (LSWU), verify if the system and the databases are in sync. The steps are included in WBA "Warning-14-00020748". To view the WBA, log on to the Support Portal and click the Bulletins link from the menu bar. Enter the bulletin number (last eight numbers) in the search field and press Return.

Note

The SBC 7.2 release skips the SRV query if the flag in a DNS NAPTR response from the DNS server indicates to proceed with "A" record query as per RFC 2915/3403. This is a change in behavior from previous releases, where the SBC performed SRV queries irrespective of the "flag" setting returned by DNS Server.  If you use DNS NAPTR/SRV/A record query from SBC to determine peer transport address, ensure the DNS Server is configured to return ‘S’ flag to invoke an SRV query.

Note

In this release, LSWU infrastructure is added to the Platform Manager (PM), providing the ability to perform LSWU upgrades to later releases using the PM. However, this feature is not currently supported in 4.2.x releases and should not be used at this time.

Please read the following information and take necessary actions before starting your upgrade to this release.

Since the release 4.1.4, the cryptographic key pair used to sign and verify the package has been changed to enhance security. When installing/upgrading from all 4.0.x releases, all pre-4.1.4 releases (4.1.3 and earlier), and all pre-4.2.3 releases (4.2.2R00x and earlier), do one of the following, depending upon your upgrade method:

  • LSWU through CLI: Skip the integrity check during LSWU by using the CLI command below.

    During LSWU, use the integrityCheck skip option when upgrading from CLI:

    > request system serverAdmin <server> startSoftwareUpgrade integrityCheck skip package <package>
    Note

    Integrity check works as expected only when upgrades are started from 4.1.x releases (4.1.4R000 or later) or from 4.2.3R000 or later releases.

  • Upgrade through Platform Manager: If upgrading using Platform Manager, simply ignore the "Wrong Signature" warning message and continue the upgrade normally.
Note

Downgrading to any pre-5.0 release from this release requires a ConnexIP re-ISO installation. For more information, refer to:

Customer running 7.1 or 7.2 releases must check the eventLog configuration to confirm that the memusage log type has a server1 syslog configuration and if it is not present, they need to manually create before attempting to upgrade to the latest code.

The following command example output shows how to confirm with the server1 config is present for the memusage log type:

show configuration oam eventLog typeAdmin
typeAdmin packet {
  
state      enabled;  
fileCount   64;  
fileSize    10240;
filterLevel info;
servers server1;
 }
 
 typeAdmin memusage {
 state enabled;
 }
 
Update the configuration with the following commands -
configure
 set oam eventLog typeAdmin memusage servers server1


Supported Live Software Upgrade (LSWU) Paths

ATTENTION

This release includes all bug fixes implemented in the releases which are documented in the Supported Upgrade Paths table below. To view bug fixes in previous releases, refer to the release note(s) of interest from thSBC 5xx0-7000-SWe Documentation Home page.


The SBC Core supports Live Software Upgrade from releases listed in the table below:

Supported Upgrade Paths

V05.00.xxV05.01.xxV06.xxV07.xx
V05.00.00R000V05.01.00R000V06.00.00R000V07.00.00R000
V05.00.00R001V05.01.00F001V06.00.00R001V07.00.00F001
V05.00.00S102V05.01.00F002V06.00.00F001V07.00.00F002
V05.00.00S104V05.01.00F003V06.00.00F002V07.00.00F003
V05.00.00S200V05.01.00F004V06.00.00F003V07.00.00F004
V05.00.00S201V05.01.00F005V06.00.00F004V07.00.00F005
V05.00.00S202V05.01.00F006V06.00.00F005V07.00.00F006
V05.00.00S203

V05.01.00F007

V06.00.00F006V07.01.00R000
V05.00.00S204V05.01.00F008V06.00.00F007V07.01.00R001
V05.00.00F001V05.01.01F001V06.00.00F008V07.01.00R002
V05.00.00F002V05.01.01F002V06.00.00F009V07.01.00R003 
V05.00.00F003V05.01.01F003V06.00.00F010V07.01.00R004
V05.00.00F004V05.01.01F004V06.00.00F011V07.01.00F001
V05.00.01R000V05.01.01F005V06.00.00F012V07.02.00R000
V05.00.01R001V05.01.01F006V06.01.00F001V07.02.00R001
V05.00.01R002V05.01.00S608V06.01.00F002V07.02.00R002
V05.00.01S001V05.01.00S610V06.01.00F003V07.02.01R000
V05.00.01F001V05.01.00S611V06.01.00R000V07.02.01R001
V05.00.01F002V05.01.00S612V06.01.00R001V07.02.01F001
V05.00.01F003V05.01.00S613V06.01.00R002V07.02.01F002
V05.00.02R000V05.01.00S614V06.01.00R003V07.02.01R002
V05.00.02R001V05.01.00S617V06.01.00R004V07.02.01R003
V05.00.02A059V05.01.00S619V06.01.00R005 V07.02.01F004
V05.00.02A061V05.01.00S620V06.01.00R006V07.02.01F005
V05.00.02F001V05.01.00S621V06.01.00R007V07.02.01R004
V05.00.02F002V05.01.00S622V06.01.00R008 V07.02.01R005
V05.00.02F003V05.01.01R000V06.02.00R000V07.02.01R006
V05.00.02F004V05.01.01R001V06.02.01R000
V05.00.02F005V05.01.02F001V06.02.01R001
V05.00.03R000V05.01.02F002V06.02.01R002 
V05.00.03R001V05.01.02F003V06.02.01F001
V05.00.03R002V05.01.02F004V06.02.01F002
V05.00.03R003V05.01.02F005V06.02.01F003
V05.00.03F001V05.01.02F006V06.02.01F004
V05.00.03F002V05.01.02F007V06.02.01F005
V05.00.03F003V05.01.02F008V06.02.02R000
V05.00.03F004V05.01.02S001V06.02.02F001
V05.00.03F005V05.01.02R000V06.02.02F002
V05.00.03F006V05.01.02R001V06.02.02F003
V05.00.03F007V05.01.02R002V06.02.02F004
V05.00.03F008V05.01.02R003V06.02.02F005
V05.00.04F001V05.01.02R004V06.02.02F006
V05.00.04R000V05.01.03R000V06.02.02F007
V05.00.04R001V05.01.03F001V06.02.02F008
V05.00.05F001V05.01.03F002V06.02.02R001
V05.00.05F002V05.01.03F003

V05.00.05F003V05.01.03F004

V05.00.05F004V05.01.03F005

V05.00.05F005V05.01.03F006

V05.00.05F006V05.01.03F007

V05.00.05F007V05.01.03F008

V05.00.05F008V05.01.03F009

V05.00.05R000V05.01.03F010

V05.00.06R000 V05.01.04R000

V05.00.06F001V05.01.04F001

V05.00.06F002V05.01.04F002

V05.00.06F003V05.01.04F003

V05.00.06F004V05.01.05R000

V05.00.06F005V05.01.05F001


V05.01.05F002


V05.01.05F003


V05.01.05F004


V05.01.05F005

Note

Prior to upgrading to 7.x, run the following command to verify availability of at least 40 MB free disk space in the /boot partition.

df -kh


New Features

New Features in 07.02.01R007 Release

There are no new features in this release.

New Features in Previous Releases

For new features in previous releases, refer to:

Resolved Issues

Resolved Issues in 07.02.01R007 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution
SBX-932622

The SBC generates a RTCP goodbye to ingress after the 200 OK.

Impact: When Downstream forking is enabled and the Early Media Response is set to "last received SDP" - when the call gets answered the resource chain will be re-built and the RTCP BYE will be generated.

Root Cause: Root cause lies in feature completed in a previous release. The feature required that if the ingress peer does not have 100 rel support, and egress gets multiple 18xs, then the transcode is forced even though pass through is possible to support codec change.

Steps to Replicate: Enable Downstream Forking and forking response as anything except the first prov response.

Keep PSP's are setup to perform a transcode only.

Platform/Feature: SBC

The code is modified to address the exact scenario that was presented to us in a previous release.
1. Downstream forking is enabled.
2. Early media behavior - non FIRST PROV RESP.
3. One forking dialogue.
4. No SDP is sent in 2xx if the 18x reliable.

SBX-93874 / SBX-861802

Portfix SBX-86180: PolicyDBSyncStatus data is being removed by the logrotate.

Impact: Policy Data shows a sync in progress.

Root Cause: File paths were being removed by the logrotate. When the new file was created in the writing process, it did not have the correct privileges to be read by a status reporting session, so the status reporting process wrongly reported sync in progress.

Steps to Replicate: On SBC ERE, after nightly logrotate job finishes, the file must not be removed.

Platform/Feature: SBC: Application

Stop the logrotate from removing this file.
SBX-935462

Call Transfer call to PSTN gets failed second time, when a MOH is played in the initial call.

Impact: After multiple times on hold and resume, if the first call transfer fails due to reject by transfer target, then the transferee and transferor are reconnected successfully. For any subsequent call transfer, the SBC rejects the call transfer request.

Root Cause: When the first call transfer got failed, the SBC tries to reconnect the original call. Due to this re-connection, the original call is not moving to the stable state. Any call transfer request in such state is rejected by the SBC.

Steps to Replicate:

1.TEAMS to PSTN1 call.
2.TEAMS hold and resume the call.
3.TEAMS transfer call to PSTN2.
4.PSTN2 rejects the call.
5.TEAMS resume the call and transfer again to PSTN2.

Platform/Feature: SBC: MS Teams

The code is modified to move the original call state to the stable state during re-connection.
SBX-931032

No relay of UPDATE with a SDP when the media mode changed and the DRBT is configured.

Impact: When the Downstream Forking and DLRBT is enabled, an UPDATE is received from the ingress are not going out to egress (UPDATE received after the media cut-thru has happened because of receipt of RTP from egress).

Root Cause: The code had been modified in a previous release that when an 18x with the SDP is received from a particular dialog, it is marked as OA_COMPLETE. If it is marked as OA_COMPLETE, the UPDATEs received are sent to the other leg if that other leg is 100rel/PRACK supported. This issue was caused due to some legs not being marked as OA_COMPLETE due to an incomplete implementation.

Steps to Replicate: Set Downstream Forking and DLRBT as enabled.

Platform/Feature: SBC

The code is modified to mark OA_COMPLETE in all instances where the parallelRingPsp is being appended with the new SDP's received in 18x's.
SBX-932552

Not able to change the Source Port to any on EMA, IPAccessControlList screen.

Impact: Not able to change the Source Port to any on EMA, IPAccessControlList screen.

Root Cause: The source port attribute is validated as an integer instead of an Alpha Numeric.

Steps to Replicate:

  1. Log on to the EMA application.
  2. Select 'ALL' -> 'Address Context' -> 'IP Access ControlList' -> 'Rule' -> 'default'.
  3. Ensure that SourcePort number is changing from integer to 'any' and 'any' to integer.

Platform/Feature: SBC

The code is modified to validate a source port as a type of alpha numeric instead of an integer.
SBX-936013

MS Teams Call Park has an intermittent failure.

Impact: In a Microsoft Teams environment, Microsoft has a bug in the client code that can randomly cause messages to be sent out of sequence. For example, when trying to transfer calls, Microsoft can send REFER and then INVITE with a=inactive afterwards. The out of sequence message processing was causing processing issues on the SBC and the call did not complete.

Root Cause: Microsoft agrees that there message sending is broken and are working on a fix.

Steps to Replicate: Repeatedly run Microsoft Teams Call Park scenarios. The problem is not always reproducible and is possibly dependent on the Microsoft server and location of the associated client.

Platform/Feature: SBC: MS Teams

The code is modified to be more defensive against the out of sequence messaging, such as:
1) Reject the INVITE with 491 if REFER is being processed on a call leg.
2) Reject the REFER if the SBC has an outstanding INVITE waiting to be sent.

SBX-935482

When a transfer call is not answered from the PSTN, MS TEAMS client is not able to resume the existing call.

Impact: In a Microsoft Teams call flow where the call gets transferred, the C-party sends back a 180 with no SDP that triggers the SBC to play RBT and then C-party sends a 183 with SDP and finally rejects with 6xx. This results in the SBC internally getting into a bad state. This results in the SBC being unable to resume the call and the call getting released.

Root Cause: The resource management in the SBC was getting confused on the packet service profile for the various call legs, which lead to the call being released.

Steps to Replicate:

1.TEAMS to PSTN1 call.
2.TEAMS transfer call to PSTN2.
3. PSTN2 does not answer the call.
4.TEAMS resume the call and transfer again to PSTN2.

Platform/Feature: SBC: MS Teams

The code is modified to correctly manage the packet service profile and other call leg information, so it can correctly handle the transfer rejection from C-party.
SBX-911542

Call failure due to FQDN in request URI.

Impact: When the SBC sends a query for the SRV record to external server and the Peer Domain in reqURI is disabled, the SBC intermittently sends a FQDN in the reqURI of egress INVITE. The correct behavior is to send an IP and address in the reqURI of egress INVITE. Without a fix, the SBC will send a FQDN in reqURI even when a Peer Domain in reqURI is disabled.

Root Cause: The SBC does not use formatted SIP messages when an external query is made for finding an SRV record and when a record is found in cache. The SBC cannot apply setting of "Peer Domain in ReqURI" flag in an egress SIP message.

Steps to Replicate:

Reproduce the issue.

  1. Follow the configurations on PSX.
    1. Set IP PEER as FQDN abc.com instead of IP address.
    2. Enable "noPortNumber5060" on IPSP [ This is for done for NAPTR, SRV query ].
    3. Disable "Peer Domain in ReqURI " on IPSP.
  2. Use External DNS server.
    1. Configure SRV record and A record on external DNS server with different Time To Live values.
  3. Run high number of calls.

With a fix, the SBC is sending an IP and Port for all the calls since the Peer Domain in ReqURI is disabled.

Platform/Feature: SBC

The code is modified to ensure the SBC uses the saved formatted SIP message when an external DNS query is made for the SRV record and a record is fetched from a cache. The modified code allows the SBC to apply the "Peer Domain in ReqURI" flag setting in an egress SIP message.


Resolved Issues in 07.02.01R006 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-93320 / SBX-89414

2

Multiple Refer calls are failing in both the ISBC and DSBC.

Impact: When the music on hold is deployed with MS Teams environment and call is put on hold/resumed multiple times, it results in the call being released by the SBX.

Root Cause: The music on hold service requires multiple REFER / INVITE with replace attempts and leads to a race condition where the call control state machine did not get back to a stable state after the call was put on hold. This unstable call led to an internal failure when trying to take the call off hold.

Steps to Replicate: Attempt to put a call on hold and resume; the call may fail after 3 attempts or up to 6 attempts.

Platform/Feature: SBC: MS Teams

The code is modified to allow call control to correctly transition back to a stable state and that the resume handling is processed correctly.

SBX-924702

A slow SAM Process memory leak when running GW-GW calls.

Impact: Possible slow memory leak in the SAM process when running GW-GW calls.

Root Cause: The GWFE is leaking a copy of an incoming PDU, which was queued internally.

Steps to Replicate: The steps are not reproducible because the trigger is a race condition that cannot be forced.

Platform/Feature: SBC

The code is modified to free the memory that was being leaked.
SBX-933672

MS Teams call flow for hold/resume then transfer causes a SCM crash.

Impact: When music on hold is used in the deployment and a call is put on hold/resumed and than transferred its causing the SBC to coredump in the SCM process.

Root Cause: The SCM process was dereferencing a null pointer.

Steps to Replicate: Music on hold is used in the deployment and a call is put on hold/resume and then transferred.

Platform/Feature: SBC: MS Teams

The code is modified to validate the pointer is not null before attempting to use it.
SBX-920921

Possible Memory leak in the Sam process.

Impact: The SAM process will leak memory in the case where a De-REGISTER is received and then within less than 30 seconds, another REGISTER in the same AOR is received.

This will only happen if Multiple contacts in the AOR flag is disabled.

Root Cause: The code does not free certain memory blocks.

Steps to Replicate:

  1. Multiple contacts per AOR flag will be disabled
  2. Do a Register for particular AOR and do a de-register.
  3. Within less than 30 secs, re-send the registration for same AOR so that SIPFE selects the same preferred slot which was used for registering the same AOR earlier. By registering multiple users with same time period, leak will be reproduced.

Platform/Feature: SBC

The code is modified to free the memory blocks.
SBX-921551

The SBC is releasing the Call with 504 when the DLRBT and Downstream Forking are enabled.

Impact: The SBC releasing the Call with 504 the when DLRBT and Downstream Forking are enabled.

Root Cause: Race condition is not handled properly. When first 180 without the SDP is received, there is an updated forking list and stored the message. On a second time when the 180 without the SDP is received, update the forking list and store the new 180 received.

Steps to Replicate: Send RTP before sending 180 Ringing ( CSeq: 961529 INVITE RSeq: 629928).

Platform/Feature: SBC

If RTP learning occurs before the corresponding 180 with SDP is received, save the SDP into the queue of possible SDPs to cut-thru for use while 200 OK is received.

Resolved Issues in 07.02.01R005 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-91273

1

When a user navigates to a SIP trunk group or DM PM rule creation screen, there is no response from the UI and after some interval of time, "Proxy error" is shown to the user.

Impact: The browser is timed out, resulting in "Proxy error" to the user.

Root Cause: The EMA reads the DM PM Rule, DM PM Sub Rule and DM PM Criteria data from CDB via Netconf interface. With large amount of data, there is a significant delay in rendering the UI. Due to the request, the browser is timed out resulting in "Proxy error" to the user.

Steps to Replicate:

1. Configure more than 25000+ DM PM Criterias and 25000+ DM PM Rules
2. Navigate to SiP Trunk Group Creation Screen or DM PM Rule creation screen
3. The create screen doesn't load and after some time results in Proxy error

Platform/Feature: SBC

Instead of CDB, the EMA reads the data for a DM PM Rule, DM PM Sub Rule and DM PM Criteria directly from the Oracle Database, reducing the delay to a larger extent in rendering the UI.

SBX-915702

If there is an SBC switch-over after a call is established, there may be a delay (for example, 30 seconds) when re-establishing the media from PSTN to MS Teams direction.

Impact: The stored SSN value does not update before the SBC switch-over occurs.

Root Cause: The stored SSN value is not updated before the SBC switch-over occurs, and it causes the SSN to jump backwards after switch-over, which causes a one way audio issue until the SSN value increments past the previously sent value.

Step of Replicate: MS Teams to PSTN call flow with DLRBT enabled on a software SBC. Perform a switch-over after the LRBT is played and check there is no one way audio issue.

Platform/Feature: SBC / MS Teams

After the LRBT is played, the latest SSN value is sent to the standby SBC so it can correctly jump the SSN forward on switch-over and media flow continues without delay post switch-over.
SBX-924792

In the I-SBC, the PKT Port redundancy support is not present in 7.2.2 release.

Impact: The PKT Port redundancy support is not present in 7.2.2 release.

Root Cause: In the I-SBC, PKT Port redundancy support added in 8.x releases.

Steps to Replicate: Configure the pkt port redundancy, port switchover to see the service continuity on PKT ports with redundancy enabled.

Platform/Feature: SBC

The PKT Port redundancy is back ported the support added in 8.x to 7.2.2. release.

Resolved Issues in 07.02.01R004 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-91726 / SBX-87861

1

PortFix SBX-87861: The SWe_NP thread hang was observed on a packet port pull out. (Originated in Release 8.1.0).

Platform/Feature: SBC

The thread health check mechanism is fixed on the port reset.

SBX-918201

The SBC was immediately disconnecting the SRS call after establishing the SIP Rec session with the next available SRS, when the initial SRS has responded with a failure 4xx response.

Platform/Feature: SBC

Invoked State machine with a proper event with only an old Sip Rec Call Block data is removed and the new Sip Rec Call Block data is retained. This avoids immediate disconnection of a new SIPREC Call, which is established with a second SRS.
SBX-917231

Portfix SBX-91493: On a CLI port switch over, a packet interface with random connectivity loss is observed for few seconds on other interfaces. (Originated in Release 8.1.0).

Platform/Feature: SBC

The correct NIF control blocks are added for standby ports.
SBX-881222

In scenarios where MS Teams referred the call to another user, the SBC started to play an RBT (ring back tone) and if the REFER failed due to the C-party not answering, the media is not established again between the A and B party.

Platform/Feature: SBC: MS Teams

The code is modified to correctly free up the RBT resources so the A to B call can be re-established.
SBX-918663

When the SBC sends out re-INVITE messages on a call leg supporting ICE, it can still include the "a=rtcp:<rtp port + 1>" value in the SDP that is different to the previously agreed RTP/RTCP mux setup on the remote end.

Platform/Feature: SBC: MS Teams

The code is modified to send an a=rtcp:<rtp port> value when sending re-INVITE messages for streams previously agreed to support muxed behaviour.
SBX-91813 / SBX-913321

PortFix SBX-91332: Getting the IP peer current statistics for an individual IP peer was not working. The issue is reproduced when multiple IP peers are configured under the same zone. (Originated in Release 8.1.0).

Platform/Feature: SBC

The code is modified by adding the comparison for IP peer specified in the CLI against the IP peer statistics list along with other existing validations.
SBX-91838 / SBX- 903082

PortFix SBX-90308: When the LRBT is enabled for an ICE call, the egress endpoint responds to initial INVITE with a 183 progress message with SDP parameters followed by a 180 without an SDP and a 200 OK with SDP. Following the local ring back tone, the SBC instigates a re-INVITE to the egress endpoint, which is missing ICE ufrag, password and RTCP candidate line in the SDP. (Originated in Release 7.2.2).

Platform/Feature: SBC: SIP, MS Teams

The code is modified to not clear the ICE information in this scenario.

Resolved Issues in 07.02.01F005 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-91098 / SBX-90673

2

PortFix SBX-90673: When multiple users registered from the same source IP and if the SBC receives SUBSCRIBE from second user, incorrectly fetches the RCB of first user (The pilot number) and forwards the SIP pdu to the wrong SIPSG slot. The SIPSG is not able to locate the RCB and rejects the SIP message with an 403 error response. (Originated in Release 6.2.5)

Platform/Feature: SBC

SIPFE uses the user name or pilot number (pilot number selected based on user name) while fetching the RCB. If the RCB is found at the SIPFE level, then it forwards the SIP pdu to the correct SIPSG slot.

SBX-903882

The NRS task failed healthcheck when there was over 3000 status requests per minute.

Platform/Feature: SBC

The NRS packet for the LIF status request process routine is updated to retrieve address context ID from a local cache instead of calling out to CONFD.
SBX-90540    2

When an SRS does not respond to the SBC's request, and if no redundant SRS is configured, the SBC sends a BYE response towards an SRS without XML. Also, the SBC terminates all the SIPREC calls towards the SRS by sending BYE responses.

Platform/Feature: SBC

The code is modified to invoke the API responsible for building XML body.

The code is modified so that when there is no response from SRS for the Re-Invite, the SBC terminates only the specific SIPREC call that did not receive the response.


Resolved Issues in 07.02.01F004 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-91386 / SBX-88070

1

Portfix SBX-88070: If a call to the sonusPeerUpload.expect is made and the peer goes down, the user may get stuck waiting for the scp connection, resulting in the application healthcheck timing out after 10 seconds. The timeout causes the application to crash. (Originated in Release 7.2.2)

Platform/Feature: SBC

A timeout for the scp is used in sonusPeerUpload.expect script to ensure that a user does not wait longer than 2 seconds for the scp connection to establish.

SBX-911141

SRTP enabled calls in the SWe SBC, causing sporadic NP worker crashes.

Platform/Feature: SBC

The SRTP SSRC update checks in the packet processing to verify whether API updates have cleared the reference to avoid null access.
SBX-914041

The audio becomes one way after there is a call transfer on the SWe when Ring Back is enabled with SRTP towards a MS TEAM. The enabled Ringback with SRTP relays the one way call transfer back to the PSTN behind the SBC. 

Platform/Feature: SBC

The NP code is modified to retain the enc contexts required for re-enabling and to start accepting media at the endpoint.
SBX-91370 / SBX-898771

Portfix SBX-89877: If the server sends multiple notifications without a record-route before the subscribe is stable, the SBC may core because the free memory being duplicated. (Originated in Release 7.2.2)

Platform/Feature: SBC

A NULL pointer is properly initiated after the memory free. 
SBX-912262

Unable to upload a configuration in the SBC Provision Management.

Platform/Feature: SBC: EMA/EMS

The code is modified to create an export directory to store a configuration file.
SBX-91394 / SBX-864271

Portfix SBX-86427: When large SIP PDU's(4096 B) are sent towards a monitoring server, the SBC cores because of buffer overflow. (Originated in Release 7.2.2)

Platform/Feature: SBC

Use TCP as transport towards monitoring server when PDU's towards monitoring server are large.
SBX-908972

In the Configuration Script and Template Import page, when you select 'Create Configuration from Template', you choose a Configuration from the table, and select Next. This template form is not getting displayed due to some failure.

Platform/Feature: SBC

The code is modified to display the Configuration template form properly when a Configuration is chosen from the table. A change is made to always display the Configurations list table first when 'Create Configuration from Template' is selected.

Note

 SBC v07.02.01F003 has been deprecated.


Resolved Issues in 07.02.01R003 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-91257 / SBX-90664

2

Portfix SBX-90664: The SBC was playing ring back tone while processing REFER and transferring the call. However, the tone was not heard on the original call leg because MS Teams had put the original call on hold. (Originated in Release 7.2.1R2)

Platform/Feature: SBC/MS Teams

The code is modified to send out re-INVITE message to take the original call off hold so that it can hear the ring back tone being played.
SBX-906542

The SBC was unable to retrieve a parked call. The call did not working correctly due to the NRMA process incorrectly swapping PSP information on the call legs. (Originated in Release 7.2.1R2)

Platform/Feature: SBC/MS Teams: SIP

The NRMA module is modified to correctly process PSP information on the different call legs during parking and retrieval of the call.
SBX-887431

Scm Process cores on receiving notifications from PCRF, which Registration Control Block does not exists. (Originated in Release 5.1.5R0)

Platform/Feature: SBC

The code is modified to terminate RX session on receiving De-Registration, so that PCRF will not send any notifications to the SBC. A fix is also added to handle notifications received from PCRF for which Registration Control Block does not exit. 
SBX-903882

NRS task failed healthcheck when there was over 3000 status requests per minute.(Originated in Release 7.2.1R2) 

Platform/Feature: SBC: Application, confd

Updated the NRS packet LIF status request process routine to retrieve address context ID from a local cache, instead of calling out to CONFD.
SBX-91188 / SBX-900613

Portfix SBX-90061: When the SIP trunk group->signaling->s8hrSupport flag is enabled, the SBC requests the PCRF for PLMN ID and waits for response. On getting PLMN ID response (or timeout), the SBC continues the call processing but did not free up all the internal resources causing a memory leak. (Originated in Release 7.2.1R0) 

Platform/Feature: SBC

The code is modified to correctly free all internal resources when the SBC continues call processing when retrieving PLMN ID or times out waiting on response to avoid memory leak.
SBX-90789 / SBX-900854

Portfix SBX-90085: When special character inputs are used for called number filter in the CDR viewer table, the input validation fails and the page keeps showing the table as 'Loading...'. (Originated in Release 6.2.0R0) 

Platform/Feature: SBC

The code is modified that the user can filter the Called number data in the CDR Viewer table, with numbers and few special characters such as #, *, +, -.
SBX-90135 / SBX-900882

Portfix SBX-90088: NOTIFY is rejected with 489 Bad Event after a double switchover. (Originated in Release 7.2.0R0)

Platform/Feature: SBC

Set the present bits of relayCbPtr->ingressTranspProfile and relayCbPtr->egressTranspProfile in SipSgActivateRelayCb.
SBX-90128 / SBX-889963

Portfix SBX-88996: The single character search is an exhaustive search operation and the browser witnesses Timeout Exception and renders a the blank screen to the user. (Originated in Release 6.2.4R0)

Platform/Feature: SBC: EMA

The code is modified to avoid and disallow single character search by rendering an appropriate error message to the user, in case the input does not match the criteria.
SBX-90044 / SBX-879842

Portfix SBX-87984: Web server leaks a private IP address through its HTTP headers. The leak will expose internal IP addresses that are usually hidden or masked behind a Network Address Translation (NAT) Firewall or proxy server. (Originated in Release 6.2.2R0)

Platform/Feature: SBC: EMA, Security

Header is modified before sending the response from Apache 2 server.
SBX-904153

All filters do not display for the tables like Call Detail Status, Call Media Status, Call Resource Detail Status, etc. (Originated in Release 7.2.0R1)

Platform/Feature: SBC

The code is modified to display filters for all columns in the Call Detail Status, Call Media Status, Call Resource Detail Status, etc. tables.
SBX-905812

When using EMA and accessing the Call Trace/Logs/Monitors > Log Management > TShark, the screen does not list the files if there are more than 130 files in the directory. (Originated in Release 7.2.0R0)

Platform/Feature: SBC

The code is modified to avoid setting the header transfer-encoding explicitly in java code for the SBC platform manager functionalities. Header transfer-encoding is handled by configuration files.
SBX-89996 / SBX-895863

Portfix SBX-89586: Token load option is not loading values into a template. No action is triggered even after a user clicks on Token load. (Originated in Release 8.0.0R0)

Platform/Feature: SBC

The code is modified to successfully load the Token load and display the value corresponding to attributes.

Resolved Issues in 07.02.01R002 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-88882

2

200 OK of INVITE received immediately after UPDATE/200 OK gets stuck and the call fails. 

Platform/Feature: SBC

Race conditions were handled by avoiding tone swap when 200 OK of INVITE is received immediately after UPDATE/200 OK.

SBX-88326

2

PRACK for locally generated 18x is relayed to other leg. This is because of bNw18xRcvd flag not reset when CallProgressCmd is called.

Platform/Feature: SBC

Reset the bNw18xRcvd flag in CallProgressCmd sp that prackEntry List has the right value updated.

SBX-87795 / SBX-87053

2

PortFix SBX-87053 (Originated in Release 8.0.0): Failed to apply ARS procedure on getting 503 (when FQDN and uriPreference configured on Egress side).

Platform/Feature: SBC

A fix is added in SipCallGetPeerSignalingInfoCmd() to get peer address from pstNextHopAddr only if it is valid.

SBX-89651 / SBX-87342

1

PortFix SBX-87342: SIP 503 error occasionally occurs in a test.

The issue is seen because the SBC wrongly identified INVITE PDU type as OTHER and not INVITE only in the case when the first partial PDU is received over TCP as a fractional INVITE word.

Platform/Feature: SBC

The SBC corrected the pre-parsing logic in partial PDU cases when the INVITE word received in first partial PDU is fractional, and the rest of the PDU in a second partial PDU.

SBX-89333 / SBX-87140

1

PortFix SBX-87140 (Originated in Release 7.2.2): First, DNS query was getting initiated through management even if IP was configured.  As default static routes are configured and management gets the preference, the DNS query was initiated through the management interface. 

Secondly, the Patchcheck process core dumped when a truncated DNS response was received from DNS server. The Patchcheck process core dump was happening because of its inability to handle a truncated DNS response. 

Platform/Feature: SBC

Static route for IP interface to the DNS server is provided to fix the issue of the DNS query not going through the IP interface. 

SBX-89383 / SBX-86553

1

PortFix SBX-86553 (Originated in Release 7.2.2): The SBC is not responding for ping request of higher bytes of 2000 using x710 NIC's.

SBX-89383: IP Fragmented Packets on X710 NIC will have issues and will get dropped. Due to this large packets with or without VLAN will be dropped and not handled by the SBC.

Platform/Feature: SBC

The X710 driver/hardware buffer size is adjusted properly to handle fragmented packets with VLAN and also to take care of the i40e driver overhead. This makes sure that packets of size 1518 are handled properly by the x710 NIC. However, jumbo packets are no supported.

SBX-89110

3

The SCM deadlock core dumps.

Platform/Feature: SBC: Application

Modified SIPSG and MRFRM to avoid CONFD lookup on the call processing path.

SBX-89567

1
A core dump was observed as memory of a few structures were not memzero.

Platform/Feature: SBC

When memory is allocated for the structures responsible for storing, the req-uri sets to memzero.
SBX-880543

BMC Serial Port skips character of input data, causing command failure.

Platform/Feature: SBC: BMC

The code is modified in BMC to trigger FIFO level to 4 bytes, by setting 0x41 in UART_FCR register.
SBX-890422
Locator LED is not blinking.

Platform/Feature: SBC
The code is modified in BMC to turn on and off locator LED.

Resolved Issues in 07.02.01F002 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution
SBX-880593

When a high number of endpoints are registering and un-registering frequently, the ScmProcess core dumps while deleting the registration control block for registration where the SIP redirecting server sent multiple contacts in a SIP 3xx response.

The SBC system starts and stops a very high number of timers for call and registration functionality to work correctly and assigns a timer ID as an incremented integer value. When the number of timers the SBC has started since startup is more than 4 billion (unsigned int32 bit max value), the next timer ID the SBC assigns is a wrapped value of 1. At this time, if there are any timers in use using a low timer ID, the SBC will fail to start the timer. If the start timer fails for a registration with the redirecting server sending multiple contacts to the SBC, the ScmProcess may core dump while deleting the registration control block.

Platform/Feature: SBC Core: Platform

The code is modified to ensure that timers that are present throughout the life of the SBC system are restarted with the new timer ID value.
SBX-873253

The Scm Process core dumps while trying to double free the memory associated with the username of registration of the AOR.

The previous register AOR block was freed. However, the username field was not set to NULL and a subsequent re-registration or refresh reuses the heap memory that was freed for the previous registration. When trying to free the current registration block, double free is detected and core dump occurs.

Platform/Feature: SBC

A defensive check for stEndpointAOR.puchUserName is added, and the value is set to NULL after it is freed to avoid double free.

Resolved Issues in 07.02.01F001 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-88482/SBX-87601/SBX-88477/SBX-85988

3

PortFix SBX-87601: The SBC is dropping the userpart in the RURI of the outgoing INVITE.

Platform/Feature: SBC

The code for SBX-62769 is modified to fix the issue.
SBX-88483 / SBX-882542

PortFix SBX-88254 (Originated in Release 6.2.3F3): The SBC rejects SUBSCRIBE requests with 403.

Platform/Feature: SBC

The code is modified so that the SUBSCRIBE requests are not rejected.
SBX-88439 / SBX-879442

PortFix SBX-87944: A blind transfer call occurs due to DLRBT. The internal tone flag on leg B was not reset properly. As a result, leg C fails to cancel the tone. 

Platform/Feature: SBC

The tone flag is reset when leg B is connected. 
SBX-87171  3

PortFix SBX-86593 (Originated in Release 6.2.4): The EMA Template fails to import the configuration when Special Characters are present.

Platform/Feature: SBC

The code is modified so that unwanted conversion of a String to its HTML entity representation is avoided.
SBX-886102

A memory leak occurs when rewriteIdentities is enabled on a SIP trunk group. If a SIP trunk group has rewriteIdentities enabled, there is a case in which memory that was allocated for temporary storage of a toHeader is never freed.

Platform/Feature: SBC

The code is modified so that in all scenarios, memory which is allocated for temporary storage of the toHeader is freed.

Resolved Issues in 07.02.01R001 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-86783 / SBX-73424

2
PortFix SBX-73424 (Originated in Release 6.2.4R0): The CDR field 8 in START and STOP records always shows zero even if there is a delay in the PSX response.

Platform/Feature: SBC: CDR

The code is modified to correctly calculate the delta of the setup message time and PSX response time.

SBX-86608

2
The problem occurred in the case of load scenarios where the generated key/salt values that depends on retrieval of Random Numbers returned zero value at first byte. The SBC SipRec fails to establish session and sends BYE.

Platform/Feature: SBC

Wrt key-salt generation validation is added.

SBX-86790 / SBX-86589

2

PortFix SBX-86589 (Originated in Release 7.2.2R0): Sip sig port is not responding to ARP if the ARP request comes on an interface which the sip sig port is not bound to.

Platform/Feature: SBC Core: Platform IP/Media Services

The signaling port address are properly relocated to an ipInterface with the matching subnet if the address is currently bound to an ipInterface in a different subnet. 

SBX-85675

1

Random Java code writing from Rest interface as the json dependency was not loaded.

Platform/Feature: SBC

Json dependency is added in the xml file.

SBX-86735 / SBX-86694

2

PortFix SBX-86694 (Originated in Release 8.0.0R0): Transfer cases failing as E2E PRACK needs to be disabled on transfer Leg, as provisional responses will not be relayed to other leg.

Platform/Feature: SBC

Code changes are made to ensure E2E PRACK functionality does not kick in after a call is transferred to prevent relaying provisional to the other leg.

SBX-85676

1

Reading any file from un-privilege Rest User from REST GET Request is not validated as the curl command was not sanitized.

Platform/Feature: SBC

Sanitization is added to correct this issue.

SBX-85742

2

Support for In dialogue REFER request when Response is present.

Platform/Feature: SBC

The code is modified in the SIP stack. If the Message type is REFER and PSX Response profile is configured before a response is sent to network, add the Custom Reason Text from the PSX Response Profile and not the default one.

If in the IPSP "Include Reason Header" is enabled, the SBC will Add Q.850 Reason header with the cause code, Reason text of Q.850 Reason Header configured into Response Profile.

SBX-864933

When the SBC does not find the route information for incoming call, it rejects it with Error response. In the error response message, Max-Forwards header was being added. 

Platform/Feature: SBC

The code is modified to avoid Max-Forwards header addition in Error response message.
SBX-858241

Issue 1: A 488 was sent because of Nrma Modify Failure when UPDATE followed by 18x without SDP was received. This is caused by Prack pending.

Issue 2: A 491 is issued when UPDATE is received immediately after 18x without SDP. This is again caused by Prack pending.

Platform/Feature: SBC

Issue 1: Added a flag check and OfferAnswer check to avoid this issue.

Issue 2: Added a flag check to avoid this issue.



SBX-867962

REFER Relay is not working in S-SBC.

The SBC allows REFER to be Relayed to the egress side in a D-SBC environment. It would reject REFER that should be acted upon if REFER Relay is not enabled.

Platform/Feature: SBC

Added to Relay In-Dialog Refer in S-SBC if the flag REFER Relay is enabled. If the Flag is disabled, the SBC rejects In-Dialog REFER.
SBX-867481

The SBC does not handle IP fragment timeout properly. When IP fragment timeout occurs, the fragment context is deleted and the per-nif in use count is decremented. There is a problem in the code where it decrements the incorrect nif.

The SBC's ability to handle de-fragmented packets will deteriorate. The NO DEFRAG MATCH count in "show table system networkProcessorStatistics defragStatistics" increments rapidly. If PSX responses are large and the IP packets are fragmented, you may see the SBC retry multiple times due to reassembly failures resulting in packet drops. 

Platform/Feature: SBC

The fragment timeout logic that is decrementing the wrong interface's current in-use count is modified. This problem only impacts hardware SBC. 
SBX-865231

When pcrf is enabled, SCM may core on switchover. 

Platform/Feature: SBC

The code is modified to prevent the pcrf related SCM core on switchover.
SBX-87110 / SBX-688582

PortFix SBX-68858: The SBC CDR 'GMT' timestamps jumped forward and backward.

Platform/Feature: SBC: CDR

The code is modified to calculate the correct timestamps when daylight savings time begins and ends.
SBX-86480 / SBX-869922

PortFix SBX-86992 (Originated in Release 6.2.4R0): SCM may core due to memory corruption caused by processing of Global PCDR Info received from Policy Server.

Platform/Feature: SBC

The code is modified to free previously allocated Global PCDR Info structure before allocating a new one. 
SBX-863482

While triggering a recording call towards SRS for a SIPREC Redundancy scenario, the SBC fails to build the XML Metadata Information which failed to trigger the Recording call.

Platform/Feature: SBC

Initialized the PeerGcid to default value.
SBX-856422

False alarms for unused mgmt interfaces on the SBC 5400.

Platform/Feature: SBC

The alarm is not generated if the management port does not have any LIF configured on the port.
SBX-87467 / SBX-635712

PortFix SBX-63571 (Originated in Release 5.1.6R0): The Active CE may fail to synchronize ("Call/Registration Data" stays in syncInProgress) after LSWU upgrade of Standby CE, when ipPeer pathCheck is used. The RTM process was not able to handle pathCheck messages that may occur during LSWU.

Platform/Feature: SBC: Application

The RTM process is updated to handle pathCheck messages which may occur during LSWU.
SBX-862772

CallFlow is captured properly but the sequence of the packet is out of order.

Platform/Feature: SBC

The code is modified to log the packets in the proper order.
SBX-858581

Non-default addressContext ACLs are not working.

Platform/Feature: SBC

The code is modified so that the non-default address context ACLs work properly.
SBX-866532

Log packets before and after SMM translations.

Platform/Feature: SBC

The code is modified to log the packets in the proper order.
SBX-874102

NRMA fails to select the AMR codec when restricted mode set is present in Offer and Route PSP during tone play.

Platform/Feature: SBC

An option under NrmaCodecIsBestPossibleMatch handled this issue.
SBX-875112

The SBC is not printing ingress details in callDetailStatus/callMediaStatus after switchover for REFER flow.

Platform/Feature: SBC

The code is modified so that the details are shown properly.
SBX-875292

The SBC is not intercepting media packets of one stream post REFER.

Platform/Feature: SBC

The code is modified so the SBC is able to intercept all streams of A leg post REFER.
SBX-877681

This issue occurred as routers respond to the ARP probe request sent by the SBC with a GARP request, and the target MAC in that ARP request is set to a broadcast MAC. The SBC expects the target MAC in the ARP response sent by router to contain the MAC address of the SBC port from which the request was sent. The SBC was not treating this as a valid response, which resulted in reporting standby links as DOWN.

Platform/Feature: SBC

The code is modified to compare the target IP address received in ARP response to the destination IP configured in Link Monitor when target MAC comparison fails. In case of GARP request/response, the target IP would be set to IP of the router sending these packets. This change will result in considering GARP request sent by the router as a valid response and reports link up.
SBX-877392

The SBC is not able to send local ACK after REFER when E2E ACK is enabled.

Platform/Feature: SBC

E2E ACK functionality should not kick in after call is transferred as 200 OK response does not need to be relayed to other leg. Code changes are made.

SBX-87730 / SBX-876483

XRM deadlock. Standby keeps restarting.

Platform/Feature: SBC

The issue is fixed by the XRM inserting the xres into the encryption hashtable after state becomes active, and by processing the modify (deactive-reactive) scenario, the hash entry in map should be updated, otherwise it causes the duplicate issue.

SBX-876222

The SBC does not honor the expires value from the registrar.

Platform/Feature: SBC

The code is modified to accept the expires value from the known contact of 200 OK when there are multiple contacts in 200 OK to REGISTER.

Resolved Issues in 07.02.01R000 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSeverityProblem DescriptionResolution

SBX-75934

2
Reject options with 503 internal error when blockdirection in TG is set to incoming/both.

Platform/Feature: SBC Core: SIP-Peering
The code is modified to reject the options (Max-Forwards:0) when the TG is configured with block direction incoming/both direction.
SBX-76448 / SBX-761211

PortFix SBX-76121: The SBC core dumps if P-Com.Session-info with SIP URI of the format sip:host is received. 

Platform/Feature: SBC CE: SIP

The code is modified to handle P-Com.Session-info with SIP-URI of the format sip:host.

SBX-76571 / SBX-74056

2

PortFix SBX-74056: Call scenario is inconsistent in the case of a SIP-I/SIP call with Hold on 180.

Platform/Feature: SBC 5000/7000 Series: SIP

Validation code is added to ensure that the SBC does not send out a generic notification with hold in the backward direction until after the call is answered. It is only sent out in the forward direction after the call has routed. Retrieve is also not sent out unless hold has previously been sent out.

SBX-76013 / SBX-75378

2

PortFix SBX-75378: Code to free a structure is missing from camRecordDestroyOptionalFields

Platform/Feature: SBC 5000 Series: Call Control

Code is added in camRecordDestroyOptionalFields to free the CAM_GLOBAL_CHARGE_REF_STR structure.

SBX-76041 / SBX-74899

3

PortFix SBX-74899: The SBC disconnects calls intermittently. After that, the UAC sends Re-INVITE without any change in SDP, so the SBC responds locally.

Platform/Feature: SBC Core: Application

Do not modify RID to enable Snoop if RID is disabled. Support is added to LE2LE BRES types so that RIDs are not enabled if the destination MAC address is not resolved.

SBX-76017 / SBX-75618

2

PortFix SBX-75618: SIPFE found the wrong Reg AOR and route Options to the wrong SG (slot).

Platform/Feature: SBC Core: SIP Access

The code is modified to route both Regs to the same slot and send Verify Options to the correct AOR endpoint.

SBX-76052 / SBX-74160

2

PortFix SBX-74160: If a T.38 packet arrives typically within 10 ms of channel activation, all appropriate initializations may not be completed.

Platform/Feature: SBC 5000/7000 Series: DSP

The code is modified so that early packets are rejected.

SBX-76016 / SBX-75864

2

PortFix SBX-75864: A memory leak occurs during configuration dialog authentication. 

Platform/Feature: SBC Core: SIP Applications

The code is modified so that memory is properly freed.

SBX-76012

1

The SBC does not allow "modify" or "add new header" when the last or final action was "reject" or "teardown".

Platform/Feature: SBC Core: Application

In the case of "reject" or "tear down", though failure status is returned, if the message is modified previously using any other SMM, the modified message will be considered.

SBX-76062 / SBX-75057

2

PortFix SBX-75057: SMM Dialog Statefull Variables with Dialog Transparency is not working. 200 OK for Re-INVITE sent, Bye Received and 200 OK is re-transmitted.

Platform/Feature: SBC Core: SIP

The Record-Route should be sent in 200 OK of Re-INVITE so that SMM with Dialog Transparency works.

SBX-76494 / SBX-76310

3

PortFix SBX-76310: In downstream forking and 18x without PRACK, the SBC does not relay a 180 response.

Platform/Feature: SBC Core: SIP

The code is modified so that the 180 response is not dropped.

SBX-76492 / SBX-76059

3

PortFix SBX-76059: NTP security improvements needed.

Platform/Feature: SBC 5000/7000 Series: Security

The fix contains NTP security improvements.

SBX-72863

3

TPAD crashed when it was setup for internal (IDP) format but received a mix of RTP and IDP packets. This caused TPAD to delete the buffer pool, and inconsistency resulted in illegal memory access resulting in a crash. 

Platform/Feature: SBC 5000/7000 Series: DSP

The code is modified to not delete the buffer pool because IDP channel is expected to receive only fixed size IDP packets. If it receives RTP packets, it will drop RTP packets but not re-carve buffer pool. 


SBX-76453 / SBX-75458

2

PortFix SBX-75458: When 180 Ringing is received before completion of UPDATE-200OK during an egress precondition inter-working scenario, an issue is seen.

Platform/Feature: SBC 5000/7000 Series: SIP

The code is modified to queue this 180 response event and release it when 200 OK for UPDATE is received.

SBX-76456

3

PortFix SBX-76182: Issues occur after SBC7K receives 181 on Egress.

Platform/Feature: SBC 5000/7000 Series: SIP

The Preconditions Update needs to be sent for 18x with SDP, and Ignore 18x needs to be sent without SDP.

SBX-75249

2

The error "Unable to login to peer shell, IP: 169.254.88.1" was observed after LSWU.

Platform/Feature: SBC SWe: Application

The code is modified to ensure the local file is always updated with the correct encrypted string present in the database.

SBX-76097


2

The new MAC address in the received Gratuitous ARP sent by the next-hop router will update the media packet headers of the existing calls.

The previous SBC behavior was to use the new MAC address from Gratuitous ARP (G-ARP) only if the IP address in G-ARP belonged to the peer. If the peers are reachable via the next-hop router, the existing calls can experience one-way audio when the next hop router’s MAC address changes.

Platform/Feature: SBC Core: Common Sonus Platform Services, Platform IP/Media Services

The code is modified to include processing G-ARP from the next-hop router when the media peers of existing calls are reachable via the next-hop router.

SBX-76851 / SBX-62682

2

PortFix SBX-62682: Deleting the IP interface while in dryUp action does not work correctly.

Platform/Feature: SBC 5000/7000 Series: CLI, EMA

The CLI warning is updated to inform the user about possible issues when deleting ipInterface in dryUp mode while there are active calls.

SBX-76844 / SBX-74460 

2

PortFix SBX-74460: The SBC releases ACK based on Stack State, while unaware of delayed ACK and Faking from Stack.

Platform/Feature: SBC 5000/7000 Series: Application

The code is modified to consider the delayed ACK.

SBX-76857 / SBX-76611

3

PortFix SBX-76611: Standby Subscribe with registration accessed an invalid address, causing a core dump.

Platform/Feature: SBC Core: SIP Applications

The code is modified to validate the address before giving access to it.

SBX-76856 / SBX-74725

2

PortFix SBX-74725: "Minimize relaying of media changes from other Call Leg All" is suppressing Re-INVITE to pass through codec in REFER scenario.

Platform/Feature: SBC Core: SIP

The code is modified to check the peer and the new codec.

SBX-76794 / SBX-76119


2

PortFix SBX-76119: For a SIP to SIP call using GW protocol between 2 SBCs with "Include OTG" selected, the OTG parameter in Egress Invite will contain GW trunk name instead of name of ingress SIP trunk group from ingress GW. 

Platform/Feature: SBC Core: Gw-Gw

The code is modified to work the same as if “SIP core” is being used between two SBCs, and put the name of ingress SIP trunk group from ingress GW into OTG parameter in egress INVITE (instead of the “interconnect” trunk group name (GWTG1)). 

SBX-76845 / SBX-71646

2

PortFix SBX-71646: While sending input data for certificate content, content is encoded and not read by netconf properly.

Platform/Feature: SBC Core: EMA

A check is added to not encode the certificate content while doing an import certificate for the PKI certificates.

SBX-76876 / SBX-74280

2

PortFix SBX-74280: After a user logs out of EMA, some of the http sessions are not cleared, which results in stale http sessions in the heap, causing an out of memory error. 

Platform/Feature: SBC 5000/7000 Series: EMA

The code is modified to terminate all http sessions during logout. Also if user logins to EMA with user session timeout set to disabled and closes the browser, then after 24 hours user session will be terminated.

SBX-76971 / SBX-75802

2

PortFix SBX-75802: A Radius account timeout occurs.

Platform/Feature: SBC SWe: Application

A check is added to avoid killing the session for a Radius user.
SBX-76916 / SBX-750862

PortFix SBX-75086: SCM core dumped due to an attempt to de-reference a NULL pointer. 

Platform/Feature: SBC 5000/7000 Series: Application

The code is modified to check that the pointer is non-NULL before attempting to de-reference it.

SBX-76972 / SBX-67707

3

PortFix SBX-67707: A swagger interface was exposed.

Platform/Feature: SBC: EMA, Platform, Security

The index.html file is removed, and the servlet entry from web.xml file is removed.

SBX-77014

3

Servers1 is not created in memusage log during upgrade from 5.1 to 7.1.

Platform/Feature: SBC: Install/Upgrade(Platform)

The code is updated to correctly create the servers1 field in the memusage log type so that upgrades complete correctly.
SBX-767572

The SBC adds duplicate Via headers.

Platform/Feature: SBC Core: SIP Applications

The code is fixed to remove duplicate VIA Headers.
SBX-85176 / SBX-746082

PortFix SBX-74608: When the minimize flag is off, and after egress resume on a call on hold takes place, the SBC sends an unnecessary INVITE.

Platform/Feature: SBC Core: SIP

The code is modified to suppress re-INVITE while the call is on hold.

SBX-85207 / SBX-746112

PortFix SBX-74611: When multiple switch over occurs, includeQ850Reason and unrecAction flags configured on custom cpcToSipCauseMapProfile are not honored and instead default values from baseProfile is used. Consequently, mapping between CPC to SIP cause code is incorrect. 

Platform/Feature: SBC Core: SIP

The code is modified to make sure the SBC honors the includeQ850Reason and unrecAction flags configured on a custom cpcToSipCauseMapProfile.
SBX-770212

The platformManager has broken logic.

Platform/Feature: SBC Core: ConnexIP OS, Platform

A postrotate configuration is added to make apache2 re-read its configuration after logrotate.
An issue where logs in /var/log/sonus/cnxipm/admin were not being rotated due to insecure permissions of parent directory is fixed.
All exim4 cron jobs and logrotate configurations were removed as they were causing an error during logrotate.
SBX-85185 / SBX-638962
When Dynamic LRBT is enabled, UPDATE with SDP change after call is connected is not sent to other leg and responded with 200OK. 

Platform/Feature: SBC 5000/7000 Series: SIP Applications

The code is modified to make sure if the dynamic LRBT is enabled, the UPDATE with SDP is handled and the SDP change is sent to the other leg and not responded to with 200OK.
SBX-76781 / SBX-750763

PortFix SBX-75076: If the SBC is re-ISOed and then loadConfig is performed, it results in the loss of confd.conf encryption keys. The encrypted fields in CDB then become non-decryptable. If an upgrade is performed in such a scenario from 4xx/5xx to 7.2.x, then it will fail as confd will fail to decrypt the mandatory encrypted fields and so the fields will remain blank in CDB. During startup post upgrade, confd will exit during validation phase as it will find blank for mandatory field.

Platform/Feature: SBC Core: Install/Upgrade(Platform), IPSec

To prevent upgrade failure, upgrade code is introduced, which fills in a dummy value if an empty value fund for mandatory encrypted fields.

SBX-85446

2

Apache Commons FileUpload package requires security upgrade.

Platform/Feature: SBC

Commons FileUpload package file to the latest version is updated to the latest version.

SBX-85110


2

The SBC is rejecting EVS Passthrough call for an invalid attribute added in fmtp line.

Platform/Feature: SBC

The code is modified to fix this issue.
SBX-857812

LSWU failure. Synchronization Failed For DNSC.

Platform/Feature: SBC : Install/Upgrade(Platform)

The Serialization code is corrected.
SBX-85661 / SBX-852731

PortFix SBX-85273: SMMs are not properly displayed in EMA.

Platform/Feature: SBC : EMA

The code is modified to display SMM rules properly while using 'View CLI'.
SBX-85501 /

SBX-85455

1

PortFix SBX-85455:

When the SBC receives an INFO message with content type as media_control + XML and XML body does not contain any tags, ScmProcess core dumps.

Example of an INFO message:

INFO sip:8906661212@10.7.5.110:5060 SIP/2.0 
Via: SIP/2.0/UDP 10.7.20.75:5061;branch=z9hG4bK-7225-1-5 
From: sipp <sip:sipp@10.7.20.75:5061>;tag=1 
To: sut <sip:8906661212@10.7.5.110:5060>;tag=gK00800082 
Call-ID: 1-7225@10.7.20.75 
Cseq: 2 INFO 
Contact: <sip:sipp@10.7.20.75:5061> 
Max-Forwards: 70 
Content-Type: application/media_control+xml 
User-Agent: ENSR3.0.67.5-IS1-RMRG348-RG930-CPI1-CPO777 
Content-Length: 20

X-Header=trying.

Platform/Feature: SBC Core: Memory Management

The code is modified to make sure ScmProcess does not core when the SBC receives INFO message with content type as media_control + XML and XML body is malformed. 
SBX-76553 / SBX-764082

PortFix SBX-76408: When Lawful Intercept is configured, the SCM process may leak memory. 

Platform/Feature: SBC 5000/7000 Series: SIP Applications

The code is modified to free the memory that is allocated for each call when Lawful Intercept in enabled.
SBX-76063 / SBX-679662

PortFix SBX-67966: ssreq launched from EMA was blank and was not loading. 

Platform/Feature: SBC 5000/7000 Series: EMA

A platform type check for the SBC is added.


SBX-856793

An EMA issue where Subscriber Numbers are in the Surrogate Registration Profile occurs when validation is missing for the Subscriber Numbers field.

Platform/Feature: SBC

The code is modified to validate the Subscriber Numbers field.
SBX-85622 / SBX-76903 3

PortFix SBX-76903: SMM headerInfo requirement different in EMA and CLI. The SMM entered in CLI will give an error in EMA.

Platform/Feature: SBC Core: EMA


The check for requestAll and responseAll message types where the method type is not added in the response is removed.
SBX-85012 / SBX-764692

PortFix SBX-76469: An SRTP Crypto call with x-dmi is corrupting Egress SDP.

Platform/Feature: SBC 5000/7000 Series: Common Sonus Platform Services

A bug in SIPSG that used incorrect NSD buffer when converting DM NSD to SDP and caused corruption in the result SDP is fixed.
SBX-85197 /

SBX-74066

2

PortFix SBX-74066: No audio is passed across in the early stage of the dialog.

Platform/Feature: SBC Core: Media

A check is applied so that PEM header on Ingress does not make a difference as it should only be used when received from Ingress.

SBX-76915 / SBX-66015


2

PortFix SBX-66015: G.711 playout buffer sizes were increased in release 6.0 as part of SBX-57507 so that the initial playout delay and jitter minimum occupancy threshold could be set at values up to 200 ms. However, the TPAD playout buffer was not increased in size, so this large setting of initial playout delay can result in a core dump.

Platform/Feature: SBC Core: DSP

The code is modified to ensure that the initial playout delay and the jitter minimum occupancy threshold will never exceed 50 ms.



SBX-761692

An issue occurs when DB backup was restored when backup was taken from the unsupported version.

Platform/Feature: SBC: Common Sonus Platform Services

The code is modified to set the bitmask. This bitmask is used to check when to reach into the signaling IP.
SBX-85918 / SBX-853121

PortFix SBX-85312:  After call transfer, the media loss detection feature turned OFF as the logic hit the MGSG feature, which accidentally turned the feature OFF.

Platform/Feature: SBC: Media

The code is modified so that if not MGSG, then the feature does not turn OFF.

SBX-758452

When HTP all header transparency is set with ignoring some headers related to Privacy, though IPSP Privacy transparency is disabled, we still send those ignored headers transparently. 

Platform/Feature: SBC: SIP, SIP Access

When sipHeader all transparency is enabled in HTP, and Privacy related headers transparency needs to be ignored, then all following headers should be ignored in HTP.

Refer to SBC SIP Transparency Implementation Guide for more information.

SBX-76972 / SBX-677073

PortFix SBX-67707: Swagger interface exposed.

Platform/Feature: SBC: EMA, Platform, Security

Swagger API documentation has been removed.



SBX-76857 / SBX-766113

PortFix SBX-76611: Standby Subscribe with a registration access invalid address caused a core dump.

Platform/Feature: SBC Core: SIP Applications

The code is modified to validate the address before accessing it.


SBX-76494 / SBX-763103

PortFix SBX-76310: Downstream forking and 18x w/o PRACK, cause the SBC to drop subsequent 180.

Platform/Feature: SBC Core: SIP

The code is modified so that the SBC does not drop 180.
SBX-852232

The SBC was unable to reach the benchmarking count of 150000 on bluefin setup.

Platform/Feature: SBC Core: Performance

The XRES hash table size is fixed, as it is unintentionally sized too small.
 SBX-71308 / SBX-713092

Fax tone treatment setting not working in a fax call with multiple m lines.

Platform/Feature: SBC 7000 Series: Media (FAX), SIP

The code is modified so that the call flow works.
SBX-72663 / SBX-85781 2

LSWU failure. Synchronization Failed For DNSC.

Platform/Feature: SBC SWe: Install/Upgrade (Platform)

 The serialization code is corrected.
SBX-765871
When a TCP connection is idle for more than 60 minutes, due to the Aging timer expiry, the connections are treated as inactive and will be disconnected by the S-SBC.

Platform/Feature: SBC: SIP-Peering

A New configuration flag, sipTcpConnectionAgingState, is introduced to control the Aging timer. 

If sipTcpConnectionAgingState is disabled, then TCP connections are maintained even if they are Idle for more than an hour. 

If sipTcpConnectionAgingState is enabled, then TCP connections are guarded by the Aging Timer and connections are removed if they are found Idle for more than an hour.

SBX-85035 / SBX-769782

PortFix SBX-76978: When the SBC has /var/log mounted on the external cinder volume, /home/sftproot/evlog is missing. This causes EMS statistics collection to fail.

Platform/Feature: SBC: Install/Upgrade(Platform)

The code is modified to replicate evlog dir on /home/sftproot/evlog, since /home/sftproot is the chroot directory for SFTP access.  
SBX-76862 / SBX-768612

PortFix SBX-76861: AIDE service is disabled initially, but can be enabled by user. False positives are reported by AIDE.

Platform/Feature: SBC: Common Sonus Platform Services

Temporarily disable AIDE to avoid false positives. Full implementation to provide user controls will undo this change.

AIDE can be enable by following these steps:

1. Copy /opt/sonus/sbx/scripts/aide.sh to /etc/cron.daily/aide 
Command: 
    cp /opt/sonus/sbx/scripts/aide.sh /etc/cron.daily/aide 
2. Run the aideinit to create baseline 
Command: 
   /usr/sbin/aideinit -c /etc/aide/aide.conf -f -y > /var/log/sonus/hids/aide_init.log

SBX-862762

Max-Forwards value is not getting decremented when the rfc7332ValidateMaxForwards flag is enabled for end to end ACK scenario.

Platform/Feature: SBC Core: SIP Applications

When endToEndAck and rfc7332ValidateMaxForwards flags are enabled, the SBC now decrements the value of the max-forwards value received from ingress by 1 and sends it to egress endpoint.
SBX-86289 / SBX-860031

PortFix SBX-86003: The SBC includes SDP in subsequent 18x while Update offer is pending. 

Platform/Feature: SBC Core: SIP Applications

Do not include SDP in 18x if the flag "include SDP in subsequent 18x" is disabled.
SBX-86340 / SBX-860942

PortFix SBX-86094: Late answer Onhold caused mismatch codecs.

Platform/Feature: SBC Core: SIP Applications

Ignore the response from Onhold while there is a pending Offhold about to send out. 


SBX-858592

In the case of a DNS crankback, TCB is getting replaced in pstCall and we do not have access to it. In the case of an MRF call application, CCB can be deleted because of an error event.

Platform/Feature: SBC

In the case of a DNS crankback when we replace pstTcb, set the pvCorrelationtag to NULL, Increase the 100 Trying Timer to 72, and remove correlation tags when destroy mrfRM CCB is called.

Resolved Issues in 07.02.00R002 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSevProblem DescriptionResolution

SBX-85187 / SBX-76066


2

PortFix SBX-76066: When the RTP monitoring profile is configured for a non-zero monitoring period, NP does not send any notification to the application for IPV6 RTP packets.

Platform/Feature: SBC CE: Application

The code is modified to match the IPv6 SRC IP address in the RTP packets so that a notification can be sent after the configured number of RTP packets have been received.

SBX-76501


2

The SIP Contact does not contain RegInfo with embeddedRegInfoinUserPart enabled.

Platform/Feature: SBC Core: SIP Access

With the embeddedRegInfoInUserPart flag enabled, the SBC now sends the same Contact's userpart in the request/responses towards the application server which is sent earlier in the REGISTER message.

SBX-85190

1

The UserPart received in Request URI of INVITE was truncated in the SBC, leading to call failures. 

Platform/Feature: SBC Core: Application

The code is modified to avoid the operation that caused the UserPart to be truncated.
SBX-852992

Verstat parameter is sent in the egress INVITE in the PAI header when privacy transparency is enabled in PSX and 'Do not Sent Received value' for verstat param is enabled in the STI Profile.

 Platform/Feature: SBC SWe: SIP

The code is modified to give precedence to the STI profile control and allow modification to the PAI header according to that profile setting. This change in precedence allows the "verstat" parameter to be removed from the PAI header if configured within the STI profile.


SBX-852911

NWDL License activation failed and core dumped was observed on standby node.

Platform/Feature: SBC CE: EMS

The buffer overrun is corrected.
SBX-770572

The SIPREC leg media changes to SRTP after the ingress leg of the CS call sends a re-INVITE.

Platform/Feature: SBC: Call Control

The code is modified to handle RE-INVITE cases when SRTP towards SIPREC is disabled. This takes care of both the INVITE and REINVITE cases whenever SRTP is supposed to be disabled towards SRS.
SBX-855552
When a 503 Error Response is received from MRF, MRFRM is not clearing its context. Calls are hanging towards the MRF Leg when FQDN is being used in the MRF Profile.

Platform/Feature: SBC CE: Media
The MRF context is cleared when 503 is received from MRF using FQDN.

Resolved Issues in 07.02.00R001 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSevProblem DescriptionResolution
SBX-76449 / SBX-764481

PortFix SBX-76448: The SBC core dumped if P-Com.Session-info with SIP URI of the format sip:host is received.

The SBC does not handle sip:host URI in P-Com.Session-info.

Platform/Feature: SBC CE: SIP

The code is modified to handle P-Com.Session-info with SIP-URI of the format sip:host.
SBX-76742 / SBX-764972

PortFix SBX-76497: M-SBC #3 in cluster 1 does not report in sync in the rgStatus. It is stuck in a sync state until rebooted.

Platform/Feature: SBC CE: Redundancy

Changes were made to clear node parameters for the node on which a member-failed event is received. Changes were also made to update the current role and service ID for the standby node in case member-failed is received for any other node, in order to avoid the race condition where member-failed and custom event may be received in quick succession due to a very short duration network glitch (< 1second).

SBX-767323

After setting the new CLI aggregate policer to unlimited, the bucket size and fill rate are set to 0pkt/s and block all packets.

Platform/Feature: SBC 5000/7000 Series: Security

The code is modified for an unlimited callrate or bucket size scenario.

SBX-76829 / SBX-765002

PortFix SBX-76500: Dead air occurs on the node after network maintenance because the same IP address is assigned to different SBCs.

Platform/Feature: SBC CE: Redundancy

The code is modified to generate an AMF_NODE_ARRIVE event in case of distributed (N:1) mode, so that NRS can process it and generate GARPs when the node is coming up in a standby role in the redundancy group. CHM handling of this event is also updated so that the northbound interface for the Cloud N:1 distributed mode is not disabled.
SBX-76862 / SBX-768612

PortFix SBX-76861: AIDE service is temporarily disabled as false alarms are generated.

Platform/Feature: SBC Core: Common Sonus Platform Services

AIDE is temporarily disabled to avoid false positives. Full implementation to provide user controls will undo this change.
SBX-76902 / SBX-742443

PortFix SBX-74244: ScmP core dumped due to a NULL pointer accessing a service group table entry.

Platform/Feature: SBC SWe: SIP

A NULL check is added before accessing the service group table entry.
SBX-76852 / SBX-626822

PortFix SBX-62682: Deleting the IP interface while in dryUp action causes an error.

Platform/Feature: SBC 5000/7000 Series: CLI, EMA, Platform IP/Media Services

The CLI warning is updated to inform the user about possible issues when deleting ipInterface in dryUp mode while active calls are taking place.


SBX-76919 / SBX-629172

PortFix SBX-62917: Configuration restore brings mgmtIntf4 interface to mgmtGroup.

Platform/Feature: SBC 5000/7000 Series: confd

The Active CHM process is enhanced so that is does not merge XML files received from the standby process in a CLI loadConfig scenario.
SBX-770362
Ingress trunkgroup stiProfile setting was assumed to be enabled and did not take into account that this setting might not be enabled. Therefore, the “null pointer" check was not in place, causing a coredump.

Platform/Feature: SBC Core: Application, SIP

The code is modified so that the setting is enabled and the core dump does not occur.

SBX-76495


1

The IKE process core dumped.

Platform/Feature: SBC CE: Application

The IKE timeout schedule callback function is updated to properly terminate and free the schedule structure, which prevents memory corruption from occurring.

SBX-76978


2

When the SBC has /var/log mounted on the external cinder volume, /home/sftproot/evlog is missing due to EMS stats collection failing.

Platform/Feature: SBC CE: Install/Upgrade (Platform)

The code is modified to replicate evlog dir on /home/sftproot/evlog, since /home/sftproot is the chroot directory for sftp access. 

SBX-76587

1

The S-SBC disconnects TCP connection after 60 minutes.

Platform/Feature: SBC Core: SIP-Peering

Based on the new configuration flag (sipTcpConnectionAgingState) if the flag is disabled, then every TCP connection in the SBC will be added in to the NON-AGING list.

Resolved Issues in 07.02.00R000 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSevProblem DescriptionResolution
SBX-624312

Update of attributes through the CLI and EMA do not reflect in Visual First Call Setup.

Platform/Feature: SBC 5000/7000 Series: EMA/EMS

IP changes should be made within the Visual First Call screen.
SBX-626672

The Cloud T-SBC allocates resources for Xcode calls even if the compression ratio is set to 0.

Platform/Feature: SBC SWe, CE: Platform IP/Media Services

The show table system mediaProfile and set system mediaProfile CLI commands have been hidden in SWe and Cloud variants.
SBX-63216

2


Some "STOP" records are missing in the CDR viewer.

Platform/Feature: SBC 5000/7000 Series: EMA

The Logstash has been upgraded from version 1.4.1 to version 1.5.6.
SBX-643823

Live Monitoring plotted graph time and system time do not match.

Platform/Feature: SBC CE: EMA

The code is modified so that the correct times show after changing the timezone without having to restart the server.

SBX-66254


2

The SBC does not support Interception for target update in Re-INVITE when E-E Re-INVITE is enabled.

Platform/Feature: SBC CE: Application

A light weight policy dip for RE-INVITE with P-Com.Session-info header to be relayed is triggered (when End to END Re-Invite flag is enabled). 

The LI is triggered when policy response is received.

SBX-670293

The SBC handles a SIP REFER blind transfer differently depending on the call leg (Ingress vs. Egress) where the REFER is received.

Platform/Feature: SBC Core: SIP

If the Refer TG is different than the original Egress TG then a PSX DIP is performed if skipRerouteQuerytoPsx is disabled.

If Refer TG is different than the original Egress TG then a PSX DIP is not performed if skipRerouteQuerytoPsx is enabled.

skipRerouteQuerytoPsx can be enabled only on Egress TG.

SBX-67191 / SBX-67938 / SBX-67939

2

With 1000 CPS and 120K sessions, a 99.999% success rate in the RHOSP setup is not achieved.

Platform/Feature: SBC 5000/7000 Series: Application

A new CLI parameter, operatorAggregatePolicer, is added.

SBX-69024

3

Two cipher suites were added to tlsProfile's supported ciphers.

Platform/Feature: SBC Core: Security, TLS

Two cipher suites were added to tlsProfile:

  • TLS_RSA_WITH_AES_128_GCM_SHA256
  • TLS_RSA_WITH_AES_256_GCM_SHA384

The changes were documented in the appropraite guide.

SBX-703242

Certain SIP Access call flows fail due to an ARP lookup failure after an upgrade to 6.2.1R1.

Platform/Feature: SBC Core: SIP Access

ICMP Echo Request is used to resolve the ARP failure.

SBX-71637

2

The SBC adds port 5060 instead of 5061 in the outgoing Route header in PRACK when Record-Route in incoming 18x contains transport=tls AND urihostport is missing.

Platform/Feature: SBC Core: SIP

The code is modified to set the port as 5061 in the Route Header.
SBX-71761 / SBX-683002

PortFixSBX-68300: IP fragmented signaling packets received on a signaling port within the media port range are dropped as rogueMedia. Calls utilizing signaling packets that are large enough to be fragmented fail.

Platform/Feature: SBC Core SIP

The code is modified to allow IP fragment reassembly of fragmented IP/UDP packets that are received on a SIP signaling port within the media port range. (With the exception of the default SIP signaling port of 5060).

SBX-71964 / GSX-57791

2

PortFix SBX-57791: Nature of Address (115) support is missing from ITU SIPROU variant for SIP-I calls.

Platform/Feature: SBC Core: Call Control, SIP

The code is modified to allow Nature of Address (115) for ITU variant.
SBX-721613

T-shark "Stop & Save Trace" from EMA does not stop the capture, the file still grows as _ECHO constant was added at the end of the file.

Platform/Feature: SBC 5000/7000 Series: EMA

__ECHO is added in alphabetical order.
SBX-722623

DSCP marking for T.140 Text media - new flag t140Dscp needs to be documented.

Platform/Feature: SBC 5000/7000 Series: SIP

Flag t140Dscp is added and documented.

SBX-72359


3

In the EMA Dashboard PSX Status, Standby needs to be added in a different color.

Platform/Feature: SBC 5000/7000 Series: EMA

A new color is added for Policy Server standby mode.

A figure and note are added to the documentation.

SBX-725432
The incorrect egress TG name is logged in the CDR and the CLI Display for outbound calls when configured for useRouteSet.

Platform/Feature: SBC SWe: CDR

The code is modified so that the correct egress TG name is logged.

SBX-727443

AMR andAMRWBchanges for improving SWE channel density.

Platform/Feature: SBC SWe, CE: DSP

The AMR and AMRWB improved the capacity code. Code is added, but channel density is not increased.


SBX-729292

The feature control flag is at IP peer level. Because of this, SIPFE goes for hash lookup to access Advance peer details for every call and the flag sits inside the peer.

Platform/Feature: SBC 5000/7000 Series: SIP Applications

The advancePeerControl flag is moved to Zone level from IP peer level. 

SBX-72970 / SBX-620833

PortFix SBX-62083: If an incoming call has contact in the FQDN, then ipPeer is missing in the trace for the incoming Invite.

Platform/Feature: SBC Core: SIP

The code is modified to get the peer IP from the activePeerIP field. 
SBX-730202

The Cloud I-SBC does not come up with Multiqueue enabled on RHEL 7.5 when multi-queue is enabled on RHEL 7.5. As soon as the instance was spawned with multi-queue in RHEL 7.5, the instance will disconnect automatically.

Platform/Feature: SBC CE: Application

The code is modified so that the instance does not disconnect automatically.

SBX-73082 /SBX-730253

PortFix SBX-73025: The sonusEma stop/start script does not return to prompt as an exit command is missing if the user stops EMA.

Platform/Feature: SBC Core: ConnexIP OS

An exit command is added if the user chooses to stop EMA.
SBX-73087 / SBX-679543

PortFix SBX-67954: While evaluating a displayWhen condition that involves an instance attribute, if the instance attribute is not set in CDB then the displayWhen condition evaluates as false. As a result, the EMA does not show the Exclude methods value.

Platform/Feature: SBC 7000 Series: EMA

The displayWhen handling code is modified so that the Exclude methods value is shown.
SBX-73089 / SBX-696142

PortFix SBX-69614: In the SIP Adaptor (SMM) Profile, the View CLI script outputs rules in the reverse order.

Platform/Feature: SBC 5000/7000 Series: Platform

A Rule sorter and action/criterion sorter were added to sort the rules based on index.
SBX-731282

Call trace cannot be disabled from EMA as the values entered for the attribute state were not saved properly. 

Platform/Feature: SBC SWe: EMA

The code is modified to ensure that the values entered for the attribute state are saved properly.
SBX-73157 /SBX-729732

PortFix SBX-72973: "Do not include SS in re-Invite" IPSP flag Config on egress but affect on ingress.

Platform/Feature: SBC Core: SIP

The code is modified to check the flag based on Ingress or Egress leg.

SBX-73174

 

3

The SBC should not allow a user to configure more than one URI in aorGroupProfile preferredIdentity.

Platform/Feature: SBC Core: CLI

The code is modified so that more than one URI cannot be configured.
SBX-73200 / SBX-731492

PortFix SBX-73149: SIP-SIP call flow works, but the SBC is still sending PEM to Ingress once it sends INVITE to Egress instead of waiting until Egress media cutthrough is done.

Platform/Feature: SBC Core: SIP

The Preconditions supported configuration issue where extra 18x is sent is fixed.

SBX-73360


3

CDR version for 7.2 needs to be captured in the relevant documents. CAM header fields need to be updated.

Platform/Feature: SBC Core: CDR

The documentation is updated.
SBX-73434 / SBX-730402

PortFix SBX-73040: For a SIP-GW-GW-SIP call flow, when the PSX sends a translated number to Ingress SBC1, the Egress SBC2 sends a translated number to Egress SIP endpoint. This behavior was altered starting with SBC 6.0.

Platform/Feature: SBC Core: Gw-Gw, SIP

The code is modified to ensure that the Egress SBC sends the original called number to the Egress SIP endpoint in the outgoing INVITE.


SBX-73475 / SBX-734172

PortFix SBX-73417: A queued reINVITE, race 491 conditions, and ACK with a different branch parameter value causes call failure. 

Platform/Feature: SBC Core: SIP

The UA layer is modified to prevent sending reject SDP to appl.
SBX-73467 / SBX-727763

PortFix SBX-72776: Based on a coredump analysis, the openSSL stack was automatically clearing sessions resulting in corruption, triggering a coredump. 

Platform/Feature: SBC 7000 Series: Application

The code is modified to prevent the openSSL code from automatically clearing sessions.

SBX-73477 / SBX-73327

2

PortFix SBX-73327: A small window of race condition for a rare case of digit insertion causes NP to crash.

Platform/Feature: SBC 5000/7000 Series: Platform

The NP design code is modified to prevent the crash.
SBX-73602 / SBX-735732

PortFix SBX-73573: A dummy sessionDescriptionPtr was created in SIPSG and then passed to NRMA. NRMA uses the dummy sessionDescriptionPtr passed from SIPSG where sRTPAdminState is disabled, causing the SRTP late media call to fail.

Platform/Feature: SBC SWe: Media

The code is modified so that if NRMA receives a dummy sessionDescriptionPtr, it checks for the notFullyQualified flag. If notFullyQualified is set to TRUE, sessionDescriptionPtr is ignored.
SBX-73717 / SBX-685912

PortFix SBX-68591: The SBC reports "Policy Data syncInProgress".

Platform/Feature: SBC 5000/7000 Series: Install/Upgrade (Platform)

The change done by SBX-59731 is reverted as policyDBSyncStatus can have 600 permissions when generated by Oracle.


SBX-73817 / SBX-734882

PortFix SBX-73488: The SBC coredumps when free memory is duplicated for transparency headers.

Platform/Feature: SBC Core: SIP

The cloning headers code is reworked to ensure that it is not accessing the invalid address.
SBX-74059 / SBX-739553

PortFix SBX-73955: SipFe is not able to find registration, when the From header is missing the userpart, resulting in SipFe being unable to find the correct slot for routing the call.

Platform/Feature: SBC Core: SIP

The code is modified to allow SipFe to continue looking for registration based on src Ip/port.
 
SBX-74153 / SBX-731623

PortFix SBX-73162: Privacy is handled incorrectly in the outbound INVITE as the SBC sends a restricted userpart in the From header.

Platform/Feature: SBC Core: SIP

The code is modified so that the SBC sends out Anonymous@Anonymous.invalid in the From header.
SBX-74319 / SBX-740732

PortFixSBX-74073: The SBC gives a response error when itrecievesa generic parameter with IPv6reference value.

Platform/Feature: SBC Core: SIP

The code is modified to support IPv6reference. 
SBX-74329 / SBX-742342

PortFix SBX-74234: During split brain recovery, the becoming-standby SBC may send packets out of pkt interfaces after GARPs are sent by the active SBC.

Platform/Feature: SBC 5000/7000 Series: HA

The code is modified to disable the packets NIFs to prevent ARP/GARPs from being sent from the becoming-standby before it restarts to become standby and after the active has sent GARPs
SBX-74332 / SBX-739132

PortFix SBX-73913: Split brain recovery may lead to blacklisted IP peers. In a split-brain scenario when the SBC application is brought down, the cleanup script invoked toggles the pkt ports. When the pkt port goes up, ICMPV6 packets are sent out to the pkt ports. The switch may map the wrong port with the active MAC address and start sending packets to the standby SBC. The packets should not be sent.

Platform/Feature: SBC Core: Application, Platform

When the SBC is brought down, the clean up script will leave the pkt ports at the "down" state at Linux level and also disable the pkt NIFs at the NP level. 
SBX-74338 / SBX-691372

PortFix SBX-69137: During IMS-AKA registration, IPSec policy and SA are configured in kernel and during de-registration, they are removed from kernel.

An issue in kernel IPSec code causes memory allocated for IPSec policy to not be freed even though IPSec policy was removed from kernel by application. This causes a memory leak in kernel module for each registration and the memory leak gradually increases as the number of registrations increases. 

Platform/Feature: SBC SWe: IPSec, SIP

The Kernel code is fixed so that memory allocated for IPSec Policy gets freed when the policy is removed from kernel by the application code.
SBX-74342 / SBX-741273

PortFix SBX-74127: MemUsage logs are not displayed in EMA.

Platform/Feature: SBC 5000/7000 Series: EMA

The code is modified to add support for Memory Logs.


SBX-74476 / SBX-727742

PortFix SBX-72774:  SBC was not able to convert when a state where ICE learning was completed to a state where ICE was not required on the call flow due to call forking. This lead to no audio after the call was set up. 

Platform/Feature: SBC Core: SIP

The code is modified so that there is audio after the call is set up.
SBX-74589 / SBX-743872

PortFix SBX-74387: E2E reINVITE caused the application offer to timeout. If a new offer is the same as a previous SDP, SIPS fails to send out a reINVITE.

Platform/Feature: SBC Core: SIP

The code is modified to force SIPS to send the reINVITE.
SBX-74813 / SBX-734332

PortFix SBX-73433: Call failures occur due to Lif with no available ports.

Platform/Feature: SBC 7000 Series: Platform IP/Media Services

The NRMA call allocation function to initialize media port range values in the call leg structure is updated.
SBX-74857 / SBX-743752

SBX-74375: SCM cored as a result of an attempt to copy from unmapped memory. 
This problem is not predictable - but will only happen if sipSigSrvcGrpRewriteIdentities is configured. 

Platform/Feature: SBC 5000/7000 Series: SIP

The code is modified to prevent copying from unmapped memory.

SBX-74863 / SBX-736361

PortFix SBX-73636: The SBC did not auto-recover after double failure.

In a case where both active and standby SBC processes go down in succession, it can lead to a state where active SBC node may continue to run as standby even if there is no node running in active mode in the redundancy group.

Platform/Feature: SBC CE: Platform

The code is modified to ensure service continuity in case of SBC double fault. 
SBX-75021 / SBX- 733912
PortFix SBX-73391: SCM process may coredump during multi-party redirection call flows.

Platform/Feature: SBC Core: Application

The code is modified to correctly define the size of the buffer used to transfer the peer active leg information, and copy the correct amount of data (from source to destination ICM messages).
SBX-75075 / SBX-745142

PortFix SBX-74514: The SBC (which later becomes standby) sends GARPs after GARPs are sent by the SBC (which stays active) after split brain recovery.

Platform/Feature: SBC 5000/7000 Series: HA

The code is modified to issue GARPs from the active node when a standby node joins the cluster.
SBX-749052

The application shuts down and restarts due to disk space usage.

Platform/Feature: SBC 5000/7000 Series: Platform

The code is modified so that the service shuts down instead of restarting.
SBX-74993 / SBX-653963

PortFix SBX-65396: EMS (SBC-Manager) and EMA are out of sync due to missing code for handling and accessing custom perspectives in the SBC. 

Platform/Feature: SBC 5000/7000 Series: EMA/EMS

Rest Services are implemented to ensure that custom perspectives are handled appropriately in the SBC.
SBX-751772

T38 stack v3.35 from Commetrex has broken v0 fax calls and should be reverted to the previous version.

Platform/Feature: SBC 5000/7000 Series: DSP

The code is reverted to the previous version.
SBX-73465 / SBX-733742

PortFix SBX-73374: PRS cored when SBX received a STUN message with a bad UDP header (UDP length field contained an invalid value). 

Platform/Feature: SBC 5000/7000 Series: SIP, TLS

The code is modified to ignore a STUN message if the UDP length field contains an invalid value.
SBX-752211

The SBC EMA does not allow uploading token files with the file upload as the token file extension is not supported in the file upload.

Platform/Feature: SBC Core: EMA

The code is modified to allow token files to upload successfully and to load the values from the token file into the Configuration script form.

SBX-75333 / SBX-740513

PortFix SBX-74051: Under a heavy load, while using IPSec AKA TCP feature, the SAM process may coredump due to the code not handling an error condition correctly.

Platform/Feature: SBC SWe: IPSec, SIP

Error handling for IPSec AKA TCP is improved. 
SBX-75335 / SBX-677132

PortFix SBX-67713: When sendRouteUriToPsx is enabled, useRouteSet is set as received, and the SBC receives NOTIFY before 200OK for SUBSCRIBE is received, the SBC sends NOTIFY received from the core side back to the core side instead of relaying it to the access side. 

Platform/Feature: SBC Core: SIP

The code is modified to ensure the SBC relays NOTIFY received before 200OK for SUBSCRIBE to the correct leg. 
SBX-753692

The M-SBC cannot establish IPSec connections after reboot/respawn during LSWU initiated switchover due to a pre-shared key getting re-encrypted. Encryption keys are not installed to the upgraded instances, due to which the instances are not able to decrypt the pre-shared key.

Platform/Feature: SBC CE: Application

The code is modified to install the keys from an older version of the configuration database.
SBX-75444 / SBX-725472

PortFixSBX-72547: GW-GW call fails when a LM Re-INVITE is received with passthrough configuration as the PAM message is not sent to egress gateway.

Platform/Feature: SBC 5000/7000 Series: SIP

The code is modified so that GW-GW calls do not fail. GW1 now sends MCS PAM to GW2 on receiving a Re-INVITE without SDP.

SBX-75492 / SBX-75463 2

PortFix SBX-75463: After TG delete, the SBC accesses an invalid TG address, causing SCM to coredump.

Platform/Feature: SBC Core: SIP Applications

The TG address is validated before access.


SBX-75559 / SBX-750522

PortFix SBX-75052: After a switchover, SBC will randomly pick a media IP address on sipTrunkGroups that has mediaIpAddress configured. 

Platform/Feature: SBC SWe: SIP

The code is modified to pick the configured mediaIpAddress.
SBX-74893 / SBX-734842
PortFix SBX-73484: The SBC does not send 180 ringing and 200 OK from GSX CPG and ANM, because of Downstream Forking Flag being enabled on Ingress TG.

Platform/Feature: SBC Core: SIP


The code is modified so that the SBC sends the 180 and 200 OK.
SBX-75507 / SBX-641752

PortFix SBX-64175: In SIP call forking, there is dead air after 200 OK.

Platform/Feature: SBC 5000/7000 Series: Media Resource Management, Platform IP/Media Service


If subsequent 18X responses are received for particular peer with the same SDP, then stop performingcutthroughfor subsequent responses.
SBX-75486 / SBX-729452

PortFixSBX-72945: Short Spikes in CPU Utilization of Management Processes triggers resource DRM Congestion Level 3 Alarms.

Platform/Feature: SBC SWe: Platform

The code is modified so that the alarms are not triggered.
SBX-75466 / SBX-750732

PortFix SBX-75073: SIP Recording of a call using SRTP to a SIP Recording Server (SRS) does not work. The SBC generates malformed SRTP packets which do not reach the SRS.

Platform/Feature: SBC SWe, CE: SIP

The SBC's packet snoop encryption software is fixed to adjust the packet data pointers due to the addition of the 10 byte authentication tag at the end of the packets.
SBX-75624 / SBX-594222

PortFix SBX-59422: PassThrough call converted to DM after HOLD/UNHOLD resulting in packets getting discarded after unhold.

Platform/Feature: SBC Core: SIP

The code is modified so that the packets are not discarded afterunhold.
SBX-752211

The SBC EMA does not allow uploading Tokens file with the Fileupload.

Platform/Feature: SBC Core: EMA

Configuration files are modified with the correct field names and the correct indexing.
SBX-730202

The Cloud I-SBC does not come up with Multiqueue enabled on RHEL 7.5.

Platform/Feature: SBC CE: Application

Multi-queue virtio instances support on OpenStack requires below command to be executed on the compute node:

  1. audit2allow -a -M attach_queue. 
  2. semodule -i attach_queue.pp 
  3. Try spawning SWe instance again.

Known Issues

Known Issues in 07.02.01R007 

There is no known issues in this release.

Known Issues in 07.02.01R006 

The following issues exists in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-935593

MS Teams calls that are put on hold and resumed multiple times can intermittently fail.

Platform/Feature: SBC

Impact: The timing of messages received from MS Teams can be occasionally different leading to out of sequence handling on the SBC, which causes the call to fail.

Workaround: No workaround available.

SBX-930522

MS Teams call flows that try to use call queue capability can fail to complete. 

Platform/Feature: SBC

Impact: The SBC does not include the transport=tls attribute in the contact header of the 200 OK message, sent back in response to the INVITE with replaces from the MS Teams.

Workaround:

Apply the SMM to the output adapter on the Microsoft Teams trunk group similar to the following:

set profiles signaling sipAdaptorProfile TEAMSOUT profileType messageManipulation
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 applyMatchHeader one
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 1 type message
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 1 message
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 1 message messageTypes response
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 1 message statusCode 200
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 type header
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 header
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 header name Contact
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 header condition exist
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 criterion 2 header hdrInstance all
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 type header
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 operation regsub
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 headerInfo headerValue
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 from
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 from type value
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 from value "5061;transport=tls>"
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 to
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 to type header
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 to value Contact
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 regexp
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 regexp string "5061\>"
set profiles signaling sipAdaptorProfile TEAMSOUT rule 13 action 1 regexp matchInstance all

Known Issues in 07.02.01R004 and 07.02.01R005

There are no known issues in these releases.

Known Issues in 07.02.01F004 and 07.02.01F005

There are no known issues in these releases.

Known Issues in 07.02.01R003

There are no known issues in these releases.

Known Issues in 07.02.01R002 

The following issue exists in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-877402

LI call not working when standby MSBC is upgraded.

Platform/Feature: SBC

Impact: Interception of calls fail during upgrade (for instance, when the setup has S-SBC and the M-SBC running on different versions). The impact is only for in-service upgrade. No impact with respect to calls, when the VNF is brought down and re-created for upgrade.

Workaround: No workaround available.


Known Issues in 07.02.01F001 and 07.02.1F002 Releases

There are no known issues in these releases.

Known Issues in 07.02.01R001 Release 

The following issue exists in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-880031

 If there are any PRACK drops and call fails, a memory leak occurs.

Platform/Feature: SBC

Impact: In the rare case where a PRACK for 18x is dropped and the call eventually fails, a small leak of SCM memory can occur.

Workaround: No workaround available.

Known Issues in 07.02.01R000 Release 

The following issues exist in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-85825 2

When a headend cluster configuration is pushed, the Standby SBC reboots and hangs without getting the Configuration.

When a Standby SBC is rebooted, it transitions to registered online then later unregistered offline. This also happens in #1, Standby reboot after Configuration is pushed.

Platform/Feature: SBC Core: EMA

Impact: When a headend cluster configuration is pushed, Standby SBC fails to download the configuration and so fails to come up properly.

Workaround: To resolve the above issue, the fill rate and bucket size needs to be increased in lca.py script and the Standby SBC system needs to be rebooted so that it can download the configuration again.

SBX-863542

CallMedia and CallDetailstatus do not show in the EMA during the load run.

Platform/Feature: SBC Core: EMA

Impact: Call details Status and Call Media Status are intermittently not visible in the EMA.

Workaround: Call details status and Call Media status can be viewed from CLI.

SBX-858241

Egress peer sends back two UPDATES messages during call setup. The second UPDATE is rejected with a 488. During the processing of the second UPDATE a 183 without SDP is also sent and forwarded to the ingress with 100rel.

Platform/Feature: SBC Core: Application

Impact 1: 488 because of Nrma Modify Failure when UPDATTE followed by 18x w/o SDP received. This is because of PRACK is pending.

Impact 2: 491 is issued when Update is received immediately after 18x without SDP with E2E Prack. This is again because of PRACK pending.

Workaround 1: Enable E2E Update so that update will be queued when PRACK is pending.

Workaround 2: No workaround available.

SBX-852282

Observed M-SBC reboot and PrsProcess crash during 30000 NP based tones playing.

Platform/Feature: SBC Cloud

Impact: Under load with 30,000 simultaneous NP tones playing M-SBC switches over. M-SBC system confirmed to perform fine up to 28,000 simultaneous NP tones.

Workaround: No workaround available.

Known Issues in 07.02.00R002 Release 

The following issues exist in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-850713

The SBC did not like the <4K size INVITE PDU since the maxPduSizeValue = 6K.

Platform/Feature: SBC

Impact: A PDU of a size less than 6K is rejected with 400 Bad Request, when maxPduSizeValue is set to 6K.

Workaround: Increase the maxPduSizeValue to 15k.

SBX-770542

An LSWU Upgrade from 7.0 to 7.1 failed.

Platform/Feature: SBC 5000/7000 Series: Application

Impact: While upgrading from pre-7.1 releases to 7.1 and 7.2 releases, if the SNMP trap targets are setup with <space> in the name field then the upgrade fails. This affects all the platforms (SBC 5xxx/7xxx/SWe).

Workaround: Prior to the upgrade, the user must check and delete/replace any trap targets that are setup with <space> in the name.

SBX-86003

1

While UPDATE is pending and a subsequent 18x is received on Egress, the SBC includes SDP in the subsequent 18x on Ingress.

Platform/Feature: SBC Core: SIP Application

Impact: The peer may reject the call.

Workaround: No workaround available.

SBX-858241

Issue 1: 488 occurs because of Nrma Modify Failure when UPDATE followed by 18x w/o SDP received. This is because we try to fake when Prack is pending.

Issue 2: A 491 issue occurs when UPDATE is received immediately after 18x w/o SDP with E2E Prack. This is again because of prack pending.

Platform/Feature: SBC Core: Application

Impact: UPDATES are rejected.

Workaround:

For issue 1: Enable E2E Update so that update will be queued when Prack is pending.

For issue 2: No workaround available.

SBX-860942

Call fail after onhold and offhold.

Platform/Feature: SBC Core: SIP Application


Impact: A call onhold/offhold before being connected by Update may fail.

Workaround: Enable E2E Update.


SBX-858592

A race condition occurs under a 3x load scenario where MRF is configured as FQDN and none of the MRF server responds.

Platform/Feature: SBC: DSBC

Impact: The SCM process may core dump.

Workaround: No workaround available.



Known Issues in 07.02.00R001 Release 

The following issues exist in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-760662

The SBC is discarding media packets when the SBC is monitoring and media packets are received from IPV6 terminated peer.

Platform/Feature: SBC CE: Application

Impact:

The RTP monitoring feature will not work for IPv6 terminated peers, and therefore the following behavior will be observed.

  1. If The SBC is in tone playing state and expecting media cut through after successful monitoring, the SBC will continue the tone play even though the expected RTP packet count is received, which is discarded by the SBC because of this issue.
  2. If the SBC does not have conditions for delayed tone play, is not in tone playing state and is expecting media cut through after successful monitoring, the SBC will discard media packets because of this issue.
  3. If the SBC has conditions for delayed tone play, is not in tone playing state, and is expecting media cut through after successful monitoring, the SBC will discard media packets because of this issue and therefore the delayed tone play starts because of the monitoring failure.

Workaround: no workaround for IPv6, but the same feature works for IPv4.

SBX-850713

The SBC did not like the <4K size INVITE PDU since the maxPduSizeValue = 6K.

Platform/Feature: SBC

Impact: A PDU of a size less than 6K is rejected with 400 Bad Request, when maxPduSizeValue is set to 6K.

Workaround: Increase the maxPduSizeValue to 15k.

SBX-770542

An LSWU Upgrade from 7.0 to 7.1 failed.

Platform/Feature: SBC 5000/7000 Series: Application

Impact: While upgrading from pre-7.1 releases to 7.1 and 7.2 releases, if the SNMP trap targets are setup with <space> in the name field then the upgrade fails. This affects all the platforms (SBC 5xxx/7xxx/SWe).

Workaround: Prior to the upgrade, the user must check and delete/replace any trap targets that are setup with <space> in the name.


Known Issues in 07.02.00R000 Release

The following issues exist in this release:


Known Issues

Issue ID

Sev

Problem Description

Impact/Workaround

SBX-74179


1

Cannot ping the G/W from the V6 interface alternatively when Alt_IP's are configured in X710 NIC card server.

Platform/Feature: SBC CE: Application, Platform

Impact: IPv6 with X710 NIC cards in SRIOV mode will not work as multicast packets will be dropped by the PF.

Workaround:

Set the trust mode to "on" for all the VFs on the computes.

ip link set dev <PF name> VF <vf id> trust on

This needs to be done for all computes and all created VFs (this change is not persistent across reboots). This will allow Multicast promiscous mode to work.

Otherwise, add a static neighbor table entry on the remote servers connecting to the SBC using the following command:

ip -6 neigh add <IPv6 address> lladdr <link-layer address> dev <device>

SBX-73218


 1

The S-SBC is unable to register 1M endpoints with 1000 RPS and is having a 180 second refresh Register with RHEL 7.5, RHOSP 13 (Queens) setup.

Platform/Feature: SBC CE: Application

Impact: Virtual ports intermittently stop responding on compute node running on RHOSP 13 (Queens) under certain conditions. Specifically, at 1000 RPS with refresh registration interval at 180 seconds, virtual ports stop responding after reaching 500K registrations. This issue is not seen when the refresh registration interval is configured as 200 seconds and above

Workaround: Use SR-IOV ports only when using RHOSP 13 (Queens) release.

SBX-73943


2

The SBC does not add all codecs when Update is received with updated SDP from egress and sends 200 OK for Update with all supported codecs towards egress, the SBC is playing tone.

Platform/Feature: SBC Core: Application

Impact: The call signaling and media work properly, but media clipping can occur if the final cut-thru codec received from UAS is different from the codec that is being used for playing tone. 

Workaround: No workaround available.

SBX-74945

 4

Unable to commit pkt and sip-sig config with single commit command. An error message is thrown when the commit command is given.

Platform/Feature: SBC Core: CLI

Impact: Commit cannot be issued in for all set commands until the ipInterfacegroup is committed.

Workaround: Commit should be issued for ipInterfacegroup first and then commit for the remaining set commands can be executed.

SBX-73660


 2

Unable to view TRAPS under Fault Management in Cloud-ISBC (Openstack Nova Platform) in EMS.

Platform/Feature: SBC CE: Application, EMA/EMS

Impact: EMS will not be able to identify the trap since the source IP address is packet interface.

Workaround: Add a static route to EMS from the SBC through management interface.

SBX-725132

Memory congestion was observed when executing around 64K calls in the 32GB SWe system.

Platform/Feature: SBC SWe: SIP-Peering

ImpactOn a SWe system with 32GB 32vCPU, the SBC is only able to scale up to 60K calls instead of 64K, due to per call memory increase.

Workaround: No workaround available.

SBX-713032

Observing 503 response for more time post port SWO in S-SBC.

Platform/Feature: SBC CE: Application

Impact: The load is 1000cps/120K calls. After doing port SWO on S-SBC, SBX rejects calls with a 503 response for 86 seconds. Later SBX again responds with 503 responses for approx 36 seconds. After that, it stabilizes.

Workaround: No workaround available.

SBX-727362

The SBC is not able to handle 150 Sa/Sec IPsec load on the Yellowfin Platform.

Platform/Feature: SBC 5000/7000 Series: SIP

Impact: If the rate for IPsec SA setup using IKE is increased beyond 60 SA/s, errors are seen.

Workaround: No workaround available.

SBX-72652


2

The PSBC observing system is in continuous iRTT congestion during the overload test.

Platform/Feature: SBC CE: Application

Impact: IRTT congestion is observed continuously for the 15 mins duration of 3x overload. There is no congestion during normal 1x load. This is 1000cps/120K in DSBC (PSBC).

Workaround: No workaround available.

SBX-745462

The SBC failed to generate Enum lookup after updating the dynamic metaVariable.

Platform/Feature: SBC CE: Application

Impact: Enum lookup fails to generate if the meta variable related to sipSigPort (used for the Enum lookup) is dynamically updated.

Example:

Before updating sipSigPort with new dynamic metaVariable:

admin@vsbc1% show global servers lwresdProfile

lwresdProfile DEFAULT {

    description          DEFAULT;

    enumDomainNameLabel  DEFAULT_ZONE_LABEL;

    enableLwresdLog      disable;

    type                 signalingIp;

    addressContext       default;

    eDnsGlobalBufferSize 4096;

    eDnsMonitorInterval  120;

    zone                 ZONE_ING_V6;

    sipSigPort           3;

    ipInterfaceGroupName LIG_ING_V6;

}

admin@vsbc1% show addressContext default zone ZONE_ING_V6 sipSigPort

sipSigPort 3 {

    ipInterfaceGroupName      LIG_ING_V6;

    portNumber                5060;

    mode                      inService;

    state                     enabled;

    transportProtocolsAllowed sip-udp,sip-tcp;

    ipVarV6                   IF2.IPV6;

}

[root@VSBCSYSTEM-vsbc1 linuxadmin]# lsof -ni:5060

COMMAND     PID       USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME

CE_2N_Com 32059 sonusadmin  110u  IPv6 3716854      0t0  UDP [fd00:10:6b50:5d20::c9]:sip

CE_2N_Com 32059 sonusadmin  111u  IPv6 3716855      0t0  TCP [fd00:10:6b50:5d20::c9]:sip (LISTEN)

CE_2N_Com 32059 sonusadmin  112u  IPv6 3716856      0t0  UDP [fd00:10:6b50:5d20::a9]:sip

CE_2N_Com 32059 sonusadmin  113u  IPv6 3716857      0t0  TCP [fd00:10:6b50:5d20::a9]:sip (LISTEN) 

ENUM query is successful from sipSigport (fd00:10:6b50:5d20::a9)

After updating sipSigport to new dynamic metaVariable:

admin@vsbc1> show table system metaVariableDynamic

CE NAME              NAME     VALUE                 

-----------------------------------------------------

vsbc1-10.34.195.109  lpl_egg  fd00:10:6b50:5d20::c9 

vsbc1-10.34.195.109  lpl_ing  fd00:10:6b50:5d20::c7 

admin@vsbc1% show addressContext default zone ZONE_ING_V6 sipSigPort

sipSigPort 3 {

    ipInterfaceGroupName      LIG_ING_V6;

    portNumber                5060;

    mode                      inService;

    state                     enabled;

    transportProtocolsAllowed sip-udp,sip-tcp;

    ipVarV6                   lpl_ing;

}

[root@VSBCSYSTEM-vsbc1 linuxadmin]# lsof -ni:5060

COMMAND     PID       USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME

CE_2N_Com 32059 sonusadmin  110u  IPv6 3716854      0t0  UDP [fd00:10:6b50:5d20::c9]:sip

CE_2N_Com 32059 sonusadmin  111u  IPv6 3716855      0t0  TCP [fd00:10:6b50:5d20::c9]:sip (LISTEN)

CE_2N_Com 32059 sonusadmin  112u  IPv6 3716856      0t0  UDP [fd00:10:6b50:5d20::c7]:sip

CE_2N_Com 32059 sonusadmin  113u  IPv6 3716857      0t0  TCP [fd00:10:6b50:5d20::c7]:sip (LISTEN)

ENUM query is not picking new sipSigport (fd00:10:6b50:5d20::c7) updated with dynamic metaVariable


Workaround: Do not update the metavvariable associated with a sipSigPort if Enum is being used.

Example:

Don't update the sipSigport to new metaVariable

admin@vsbc1% show addressContext default zone ZONE_ING_V6 sipSigPort

sipsigPort 3 {

    ipInterfaceGroupName      LIG_ING_V6;

    portNumber                5060;

    mode                      inService;

    state                     enabled;

    transportProtocolsAllowed sip-udp,sip-tcp

    ipVarV6                   IF2.IPV6;

}

SBX-756092

The SBC VM is failing to join back the cluster post switchover after healing (Recreate_destroy) N:1 MSBC VM.

Platform/Feature: SBC CE: Install/Upgrade(Platform)

 Impact: The Ribbon VNF Manager provides functionality to manually heal a VM within an  orchestrated VNF.  There are a number of options for healing provided, including a Recreate_destroy option.  There is an issue if the Recreate_destroy is executed on a VM that has DHCP enabled on its interfaces.  In this case, the VM is provided new IP addresses, causing that VM to be unable to re-join in the cluster.

Workaround: There is no workaround that is not service impacting.  Do not execute the Recreate_destroy option on a VM that has DHCP enabled.

SBX-742692

The IPv6/v4 Interface update with a new dynamic meta Variable is not deleting the old IP address.

Platform/Feature: SBC CE: Application

Impact: The old IP address is not getting deleted when the ipInterfaceGroup is updated with new dynamic meta variable.

Example:

Before updating ipInterfaceGroup with dynamic metaVariable:

admin@vsbc1> show table system metaVariable | match IF2.IPV6

vsbc1-10.34.195.109  IF2.IPV6      fd00:10:6b50:5d20::a9 

admin@vsbc1% show addressContext default ipInterfaceGroup LIG_ING_V6

ipInterface PKT_ING_V6 {

    ceName      SSBCACTIVE;

    portName    pkt0;

    mode        inService;

    state       enabled;

    ipVarV6     IF2.IPV6;

    prefixVarV6 IF2.PrefixV6;

    vlanTagVar  IF2.VlanId;

}

pkt0.609  Link encap:Ethernet  HWaddr fa:16:3e:ee:70:92 

          inet6 addr: fd00:10:6b50:5d20::a9/60 Scope:Global

          inet6 addr: fe80::f816:3eff:feee:7092/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:8954 errors:0 dropped:0 overruns:0 frame:0

          TX packets:9060 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:780288 (762.0 KiB)  TX bytes:902476 (881.3 KiB)                                                          

Creating dynamic metaVariable:

admin@vsbc1> show table system metaVariableDynamic

CE NAME              NAME  VALUE                 

--------------------------------------------------

vsbc1-10.34.195.109  lpl   fd00:10:6b50:5d20::cf 

vsbc1-10.34.195.110  lpl   fd00:10:6b50:5d20::ff 

[ok][2018-11-13 07:11:41]

After updating ipInterfaceGroup with dynamic metaVariable (lpl) old IP (IF2.IPV6) is not deleted from interface

admin@vsbc1% show addressContext default ipInterfaceGroup LIG_ING_V6

ipInterface PKT_ING_V6 {

    ceName      SSBCACTIVE;

    portName    pkt0;

    mode        inService;

    state       enabled;

    ipVarV6     lpl;

    prefixVarV6 IF2.PrefixV6;

    vlanTagVar  IF2.VlanId;

}

pkt0.609  Link encap:Ethernet  HWaddr fa:16:3e:ee:70:92 

          inet6 addr: fd00:10:6b50:5d20::a9/60 Scope:Global

          inet6 addr: fe80::f816:3eff:feee:7092/64 Scope:Link

          inet6 addr: fd00:10:6b50:5d20::cf/128 Scope:Global

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:9093 errors:0 dropped:0 overruns:0 frame:0

          TX packets:9209 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:792396 (773.8 KiB)  TX bytes:917382 (895.8 KiB)


Workaround: To change an addressContext ipInterfaceGroup to use a different ipVarV6 you must delete the ipInterfaceGroup and recreate it.

Example:

Delete the interface group:

 delete addressContext default ipInterfaceGroup LIG_ING_V6

Create interface group with new dynamic metaVariable:

admin@vsbc1% show addressContext default ipInterfaceGroup LIG_ING_V6

ipInterface PKT_ING_V6 {

    ceName      SSBCACTIVE;

    portName    pkt0;

    mode        inService;

    state       enabled;

    ipVarV6     lpl;

    prefixVarV6 IF2.PrefixV6;

    vlanTagVar  IF2.VlanId;

}

pkt0.609  Link encap:Ethernet  HWaddr fa:16:3e:ee:70:92 

          inet6 addr: fd00:10:6b50:5d20::cf/60 Scope:Global

          inet6 addr: fe80::f816:3eff:feee:7092/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:9093 errors:0 dropped:0 overruns:0 frame:0

          TX packets:9209 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:792396 (773.8 KiB)  TX bytes:917382 (895.8 KiB)

 Note: Similar procedure for IPv4.

SBX-758473

The RTCP port is not transparently passed in Direct Media.

Platform/Feature: SBC Core: Application

Impact: In case of a Direct Media call, the SBC will add an RTCP port in the outgoing INVITE SDP, when RTCP is enabled on Egress PSP and the RTCP port is not received in the incoming INVITE SDP.

Workaround: Disable RTCP flag on Egress PSP.

set profiles media packetServiceProfile PSP_DM_DTLS rtcpOptions rtcp disabled


Known Limitations

The following limitations exist in this release:

  • Due to a known EMA GUI issue, it can take up to 10 minutes to process each SMM rule when provisioning SMM on the SBC using the EMA. This will be fixed in a future release.

  • The Access Control List (ACL) is not installed to configure SNMP traps for accepting traffic. A dynamic ACL is added to configure SNMP traps. An ACL must be installed for SNMP traps for accepting traffic.
  • Ensure the physical NIC connectivity is in active state at the hypervisor level before starting the SWe instance on the SBC SWe platforms. In case of SWe instance with SR-IOV interfaces, manual restart of the SWe instance is required if physical NIC connectivity goes down while the instance is in progress.
  • The Antitrombone feature is not supported on the D-SBC.
  • EMS identifies the nodes based on the VNFC-ID. While instantiating SBC/PSX cloud nodes, ensure that you use a unique VNFC-ID only. If you reuse an existing VNFC-ID, EMS treats this as a re-registration request and overwrites the existing data on the cloud node.
  • While configuring the SBC SWe Cloud instances, the CLIs commits successfully even if any metaVariable provided is incorrect. The SBC SWe Cloud instance cannot validate the CLIs, as the CDB configuration file is stored in the SBC Configurator and is shared among all the other SBC SWe Cloud instances in the cluster.
  • Editing IP Interface is not reflected in the if configuration (ifConfig). This behavior is observed only on the S-SBC when action is set to "dryup" mode on the IP Interface. The IP address changes are not updated in the kernel and do not display when ifconfig linux command is executed. In case of S-SBC, if you need to modify the ipInterface configuration, and if the action is set to "dryup" in ipInterface configuration, you must set to "force" before disabling the ipInterface and making any changes.
  • Perform a LSWU on an SBC 7000 only when the total number of active calls on the system is below 18,000. If the criteria is not met, a double failure during the upgrade may occur thereby losing all active calls. If such a failure occurs, both active and standby SBC services will go down.  Contact Ribbon Support immediately.

The VLAN tagged SRIOV packet interfaces are unable to ping endpoint Gateway IPs in the VMware platform because of an issue with VMWare.

Performing Heat Stack Update when userdata is Updated with SSH Keys

When upgrading SBC SWe cloud instances to release 7.2, you must update your Heat template userdata section to include mandatory SSH key information. An issue in OpenStack requires that you use the stack-update process rather than re-launch after updating the template, which leads to a new UUID for the instance. As a result, you must regenerate and apply new license bundles to the upgraded instances during the upgrade.

Refer to Upgrading M-SBCs in an N:1 Redundancy Group for the relevant procedure. 

Restricted Functionality with SBC

The following functionalities are not supported with SBC Microservices:

  • SRTP
  • Far end NAT traversal
  • DTMF inter-working
  • RTCP termination for pass-through calls
  • Direct Media and Antitrombone
  • NICE, SIP-REC
  • Rx, Rf interfaces
  • Multimedia - MSRP, BFCP  
  • Fax detection
  • ICE/STUN
  • SIP REFER
  • SIP REPLACE
  • Two stage calls

  • H323 support
  • GW signaling support

Network Licensing Limitations

After switchover during grace period, when the new standby SBC comes up and establishes itself as standby, there is a short period (a few minutes) when the standby is synchronized for normal operation, but the new standby has not yet completed establishing its licensing state using the grace license information. If there is a second SBC switchover during that window, the new active SBC (which became active before completing license state synchronization) loses calls until it re-acquires the grace licenses.

For configuring Network Wide Licensing, refer to Configuring Network Wide Licensing on D-SBC. This procedure is common for D-SBC and SBC.