Skip to end of metadata
Go to start of metadata

Table of Contents

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 Sonus' Session Border Controller (Sonus SBC Core).

Please note that all Sonus bugs reported by customers on a given software release will be 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 Sonus SBC Core 06.02.xx documentation is located at the following Sonus Wiki space: Sonus SBC Core Documentation.

Release Notes Use and Distribution

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

Associated Sonus Bulletins

The following Sonus Bulletins are referenced in this release note:

  • Warning-18-00022905: LSWU failure can be caused by IP Peer PathCheck Profile misconfiguration. 
  • Warning-17-00022867: SM process may core dump after upgrading to the version 3 of the BMC software
  • Warning-17-00022848: Upgrade to the SBC 6.1.x version prior to 6.1.0R3 may fail
  • Warning-17-00022847: The DNS configuration parameters within the address contexts may cause certain configurations to fail during an upgrade to the SBC 6.2.0
  • Warning-17-00022689: Duplicate Trunk Group or Zone names can cause unexpected behavior
  • Warning-15-00021848: Some maddr call flows may fail if honorMaddrParam flag is not enabled beginning with 4.2.4
  • Warning-14-00020748: Verify system and databases are fully in sync prior to Live Software Upgrade (LSWU)

To view/download Sonus 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.

Problems or Questions

For problems or questions, contact the Sonus Technical Assistance Center (TAC) through telephone, fax, or e-mail:

Worldwide Voice: 1 (978) 614-8589

USA Toll-free: 1 (888) 391-3434

Worldwide Fax: 1 (978) 614-8609

About SBC Core

The Sonus 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 Sonus SBC Core software interoperates with the following:

  • SIP/H.323 compliant IADs and IP-PBXs
  • Sonus PSX Policy Server Softswitch via SIP redirects and/or Diameter+ protocol
  • Sonus SBC 9000 through SIP call signaling and Sonus Networks MCS protocol
  • Sonus 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, connectivity to the SBC will be lost any time 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 Sonus Products

Tip

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

Info

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

Refer to SBC 5000-7000-SWe Interoperability Matrices for the latest and minimum compatible Sonus product versions supporting 06.02.01R000 release.

Sample Heat Templates Included in This Release

To instantiate the SBC instances, the following templates are used:

Table : SBC Heat Templates

 Template NameDescription

heatConfiguratorNoDhcp.yaml

SBC Configurator Heat Template

heatRgNoDhcpDualStack.yaml

M-SBC/S-SBC Heat Template for IPv4 and IPv6 Dual Stack.

heatRgNoDhcp.yamlM-SBC/S-SBC Heat Template for IPv4 DHCP. These templates are used for port redundancy.

SBC SWe Cloud Requirements for OpenStack

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

Table : Server Hardware Requirements

 
ConfigurationRequirement
Processor

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

Note

It is recommended to use Westmere (or newer) processors for better SRTP performance. These processors have the AES-NI instruction set for performing cryptographic operations in hardware. 

 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 PKT ports must be 10 Gbps SR-IOV enabled port.

Note

6 NICs are required for supporting PKT port redundancy.

The system hosting SBC SWe must meet the following requirements: 

Table : S-SBC SWe Requirement

S-SBC SWe RequirementNotes

40 vCPUs

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

128 GiB RAM

It must be Huge Page memory and the minimum page size is 2048 KiB.

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.

Table : M-SBC SWe Requirement

 M-SBC SWe RequirementNotes

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

It must be Huge Page memory and the minimum page size is 2048 KiB.

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.

Table : SBC Configurator Requirement

 SBC Configurator RequirementNotes

4 vCPUs

None

16 GiB RAM

None

80 GB Disk

None

4 vNICs

Attach MGT0 port to the Management VirtIO Tenant network.

HA port has to be on IPv4 VirtIO Tenant network.

OpenStack Requirements

This section details the OpenStack requirements.

Note

Sonus tested SBC SWe Cloud on OpenStack Newton with RHOSP 10 and RHEL 7.4.

SoftwareVersion
OpenStackNewton

SBC SWe Cloud Requirements for AWS

Note

Prior to 6.2.1 release, the default CLI admin user name and password for AWS SWe was admin/admin. The hard coded password must not be used for the security vulnerability on the AWS SWe platform. In AWS Outputs tab, the field DefaultCliAdminPassword displays the default password to login to the CLI/EMA/PM admin user. For more information, refer to the sections Instantiating a Standalone SBC SWe Instance and Instantiating an SBC SWe HA Instance.

  • The default password is “eth0” interface ID for standalone instance.
  • The default password is “eth0” interface ID of assigned role active instance (instance with “-1” in the name) for an HA pair.
  • The system hosting AWS requires 65GiB of disk size.
  • You require an AMI ID to launch an instance. Contact Sonus sales representative to get access to AMI ID.

Note

Sonus recommends c4.2xlarge or higher instance type if this instance type is available in your zone. Use c4.2xlarge instance type or higher to handle more calls with transcoding.

You can use m4.xlarge instance type if the number of calls are less and does not require transcoding.

SBC SWe Requirements for KVM

The following table lists the server hardware requirements.

Table : 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

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


 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.


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:

Table : Server Hardware Requirements

 
 ConfigurationRequirement
Processor

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

Note

Westmere (or newer) processors are recommended 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 requires approximately 2 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 future SWe optimizations).

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

Only Intel I350 Ethernet adapter is supported for configuring as VMDirectPath I/O pass-through device.

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/7000 series software and firmware versions are required for this release:

Table : Required Software and Firmware Versions

Components

Software/Firmware

Version

SBC Platform

  

SBC 5000 series BMC

V03.15.00-R000

SBC 5000 series BIOSV02.06.00-R000
SBC 5400 FirmwareV03.15.00-R000

SBC 7000 Firmware

V03.15.00-R000

SBC Application

 

 

Operating System (OS) Version

V05.01.00-R000
SonusDB

V06.02.01-R000

SBC Application

V06.02.01-R000

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_6.2
  • SBC5x7x_6.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 Firmware

  • bmc5X00_v3.15.0-R0.rom
  • bmc5X00_v3.15.0-R0.rom.md5sum
  • firmware-5XX0-V03.15.00-R000.img

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

SBC 5400 Firmware

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

SBC 7000 Series Firmware

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

Note

Execute the Method Of Procedure (MOP) only for upgrading the FPGA image of an SBC 7000 DSP-LC card when the system is running firmware version 1.25.0, and the DSP-LC card has an FPGA image version that is older than 2014/06/11. 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-V06.02.01R000-connexip-os_05.01.00-R000_4_amd64.iso
  • sbc-V06.02.01R000-connexip-os_05.01.00-R000_4_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-V06.02.01R000-connexip-os_05.01.00-R000_4_amd64.qcow2
  • sbc-V06.02.01-R000.x86_64.tar.gz
  • sbc-V06.02.01-R000.x86_64.md5
  • sbc-V06.02.01-R000.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 TAC immediately.

Note

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

Note

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

06.02.01R000 Upgrade Information

Warning

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

Warning

Prior to performing an upgrade to 6.2 release, the duplicate trunk groups or zones must be removed. The steps to accomplish this are included in WBA "W-17-00022689". To view the WBA, log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) 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 06.02.01R000 release, execute the Method of Procedure, MOP to Re-configure 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 Supported Upgrade Paths.

Support of maddr Post-Upgrade

When upgrading SBC Core to release 5.0.0 (and above) from a pre-4.2.4 release, please take the following action immediately after the upgrade, if applicable:

  • If you are using the SBC with a Broadsoft system and SBC is configured for registration access (where SBC sits between SIP phones and the Broadworks System), you must take the following action immediately after the upgrade. 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, you must also make the below change immediately after the upgrade.

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. Default is ‘disabled’.

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

Info

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 "Adjust Resource Allocations" procedure on the 5.0.x page 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 manually check for the Hostcheck Validation Failed message in the upgrade.out log

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

  2. Check for /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

During an upgrade from pre-5.1.3 R000 to 6.2.0R000 release (with the BMC version 03.14.00), the SM process may coredump. The steps to accomplish this are included in WBA "Warning-17-00022867". To view the WBA, log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) and click the Bulletins link from the menu bar. Enter the bulletin number (last eight numbers) in the search field and press Return.

Warning

Prior to performing a Live Software Upgrade (LSWU), verify if the system and the databases are in sync. The steps to accomplish this are included in WBA "Warning-14-00020748". To view the WBA, log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) 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 6.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:

Supported Live Software Upgrade (LSWU) Paths

Warning

Prior to performing an upgrade to 6.2 release, the duplicate trunk groups or zones must be removed. The steps to accomplish this are included in WBA "W-17-00022689". To view the WBA, log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) and click the Bulletins link from the menu bar. Enter the bulletin number (last eight numbers) in the search field and press Return.

Warning

Prior to performing an upgrade to 6.2 release, the dnsGroups with type mgmt must be specified/updated with "interface" field. The steps to accomplish this are included in WBA "W-17-00022847".To view the WBA, log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) 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 a Live Software Upgrade (LSWU), verify if the system and the databases are in sync. The steps to accomplish this are included in WBA "Warning-14-00020748". To view the WBA, log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) and click the Bulletins link from the menu bar. Enter the bulletin number (last eight numbers) in the search field and press Return.

Warning

During an upgrade from pre-5.1.3 R000 to 6.2.0R000 release (with the BMC version 03.14.00), the SM process may coredump.The steps to accomplish this are included in WBA "Warning-17-00022867". To view the WBA, log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) and click the Bulletins link from the menu bar. Enter the bulletin number (last eight numbers) in the search field and press Return.

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

Table : Supported Upgrade Paths

V04.00.xx V04.01.xx V04.02.xx V05.xx V06.xx
V04.00.00R000 V04.01.00R000 V04.02.00R000 V05.00.00R000 V06.00.00R000
V04.00.00S100 V04.01.01R000 V04.02.00S100 V05.00.00R001 V06.00.00R001
V04.00.00S101 V04.01.01F001 V04.02.01R000 V05.00.00S102 V06.00.00F001
V04.00.00S102 V04.01.02R000 V04.02.01F001 V05.00.00S104 V06.00.00F002
V04.00.01R000 V04.01.02S001 V04.02.01F002 V05.00.00S200 V06.00.00F003
V04.00.01F001 V04.01.02F001 V04.02.01F003 V05.00.00S201 V06.00.00F004
V04.00.02R000 V04.01.02F002 V04.02.02R000 V05.00.00S202 V06.00.00F005
V04.00.02F001 V04.01.02F003 V04.02.02R001 V05.00.00S203 V06.00.00F006
V04.00.02F002 V04.01.03R000 V04.02.02R002 V05.00.00S204

V06.01.00F001

V04.00.02F003 V04.01.04R000 V04.02.02F001 V05.00.00F001 V06.01.00R000
V04.00.03R000 V04.01.04R001 V04.02.02F002 V05.00.00F002 V06.01.00R001
V04.00.03F001 V04.01.04F001 V04.02.03R000 V05.00.00F003 V06.01.00R002
V04.00.04R000 V04.01.05R000 V04.02.03F001 V05.00.00F004 V06.01.00R003
V04.00.04F001 V04.01.05R001 V04.02.03F002 V05.00.01R000 V06.01.00R004
V04.00.05R000 V04.01.05R002 V04.02.03F003 V05.00.01R001 V06.02.00R000
V04.00.05F001 V04.01.05F001 V04.02.03F004 V05.00.01R002  
V04.00.05F002 V04.01.05F002 V04.02.03F005 V05.00.01S001  
V04.00.05F003 V04.01.05F003 V04.02.03F006 V05.00.01F001  
V04.00.05F004 V04.01.05F004 V04.02.03F007 V05.00.01F002  
V04.00.05F005 V04.01.06R000 V04.02.03F008 V05.00.01F003  
V04.00.05F006   V04.02.03F009 V05.00.02R000  
V04.00.06R000   V04.02.03F010 V05.00.02R001  
V04.00.06F001   V04.02.04R000 V05.00.02F001  
V04.00.06F002   V04.02.04R001 V05.00.02F002  
V04.00.07R000   V04.02.04R002 V05.00.02F003  
V04.00.07F001   V04.02.04S100 V05.00.02F004  
V04.00.08R000   V04.02.04F001 V05.00.02F005  
V04.00.08F001   V04.02.04F002 V05.00.03R000  
    V04.02.04F003 V05.00.03R001  
    V04.02.04F004 V05.00.03R002  
    V04.02.04F005 V05.00.03R003  
    V04.02.04F006 V05.00.03F001  
    V04.02.04F007 V05.00.03F002  
    V04.02.04F008 V05.00.03F003  
    V04.02.04F009 V05.00.03F004  
    V04.02.04F010 V05.00.03F005  
    V04.02.04F011 V05.00.03F006  
    V04.02.04F012 V05.00.03F007  
    V04.02.04F013 V05.00.03F008  
    V04.02.04F014 V05.00.04F001  
    V04.02.04F015

V05.00.04R000

 
    V04.02.04F016 V05.00.04R001  
    V04.02.04F017 V05.00.05F001  
    V04.02.05R000 V05.00.05F002  
    V04.02.05R001 V05.00.05F003  
    V04.02.05F001

V05.00.05F004

 
    V04.02.05F002 V05.00.05R000  
    V04.02.05F003 V05.01.00R000  
    V04.02.05F004 V05.01.00F001  
    V04.02.05F005 V05.01.00F002  
    V04.02.05F006 V05.01.00F003  
    V04.02.05F007 V05.01.00F004  
    V04.02.05F008 V05.01.00F005  
    V04.02.05F009 V05.01.00F006  
     V04.02.05F010

V05.01.01F001

 
    V04.02.05F011 V05.01.01F002  
    V04.02.05F012 V05.01.01F003  
    V04.02.05F013

V05.01.01F004

 
    V04.02.05F014

V05.01.01F005

 
      V05.01.01F006  
     

V05.01.00F007

 
      V05.01.01R000  
      V05.01.01R001  
      V05.01.02F001  
      V05.01.02F002  
     

V05.01.02F003

 
      V05.01.02S001  
      V05.01.02R000  
     

V05.01.02R001

 
      V05.01.02R002  
      V05.01.02R003  
      V05.01.02R004  
      V05.01.03R000  

New Features

The following features are added in this release:

SBX-25205 SRTP to RTP Fallback on Receipt of 488

The SBC Core inter-works seamlessly with different types of endpoints on the access side for the successful call completion. With the increased usage of the SBC in the enterprise domain, it is exposed to work progressively with more endpoints, irrespective of their support for the Secure Real-Time Transport Protocol (SRTP), and/or IPv4 or IPv6 or not, on the same Trunk Group.

For more information, refer to:

SBX-54065 and SBX-35444 SWe Capacity Improvement and Estimation

The performance of the SBC VM can be optimized if the call mix is provided while configuring the SBC SWe instance. A set of predefined call mixes are provided, these are called standard traffic profiles. Additionally, a user can create custom traffic profiles, with a call mix that is more appropriate for the SBC SWe.

For more information, refer to:

SBX-56455 AWS: Benchmark SBC SWe with gp2 EBS Volume Support

This feature provides the performance statistics for AWS.

Note

  • HA Instances are launched on dedicated host.
  • PKTART Tools are also launched on dedicated host and flavor used is c4.2xlarge.
  • SweActiveProfile used for pass-through call is Standard pass-through and for transcoded its Standard transcoded.
  • Bench-marking numbers obtained can vary based on AWS network and also currently we are facing issue with AWS infrastructure where we are not able to pump the call load >2000 per leg on c4.2xlarge.

For more information, refer to AWS Performance Metrics.

SBX-61136 1:1 HA Support for AWS and non D-SBC Cloud

The parameter mgmtMode is added to system. This parameter specifies whether the instances are managed manually, or through EMS/VNFM.

For more information, refer to:

SBX-63432 RFC-4117 MRF Mid-Call Modification Enhancement

The SBC sends only a commit INVITE to the MRF server, and does not send any reserve INVITE to the MRF. This is applicable only for D-SBC on Openstack.

For more information, refer to D-SBC with Third Party MRF as Transcoder.

SBX-63665 RTCP Interworking Enhancements

The SBC is enhanced to support:

  • Relaying RTCP packets irrespective of zero or non-zero RS and RR values. 
  • Passing the received RS and RR values without changing them.
  • Sending the RR and RS values in the outgoing SDP (to peers or Media Resource Function (MRF)) only when the SBC receives these values.

Note

  • The RTCP must be enabled on both the legs (route PSPs).
  • The flags enableRTCPForHeldCalls and terminationForPassthrough must be disabled on both the route PSPs.
  • The RR and RS values must be configured to the maximum values of 4000 bps and 3000 bps respectively.

For more information, refer to AMR and RTCP Enhancements.

SBX-64632 SBC Supports of TIP Protocol

The SBC supports Telepresence Interoperability Protocol (TIP) to support multi-screen conferences. The TIP protocol is used to multiplex multiple screens, multiple audio streams, and an auxiliary-data screen into respective Real-Time Transport Protocol (RTP) flows using a multiplexing technique both for audio and video data. It enables point to point and multipoint sessions and mix of multi-screen and single-screen endpoints.

For more information, refer to TIP Protocol Support.

SBX-65039 An Alarm is Generated for Fatal DSP Device or Card Failure

The SBC is enhanced to generate the alarm sonusSbxDspCardOrDeviceFailureNotification when the DSP card fails:

  • to load during the server startup, or
  • during normal operation.

For more information, refer to:

SBX-65495 Performance Metrics for SBC Microservices on OpenStack

This feature provides performance statistics for SBC microservices on OpenStack.

For more information, refer to Microservices SBC on OpenStack: Performance Metrics.

Ported Features from Previous Releases

Release 06.00.00F005

SBX-65110 CPC Parameter Settings in PAI SIP-URI

The SBC is enhanced to collect the Calling Party's Category (CPC) parameter value from the SIP URI of a P-Asserted-Identity header or from a MIME body (in SIP-I scenario) on the ingress side of the trunk group. The value of the same CPC parameter is generated on the egress side.

For more information, refer to:

SBX-65112 New NNI Profile flags

In this enhancement, two flags are added to the profile NNIProfile. The flags are:

  • setHiPresentationRestricted
  • addUserEqualPhoneforDivHiInterworking

 For more information, refer to:

Release 05.01.03R000

SBX-58909 Enhancement to SIP Ladder Diagram

The SBC is enhanced to provide following information in the complete SIP PDU message:

  • CDRs at the beginning of the file.
  • Directions of the messages (ingress/egress or received/sent)
  • Transport protocol (UDP/TCP/TLS/SCTP)
  • Date next to the time (part of timestamp)
  • IP addresses with the port numbers of the senders and receivers

For more information, refer to Troubleshooting Tools - CDR Viewer.

SBX-59735 Support for Multiple TLS Peer Name per TG Required

The SBC is enhanced to support the user to specify multiple TLS peer names in the Sip Trunk Group separated by comma. This feature is used to specify multiple TLS peer names in the Sip Trunk Group.

Note

This feature does not support the use of the wild card or regex.

For more information, refer to:

Issues Resolved

Issues Resolved in 06.02.01R000 Release

The following issue are resolved in this release.

Table : Resolved Issues

Issue ID Sev Problem Description Resolution
SBX-34414 3

The password encryption method must be changed to SHA-512 method. The current BMC user password encryption method is md5sum, which is easy to brake the password.

Platform/Feature: SBC 5000/7000 Series: BMC

The code has been modified to change the Linux user password encryption from MD5SUM to SHA512.
SBX-46014 2

Re-installing the SBC from an ISO image followed by restoration of a previous configuration backup file can lead to the loss of encrypted configuration parameters. This can cause Radius authentication to fail unless the radiusSharedSecret is re-entered and CDRs also fails to be sent to the CDR server.

Platform/Feature: SBC Core: Platform

Restoration from backup configuration will re-install the encrypted keys required for the restoration of the encrypted configuration parameters.

Note: The backup configuration must be obtained from the SBC versions, which has the fix for SBX-46014.

SBX-47332 2 During an SBC upgrade from 5.1.x to 6.1.x version, the administrator or the valid user can view a generic message stating "Invalid Username/Password" instead of showing the exact reason in case the administrator or the user cannot log on to the EMA GUI.

Platform/Feature: SBC 7000 Series: EMA/EMS

 

The code has been modified to verify:

  • the display of the appropriate messages in case of error scenarios.
  • the password change per day for non-admin users in the CLI.
  • that there is no discrepancy in EMA GUI and auth.log error message.
SBX-49377 3 The TCP calls drop after an SBC switchover.

Platform/Feature: SBC Core: SIP

When a reINVITE is received from the application server before the Access re-registers, the SBC tries to send this INVITE towards the access. As the TCP connection was lost due to switchover and the UE has not established TCP connection yet, the SBC responds with 480 to the server from the SIP stack. This response is not sent to the server. Once the sync is completed from the the switchover, the session refresh INVITE is sent to the phone.
SBX-53980 3

The licenseInfo parameter does not show updated expiration date once the license expires with multiple bundles. 

Platform/Feature: SBC Core: Platform

When the expiration date of the license changes, the new expiration date is now updated in the licenseInfo status command output.

SBX-60569 3

The wrong display of CPU utilization data in top command output after the SBC was upgraded to Kernel version 3.16. This is a known issue with all 3.16 and higher kernels.

Platform/Feature: SBC SWe: Call Control/Platform

To resolve this issue, the 06.02.01 documentation is updated with the following note:

For applications using Linux kernel version 3.16 or higher (for example, SBC v06.02.00 and higher), the output of the top command displays wrong, and sometimes unrealistic, values about CPU utilization. This is a known issue with all 3.16 and higher kernels (refer to this CentOS page for more information).

Likewise, the information and graphs displayed in this EMA window may display wrong values of CPU utilization.

You can use top -H or mpstat commands to check the memory and CPU utilization.

SBX-61489 2 The remote NTP server responds to mode six queries.
 

Platform/Feature: SBC Core: Application: SBC Swe Cloud: Application

The ntp config code has been modified to resolve this issue. The NTP mode six queries are not possible on the port 123. Nessus is logging into the SBC and then running an ntpq command. This is a false positive as in a general situation, the ACL rules for the port 123 is not open. Thus, the ACL rules cannot reach mode six queries of SBC, which acts as a ntp client. The following additional restriction is added to the ntp config:

 kod nomodify notrap nopeer.

SBX-61713 3

The BMC does not support DHCP. The DHCP option is available in BMC WEB UI.

Platform/Feature: SBC 5000/7000 Series: BMC

The code has been modified to remove the DHCP option from the BMC WEB UI.
SBX-62623 /
SBX-62327
2 The EVS codec is not sent transparently though Audio Transparency Feature is enabled.

Platform/Feature: SBC 7000 Series: Media

The code has been modified to use the proper codec index while copying FMTP Attributes for known Codecs.
SBX-63016 /
SBX-63927
3

During upgrade of standby server, availability of upgrade packages, is checked on active server, which can sometimes return errors and cause upgrade failure.

Product/Feature: SBC Core: Application

The issue is because of incorrect sequence of commands sent from standby to active and expecting responses in a certain order. Fixes are made to address the issue.
SBX-63113 /
SBX-62734 /
SBX-62856
2 With dialog transparency and downstream forking enabled, and with preconditions defined, the SBC does not properly relay 18x and 200 OK messages to the ingress leg after the preconditions are met. After the affected call disconnects the SBC ScmProcess coredumps. 

Platform/Feature: SBC 7000 Series: SIP

The SBC call forking logic has been enhanced to properly relay messages to the ingress leg and to prevent a coredump.
SBX-63280 /
SBX-67107
2

The file permissions do not follow least privilege.

Platform/Feature: SBC 5000/7000 Series: BMC

The code has been modified so that the shadow and password files are protected by non root users.
SBX-63407 /
SBX-62759
2 With dialog transparency and downstream forking enabled, a race condition when setting preconditions causes calls to fail.

Platform/Feature: SBC Core: SIP

The code has been modified to avoid race conditions allowing forked calls to be set up successfully.
SBX-63413 3

Time zone once set to any zone resets after reboot and after firmware upgrade.

Platform/Feature: SBC 5000/7000 Series: BMC

The code has been modified to preserve the timezone after BMC reboot and upgrades.
SBX-63469 3

The BMC's version of ipmitool does not disable watchdog properly.

Platform/Feature: SBC 5000/7000 Series: BMC

There is an issue in the ipmitool, which reports failure even command (ipmitool -H127.0.0.1 -U root -P $passBmc mc watchdog off ) is successful.
SBX-63477 /
SBX-64171 /
SBX-65633
3

The output from the AIDE cron job contains false positive indicators that the software was changed.

Platform/Feature: SBC Core: Platform

The issue arose because the AIDE database was being initialized before all installation changes were completed. The AIDE database initialization now occurs later in the sequence to ensure the database is initialized properly before the cron job runs.
SBX-63615 /
SBX-63474
2

 In a downstream forking scenario, the SBC is adding SDP to the 200 OK response to an INVITE from the ingress leg when the 200 OK received from the egress leg did not contain SDP.

Platform/Feature: SBC 7000 Series: Call Control

The SBC forking logic has been modified so that it no longer adds SDP to the 200 OK response in this scenario.
SBX-63641 /
SBX-63312
2 In a forking scenario involving multiple 18x messages, the SBC responds with a PRACK message containing an improper RAck after receiving a 18x message that does not contain the 100rel option tag or RSEQ value.

Platform/Feature: SBC 7000 Series: SIP

The SBC now sends the correct RAck header value because it no longer updates the PRACK list for 18x messages that do not contain Require:100rel.
SBX-63684 2

Invalid username format when user contains ".". When the username contains "." in the name, the user is created in the CDB instead of OS.

Platform/Feature: SBC Core: Platform

The code has been modified to add SonusUserName type in the yang for specifying allowed and disallowed characters in the user name rules.
SBX-63858 3

In SBC 5400, chassis.sh -r was reading wrong register values.

Platform/Feature: SBC 5000/7000 Series: BMC

There is an issue in the chassis.sh script. Thus, the chassis.sh script must be used through i2c command:

i2c-test -b 1 -s 0x58 -m 1 -rc 1 -d 0

SBX-64033 / SBX-65321 2

The EMA node name displays incorrect value.
There was no predicate condition with cename.

Platform/Feature: SBC Core: Platform

The code has been modified to add predicate to display correct node name.
SBX-64189 /
SBX-63843
2

SIP INFO DTMF to RFC2833 Inter working fails when ICE is enabled.

Platform/Feature: SBC Core: Platform

The code has been modified to allow RFC2833 digit insertion on ICE and/or DTLS media calls.

SBX-64232

2

An unexpected response from the licensing server caused the licensing client to repeatedly loop trying to retrieve the SWE-INSTANCE License. 

Platform/Feature: SBC SWe: Application

The code has been modified to handle the unexpected response from the licensing server.
SBX-64283 /
SBX-64095
2 In a forking scenario, the Require header in a 183 response in the second dialog is separated into two lines.
 

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified so that the Require header appears on a single line with values separated by a comma.

SBX-64313 /
SBX-63782

3 The SBC does not send a DNS NAPTR query when transport type preference is not specified.
 

Platform/Feature: SBC 7000 Series: Call Control

The SBC code has been modified to add a transport parameter to Record Route once the transport type is resolved.  The dialogTransparency flag must be enabled in this scenario.
SBX-64316 /
SBX-63508
2

In a forking scenario, the SBC does not relay PRACK and UPDATE messages properly between the different dialogs.

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to address a race condition. Thus, the SBC relays the messages to the proper dialogs.

SBX-64322 /
SBX-63863 /
SBX-63862

1

In a forking scenario, the SBC does not relay the SDP in the second dialog 18x message if it is received at the same time as the first dialog 18x.

Platform/Feature: SBC 7000 Series: Call Control

The SBC uses a queue mechanism to handle overlapping 18x message sequentially, which allows the SBC to relay the SDP for the second dialog 18x.
SBX-64324 /
SBX-63866
3 In a multiple dialog scenario, the SBC does not relay 183 and UPDATE messages received in a third dialog.
 

Platform/Feature: SBC 7000 Series: Call Control

The SBC now maintains the PRACK status properly for multiple dialogs so that it does not drop any messages.
SBX-64326 /
SBX-63889
3 In a forking scenario, the SBC is sending out an incorrect Cseq value in a RAck header.
 

Platform/Feature: SBC 7000 Series: SIP

The code has been modified to reject retransmissions and to ensure that the correct Cseq values are relayed in RAck headers in PRACK messages based on the 18x message received.
SBX-64331 /
SBX-64098
2 In a forking scenario when the SBC is processing an UPDATE message and 18x response from different dialogs simultaneously, the 200 OK response to the UPDATE is not being relayed properly to the ingress leg.
 

Platform/Feature: SBC 7000 Series: Call Control

The SBC code has been modified to properly maintain the "To" tag so the 200 OK is now relayed to the ingress leg.
SBX-64338 /
SBX-64246
2 In a multiple dialog scenario, the SBC is updating the "To" tag in the active dialog improperly.
 

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to properly update the "To" tag in cases where the SBC receives an UPDATE message from the ingress leg at the same time it receives a 18x response from the egress leg for a different dialog.
SBX-64412 /
SBX-65682
2

User sftpadmin account expiration is not automatically extended with each usage.

Platform/Feature:SBC Core: Platform

The code has been modified to change account expiration for sftpadmin N days (configured by user) from the day sftpadmin is used.
SBX-64445 /
SBX-64420
2 In a multiple dialog scenario, the SBC is sending a 491 response to an UPDATE message sent from the ingress side.
 

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to queue 18x responses it receives at the same time from different dialogs and to properly switch dialogs when processing the queue of 18x responses. 
SBX-64551 /
SBX-64494 /
SBX-64538
1

The SBC sends a 481 response to a reINVITE requesting to retrieve a call that is on hold. 

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to properly respond to a reINVITE request for a call on hold and does not return error responses.

 

SBX-64567 2

In an SBC cloud environment, when a snapshot of an instance is taken, metadata and user data are missing when attempting to use the snapshot to restore the instance.

Platform/Feature: SBC SWe/SBC SWe Cloud: Platform

The software has been updated to preserve user data and metadata when a snapshot of an instance is taken and restored.
SBX-64679 2 When PAM requests are send at 20 requests per second, EPAM memory increases continuously. This is due to the use of an third party tool.

Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified to update the application to use new version of confd.

SBX-64724 /

SBX-64068 /
SBX-64757
2

The SBC fails to load new announcements into NP Memory and the standby instance is not running the 10-minute timer.

Platform/Feature: SBC Core: Application

The code has been modified to set the 10-minute timer even in the standby mode.

SBX-64730 /
SBX-64498 /
SBX-64729

1

The SBC is adding a 100rel to reINVITE requests.

Platform/Feature: SBC 7000 Series: Call Control

The SBC now sets the PRACK level to off when a call is connected, and it does not insert 100rel in reINVITE requests.

 

SBX-64732 /

SBX-64498
1 The SBC is adding a 100rel option tag to re-INVITE requests.
 

Platform/Feature: SBC 7000 Series: Call Control

The SBC now sets the PRACK level to off when a call is connected, and it does not insert 100rel in re-INVITE requests.
SBX-64732 /
SBX-64525
1

The SBC does not properly process a 183 response without SDP received after an UPDATE message.

Platform/Feature: SBC 7000 Series: Call Control

The SBC code was modified to properly handle 183 responses received after UPDATE messages by setting the "Updated Answer Flag" only when appropriate and basing SDP on what is received in subsequent 18x messages.
SBX-64782 /
SBX-63428
3

In a downstream forking scenario with preconditions, the SBC is not properly negotiating the preconditions for multiple forked 18x responses.

Platform/Feature: SBC Core: SIP

When precondition inter-working is enabled on egress, the precondition is negotiated by sending an UPDATE message from the SBC for the multiple forked 18x responses.
SBX-64845 2 The alarm is not generated for fatal DSP device or card failure.

Platform/Feature: SBC Core: DSP

The alarm sonusSbxDspCardOrDeviceFailureNotification is generated when the DSP card fails:
  • to load during the server startup, or
  • during the normal operation.
SBX-64848 3

The BMC serial login is not working after changing password encryption method to SHA512. The serial login is not build with PAM.

Platform/Feature: SBC 5000/7000 Series: BMC

The code has been modified to add PAM module to validate serial login.
SBX-64850 3

The BMC logs do not have time stamp.

Platform/Feature: SBC 5000/7000 Series: BMC

The code has been modified to add time stamp for all the BMC logs and disable unnecessary logs.
SBX-64873 3

Adding the Cpx validation for Delete operation for Variable Action Type.

Platform/Feature: SBC Core: SIP

Added the following note to the "delete" operation type on the pages listed below:

Note: The "delete" operation type is not applicable for the Action type variable.

SBX-65042 /
SBX-65059
3
In the BMC, adding a new user will set ssh login shell as "sh".

Platform/Feature: SBC 5000/7000 Series: Platform
The code has been modified to change the default shell for the new user.
SBX-65086 2 The SBC does not pass 403 once receiving 403 from the SIP server. 

For example, when AOR1 is already registered with port1 and the SBC receives Refresh Register for AOR1 with different port number and same IP. In such scenario, the SBC is locally responding to Refresh RGISTER before response from Registrar is received. This was causing mismatch in relayed response.

Platform/Feature: SBC Core: Application

The code has been modified to relay the Register even after receiving any error response for a REGISTER for same AOR with different contact.

To achieve the old behavior of locally responding with error messages if REGISTER is received from the same source, following enhanced DBL config can be used.

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 criteria offendingEvent triggerEventType receiptOfMessage methodType REGISTER methodResp 403

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 criteria occurrence countType aggrCount aggrCountValue 2 timerWindow 1000

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 criteria scope ipAddress

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 action type blacklist effectivePeriod 60

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF rule R1 state enabled

set profiles services enhancedDblProfile TEST_ENH_DBL_PROF state enabled

set addressContext default zone INTERNAL sipTrunkGroup RHEL_1 services enhancedDblProfile TEST_ENH_DBL_PROF

SBX-65088 /
SBX-64749
2

In a 200 OK response to an UPDATE message, the SBC is responding with refresher=uas when the UPDATE contained refresher=uac.

Platform/Feature: SBC 7000 Series: Call Control

The SBC now properly updates the session timer parameter even when the call is not connected for the Update message.
SBX-65090 /
SBX-64816
1

 In a multiple dialog scenario, the SBC is sending a 183 Session Progress with an incorrect "To" tag when there is a re-transmission of a 18x for an earlier dialog. 

Platform/Feature: SBC 7000 Series: Call Control

 
In a multiple dialog scenario, the SBC is now sending a 183 Session Progress with the correct "To" tag when there is a re-transmission of a 18x for an earlier dialog. The SBC added re-transmission logic to ensure the re-transmitted 18x is dropped.
SBX-65092 /
SBX-64829
1 In a multiple dialog scenario, the SBC is failing to send a 200 OK response to a PRACK message in the first dialog if it is received very late.
 

Platform/Feature: SBC 7000 Series: Call Control

The SBC now relays the 200 OK for a PRACK for the first dialog to the ingress side even when it receives it very late.

SBX-65094 /
SBX-61870

2

The SBC is changing the position of the b-line in the SDP when it sends an INVITE message.

Platform/Feature: SBC 5000 / 7000 Series: Application

The SBC now orders the lines in the SDP according to RFC 4566.
SBX-65096 /
SBX-64623
3

The SBC does not send an ACK message in response to a 487 response or a 481 response to an outstanding UPDATE message for a canceled dialog.

Platform/Feature: SBC Core: SIP

The SBC now sends an ACK message for 487 responses and sends a 481 response to all outstanding requests at the time processing is canceled for a dialog.
SBX-65100 /
SBX-65646
2

In a SIP-T inter-working scenario, the SBC does not send a 183 response with SDP (ACM) until it receives a 200 OK with SDP (ANM).

Platform/Feature: SBC Core: Application

For data calls, the SBC now relays the 18x (ACM) response to an INVITE request without waiting for a 200 OK (ANM) response.
SBX-65172 /
SBX-60575
2

When large number of Tone profiles are configured, SBC plays wrong tone during local ring back.

Platform/Feature: SBC 7000 Series: Application

The code has been modified to ensure that the SBC plays correct tone.

 

 

SBX-65173 /
SBX-58686
3

When SBC sends early progress message while handling unsupported MIME parameter in the ingress INVITE, the SBC does not honor methods as per allowed configuration at the ingress SIP TG.

Platform/Feature: SBC 7000 Series: Application

The code has been modified to ensure that the SBC honors allowed methods configuration at SIP TG even while sending early progress message.
SBX-65200 /
SBX-58963
2

The CAC policer applied again for same call when re-attempt (crankback) happens on the same TG and ZONE and this results in call fail.

Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified not to apply CAC policer again when the same call is tried on the same trunk group and ZONE due to crankback.

SBX-65203 2

The SBC does not response session refresh (Refresher=uas) from the endpoint after the switchover on the TCP connection. After switchover, since the user is de-registering and registering with the new port, the TCP connection cannot be retrieved using RegId.

Platform/Feature: SBC Core: Application

The code has been modified to send reINVITE towards originating side after lookup using AOR. But following flag must be disabled as user is de-registered with old port and registers with the new port.


set global signaling sipSigControls multipleContactsPerAor disabled

SBX-65246 /
SBX-64453 /
SBX-65247
2

The ScmProcess coredumps in the SBC due to deadlock.

Platform/Feature: SBC 7000 Series: SIP

The code has been modified to remove the bug that caused the deadlock.
SBX-65308 2

The powerSupplyStatus cause SM deadlock.

Platform/Feature: SBC 5000/7000 Series: Platform

This issue is resolved by setting kipmid_max_busy_us=100.
SBX-65319 2

The Local Ring Back Tome (LRBT) cannot be configured when the flag makeInbandToneAvailable is disabled.

Platform/Feature: SBC 5000/7000 Series: SIP

The flag makeInbandToneAvailable must be enabled to configure LRBT.
SBX-65322 3

The EMA Routes search does not return any results. The SQL query which was used to retrieve Route details had an extra left parenthesis resulting in an error while executing the query and hence causing this issue"

Platform/Feature: SBC Core: Platform

The code has been modified to delete the extra left parenthesis to resolve this issue.

SBX-65349  /
SBX-63920
2

After receiving corrupted RTP packets, the PrsP process coredumped which triggered an unexpected switchover.

Platform/Feature: SBC 5000/7000 Series: Application

The SBC code has been modified to add defensive checks to avoid coredumps when it receives corrupted packets.
SBX-65365 /
SBX-61871
3

In the following command, the multi-line mode is enabled automatically, which allows user to import certificate contents without entering multi-line mode manually.

% request system security pki certificate <cert name> importCert certContent

Platform/Feature: SBC Core: Application

To resolve multi-line mode issue, user must enter ctrl-D manually.
SBX-65368 2

The 183 is not sent to the ingress if 183 with no SDP is received with P-Early-Media as inactive.

Platform/Feature: SBC 7000 Series: SIP

The code has been modified to initialize PEM Audio mode to inactive so that 183 will not be stopped and sent to ingress.
SBX-65388 2

The SBC does not stop TCP level re-transmission even after TCP Retransmit Timer is expired.

Platform/Feature: SBC Core: Application

The code has been modified to add a new parameter tcpUserTimeout to the Sip Signaling Port and can be configured through CLI and EMA. This parameter describes the maximum number of seconds that transmitted data remains unacknowledged before TCP forcibly closes the corresponding connection.

set addressContext default zone defaultSigZone sipSigPort 1 tcpUserTimeout 0

Note: Enter a value of 0 (use system default) or value in the range 10-3600.

Note: For more information, refer to:

SBX-65395 2

The SBC running on OpenStack with SRIOV network, does not have the ability to strip off or add on VLAN tags when the VLANS are added on the OpenStack network.

Platform/Feature: SBC SWe/SBC SWe Cloud: Platform

The support for this feature was introduced in the software. This change enables users to administer the VLAN support either on the SBC or on the SRIOV PF (cloud network) depending on the input given in the metadata for the Cloud deployments. For non-Cloud deployments, VLANs are supported only on the SBC and the SBC must not configure VLAN on the SRIOV PF.

SBX-65444 /
SBX-65219
3 The SBC is not applying SMM to re-transmitted BYE messages. 

Platform/FeatureSBC Core: SIP

The code has been modified to correct a race condition so that SMM is now applied when BYEs are received from both the sides.
SBX-65447 /
SBX-65354
2

The SBC sends a Contact header in the 200 OK response to a PRACK message when one was not received in the incoming 200 OK response.

Platform/Feature: SBC 7000 Series: Application

The SBC does not send a Contact header in the 200 OK response to a PRACK message if one was not received in the incoming 200 OK response.
SBX-65450 /
SBX-65253
2 The SBC is not properly handling the 200 OK response to an INVITE request if it is received before the PRACK message for the 183 response. 

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to handle the scenario when it receives a 200 OK response to an INVITE before it receives the PRACK message for the 183 response.
SBX-65505 /
SBX-63965
2

The SamProcess coredumps when there is an inconsistent behavior from SIP Peers sending OPTIONS ping- where the initial Via header is without branch parameter and the second OPTIONS is with a branch parameter.

Platform/Feature: SBC Core: SIP

The code has been modified to handle the Via header in the OPTIONS ping with or without branch parameter.
SBX-65523 /
SBX-63134 /
SBX-63740
3

The MADDR parameter is present in NOTIFY’s Contact header. The SBC does not support MADDR in NOTIFY Contact header.
When SBC sends refresh SUBSCRIBE, the ReqURI was missing.

Platform/Feature: SBC 5400: SIP

The SBC’s maddr processing is enhanced to handle “maddr” parameter present in the NOTIFY Contact and use it as target refresh. The flag honorMaddrParam must be enabled.

Also, the code has been modified to put user part in the ReqURI of the refresh SUBSCRIBE requests sent from the SBC.

SBX-65616 /
SBX-63260
/
SBX-65767
3 Incorrect display for integer fields in the CLI commands post switchover. The show table system ipPolicing aclOffendersList displays PORT, PROTOCOL, DISCARD count with values multiplied by two.  

Platform/Feature: SBC Core: Application

 
The code has been updated with an added a cloud specific API, which will ensure all application modules’ slave registrations are removed during switchover. Code to ensure the proper role assignment during instantiation of modules.
SBX-65670 2

The standalone software upgrade from 4.x/5.0.x to 6.2.0R000 (offline upgrade using platform manager) failed.

Platform/Feature:SBC Core: Platform

The code has been modified to support offline upgrade from 4.x/5.0.x to 6.2.1R000.

SBX-65675 /
SBX-65888

3

The new user, which is created with only key based authentication, cannot login.

Platform/Feature:SBC Core: Platform

The code has been modified to ensure to search the authorized keys for login in the correct location.
SBX-65679 /
SBX-65484
3

The SBC is writing incorrect "To" tag information in CDRs in downstream forking scenarios. 

Platform/FeatureSBC 7000 Series: CDR

The code has been modified to correctly write "To" tag information in CDRs in downstream forking scenarios.

SBX-65799 /
SBX-65174

2

In an SLA call scenario with sdpAttributesSelectiveRelay enabled, the SBC coredumps.

Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified to reject a malformed xdmi line.

SBX-65805 /
SBX-65075

2 The SBC is relaying a P-Access-Network-Info header in a 200 OK response to a PRACK message when transparency is not enabled. 

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to relay the P-Access-Network-Info header in a 200 OK for PRACK only when transparency is enabled.
SBX-65808 /
SBX-64721
3 The SBC relays P-Access-Network-Info headers in PRACK messages toward egress when not configured to do so in the Header Transparency Profile (HTP). 

Platform/Feature: SBC Core: SIP

The code has been modified to relay the received P-Access-Network-Info header in PRACK messages only when enabled in the HTP. A similar fix was applied for P-Access-Network-Info headers in 200 OK responses to BYE messages.

SBX-65846 /
SBX-65617

4 The SBC sends session timer parameters in the 200 OK response to an UPDATE message when they were not received in the UPDATE request.

Platform/Feature: SBC 5000 / 7000 Series: Application

The SBC does not send session timer parameters in the 200 OK response to an UPDATE message unless they were not received in the UPDATE request.
SBX-65905 /
SBX-64987
2

When an egress peer sends an UPDATE message with the same SDP and o-line as a previous UPDATE, the SBC repeats the same Cseq value in the re-INVITE message it sends to the ingress peer.

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to update the Cseq number in the call context data structure when another UPDATE with the same SDP and o-line is received from the egress.
SBX-65906 /
SBX-64794
1 The SBC removes the "From" tag from UPDATE messages sent towards ingress if the UPDATE received from the egress peer contains the same SDP and o-line as a previous UPDATE. 

Platform/Feature: SBC 7000 Series: Call Control

The SBC now saves the "From" tag value in the ingress call context data structure to use in an UPDATE if it contains the same SDP and o-line as a previous UPDATE.
SBX-65910 /
SBX-64429
1

The SBC fails to properly handle the 200 OK response to an INVITE request if it receives it before completing the PRACK-200 OK message sequence in response to a previous 18x response.

Platform/Feature: Application

The SBC is now able to properly send the 200 OK for PRACK to the ingress side. The SBC then successfully sends the 200 OK response to the INVITE to the ingress side.
SBX-65927 /
SBX-65317
2

The EMA SMM rules are slow to load and may throw errors.

When an SMM rule is selected, EMA in addition to loading the rule details, also generates the CLI commands required for "View CLI" functionality which takes time. Thus, SMM rule was selected slowly.  Other errors are also due to the slowness issue only.

Platform/Feature: SBC SWe Cloud: Platform

The code has been modified to avoid the slowness by avoiding a call to generate the CLI command when SMM rule is selected. Instead, the CLI commands are generated when "View CLI" option is clicked in the UI. Changes are also made to show the name of the SMM rule which is selected by the user.

SBX-65931 /
SBX-64769

3

The SBC does not relay the preconditions in the Require or Supported headers of UPDATE messages if the SDP and o-line values are unchanged from a previous UPDATE.

Platform/Feature: SBC 7000 Series: Application

The code has been modified to relay the precondition option tag when the preconditions parameter under IPTG is set to transparent.  
SBX-65933 /
SBX-65082
2

Java exceptions in SBXLoginModule - login () module

  1. The UI call that checks if the user session is valid or not was failing due to some network issue. As a result, even though the session is valid, the idle timeout notification is shown to the user.
  2. In the logs, the SBC was trying to invalidate a session even though the session was already invalidated. This was resulting an exception, which was preventing cleanup of further user sessions from the device.

Platform/Feature: SBC SWe: Platform

  1. In the case where call to check the user session fails a different message "Something went wrong, please click OK to refresh the page" is shown to the user.
  2. The code has been modified to clean up the user session to avoid the exception.
SBX-65964 /
SBX-60281
3

The following GWCM error messages are visible in the system logs.

Minor .GWCM: mcsEncodeCpcOpStr: Unknown paramtype type 333:

Platform/Feature: SBC 7000 Series: Application

The code has been modified to log this message at INFO level instead of at MINOR level.
SBX-66010 /
SBX-64256 /
SBX-63364
 

The SBC inserted an empty ttc-charging-params header in the P-Charging Vector header in the ACK response to a 200 OK message from the egress side.

Platform/Feature: SBC Core: SIP

If transparency of the P-Charging Vector header is enabled and if an NNI profile is not configured on the ingress side, then the SBC sends the P-Charging Vector to the ingress leg without the ttc-charging-params header.
SBX-66028 /
SBX-65267
3

With end to end re-INVITE enabled and preconditions set to transparent, the SBC re-sent a Re-INVITE (late media) to the calling party unexpectedly.

Platform/Feature: SBC Core: Application

The code has been modified to properly reset the relay flag when end to end re-INVITE is enabled with preconditions specified.

 

SBX-66030 3

During LSWU to 6.2.0 release, the sync timeout issue is seen.

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

Before performing LSWU to 6.2.0R0, Run the following command on both active/standby servers:

echo "PS1='~$ '" >> /home/cnxipmadmin/.bashrc

SBX-66085 /
SBX-65820
2

 The SBC is converting an ISUP Suspend/Resume event to a SIP INFO message even when mapSuspendResumeEventInPSvcInfoHeader is disabled.

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

The code has been modified to only send the SIP INFO message when configured to do so.

SBX-66088 /
SBX-64471

3 The SBC is sending a Diversion header in a redirected INVITE even though Call Forwarding > Data Mapping is set to none. 

Platform/Feature: SBC Core: SIP

The code has been modified to not send a Diversion header in an INVITE when Data Mapping is set to none in call forwarding cases.
SBX-66094 /
SBX-63889
3

In a forking scenario, the SBC is sending out an incorrect Cseq value in a RAck header.

Platform/Feature: SBC 7000 Series: SIP

The code has been modified to reject re-transmissions and to ensure that the correct Cseq values are relayed in RAck headers in PRACK messages based on the 18x message received.
SBX-66095 /
SBX-63862
1 In a forking scenario, the SBC does not relay the SDP in the second dialog 18x message if it is received at the same time as the first dialog 18x. 

Platform/Feature: SBC 7000 Series: Call Control

The SBC now uses a queue mechanism to handle overlapping 18x message sequentially, which allows the SBC to relay the SDP for the second dialog 18x.
SBX-66096 /
SBX-64099
2 In a forking scenario, the SBC does not relay the SDP in the third dialog 18x response if it receives the 18x before receiving the 200 OK response to an UPDATE request.

Platform/Feature: SBC 7000 Series: Call Control

The SBC now handles the situation when the 18x is received before the 200 OK response to an UPDATE request. The SBC queues the 18x message until the processing of the UPDATE completes.

SBX-66097 /
SBX-64243

2 In a multiple dialog scenario, the SBC encounters issues and 18x responses are sent to the ingress leg without SDP. 

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to queue UPDATE messages. The SBC is now able to process a 200 OK for an UPDATE while sending an 18x with SDP to the ingress leg.

SBX-66098 /

SBX-64423

 

2

 In a downstream forking scenario, the SBC responds with a 491 "Request pending" message if it receives UPDATE requests from different dialogs simultaneously.

Platform/Feature: SBC 7000 Series: Call Control

The code has been modified to queue UPDATE messages if one is received before the processing of a previous UPDATE completes. The SBC processes each UPDATE in the queue and does not reject the requests with a 491 response.

SBX-66103 /
SBX-64098

2

In a forking scenario when the SBC is processing an UPDATE message and 18x response from different dialogs simultaneously, the 200 OK response to the UPDATE is not relayed properly to the ingress leg.

Platform/Feature: SBC 7000 Series: Application

The code has been modified to properly maintain the "To" tag so that the 200 OK is relayed to the ingress leg.
SBX-66160 /
SBX-64764
2

When From header transparency is enabled and Include IP ports in From and To headers flag is enabled, the SBC does not transparently pass port number.

Platform/Feature: SBC 7000 Series

The code has been modified to ensure that the SBC transparently passes port number in "From" header when "From" header transparency is enabled and Include IP ports in From and To headers flag is enabled.
SBX-66282 /
SBX-65394
2

The default static route with the highest precedence even though port is down makes system unreachable.

Platform/Feature: SBC 5000/7000 Series: Platform

The code has been modified to delete the kernel auto created mgt route when physical link is down.
SBX-66284 /
SBX-66066
2

An SBC node fails when the Address Reachability Server (ARS) limit on static blacklist entries is exceeded.

Platform/Feature: SBC SWe Cloud: Application

The code has been modified to properly apply the record limit and to return an error to prevent a memory violation.

 

SBX-66290 /

SBX-66029 /
SBX-63121
 2 Corrupted STUN messages led to memory corruption which lead to the PRS process coredumping.

Platform/Feature: SBC 7000 Series: Application

The SBC code has been modified to be more defensive in handling the unrecognized and corrupted STUN messages to avoid the memory corruption which led to the coredump.

SBX-66302 /
SBX-63845

2

The Geographical Redundancy HA Mode is disabled after upgrade.

Platform/Feature: SBC 5000/7000 series: Redundancy

The code has been modified to ensure that the geographical redundancy status is retained during an upgrade from 5.0.2 SBC versions.
SBX-66311 /
SBX-63624
3 The SBC does not automatically clear the sonusCpNodeHaPortDownNewNotification alarm.

Platform/Feature: SBC 5000/7000 series: FM / Traps and Alarms

The SBC code was modified to automatically clear the sonusCpNodeHaPortDownNewNotification alarm. The description of the alarm in the SBC Alarms and Traps Guide was updated accordingly.
SBX-66313 /
SBX-66265
2

The SBC does not properly handle a re-INVITE request if the SDP in the request is unchanged.

Platform/Feature: SBC 7000 series: Application

The code has been modified to handle a re-INVITE request in which the SDP is unchanged. The SBC now sends a 100 Trying message for a session refresh INVITE and sends an ACK message to the 200 OK response for a session refresh INVITE.

SBX-66318 /
SBX-66277
2

In a precondition interworking scenario, the SBC does not send an INVITE request to the egress side when the ingress precondition is met in a PRACK message.

Product/Feature: SBC 7000 Series: Application

The code has been modified to process preconditions met in a PRACK message and to release the INVITE to the egress side once the ingress preconditions are met.

SBX-66718 /
SBX-66433

2

With SRTP enabled and DTLS-SRTP disabled in the call leg Packet Service Profile (PSP), if both SRTP (with a=crypto line) and DTLS-SRTP (with a=fingerprint line) are offered by the peer, the call leg falls back to RTP (security disabled) instead of SRTP being enabled.

Product/Feature: SBC 5000/7000 Series: Application

The code has been modified to properly enable the SRTP on the call leg under the same call conditions.

SBX-66793 2

After an upgrade to V6.1/6.2 from 5.1 release, the behavior of the REFER message changed. After the Refer message is received on SBC, it uses the original called number for the subsequent INVITE rather than the number presented in the Refer-To Header.

Product/Feature: SBC SWe: SIP

The code has been modified to select the correct calledUri.

 

SBX-66932 /
SBX-65817
2

The SBC is not sending originating carrier information to the PSX when an NNI profile is configured.

Platform/Feature: SBC Core: SIP

The SBC code has been modified so that the SBC now sends originating carrier information to the PSX.

 

SBX-66963 /
SBX-66393
2

In a downstream forking scenario, media cut-through occurs even if the SBC receives an 18x response without SDP.

Platform/Feature: SBC 7000 series: SIP

 

 

The code has been modified so that the media cut-through occurs only when the SBC receives an 18x response with SDP.
SBX-67073 /
SBX-66534
2

The Scm process core dumps when SIP-SIPI call is made with DLRBT enabled, 183 and 180 with SDP and 180 with OBCI.

Product/Feature: SBC 5000/7000 Series: SIP

The code has been modified to add NULL check for pstMsgBody > pstIsupContent as pstMsgBody is changed after retrieved from the cache.

SBX-67101 2

For SIP-I to SIP-I call, when converting ISUP CON from egress to ISUP ACM on ingress, if the CON contains a connected number parameter then the resulting ACM is not populated with all required parameters e.g. Carrier info type is missed.

If CON is received with a connected number parameter, the sent ACM sent may not contain all parameters.


Product/Feature: SBC Core: Call Control

The code has been modified to reinitialize message parameter offsets in Ss7LibGenerateAcm when mapping from CON to ACM.
SBX-67164 /
SBX-67163 /
SBX-67162 /
SBX-67161 /
SBX-66969
2

Repeated logging of a system error is causing the disk to fill up, which ultimately causes the system to switchover.

Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified to prevent the invalid parameter value from being passed to the function StrNCpyZ().
SBX-67245  3

The EMA Call Diagnostics feature does not show all the trunk groups that are available for a zone.

Product/Feature: SBC 5000/7000 Series: EMA

 The code was modified to return and display the complete list of trunk groups.
SBX-67326 /
SBX-66747
2

The request URI of REFER header is globalized.

Product/Feature: SBC 5000/7000 Series: Call Control

The code has been modified to globalize the request URI only when the flags useCalledURIasRURI and globalization are enabled.

SBX-67350 /
SBX-67076

1

When loopback is enabled and standard_callmix_profile is applied with >12vCPU VM configuration, SWe_NP was crashed because of the invalid core_id returned from the rte_lcore_id() function. This leads to array out of bound access in the SWe_NP and thus results in crash.

Product/Feature: SBC SWe: Application

Upstream thread in SWe is a non-DPDK thread, thus, calling rte_lcore_id() on non-DPDK thread is not allowed.

In SWe_NP, as part of enhancement, this issue is introduced and now it is fixed by not calling rte_lcore_id() in upstream thread.

 

SBX-67428 1

The MCT recorderType option is not supported in ERE.

Product/Feature: SBC 5000/7000 Series: Platform

The code has been modified to hide the MCT recorderType option from the call recording criteria entity. For call recording criteria entity, the recorderType node can have only SIPRec option as MCT is not supported in the ERE.
SBX-67616 3

Prior to this release, the default CLI user name and password for AWS SWe was admin/admin. The hard coded password must not be used for the security vulnerability on the AWS SWe platform.

Product/Feature: SBC SWe Cloud: Only AWS Platform

The code has been modified to support default CLI admin password as "active role assigned instance's primary interface-id (Mgt0InterfaceIDActive)". The active role of instance in the CloudFormation Template (CFT) must be assigned and the default CLI admin password can be found on the AWS stack output.

 

Issues Resolved in 06.02.00R000 Release

The following issue are resolved in this release.

Table : Resolved Issues

Issue ID Sev Problem Description Resolution
SBX-52993 2

When 30,000 routes are created, sending invalid route creation or deletion queries to the SBC causes health check failure.

Product/Feature: SBC SWe: Application

The PAM authentication performance is improved by minimizing CDB sessions.
SBX-56585 / SBX-55106 /
SBX-50596 /
SBX-49251
2

Flood of logs for the parity error messages are seen in the kernel logs.

Product/Feature: SBC 7000 Series: Platform

Third-party software code used in chip driver has been updated to a newer version to prevent flood of logs for parity errors for affected dynamic memories.
SBX-57868 2

The SBC is allowing extra calls in local mode, more than the configured licenses. The SBC must allow sessions equal to the number of configured licenses.

Product/Feature: SBC SWe Cloud: Platform

A note has been added to resolve this issue in the documentation:

"In local license mode without installing SBC-RTU license, the SBC instance process one call, if you install N number of SBC-RTU licenses SBC instance processes N+1 calls."

SBX-57896 / SBX-64857 2

The DRBD/evlog may not synchronized if one of the servers of an HA pair is re-installed or replaced.

Product/Feature: SBC 5000/7000 Series: Platform

The code has been modified to auto restart the DRBD/evlog partition to the newly installed/replaced chassis.
SBX-58497 2

Alarms are not generated by S-SBC under overload condition and overload rejects happening.

Product/Feature: SBC SWe Cloud: Application

The following new alarms are generated to resolve this issue. These alarms are documented under the Distributed SBC (D-SBC) Alarms.

  • sonusSbxDsbcNodeCongested
  • sonusSbxDsbcNodeCongestedClear
  • sonusSbxDsbcNodeCongestedV6
  • sonusSbxDsbcNodeCongestedV6Clear
SBX-59438 3

The timestamps on media packets may differ from that of the SIP signaling packets captured in the same PKT file, and may drift over time with respect to each other.

Product/Feature: SBC 5000/7000 Series: Platform

The code has been modified such that the accuracy of the media packet captures (in PKT files) has been changed from one sec (drifting to > 1 sec) to sub-millisecond accuracy on all the hardware SBC platforms.
SBX-59516 2

When an SBC is configured as an HA Pair and the Standby is stopped; if a new remote syslog Server is configured on the Active and Standby is brought back up and synchronized with the Active. The configured rsyslog.conf files on the Active and the Standby are mismatched.

Product/Feature: SBC Core: Application

The code has been modified such that during a configuration on the Active and the Standby is down; when the Standby is up and synchronized, the rsyslog.conf file on the Standby is also synchronized with the Active to ensure that there is not a mismatch in the files on both the Active and the Standby.
SBX-59856 3

Any instance which has only one SCM instance, the loopback register also lands on the same SCM instance and finds PstCall which is created on outgoing Initial register thus, loopback registration fails.

Platform/Feature: SBC 5000/7000 Series: Application

To resolve this issue, create an instance with more than one SCM process.
SBX-59906 2

During call hold, the sequence number is incremented while the timestamp is not with respect to the real time. This may be treated as a packet loss by some end-points.

Product/Feature: SBC Core: DSP

During a call hold (when packets are not transmitted), to prevent the assumption of the packet loss, in accordance to the definition of the timestamp and sequence number, the sequence number is not incremented while the SBC continues to increment the timestamp with respect to the real time.
SBX-60158 / SBX-57509 / SBX-57327 3

The T.30 CED IND packets does not pass over the NP layer in a pass-through call.

Product/Feature: SBC SWe: Application

The code has been modified to remove the bad size check to correct this issue.
SBX-60249 / SBX-57612 2

During an Audio call update to video, the SBC changes video port to zero when sending reINVITE toward the Egress Endpoint.

Once the invite is challenged, the media Information was not fetched accurately. Therefore, the video stream port was set to zero.

Platform/Feature: SBC 5000/7000 Series: SIP

The code has been modified to fetch the media information accurately.
SBX-60598 / SBX-61958 2

Inter-working calls fail when the transport parameter is sent while contact transparency is enabled (PassCompletContact/HTP or Contact header in IPSP is enabled).

Platform/Feature: SBC Core: SIP

The code has been modified to prevent the failure of inter-working calls.
SBX-60754 3

An insufficient configuration for the VM was used by the customer. Customer suggested if a corresponding error message can be populated in the LCA logs to identify such issues.

Platform/Feature: SBC SWe Cloud: Platform

The code has been modified to add a message in the login banner and customer will be notified about the issue whenever a login attempt occurs in the SBC.
SBX-60862 / SBX-59502 3

The SBC includes SDP in subsequent 18x even though the Send SDP in Subsequent 18x flag is not set.

Platform/Feature: SBC Core: SIP

The code has been modified to pass down to SIPS to queue the SDP only and not include previous SDP if the flag Send SDP in Subsequent in 18x is not set.
SBX-61046 / SBX-59859 / 2

The GW-GW calls with transcoding cause a memory leak.

In addition, the GW-GW calls in which the audio parameters are changed after the initial call setup will also cause a leak.

Platform/Feature: SBC 5000 Series: SIP

The gateway signaling code has been modified to fix the code that caused the leak.
SBX-61248 2 The DRM messages are logged in the .sys logs for pass-through calls.

Product/Feature: SBC SWe

For SBC SWe, the following alarms are generated when there is a CPU congestion. The calls may be rejected during congestion to maintain system stability.

  • sonusSystemNodeResourceCongestionWarningNotification
  • sonusSystemNodeResourceClearCongestionWarningNotification
SBX-61362 / SBX-53171 2

After executing a backup restore config, the slwresd settings are not populated in the slwresd.conf file on the standby SBC.

Product/Feature: SBC 7000 Series: Application

The slwresd.conf file is not populated after DB backup and restore. The code has been modified such that the slwresd.conf file is generated after switchover of the HA system.
SBX-61362 / SBX-53171 2

After executing a backup restore config, the slwresd settings are not populated in the slwresd.conf file on the standby SBC.

Product/Feature: SBC 7000 Series: Application

The slwresd.conf file is not populated after DB backup and restore. The code has been modified such that the slwresd.conf file is generated after switchover of the HA system.
SBX-61438 3 The SIP call is not reaching SBC when the relay port is configured before SIP Sig port.

Platform/Feature: SBC Core: Application

Sub-system signaling ports (such as SIP signaling ports, relay ports, D-SBC signaling ports, H.323 signaling ports) must use different IP addresses because each IP address adds one system ACL, and IP addresses are not prioritized when measured in the same ACL. This best practice will avoid any IP addressing overlaps and ensure proper policing of packets.
SBX-61475 2

When logs are sent to the remote syslog server from a Cloud SBC, the incorrect system name is displayed in the server logs.

Platform/Feature: SBC SWe Cloud: Application

The code has been modified such that the server logs now display the correct system name and log format follows the template described in the RFC5424.
SBX-61486 / SBX-62152 3

The SBC drops packets generated by EMA trace route tool.

Platform/Feature: SBC Core: Platform

The code has been modified to use EMA trace route with ICMP protocol instead of UDP.
SBX-61545 / SBX-60272 2

The P-Access-Network-Info with parameter in IPv6 format is rejected.

Platform/Feature: SBC Core: SIP

The code has been modified to support the parameter in IPV6 format.
SBX-61546 / SBX-58022 2

When NAT direct group is deleted, ScmProcess coredumps in SBC.

Platform/Feature: SBC Core: Application

When an entry is removed from the count list, it uses listRemove flag. The code is modified to use ListtCntRemove flag, so that the counter in the list is properly decremented.
SBX-61698 2

The period execution of the AIDE file validation process does not work.

Platform/Feature: SBC Core:Security

The period execution of the AIDE file validation process now works under the proper daily or weekly schedule according to the system operation.
SBX-61743 / SBX-54820 2

Setting DTMF to Either in the PSP causes pass-through call to transcode.

Platform/Feature: SBC Core: Application

The use of DSP resources is stopped to solve this issue.
SBX-61768 / SBX-62008 2

The named-route was not updated when route was modified.

Product/Feature: SBC Core: Platform

The code has been modified to remove partially implemented named-route feature.
SBX-62010 / SBX-43885 2

The newly upgraded SBC experiences DSP coredump.

A fax relay channel configured for T.38 version 0 mode but received V34 packet (such as v8ansam pkt) instead, which caused DSP to crash and detected by MP for illegal memory access.

Product/Feature: SBC 5000/7000 Series: DSP

The fax code has been modified to reject V3 packet if the channel is configured as V0.
SBX-62016 4

Not possible to search routes on EMA using destination national query. Code merge Issue, as there was a repetition of the code used for destination national query.

Platform/Feature: SBC Core: EMA

The code has been modified to remove unwanted and redundant code.
SBX-62061 / SBX-60652 2

The SBC is including npdi parameter in the outgoing INVITE even though doNotIncludeNpdi flags is enabled. This occurs because of changes done for the flag alwaysIncludeNpdi.

Platform/Feature: SBC Core: SIP

The code has been modified such that the SBC does not include npdi parameter when doNotIncludeNpdi flag is enabled. The doNotIncludeNpdi flag has higher priority than alwaysIncludeNpdi.
SBX-62152 / SBX-61486 3

The SBC drops packets generated by EMA trace route tool.

Platform/Feature: SBC Core: Platform

The code has been modified to use EMA trace route with ICMP protocol instead of UDP.
SBX-62114 / SBX-63176 /
SBX-62387 /
SBX-63175 / SBX-63177  
2

When ARP packets are discarded at ACL policer stage, offenders are added to the aclOffendersList instead of the arpOffendersList.

Platform/Feature: SBC 5000/7000 Series: Platform

The code has been modified to raise the discard as an ARP policer event instead of ACL policer event.
SBX-62167 2

Prior to entry of FIPS mode of operation, a software integrity check is performed to verify that software has not been altered. If this check fails, FIPS mode of operation must not be entered. An error path test showed that components that fail this test are logged. However, entry into FIPS mode of operation is still permitted.

Platform/Feature: SBC Core: Security

The integrity check has been modified to prevent entry into FIPS mode of operation when any software component fails the integrity test.
SBX-62243 / SBX-61851 2

When the first SMM rule deletes a parameter in a header, and the second rule tries to modify a different parameter on the same header, the SBC coredumps after accessing the null pointers of the deleted parameter while performing the second rule.

Platform/Feature: SBC Core: SIP

The code has been modified to add validation of pointer before accessing paramName.
SBX-62250 3

Appropriate alarm must be raised when SRS IP selection fails as current alarm requires SRS IP to be printed.

Platform/Feature: SBC Core: Application

A new alarm sonusSbxSipRecSrsSelectionFailedNotification is generated to indicate the failure to initiate SIPREC recording due to any of the following reasons:

  • Failure to select SIP Recording Server
  • SRTP is enabled on the leg being recorded.
SBX-62327 2

In EVS codec transparency using Audio transparency Feature, the SBC does not relay EVS codec, which is received in SDP offer from ingress.

Platform/Feature: SBC 7000 Series: Media

When Audio less is enabled, fmtp params are not sent transparently. The code has been modified to use the proper CodecIndex to fill fmtp params.

Note: The Audio Transparency flag must be enabled.

SBX-62328 2

IP routes remain in routing table after LDG failure.

Platform/Feature: SBC Core: Platform

The code has been modified to make the necessary changes to delete the routes on interface upon link detection failure and re-installed upon recovery.
SBX-62367 / SBX-62218 3 The SBC rejects the INVITE message if it contains tel URI with hexa-digit "e" and "f" in the "From" and "To" headers.

Platform/Feature: SBC Core: SIP

The code has been modified to accept hexa-digit "e" and "f" in the tel URI format.
SBX-62438 3

The SBC cannot delete microflow if hash ID is 0.

Platform/Feature: SBC 7000 Series: Application

The code has been modified such that a hash ID of 0 is considered valid and proceed with deleting the microflow resource.
SBX-62440 / SBX-59762 3

When Honor Embedded Header in 3xx is enabled and the SBC received 3xx with embedded headers in contact, the SBC sends out Invite with malformed embedded header.

Platform/Feature: SBC Core: SIP

The logic of converting escaped characters in embedded header was wrong. The code has been modified to correct the logic error.
SBX-62476 / SBX-62074 3

The SBC coredumpes in SIPS Module (SipsDnsProcessNaptrResponse function) as DNS server is configured with only ENUM records and there are no NAPTR records configured for a FQDN. The SBC expects NAPTR records (replacement field in NAPTR response) from DNS server but receives only ENUM records from DNS server, as replacement field is NULL.

Platform/Feature: SBC Core: SIP

Whenever ENUM records are received SipsDnsProcessNaptrResponse are rejected and also NULL check is added for replace host variable.
 SBX-62489 3

The SBC duplicates Supported header in the outgoing INVITE when ingress INVITE has history info in supported header and History Info transparency is enabled.

Platform/Feature: SBC Core: SIP

The code has been modified to make sure the SBC does not duplicate supported header when ingress INVITE has History Info in supported header.
SBX-62505 3

The EMA GUI does not warn about the SBC restart when enabling first NTP server.

Platform/Feature: SBC Core: EMA

The code has been modified to read all "EXTENSIONS:emaOptions" nodes present and to support the warning message.
SBX-62586 3

The SBC does not build the NOTIFY message body properly due to transparency profile.

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

The code has been modified to add the message body only once to NOTIFY when transparency profile is enabled.
SBX-62608 / SBX-64081 2

The issue was triggered by RTCP termination, it can disrupt calls randomly when RTCP generation is enabled.

Platform/Feature: SBC SWe/SWe Cloud

The issue was resolved by correcting the defective code.
SBX-62639 / SBX-62190 2

The SamProcess coredumps in the SBC as a result of a NULL pointer access.

Platform/Feature: SBC Core: Application

The code has been modified to add a NULL pointer check to resolve this issue.
SBX-62651 / SBX-62518 2

The ScmProcess coredumps in the SBC due to call park feature segmentation issue.

Platform/Feature: SBC Core: SIP

The code is modified to add a NULL check for actSpContext->spPtr before accessing the data.
SBX-62662 2

The configuration of fileSize or fileCount under eventLog typeAdmin, and starting a load configuration immediately may cause the SBC to crash.

Platform/Feature: SBC 7000 Series: Platform

The code has been modified to remove code issuing system commands. These commands do not have sudo permission and thus, delay in processing, which eventually leads to system crash.
SBX-62924 / SBX-62736 2

When there are two or more instances of identical user ACL rules, the SBC may not load all the user ACL rules when it starts.

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

The code has been modified to continue loading next user ACL even if the current user ACL add fails.
SBX-62925 4

The Blink Locator LED documentation was incorrect.

Platform/Feature: SBC 5000/7000 Series: Documentation

Modified the Locator LED Settings description to describe the following parameters:

  • Blink LED on
  • Blink LED off
SBX-62931 2

In non-DHCP instances network issues were found when MTU size is set to default size (1500).

Platform/Feature: SBC SWe Cloud: Platform

The SBC in non-DHCP network supports only network MTU size as 1450. If the host network supports an MTU size more than 1500, ensure that the same information is propagated to VMs launched through a DHCP network.
SBX-63022 / SBX-62984 1

Memory leaks in the SBC when SIP recorder functionality is used.

Platform/Feature: SBC Core: SIP

The leak is in SIP redundancy code while using SIP Recorder functionality. The code has been modified to avoid the memory leak.
SBX-63072 / SBX-63058 2

The SBC coredumps when a SIP message that includes a P-Charging-Vector with generic parameters is received, while the SIP-GW-GW-SIP call with SIP Transparency is enabled.

Platform/Feature: SBC Core: Platform

The code has been modified to prevent the coredumps, when a SIP message that includes a P-Charging-Vector with generic parameters is received for a SIP-GW-GW-SIP call.
SBX-63075 / SBX-60660 3 The ScmProcess coredumps due to memory corruption caused by SIPSG code overwriting the end of an array. This may happen if an incoming SIP message has more than 96 headers.

Platform/Feature: SBC 5000/7000: SIP

The code has been modified to avoid memory corruption.
SBX-63112 / SBX-62734 / SBX-62856 / SBX-62807 3

In downstream forking with dialog transparency, the SBC stops relaying 18x/200 messages to the ingress call leg and once the call is disconnected ScmProces cores.

Product/Feature: SBC 7000 Series: SIP

When PRACK with SDP is received, the subsequent 18x/200 messages are dropped. The code has been modified to set the PrackPending properly has solved the issue.

Note: The Dialog Transparency, Downstream Forking, and Audio Transparency flags must be enabled.

SBX-63245 / SBX-63251 / SBX-62973 1

Multiple SMM rules or actions on the message body causes memory leak in SBC.

Platform/Feature: SBC Core: SIP

The code has been modified to allocate dynamic memory for message body modification instead of using flat buffer memory pool.
SBX-63260 3

Incorrect display for integer fields in the CLI commands post switchover.

Platform/Feature: SBC Core: Application

Added a cloud specific API, which will ensure all application modules’ slave registrations are removed during switchover. The code has been modified to ensure the proper role assignment during instantiation of modules.
SBX-63282 / SBX-58239 2

When the flag sendSdpIn200OkIf18xReliable is enabled in the 200 OK which is sent toward the ingress, video port is not updated even though SDP version is updated.

Product/Feature: SBC Core: Application

In this case, the SBC has already sent the SDP in the 183 and updates in the 200 OK message fails and SBC does not update the SDP received after the PRACK was acknowledge. Therefore, updating the SDP received for this scenario resolved the issue.
SBX-63217 / SBX-63241 2

The personalitytype.txt file was moved to a different path, which caused fileNotFound exception.

Product/Feature: SBC Core: Platform

The code has been modified to correct the file's path to the new location.
SBX-63306 3

Inter-working calls failed when the transport parameter was sent while contact transparency is enabled (PassCompletContact/HTP or Contact header in IPSP is enabled).

Product/Feature: SBC Core: SIP

The code has been modified to prevent the failure of the interworking calls.
SBX-63320 / SBX-62786 2

In call flow, SBC --> GW-GW --> GSX --> ISDN, when ingress side sends PSTN parameters to the SBC in SIP INVITE message, the SBC does not decode PSTN parameters correctly and send incorrect bearer capability to GW-GW which results in GSX sending wrong bearer capability to ISDN side.

Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified to ensure that the SBC correctly decodes PSTN parameters in INVITE and sends correct value in GW-GW setup.
SBX-63364 2

The issue is seen when transparency for PCV is enabled and ttc params in PCV are received from the egress side.

Product/Feature: SBC Core: SIP

There was no support for transparency of ttc params in PCV from egress messages.
SBX-63575 / SBX-62055 2

The ScmProcess coredumps in the SBC due to NULL pointer access for a certain HDR.

Product/Feature: SBC 7000 Series: Application

The code has been modified to add defensive check to prevent the ScmProcess coredump in the SBC.
SBX-63694 3

The SBC generates PRACK with contact header, which is against RFC 3262.

Product/Feature: SBC 7000 Series: SIP

The code has been modified to ensure that the SBC generated PRACK does not contain contact header.
SBX-63725 / SBX-58549 2

The Policy Server is stuck in the "dryup" state when it is configured as "Out of Service" on the SBC when there are outstanding requests to that Policy Server.

Product/Feature: SBC 5000/7000 Series: Platform

The code has been modified so that the Policy Server is not stuck in the "dryup" state.
SBX-63749 / SBX-62508 2

When Online Certificate Status Protocol (OCSP) checking was enabled and then disabled for SIP-over-TLS, the OCSP check was still triggered even though the OCSP check is disabled. In addition, the OCSP check can cause health-check timeouts.

Product/Feature: SBC Core: Security

The code has been modified to skip the OCSP check when the OCSP check is enabled and then disabled. Disable health-check when OCSP check is performed.
SBX-63751 2

The ipPolicingBadEtherIpHdrOffendersIntStats contains a blank addressContext and interfaceGroup name fields.

Product/Feature: SBC 5000/7000 Series:Platform

The NP stores the addressContext and interfaceGroup as an “ID” (number) and not a string name. When the IPM converts the ID to a string name, confD may have created a new ID index for the addressContext or interfaceGroup. It is also possible the user deleted the addressContext or interfaceGroup. In this scenario, the IPM does not receive the values for the addressContext and interfaceGroup names and the IPM returns the values to the above variables instead of NULL as shown below:
“addr-%-4d” ->addr-1, addr-2, addr-3, etc

“ifGrp-%-4d” -> ifGrp-1, ifGrp-2, ifGrp-3, etc

SBX-63804 / SBX-63617 2

The SBC discards DTLS SRTP packets due to SRTP authentication failure. When AES-CM-128-HMAC-SHA1-32 crypto suite is used, the SRTP authentication fails. This results in calls with one-way audio or without any audio.

Product/Feature: SBC 5000/7000 Series: Media, Security, TLS

The code has been modified such that when AES-CM-128-HMAC-SHA1-32 crypto suite is configured, it does not result in authentication failure.
SBX-63818 / SBX-60140 2

The bulk SIP registration with invalid user-agent header generated huge redundant error logs which affected the SBC performance.

Product/Feature: SBC 5000/7000 Series: Application

The code has been modified to control SMM related MAJOR Logging mechanism.
SBX-63927 / SBX-63016 3

During upgrade of standby server, availability of upgrade packages are checked on active server, which can sometimes return errors and cause upgrade failure.

Product/Feature: SBC Core: Application

The issue is because of incorrect sequence of commands sent from standby to active and expecting responses in a certain order. Fixes are made to address the issue.
SBX-63971 2 The SBC is changing the SIP-URI to Tel URI in request URI if the "TO" header is in Tel URI format.

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

The code has been modified to disable the "TO" header transparency to fix this issue.
SBX-64051 / SBX-63787 / SBX-64043 3

In some call flows with mid-call modifications to remote IP address, if server switchover occurs, one leg may no longer receive media packets. The problem is intermittent. Root cause is that loopback state is not properly mirrored from active to standby server.

Product/Feature: SBC 5000/7000 Series: Platform

The code has been modified to add the loopback state and the necessary serialization code.
SBX-64067 3

The SIPREC CLI trigger results "Siprec Recording Initiated", even after starting the NICE recorder.

Platform/Feature: SBC Core: Application

When the recording is triggered through CLI, recording will be attempted. Thus, the CLI gives the following status:

"Attemping Siprec Recording, alarm shall be raised if recording trigger fails".

SBX-64071 / SBX-63887 2

The ScmProcess repeatedly coredumps on the SBC 5000 series HA systems when advanced SMM stores greater than 1000 data into a variable.

Platform/Feature: SBC Core: Application

The code has been modified to avoid the ScmProcess coredump and the variable storage capacity is increased to support up to 5000 memory.
SBX-64073 / SBX-63284 2

When e2e reINVITE and relay 4xx-5xx enables, the SBC does not relay 491 to the other side.

Platform/Feature: SBCCore: SIP

Add logic based on configurations to relay 491 to the other leg. 

In this case, the SBC must not regenerate INVITE.

SBX-64080 / SBX-64078 /
SBX-64636
2

The PrsProcess coredumps, NP memory dump indicates ANN core took an exception. The RTCP Gen can cause announcement coredump to generate an exception.

Platform/Feature: SBC Core: Application

The code has been modified not to divide by zero while calculating the drop rate.
SBX-64125 2

In the SBC 5000 series, the IP loopback is implemented in the software and not in the hardware that exists in the SBC 5000/7000 series platforms. Thus, certain call transfer from loopback to non-loopback at the NP level was affected in the SBC 5400.

Platform/Feature: SBC 5000 Series: Platform

The issue is resolved by a simple fix to the code bug. No special configuration is needed.
SBX-64126 3

While importing the SBC configuration from 05.00.05 to 06.02.00, users are unable to login through EMA.

Platform/Feature: SBC 5000 Series: EMA

The code has been modified to add predicate to retrieve value of actualCeName.
SBX-64141 / SBX-63381 2

When contact header in IPSP is enabled, transport parameter must not be sent as interworking calls fail.

When passCompleteContact in IPSP is enabled, transport parameter is sent in the contact header, which does not cause an issue as Record-Route is added where transport parameter for that particular leg is updated appropriately.

Platform/Feature: SBC Core: SIP

The code has been modified to:
  • Avoid sending the transport parameter transparently, when contact header transparency in IPSP is enabled.
  • Send the transport parameter transparently when passCompleteContact transparency in IPSP is enabled.

However, for register messages, though passCompleteContact is enabled, transport parameter cannot be sent.

SBX-64178 3

An explanation is needed on the product page “SMM (Advanced) Examples” to identify any dialog stateful variable limitations.

Platform/Feature: SBC Core: Documentation

Added a note to the “SMM (Advanced) Examples” page explaining dialog stateful variable size limitations. Ported this detail to later releases.
SBX-64191 4
  • The SBC supported a minimum radius shared secret length of 8. However, it was discovered that some customer systems used a length of 6.
  • When radius authentication was enabled on the SBC, local authentication was only performed when the radius server was down. It was discovered that some customers wanted a selection of users through radius and some to work through local authentication.
  • If the SBC fails to contact the radius server it can be configured with an out of service duration and it must not contact the server again during this time. However, due to some uninitialized memory it was possible that the SBC can contact the radius server one hour earlier due to daylight savings time calculations.

Platform/Feature: SBC 5000 Series: Platform

The code has been modified to:

  • Allow a new minimum length of 6.
  • Try and authenticate via the radius server first but it that fails it will try local authentication, this allows for some users not be configured on the radius server.
  • Correctly initialize memory for the daylight savings time flag so the radius server is not contacted prior to the out of server duration expiring.
SBX-64184 / SBX-63917 2

The SBC coredumps if 18x is received with multi bodies and 200 OK is received without body, when downstream forking and transparency in the other body is enabled.

Platform/Feature: SBC Core: SIP

The code has been modified to initialize body properly.
SBX-64179 3 Clarification on usage of QCOW2 for Hardware and VMWare/KVM standalone upgrades and instance spin-up for Cloud.

Platform/Feature: SBC Core: Application

Added the following note to the documentation to resolve this issue.

"A new "qcow2" image file is added to the list of upgrade files for upgrade to 6.0.0 R0 and later releases. For example: "sbc-V06.02.00R000-connexip-os_05.00.00-R000.qcow2"".

SBX-64216 3

During an upgrade to 6.2 release, if DNS Group misconfiguration (supported in CLI but not in application) is present, it can cause 6.2 upgrade/LSWU failure. Thus, the DNS Group must be cleaned up before upgrading to 6.2 release.

Platform/Feature: SBC 5000/7000 Series: SIP

On the SBC 6.1 release and older, the following misconfigurations can be present:

  1. A dnsGroup is configured with an ipInterfaceGroup outside its own addressContext, the configuration was supported at the CLI but the application does not accept it, resulting in inconsistency between the CLI and application.
  2. A dnsGroup with type mgmt can be configured without an ipIntefaceGroup being specified.

The SBC 6.2 release onward, such a configuration is not supported on the CLI and thus, when performing an upgrade to 6.2, it is recommended that the DNS groups must be cleaned up by following the WBA.

Note: The WBA must be followed to clean up the DNS group misconfigurations to avoid 6.2 upgrade/LSWU failures. 

The steps to accomplish this are included in WBA "W-17-00022847". To view the WBA, log on to the Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login) and click the Bulletins link from the menu bar. Enter the bulletin number (last eight numbers) in the search field and press Return.

SBX-64263 2

The setHaConfig CLI command does not work properly to configure or revert GRHA setup.

Platform/Feature: SBC Core: Application

The code has been modified to set GRHA and bond device.
SBX-64285 / SBX-64096 2

In downstream forking scenario where multiple 18x messages are received from the egress and when 200 OK for PRACK is sent, the contact header is corrupted in case of race conditions.

Platform/Feature: SBC 7000 Series: Application

The code has been modified as contact username is having a dangling pointer for PRACK 200 OK because mergeforkedlegtoPstCall() is freeing puchContactName and assigning new memory.
SBX-64320 3

The SBC was not able to edit the configuration in the Link monitor from EMA.

When conditions added, the JSON response was not formatted properly due to the new Display.

Platform/Feature: SBC SWe: EMA

The code has been modified to incorporate JSON response appropriately.
SBX-64404 3

The EMA GUI does not display any warning message while changing the port number of the SIP Signaling Port.

Platform/Feature: SBC Core: EMA

The code has been modified based on the xpath, operation and port number check to pop-up warning message. If operation is updateInstance, the xpath value is /addressContext/zone/sipSigPort and changing port number value is different from the existing value, the SBC displays the following warning message:

“SIP signaling port should be outside configured mediaPortRange if transportProtocol is UDP: Do you want to continue?”.

SBX-64411 / SBX-63180 2

During SMM configuration, the PRACK is generated to drop 18x message. The SBC sends PRACK without unique branch param.

Platform/Feature: SBC Core: SIP

The code has been modified to generate a unique branch pram when generate PRACK for dropping 18x (support PRACK).
SBX-64414 2

Due to misconfiguration in VMWare (vSpehere client), the E1000 (default value) adapter is selected while creating virtual machine. Due to the selection of the E1000 adapter type, after ISO installation the np.log file will fill with the following error event:

"SWe_NP[2640]: EAL: Error reading from file descriptor 17: Input/output error (np.log)."

Platform/Feature: SBC SWe: Application

The code has been modified to check the adapter type as VMXNET 3 in VMWare (vSpehere client). Currently, E1000 Adapter type is not supported by DPDK. Thus, SWe_NP gracefully exits by throwing the following error message in the np.log file:

"ERR: Found e1000 adapter type,Update adapter to VMXNET3. exiting now"

SBX-64442 2

During the upgrade from BMC version 2.x to 3.x, under some rare conditions, because of timing issues next boot-up may cause core dump on host and restart. Under such conditions, application restarts itself.

Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified such that this issue should not be see after the SBC application is upgraded.
SBX-64451 / SBX-61867 2

This release contains the Linux 3.16.39 kernel, which included the changes to the TCP/IP stack which affected the reuse of the local port used in CDR transfer. This causes the CDR transfer attempted within 60 seconds of the last transfer to fail.

 Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified to add a short delay after the TCP/IP FIN verb is received from the far end to allow the connection to close completely.
SBX-64462 3

The LI AVP data between external PSX (with version >= 10.2.0 / Diameter Version >= 31) and SBC will be encrypted for both Legacy LI and IMS LI flavors.

Platform/Feature: SBC 5000/7000 Series: SIP

The code was developed to support cryptography of LI AVP data between PSX and SBC for Legacy LI (Radius packet cable LI) and IMS LI flavors.
SBX-64475 2 SIP CAC profile amendment

Platform/Feature: SBC Core: Documentation

Added the following note to the State flag on the SIP CAC Profile pages in EMA and CLI guides:

NOTE: Setting a SIP CAC profile state to "Disabled" does not disable SIP CAC functionality on IP Peers to which the SIP CAC profile is assigned. To disable SIP CAC functionality on a specific IP Peer, disassociate the SIP CAC profile from the IP Peer.

SBX-64519 /
SBX-63687
2

When Transcode if Different DTMF PT flag is enabled, the NRMA sends Wide-band as well as usual 8 KHz DTMF if honorSDPclockrate is configured.

Platform/Feature: SBC 7000 Series: SIP

The code has been modified to always add 8 KHz DTMF PT first (if not being used by any other codec) as configured in Preferred DTMF PT.

With this approach,

  • It is certain that preferredRtpPayloadTypeForDtmfRelay configuration apply to 8k, and for 16K; next available PT (most likely +1) will be used.
  • No impact on customers using this flag with 8K codecs.
  • The customers using 16K, can plan their configuration to get desired behavior (likely -1).
SBX-64546 / SBX-62538 2

The SBC does not indicate the GSX to add the charge Area Information on the egress side. The Cai=xxxxx present in the PCV header did not egressed to the GSX.

Platform/Feature: SBC Core: Application

The egress carrier code towards the GSX has modified to include a bit bag. This bit bag contains digits taken from the received or configured cai. This bit bag is sent to the GSX to resolve this issue.
SBX-64547 2

The SIPREC forking fails when SRS servers send 200 OK without SDP and Re-INVITE with SDP is received after the switchover.

Platform/Feature: SBC 5000/7000 Series: Media

The SMM used for this call flow, where initial INVITE is responded with 200 OK without an SDP is changed to "set a=recvonly" instead of "a=inactive".
SBX-64585 2

When the SBC receives reINVITE, it adds the wrong crypto from route PSP (configuration of cryptoSuiteProfile), which is not negotiated during the call establishment to the reINVITE.

Platform/Feature: SBC 5000 Series: SIP, SIP Access

The code has been modified to pick the active security PSP over the route PSP to add the correct crypto into reINVITE when it receives the session refresh.

SBX-64594 /

SBX-63482
2

The multiple INVITEs with replaces fail in the SBC. When the second INVITE with replaces is received, the SBC selects the wrong leg for bridging. Thus, the SBC rejects the second bridging.

Platform/Feature: SBC Core: Application

The code has been modified to select a proper leg for bridging.
SBX-64601 / SBX-64227 2

During call transfer, when the SBC receives NOTIFY with dialog-info containing only the call-ID and does not contain toTag and fromTag, the ScmProcess coredumps while relaying NOTIFY to the other leg.

Platform/Feature: SBC 5000/7000 Series: SIP

The code has been modified to avoid the SBC coredump while relaying NOTIFY with dialog-info.
SBX-64626 /
SBX-64573 /
2

The SBC was not populating retryafter header in the 503 response that it sends to reject a call during congestion.

Platform/Feature: SBC 5000/7000 Series: SIP

The code has been modified to copy the retry header info provided by the application to send it out in the response.
SBX-64740 2 The ClearDb on both Active and Standby SBCs does not affect the previously configured sweActiveProfile.

Platform/Feature: SBC SWe: Application

 The following note has been added to resolve this issue:

"After the database is cleared, the active profile is retained."

SBX-64785 3

From 6.2.0 release onward, the SBC determines the SRS reachability only through the SIP ARS status.

Platform/Feature: SBC SWe: Application

The following note has been added to resolve this issue:

"From 6.2.0 release onward, the SBC determines the SRS reachability only through the SIP ARS status. The pathCheckProfile must be configured to determine the reachability of the SRS peers and treat failure response like 501 as OPTIONS failure."

SBX-64787 / SBX-64436 2

The SBC reINVITE uses disrupted route header when InsertPeerAddressToRouteHeader, and call required authentication is enabled.

Platform/Feature: SBC Core: Application

The code has been modified to reinitialize the route header properly.
SBX-64833 / SBX-64053 2

During an LSWU, when TLS calls are active and standby system is upgraded, the TLS session information is synchronized to Standby. The SamProcess core dumps on standby if the TLS session data length of any session being synched is more than 2048 bytes.

Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified to avoid the SamProcess coredump during LSWU when TLS session data of the single session being synchronized is more than 2048 bytes.
SBX-64852 / SBX-64068 2

Standby instance is not running the 10 minute timer.

Platform/Feature: SBC Core: Application

The code has been modified to set the 10 minute timer in the standby mode.
SBX-65129 / SBX-63476 2

Modification from G722 to G711 is not successful and DSP starts sending 40msec packets.

Platform/Feature: SBC Core: Media

The code has been modified to always include the ptime for DRM and DDH to act upon when a call is modified from complex codec to G711.
SBX-65131 /  SBX-65005 2

The NAPT learning of media IP address and port does not work on Comfort Noise RTP packets received when using G711 with Silence Suppression.

Platform/Feature: SBC Core: Media

The SBC was explicitly ignoring Comfort Noise RTP packets for NAPT learning. The code has been modified to remove this check so that learning works on any RTP packet including Comfort Noise packets.

Known Issues

Known Issues in 06.02.01R000 Release

The following are the known issues in this release.

Table : Known Issues

Issue ID Sev Problem Description Resolution
SBX-67411 2 The SBC sends maxPtime as 60 milliseconds instead of 10 milliseconds while playing tone when transcoder free transparency is enabled.

Platform/Feature: SBC 5000/7000 Series: Application

Impact: This issue is seen only with TFT flag is enabled.

Workaround: Disable TFT flag.

SBX-67489 2

The Test SIP Adaptor Profile is not working in the EMA GUI.

Impact: This is a SIP Adaptor test utility that will test the SMM rules applied without making call. Based on the analysis, the issue is present in 6.2.0R000 build as well.  This issue is related to the utility and no impact on the SBC behavior. 

Workaround: Create the SMM rules and test the rules by making a call. 

SBX-67500 2

Observing split brain after rebooting active and standby Instance at once.

Platform/Feature: SBC SWe Cloud: Platform

Impact: When the active are standby instances are rebooted together, they try to come up at the same time and enters into split brain (both the nodes are in ACTIVE).  The scenario is a very rare occurrence as there is less possibility of both the nodes going down simultaneously. 

Workaround: Restart the node that has been configured as STANDBY.

Known Issues in 06.02.00R000 Release

The following are the known issues in this release.

Table : Known Issues

Issue ID Sev Problem Description Impact/Workaround
SBX-36464 2

In SBC SWe, the transcoded loopback call fails after a switchover and revert.

Platform/Feature: SBC SWe: Platform

Impact: For transcoded calls with loopback scenarios when a double failover happens, the voice path is lost.

Workaround: Place the end points on hold and retrieve them.

SBX-41268 3

RTCP Call: There are no alarms or calls tear down even when there are packet loss more than the threshold limit.

Platform/Feature: SBC Core: Application

Impact: There are no alarms or calls tear down even when there are packet loss more than the threshold limit.

Workaround: Enable inactivity for the packet loss to be reported.

SBX-42896

2

The SBC does not include the unknown CODEC in the SDP towards the SIP Rec even when the audio transparency is enabled.

Platform/Feature: SBC Core: SIP

Impact: Lawful Intercept, SIP REC, NICE recording may not work with unknown codec for this feature.

Workaround: If the codec is pre-determined, SMM rule can be applied to send that codec instead of G711.

SBX-43980 2

The CDR pattern mismatches in fields 152 and 153 (ingress and egress Maximum Packet Outage) for pass-through and transcoded calls.

Platform/Feature: SBC SWe: CDR

Impact: CDR for transcoded calls show excessive packet outage value that does not match actual packet gap.

Workaround: The excessive value of outage occurs because of UXPAD process jitter at the beginning of the call (approx. 10 packets). The jitter settles down later during the call and does not impact voice quality.

SBX-47125 2

DSP device memory dump contains Bit errors.

Platform/Feature: SBC Cor: Media

Impact: The DSP device memory dump collected is unfit for debugging as it contains bit-errors. This is the secondary coredump mechanism which kicks-in when single DSP core-dump fails.

Workaround: None

SBX-49769 2

Incorrect egress codec is written to CDR at egress gateway while executing 12 codec feature over GW-GW.

Platform/Feature: SBC Core: Application

Impact: The call is successful; however, the codec information reported in the CDR is incorrect.

Workaround: None.

SBX-51199 2

The SBC rejects INVITE with 414 URI too long when PCSCF + IBCF > IPX.

Platform/Feature: SBC Core: Application

Impact: This issue seen when there is double encryption by SBC.

Workaround: None

SBX-52005 3

The standby instance may require second reboot to recover after the HA links are restored from the split-brain scenario.

Platform/Feature: SBC SWe Cloud: Platform

Impact: Longer redundancy protection time, but no impact on call processing.

Workaround: Requires manual reboot of standby SBC

SBX-57551 2

The SBC does not send RTCP packets after a switchover when the signaling and media NAT are enabled both on the ingress and egress Trunk Groups.

Platform/Feature: SBC SWe: Media

Impact: For call flows with RTCP termination configured, and both RTP and RTCP NAPT configured, SBC may stop generating RTCP Sender report after switchover.

Workaround: None

SBX-58903 2

On an SBC HA infrastructure, there are active video calls. After switchover, the active calls are switched to the newly active SBC. The quality of the existing video calls will be degraded in the newly active box.

Platform/Feature: SBC 7000 Series: SIP

Imapct: There are no known call failures. There are no issues for the new video calls attempted after the switchover.

Workaround: None

SBX-60291 3

The partial config activation through Configurator fails due to Packet Service Profile config.

Platform/Feature: SBC SWe Cloud: EMA

Impact: The partial configuration update feature for the SBC SWe Cloud does not work for ERE that is, the ERE provisioning objects cannot be updated (for example, Packet Service Profile, IP Signaling Profile, and so on) using this feature.

Workaround: None

SBX-60741 2

During load, the switchover can take a couple of minutes to stabilize with sporadic call acceptance, till both the boxes stabilize once the sync is completed.

Platform/Feature: SBC SWe Cloud: Application

Impact: Sporadic call acceptance once the sync or the call audit is completed.

Workaround: None

 
SBX-61949 2

On the SBC SWe, the intermittent congestion errors may be observed when the DSP resource usage exceeds 90% in scenarios where the SBC has more than 8 CPU cores allocated for transcoding.

Platform/Feature: SBC SWe: Application

Impact: The intermittent congestion errors may be observed when the DSP resource usage exceeds 90%.

Workaround: For SWe deployment scenarios that have more than 8 CPU cores allocated for transcoding, the SBC must avoid exceeding 90% usage of compressed resources.

SBX-63256 2

The GRHA ARP bond switch from ETH0 to ETH1 causes system restart.

Platform/Feature: SBC 5000/7000 Series: Application

Impact: If something happens to the active slave device (eth0 or eth1), the bond device will properly switch to the backup but TIPC might notice the outage.  If TIPC notices the outage, there will be a momentary split brain causing one of the boxes to restart. The configured leadership algorithm (standard or enhanced) will determine which node remains active and which restarts to become standby upon recovery from the split brain.

Workaround: None

SBX-63459 2

If T.38 protocol version 3 is enabled in the Packet Service Profile and peering endpoints are sending V.34 fax, fax may fail to negotiate or fails during page transfer.

Platform/Feature: SBC SWe: Application

Impact: T.38 protocol version 3 faxes may fail to negotiate or fail during page transfer.

Workaround:The T.38 protocol version 3 must not be enabled in the Packet Service Profile. The V.34 faxes will be negotiated as T.38 version 0 protocol and pass successfully.

SBX-63933 2

Issue with the content sharing between H323 to H323 endpoints with H235 media encryption.

Platform/Feature: SBC SWe: Application

Impact: The H323 endpoint receiving H.235 encrypted content sharing will not see the shared video.

Workaround: Turn off H235 encryption.

SBX-65215 3

The sftpadmin path has changed.

Platform/Feature: SBC Core: Application

Impact: The CDR collection by NetScore does not work.

Workaround: Configure NetScore to use /var/log/sonus/sbx/evlog path instead of /var/log/sonus/evlog/evlog path for CDR collection.

SBX-65327 2

The SIPREC is not initiated after REFER if the recordingType is set as ingressLeg.

Platform/Feature: SBC Core: SIP

Impact: The SIPREC recording for recordingType ingressLeg does not work after a REFER.

Workaround: For SIPREC to work after REFER, set recordingType as egressLeg.

SBX-65346 2

The SBC application restart may be observed if timezone change (for example, set system ntp timeZone mySBCSystem zone utc) is combined with any other commands in a single configuration commit.

Platform/Feature: SBC 5000/7000 Series: Platform

Impact: The SBC restarts.

Workaround: The ‘commit’ time zone changes independently as a single command. For example,

config

set system ntp timeZone mySBCSystem zone utc

commit

If the above workaround is not followed, the SBC application may restart and can continue normal operations once application is up.  If the configuration load was partial because of restart, reload the configuration.

Known Limitations

The following limitations exist in this 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.
  • The physical NIC connectivity must be 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 HA interface must not be configured with link local address or subnet. For example, it must not be configured with 169.254.0.0/16 subnet. 

  • 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 will not be displayed when ifconfig linux command is executed. In case of S-SBC, if the ipInterface configuration needs to be modified and if the action is set to "dryup" in ipInterface configuration, it must be set to "force" before disabling the ipInterface and making any changes.
  • 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 TAC immediately.

Restricted Functionality for SBC Microservices

The following functionalities are not supported:

  • 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 

Restricted Functionality for AWS

  • The EC2 does not support VM console. The SSH must be used to access the VM.
  • The smarctl disk status is not supported on Amazon instance.
  • All the networking ports must be in different subnets.
  • The instance creation and reboot process take approximately 4 to 6 minutes to complete.
  • IP spoofing or L2 learning is not supported.
  • It is required to associate an EIP on MGT0 for an HA, and the CFN template automatically assigns the EIP. This is required for communicating with AWS servers while instance switchover. The EIP switchover takes 15-20 seconds.

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) will lose 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.