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 SBC Core.

Please note that all Ribbon 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 SBC Core 07.02.xx documentation is located at the following Wiki space: SBC Core 7.2.x Documentation.

Release Notes Use and Distribution

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

Associated Ribbon Bulletins

The following Ribbon Bulletins are referenced in this release note:

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

  • Warning-19-00028624: Custom EMA TLS certificate is overwritten with a default self-signed SBC certificate during an upgrade to versions 6.1.x, 6.2.x, 7.1.x, 7.2.x 
  • Warning-19-00028636: SBC SWe Gateway-to-Gateway signaling is disabled in certain SBC SWe versions 
  • Warning-19-00029555: CDR Viewer and Live Monitoring cannot be enabled/disabled
  • Warning-17-00022737: Re-installing an SBC from an ISO image and restoring the config. from a tar.gz backup file may cause loss of encrypted config. parameters for certain releases
  • Warning-19-00022867: SM Process may core dump after upgrading to version 3 of the BMC software
  • Warning-19-00029581: UPGRADE : Stale calls may be found on a newly upgraded SBC, if upgrading from a version prior top 6.1.0 to a later release.
  • Warning-19-00029598: SBC causes one way audio in scenarios where mediaNat is enabled and NAT device performs port translation only
  • Warning-19-00029596: Gcore collection disables with a service impact.

To view/download Ribbon bulletins, do the following:

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

The WBA section may not include all Warnings, Bulletins and Alerts associated with this release. Before attempting to upgrade to any release, it is recommended to check the Ribbon Support Portal for any newly published WBAs that may include this release in the "affected versions" section.

Problems or Questions

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

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

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

About SBC Core

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

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

Interoperability

The SBC Core software interoperates with the following:

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

Note

NetScore maintains a list of remote host keys for all nodes from which it collects data. If NetScore is deployed in your network, 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 Ribbon 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 various Ribbon products, including backwards compatibility, refer to Ribbon Product Interoperability.

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

Sample Heat Templates Included in This Release

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

SBC Heat Templates

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

Note:

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

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

SBC SWe/SWe Cloud Requirements

 

SBC SWe Cloud Requirements for OpenStack

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

Server Hardware Requirements

 

ConfigurationRequirement
Processor

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

Note

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

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

Minimum 4 NICs.

Note

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

Note

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

Note

6 NICs are required for supporting PKT port redundancy.

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

S-SBC SWe Requirement

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

32 vCPUs

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

128 GiB RAM

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

100 GB Disk

None

4 vNICs/6 vNICs

Attach MGT0 port to the Management VirtIO Tenant network.

HA port has to be on IPv4 VirtIO Tenant network.

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

M-SBC SWe Requirement

M-SBC SWe Requirements
for 30K Media Sessions
Notes

20 vCPUs

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

32 GiB RAM

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

100 GB Disk

None

4 vNICs/ 6 vNICs

Attach MGT0 port to the Management VirtIO Tenant network.

HA port has to be on IPv4 VirtIO Tenant network.

OpenStack Requirements

The SBC SWe supports the following OpenStack environments:

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

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

SBC SWe Requirements for KVM

The following table lists the server hardware requirements.

KVM Hypervisor Server Hardware Requirements

 
Configuration Requirement
Processor

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

Note

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

Note

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


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

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

Note

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


Ports

Number of ports allowed:

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

SBC SWe Requirements for VMWare

The following table lists the server hardware requirements:

Server Hardware Requirements

 
 ConfigurationRequirement
Processor

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

Note

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

Note

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

Note

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

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

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

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

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

Ports

Number of ports allowed:

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

 

 

Warning

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

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

Required Software and Firmware Versions

Components

Software/Firmware

Version

SBC Platform

  

SBC 51x0/52x0 BMC

V03.20.00-R000

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

BMC: V03.20.00-R000

BIOS: V1.17.0

SBC 7000 Firmware

BMC: V03.20.00-R000

BIOS: V2.13.0

SBC Application

 


Operating System (OS) Version

V06.02.02-R003
SonusDB

V07.02.02-R003

EMAV07.02.02-R003

SBC Application

V07.02.02-R003

Note

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

Note

SNMPV3 requires EMS Version 12.x in order to work with SBC 7.2.2R003.


How to Verify Currently Installed Software/Firmware Versions

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

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

Software Bundles

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

  • SBCSWe_7.2
  • SBC5x7x_7.2

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

SBC 5000 Series (51x0/52x0) Firmware

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

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

  • bmc5X00_v3.20.0-R0.rom.md5sum

  • bmc5X00_v3.20.0-R0.rom

SBC 5400 Firmware

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

SBC 7000 Series Firmware

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

Note

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

SBC Core Operating System Installation Package

The ConnexIP Operating System installation package for SBC Core:

  • sbc-V07.02.02R003-connexip-os_06.02.02-R003_8_amd64.iso
  • sbc-V07.02.02R003-connexip-os_06.02.02-R003_8_amd64.iso.md5


Note

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

SBC Core Application Package

The SBC Application installation and upgrade package for SBC Core:

  • sbc-V07.02.02R003-connexip-os_06.02.02-R003_8_amd64.qcow2
  • sbc-V07.02.02R003-connexip-os_06.02.02-R003_8_amd64.qcow2.md5
  • sbc-V07.02.02-R003.x86_64.tar.gz
  • sbc-V07.02.02-R003.x86_64.md5
  • sbc-V07.02.02-R003.x86_64.signature

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

Cloud Service Archive (CSAR) Packages for VNFM Deployment on OpenStack

These files are for SBC SWe deployments in the OpenStack cloud using VNFM.

For VNFM deployment, the VNF Descriptor (VNFD) file is provided in a Cloud Service Archive (CSAR) package for the type of SBC cluster being deploying. VNFs are independent and CSAR definitions are imported into the VNFM via an Onboarding mechanism. The SBC has several different CSAR variants, for different personalities (S-SBC, M-SBC) and interface types (virtio, sriov). The supported CSAR packages for the SBC are:

  • ssbc_virtio_7.2.csar
  • ssbc_sriov_7.2.csar
  • msbc_virtio_7.2.csar
  • msbc_sriov_7.2.csar

Files required for CSAR creation: 

  • createVnfmCsar.py
  • vnfmSol001VnfdTemplate.yaml
  • sbc-V07.02.02R003-connexip-os_06.02.02-R003_8_amd64.qcow2

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

Upgrade Notes

Warning

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

Note

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

Note

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

Note

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

Note

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

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

Note

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

Note

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

Note

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

Disk Space Requirements

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

Note

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

07.02.02R003 Upgrade Information

Warning

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

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

The following names are not allowed:

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

Note: Any CLI usernames consisting of digits only or not conforming to new user naming rules will be removed after performing a restore config in release 7.2.2R003. 

Warning

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

Warning

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

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

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

Support of maddr Post-Upgrade

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

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

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

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

See the following pages for configuration details:

SBC SWe Pre-Upgrade Requirements

VM CPU resource allocation requirements

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

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

Disable Call Trace feature prior to LSWU/upgrade

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

Manually check for Hostcheck Validation Failed message

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

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

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

  3. Power off the VM.

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

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

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

  7. Perform similar procedure for LSWU on Active.

Preparing for Upgrade (All Platforms)

Warning

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

Note

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

Note

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

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

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

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

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

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

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

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

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


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

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

show configuration oam eventLog typeAdmin
typeAdmin packet {
 
state      enabled;   
fileCount   64;   
fileSize    10240;
filterLevel info; 
servers server1;
 }

 typeAdmin memusage {
 state enabled;
 }

Update the configuration with the following commands -
configure
 set oam eventLog typeAdmin memusage servers server1

Supported Live Software Upgrade (LSWU) Paths

ATTENTION

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


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


Supported Upgrade Paths

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

V05.01.00F007

V06.00.00F006V07.01.00R000
V05.00.00S204V05.01.00F008V06.00.00F007V07.01.00R001
V05.00.00F001V05.01.01F001V06.00.00F008V07.01.00R002
V05.00.00F002V05.01.01F002V06.00.00F009V07.01.00R003 
V05.00.00F003V05.01.01F003V06.00.00F010V07.01.00R004
V05.00.00F004V05.01.01F004V06.00.00F011V07.01.00F001
V05.00.01R000V05.01.01F005V06.00.00F012

V07.01.00F003

V05.00.01R001V05.01.01F006V06.01.00F001

V07.02.00R000

V05.00.01R002V05.01.00S608V06.01.00F002V07.02.00R002
V05.00.01S001V05.01.00S610V06.01.00F003V07.02.01R000
V05.00.01F001V05.01.00S611V06.01.00R000V07.02.01R001
V05.00.01F002V05.01.00S612V06.01.00R001V07.02.01R002
V05.00.01F003V05.01.00S613V06.01.00R002

V07.02.01F001

V05.00.02R000V05.01.00S614V06.01.00R003

V07.02.01F002

V05.00.02R001V05.01.00S617V06.01.00R004V07.02.01F004
V05.00.02A059V05.01.00S619V06.01.00R005 V07.02.01F005
V05.00.02A061V05.01.00S620V06.01.00R006

V07.02.01R003

V05.00.02F001V05.01.00S621V06.01.00R007

V07.02.01R004

V05.00.02F002V05.01.00S622V06.01.00R008 V07.02.01R005
V05.00.02F003V05.01.01R000

V06.01.00R009 

V07.02.02R000
V05.00.02F004V05.01.01R001V06.02.00R000V07.02.02R001 
V05.00.02F005V05.01.02F001V06.02.01R000V07.02.02F001
V05.00.03R000V05.01.02F002V06.02.01R001V07.02.02R002
V05.00.03R001V05.01.02F003V06.02.01R002 
V05.00.03R002V05.01.02F004V06.02.01F001
V05.00.03R003V05.01.02F005V06.02.01F002
V05.00.03F001V05.01.02F006V06.02.01F003
V05.00.03F002V05.01.02F007V06.02.01F004
V05.00.03F003

V05.01.02F008

V06.02.01F005
V05.00.03F004V05.01.02F009V06.02.01F006 
V05.00.03F005V05.01.02S001V06.02.01F007
V05.00.03F006V05.01.02R000V06.02.01F008
V05.00.03F007V05.01.02R001V06.02.02R000
V05.00.03F008V05.01.02R002V06.02.02R001
V05.00.04F001V05.01.02R003V06.02.02F001
V05.00.04R000V05.01.02R004V06.02.02F002
V05.00.04R001V05.01.03R000V06.02.02F003
V05.00.05F001V05.01.03F001V06.02.02F004
V05.00.05F002V05.01.03F002V06.02.02F005
V05.00.05F003V05.01.03F003V06.02.02F006
V05.00.05F004V05.01.03F004V06.02.02F007
V05.00.05F005V05.01.03F005V06.02.02F008
V05.00.05F006V05.01.03F006V06.02.02F009
V05.00.05F007V05.01.03F007V06.02.02F010
V05.00.05F008V05.01.03F008V06.02.03R000
V05.00.05R000V05.01.03F009V06.02.03F001
V05.00.06R000 V05.01.03F010V06.02.03F002
V05.00.06F001V05.01.04R000V06.02.03F003
V05.00.06F002V05.01.04F001V06.02.03F004
V05.00.06F003V05.01.04F002V06.02.04R000
V05.00.06F004V05.01.04F003V06.02.04F001
V05.00.06F005V05.01.04F004


V05.01.05R000


V05.01.05F001


V05.01.05F002


V05.01.05F003


V05.01.05F004


V05.01.05F005 


V05.01.06R000


V05.01.06F001


Note

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

df -kh


New Features

New Features in 07.02.02R003 Release

 There are no new features in this release.

New Features in Previous Releases

For lists of the features in previous 7.2.x releases, refer to the following release notes:

Resolved Issues

Resolved Issues in 07.02.02R003 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSevProduct DescriptionResolution
SBX-958953

Four SCMs cored after a switchover.

Impact: The SCMs have cored after a switchover.

Root Cause: There is a bug that allows the RTM to attempt to process the Call Audit fault, while still in STANDBY mode. The Call Audit fault will only be processed while in Active Mode. This causes a core.

Steps to Replicate: The steps cannot be reproduced.

Platform/Feature: SBC

The code is modified to prevent the RTM from processing the Call Audit fault while in STANDBY mode.
SBX-954511

The SCM fast memory increase caused a delayed switchover with an outage.

Impact: If the multilevel INVITE with Replaces is run, memory and CPU utilization by the SCM Process increases drastically and leads to core dump.

Root Cause: Each INVITE with Replaces is a new Callgroup. Each call group has their own segments. For each segment, there are associated segments.

When the Release call is invoked, it releases all segments and each call segment frees associated call segments. During the release, the flow for such a call event is posted multiple times for various orig and term GCID’s.

Steps to Replicate:

  1. Test multilevel INVITE replaces (more than 15)
  2. Crash should not occur

Platform/Feature: SBC

The code is modified so the event does not need to be posted multiple times for the exactly same original and term labels.

SBX-97236 / SBX-971291

Portfix SBX-97129: After an upgrade to V08.02.00-R001, the Inbound Teams DDI call placed on hold causes a core dump.

Impact: Getting a Pes Process coredump while running registrations.

Root Cause: The CallParamMatchName function is called with a matchName, which is a 15 byte array and the strncpy is used to copy the string to the 50 byte array but with a wrong size of MATCH_NAME_SIZE, defined as 30 byte*.*.

Passing a bigger size than the actual destination string to the strncpy is resulting in padding 0’s beyond the actual 15 bytes of the matchName. This was corrupting the stack and the stack pointer, causing a segmentation fault.

Steps to Replicate: The steps cannot be replicated.

Platform/Feature: SBC

The code is modified to change the size of matchName[] size to the correct size.
SBX-927782

The Edit route action taking a long time to complete.

Impact: The Edit Route action was taking long time and failing.

Root Cause: Use of special characters, such as # in destination National field, can cause the failure of the Edit route action.

Steps to Replicate:

  1. Create Route with special character in Destination National.
  2. Select the Route that is created in Special Character.
  3. Edit Form must be load.

Platform/Feature: SBC

A few more special characters to support Destination National field in the Edit route are allowed.

NOTE: The following special characters are not supported: & = , \

SBX-970791

After the LDG triggered a switch over, the SBC is rejecting all register messages with an 500 internal error.

Impact: The SCM process may coredump when the SIP signaling port being used during a SIP registration call flow is state disabled.

Root Cause: The SCM process core dumped when it attempted to display a debug warning message that contained the disabled SIP signaling port number (but encountered a NULL pointer).

Steps to Replicate: The steps cannot be reproduced.

Platform/Feature: SBC

The code is modified to prevent accessing a NULL pointer, when attempting to generate the debug log message.
SBX-969922

TLS call failures were observed due to a port value set to 1 instead of 5061.

Impact: The SBC uses Port 1 for sending an INVITE out for the TLS protocol when the route header was received without a port.

Root Cause: The issue is because when the route header is received without a port in it, the SIPSG was incrementing the port for the TLS. Since the port was not received, the port received is considered as 0. For the TLS, increment by 1. When incremented, the port becomes 1 and this gets used for send an INVITE that is resulting in calls failing.

Steps to Replicate: Send the Route Header without port Route: <sip:ipaddr:;lr>. The SBC will use port 1 for sending an INVITE that is causing the issue.

Platform/Feature: SBC

The code is modified to check when the port is received in route header or not.
If port is received, then increment the port for the TLS. If it is not received, then increment and allow the SIP stack to handle it.

SBX-960871

SBC is not sending RTCP to egress Peer for transcode only.

Impact: In customer call flow :

Ingress Peer -(ISDN)> GSX ---(GW2GW)-> SBC --(SIP)-> Egress Peer, with PSP setting as "transcode only" and RTCP enabled, SBC does not send RTCP packets towards egress.

Root Cause: Due to changes made for feature SBX-6366, SBC does not mark XRES resource as duplex and marks it as receive only. And hence SBC does not send RTCP towards egress.

Steps to Replicate:

  1. Reproduce the problem in following call flow:
    Ingress Peer -- SIP -- GSX -- GW2GW -- SBC -- SIP -- Egress Peer
    This transcode only call and RTCP is enabled.
    Result: No RTCP sent by SBC to egress .
  2. Verify the issue by applying SamP with GWFE change but not change in ScmP. ( just debugging logs )
    Same setup.
    RTCP traffic was sent from SBC to egress.

Platform/Feature: SBC

Modified GWFE code to set RTCP send and receive bandwidth as CPC_RTCP_BW_UNKNOWN if CPC parameter is not received from Ingress SBC or GSX. This makes sure RTCP mode for XRES resource is duplex and SBC sends RTCP towards egress SIP endpoint.
SBX-960942

The SRV query is not sent to the DNS server when porting the SBX-86420 fix to 6.2 and 7.2 code branch.

Impact: In this case, even when the FQDNPort is zero, the SIPSG/SIPS port is incremented by 1 so the FQDN port is set 1. Due to this issue, the SRV query is not sent to the DNS server.

Root Cause: When the TLS tranport is selected, the SBC is trying to increment the FQDN port by 1. In this case, even when the FQDNPort is zero, the SIPSG/SIPS port is incremented by 1 so the FQDN port is set 1. Due to this issue, the SRV query is not sent to the DNS server.

Steps to Replicate:

Procedure:

  1. Send an INVITE with TGRP parameters in R-URI.
  2. The SBC sends TGRP information to the PSX.
  3. The PSX does TGRP based routing and sends the route.
  4. The SBC will send a SRV query to the DNS to resolve port and ip details when egress peer is FQDN.

Observation: The SBC does not send SRV query to the DNS but sends 'a' query.

Expected: The SBC will send a SRV query to DNS to fetch port and ip details and establish TLS connection. with peer.

NOTE: The same scenario works fine when the egress transport preference is UDP or TCP.

Platform/Feature: SBC

The code is modified to increment the remote fqdnPort by 1 only when the port is received from the PSX.
SBX-97425 / SBX-96117 / SBX-947902

The Backup/Restore file cannot be downloaded from the EMA if the file name contains a dot (.).

Impact: The Backup/Restore file cannot be downloaded from EMA if the file name contains a dot (.)

Root Cause: The issue came from the downloadSavedConfig block making an API call while running the SBC and running on the EMS at the same time.

Steps to Replicate:

  1. Login into the EMA.
  2. Navigate to Administration -> System Administration -> Backup/Restore.
  3. Download the Backup file.

Platform/Feature: SBC: EMA

The code is modified so making an API call on the EMS uses the normal method, even if it is running on the SBC.
SBX-932391

Caller eSBC cancels the call after 180: 504 to ingress, CANCEL to egress.

Impact: Late media convert call with DLRBT is not working.

Root Cause: Bad resource activation.

Steps to Replicate: Setup a late media convert call with DLRBT enabled.

Platform/Feature: SBC

When DLRBT is being played, code has been added to stop activating the full resource chain when tone is being played.
SBX-951141

The SBC IgnoreTransparency cannot be set on the EMA V6,7.2 and 8+.

Impact: The SBC IgnoreTransparency cannot be set on the EMA V6,7.2 and 8+.

Root Cause: There was no check if the "not" is applied to complete expression or not.

Steps to Replicate:

  1. Log on the EMA.
  2. Navigate to All-> profile-> services-> Transparency profile-> SIP Header
  3. Select transparency profile.
  4. Click on New Sip Header.

After that, the "Ignore Transparency " field can be seen.

Platform/Feature: SBC

The code is modified to check if "not" is applied to the whole expression or not.
SBX-945182

Disabling the media lockdown does not suppress media lockdown re-INVITE when the SRTP is enabled.

Impact: If the SBC offers crypto, and peer does not reply with crypto in the answer, a re-INVITE is sent to lockdown the crypto attribute (no crypto ). If NAT is enabled, one second media drops while re-learning for the new re-INVITE is happening. For non-NAT cases, nothing will be observable except for a signaling change.

Root Cause: The issue was the SBC's original behavior.

Steps to Replicate:

1. Setup the SBC so that it sends crypto in offer.
2. In answer from the peer - do not send any crypto attribute.

Without fix, the SBC would send yet another re-INVITE if fallback to the unencrypted is allowed. With a fix, this extra re-INVITE will be suppressed.

Platform/Feature: SBC

If a crypto line is sent in the offer and none are received in answer, if minimize media and media lockdown flags are appropriately set to minimize offer/answers, a re-INVITE to lock down cryto attribute is not sent.
SBX-953551

A SIP to SIP call no ring back tone passed into the ingress when the PEM header is enabled on the egress endpoint.

Impact: There is no RBT when the PEM header is enabled, splitting 18x into alerting and the progress flag is enabled.

Root Cause: This flow was never tested with a flag or split 18x into alerting and progress.

Steps to Replicate: Setup a call with PEM enabled on the egress and with the split 18x flag enabled.

Platform/Feature: SBC

The code is modified so before the 18x is split, the PEM header handling is done.
SBX-737193

The SMM writeCdr was failing to write to the ATTEMPT CDR when acting upon the 300 Multiple Choice.

Impact: The SBC is failing to write the SMM fields in the ATTEMPT CDR when acting upon 300 Multiple Choice.

Root Cause: The code was missing to handle the SMM information for a Redirect Scenario in the CDR.

Steps to Replicate: Use the SMM to write in the cdrField1.

The information in the SMM will be correctly written, but will not transfer to the ATTEMPT log.

Platform/Feature: SBC: CDR, SIP

The code is modified to write the SMM information in the CDR for a Redirect Scenario.
SBX-932552

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

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

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

Steps to Replicate:

  1. Bring up the SBC in 7.2.2R0.
  2. Log on to EMA.
  3. Select 'ALL' -> 'Address Context' -> 'IP Access ControlList' -> 'Rule' -> 'default'
  4. SourcePort is not changing from integer to 'any' in EMA.
  5. It working fine in CLI, SourcePort number is changing from integer to 'any' and 'any' to integer.

Platform/Feature: SBC

The code is modified to validate the source port as type alphanumeric instead of an integer.
SBX-969392

The ImPr cored when the SBC was running a call load.

Impact: The SBC ImProcess cored when the LI server became unavailable.

Root Cause: When the LI server becomes unavailable and a large number of packets are queued up for that server, the ImProcess takes more than 10 seconds to clean up all those packets, and the process core dumps.

Steps to Replicate:

  1. Establish a large number of LI calls.
  2. Bring the LI server down.
  3. Ensure that the ImProcess does not core dump.

Platform/Feature: SBC

The healthcheck is disabled while cleaning up the packets.
SBX-97072 / SBX-968342

Portfix SBX-96834: Asymmetric PRACK Interworking was not working as described.

Impact: Whenever any codec entry is deleted from codec list in the PSP and in the PSX, it rearranges the codec list immediately. There will not be any empty codec entry in the list.

The same issue is in the ERE, so it can be treated as a bug in the ERE.

Root Cause: When any CodecEntry is deleted, it is not rearranging the CodecEntry, which causes a NULL value in that place.

Steps to Replicate:

1. Configure the CodecEntry1 ,CodecEntry2 to CodecEntry12
2. Delete any CodecEntry.

Result: The call will be successful.

Platform/Feature: SBC: ERE

The code is modified so that there is no NULL value in between the two CodecEntry's.
SBX-96993 / SBX-967061

Portfix SBX-96706: Multiple switch overs causes non 5060 sipSigPorts to become inactive.

Impact: When user configured >= 2 SIP SIG ports are configured with same IP address but different port numbers, they are using the same LIF group that contained 1 LIF.

Pkt down triggered a switchover and it stayed down for an extended time. After the pkt up, a second switchover occurred, then only one SIG port became inactive. The other SIG ports were stuck in OOS.

Root Cause: Since the pkt port was down when new standby node came back online, the SIP SIG ports were restored while the LIF was OOS. The address registrations failed as a result. After the SIPCM has reached max number of retries, the LADDRs of the SIG ports, except the first one, were deleted in the NRS context.

Later when pkt port came back up, the NRS brought LIF back in service and registered the only one signaling address saved in the NRS context.

Steps to Replicate:

  1. Configure the 2 VLANs on YF or BF pkt2.
  2. Configure the 4 SSPs on the first VLAN interface; 4 SSPs on the second VLAN interface. 4 SSPs use udp/tcp port numbers 5060, 5160, 5260, and 5360 with the same IP address.
  3. Run the sbxstop command.
  4. Unplug the packet ports - YF pkt2.
  5. Run the sbxstart command
  6. Display the SSPs on VLAN interfaces.

Platform/Feature: SBC

The code is modified to only delete the LADDR before reaching the max number of retries. And restored the pendingNrsReq flag properly when the address registration failed.



Resolved Issues in 07.02.02R002 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSevProduct DescriptionResolution
SBX-933121

The SBC Memory shows High alerts.

Impact: When Local Ring back tone is configured on the SBC and egress endpoint sends 183 Session Progress with SDP followed by 180 Ringing, SCM Process does not free up memory allocated even after call is completed. Without a fix, SCM Process will leak memory.

Root Cause: When Local Ring back tone is configured and egress endpoint sends 183 Session Progress with an SDP followed by 180 Ringing, SCM Process does not free up the media session descriptor structure.

Steps to Replicate: Run call load with a Local Ring back tone configured and monitor the virtual memory usage of ScmProcess. With a fix, virtual memory of SCM Process must not be high after all the calls have been disconnected.

Platform/Feature: SBC

The code is modified to ensure memory allocated for the packet service profile structure is freed when no longer required.
SBX-921551

The SBC releasing the call with 504 when the DLRB and Downstream Forking are enabled.

Impact: The SBC releasing the call with 504 when the DLRB and Downstream Forking are enabled.

Root Cause: The Race condition was not handled properly. When the first 180 without SDP is received, the forking list was updated and the message stored. When the 18x with SDP is received a second time, the forking list must be updated and store the new received 18x.

Steps to Replicate:

Send RTP before sending 180 Ringing.

Without fix - call is not successful and with fix call is successful.

Platform/Feature: SBC

If the RTP learning occurs before the corresponding 18x when the SDP is received, save the SDP into queue of possible SDP's to cut-thru for use, while 200 OK is received to ensure the 200 OK does not have the SDP.
SBX-93388 / SBX-933872

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

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

Root Cause: The SCM process was de-referencing a null pointer.

Steps to Replicate: The music on hold is used in the deployment and a call is put on hold/resumed and then transferred.

Platform/Feature: SBC: MS Teams

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

Losing a call from MS Teams, and audio loss for 30 seconds during a switchover.

Impact: If there is an SBC switch-over after the call is established, there can be a delay (e.g. 30 seconds) when re-establishing the media from PSTN to the MS Teams direction.

Root Cause: The stored SSN value does not get updated before the SBC switch-over occurs, and it causes the SSN jump backwards after switch-over, which causes the one way audio issue for sometime until the SSN value increments pass the previously sent value.

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

Platform/Feature: SBC: MS Teams

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

The DFW1-CASBC-02 Box A had a SCMP coredump.

Impact: The SBC cored when accessing Box A, switching over to Box B instead.

Root Cause: Enabling the SDP transparency and the directMediaAllow to show a simple 18x response from the peer may cause core due to access from an invalid address.

Steps to Replicate: Disable either the SDP transparency or the directMediaAllow.

Platform/Feature: SBC

The code is modified to ensure it does not have access with an invalid address.


Resolved Issues in 07.02.02F001 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSevProduct DescriptionResolution
SBX-924702

There is a possible slow memory leak in SAM process while running GW-GW calls.

Impact: A possible slow memory leak in the SAM process.

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

Steps to Replicate: This problem is not reproducible.

Platform/Feature: SBC

The code is modified to free the memory that was being leaked.
SBX-93113 / SBX-925802

Portfix SBX-92580: The SIP Domain is missing in FROM header after an upgrade. (Originated in release 7.2.3).

Impact: The DM rule for the FROM URI is not working.

Root Cause: It was introduced in a previous bug fix to treat FROM URI for a specific RewriteIdentity.

Steps to Replicate: Configure PSX for the FROM URI, and on a SIP-SIP call. Verify FROM header is picking up the DM rule from the FROM URI.

Platform/Feature: SBC

The code is modified to support the old behavior for allowing the FROM URI to take affect even if the Rewrite Identity is disabled.
SBX-926371

The SBC introduces a static in the custom Announcement.

Impact: If the issue is not fixed, the quality of the announcement will be insufficient.

Root Cause: A software bug in the DSP was resetting the first sample of every announcement frame to zero.

Steps to Replicate:

Note: Any call flow that involves using TPAD to play announcement can work correctly.

1. The set-up requires SBC and PSX. A PSX script is implemented which has information about what announcement to play and DTMF digits that need to be entered to switch to the second stage of the call.
2. Client makes a call to SBC. In the first dip SBC plays the announcement configured in the script and waits for DTMF digits to be entered.
3. A route is present in PSX for DTMF digits entered.
4. After entering digits, PSX now goes for second dip for the new digits entered and returns a route to SBC.
5. With this route, SBC calls Egress end point.
6. Monitor the announcement quality played at step #2..

Platform/Feature: SBC

The code is modified to stop clearing the first sample.


Resolved Issues in 07.02.02R001 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSevProduct DescriptionResolution
SBX-924792

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

Impact: SBC Release 7.2.2 is missing PKT Port redundancy support, when it is listed as available.

Root Cause: In I-SBC, PKT Port redundancy support is added in 8.x releases, but not present in the 7.2.2 release.

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

Platform/Feature: SBC

Back ported the support added in 8.x to 7.2.2. release.
SBX-923861

Sending an a=inactive to the late media re-INVITE, after a peer put the SBC on hold, does not comply with RFC.

Impact: The SBC running 721R2 is responding with 'a=inactive' instead of 'a=sendrecv' in the 200ok SDP to late media re-invite causing no audio.

Root Cause: Requirement to send a=sendrecv in this scenario was missed.

Steps to Replicate:

Step 1: From logs, generate sipp scripts using the dbgDecode.pl utility provided by Ribbon TAC.
Step 2: Setup 7.2.1 system without fix.
Step 3: Run the call flow to see that the problem is observed.

 

To Verify:
Step 4: Change ScmProcess with release having the fix.
Step 5: Make call to observe that SBX is sending a=sendrecv in 200 OK.


Platform/Feature: SBC

The code is modified to send a=sendrecv to make it RFC compliant.
SBX-92409 / SBX-913321

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

Impact: Getting the IP peer current statistics for individual IP peer was not working.

Root Cause: The comparison of IP Peer specified in the CLI with the IP Peer statistics list was missing. Due to this issue, more than one IP Peer is configured under same zone, and the statistics for first IP Peer in the list are always used to get selected.

Steps to Replicate: Multiple IP Peers need to be configured under the same zone to reproduce this issue.

Platform/Feature: SBC

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

Portfix SBX-90654: A parked call was not working correctly because the NRMA process had incorrectly swapped PSP information on the call legs. (Originated in release 7.2.1).

Impact: The SBC was unable to retrieve a parked call.

Root Cause: This is a new call scenario being implemented for MS Teams interop.

Steps to Replicate: Run a test call in MS teams for call park and retrieve.

Platform/Feature: SBC: MS Teams

The code is modified to correctly process PSP information on the different call legs during parking and retrieval of the call.
SBX-92413 / SBX-881222

Portfix SBX-88122: In scenarios where MS Teams referred the call to another, the SBC started to play a RBT (ring back tone) and if the REFER failed due to the C-party not answering, the media could not be established again between the A and B party. (Originated in release 7.2.1).

Impact: Media is not re-established on A-B call when REFER to C fails.

Root Cause: The media resource used to play the RBT did not get freed up correctly when the REFER failed and this blocked the media flow from A to B being re-established.

Steps to Replicate: Make a call from PSTN to MS Teams, have MS Teams REFER the call to another user. Let the phone ring as C-party but do not answer it.

Platform/Feature: SBC: MS Teams

The code is modified to correctly free up the RBT resources so the A to B call can reestablish.
SBX-91726 / SBX-87861 1

Portfix SBX-87861: While performing a port switch-over, observed that the SBC active went for reboot and Standby did not takeover the calls. (Originated in release 8.1.0).

Impact: The SBC does not properly put calls on Standby when a switch-over occurs.

Root Cause: A cable pull was resetting calls on the interface, which took more than 5 seconds and exceeded the health check threshold, causing the thread to lock on reset.

Steps to Replicate:

  • Bring up setup in port redundancy setup.
  • Cable pull packet interface to trigger port switch over.

Platform/Feature: SBC

The code is modified so the thread health check mechanism on a port reset.
SBX-915702

If there is an SBC switch-over after the call is established, there can be a delay (e.g. 30 seconds) to re-establish the media from the PSTN to MS Teams direction.

Impact: The media may have a delay (e.g 30 seconds) when re-establishing.

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

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

Platform/Feature: SBC: MS Teams

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

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

Impact: Calls on hold do not hear the ring back tone, while original calls do.

Root Cause: The code was intentionally not sending re-INVITE messages in this scenario before.

Steps to Replicate: Run any MS Teams transfer call scenario.

Platform/Feature: SBC: MS Teams

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

The Call Graphs are showing more calls after upgrade.

Impact: Stale calls may be found on the newly upgraded SBC when upgrading from a version older then 6.1.0 to something higher.

Root Cause: As a result of changes that were made to the call ID in 6.1 code, during LSWU any calls that existed prior to the upgrade and were then modified or terminated after the upgrade started will be left in a hung state. The only way to clean up these calls is to use the following commands:

 unhide debug
 request sbx rtm debug command “cleanup <gcid>


Steps to Replicate: N/A

Platform/Feature: SBC

The code is modified to prevent calls from being hung during upgrade from versions older than 6.1.
SBX-92412 / SBX-91820 2

Portfix SBX-91820: The SBC was immediately disconnecting the SRS call after establishing the SIP Rec session with the next available SRS when the initial SRS has responded with a failure 4xx response. (Originated in release 7.2.1).

Impact: The SBC was disconnecting the SRS call.

Root Cause: The SBC, after finding next reachable SRS when the initial one has failed with 4xx, created a new SIP Rec Call Block data matching to new SRS. For the old SIP Rec Call Block, the state machine was invoked with a wrong event and this wrong event in the state machine was deleting the old SIP Rec Call Block along with new one.

Steps to Replicate:

1. Create a SRS Group with three SRS Servers
2. Configure num streams to 2.
3. SBC Tries to send SRS Invite to first two SRS
4. Send 4xx from the first SRS and 2xx from the Second SRS
6. After the 4xx SBC tries to send new INVITE to 3rd SRS
7. Send 2xx From 3rd SRS
8. At this step after ACK towards 3rd SRS, SBC Immediately sends BYE to third SRS

Platform/Feature: SBC

The code is modified that only old SIP Rec Call Block data is removed and the new SIP Rec Call Block data is retained.
SBX-908672

SSREQ server has memory leak, which could soon eat up virtual memory when there is call load via SSREQ client.

Impact: The SSREQserver memory will leak, when there is call load via SSREQ client.

Root Cause: The memory allocated for call data and call trace not being deleted properly, leaving those memory blocks idle forever.

Steps to Replicate:

Without the fix, memory growth can be seen every minute. Ribbon test observed 1 call per 5 second SSREQ traffic, the memory used by SSREQ grew from 0.5% to 10% in less than 30 minutes.

Platform/Feature: SBC

The code is modified to take care of these memory blocks, deleting every block promptly.
SBX-92378 / SBX-91682 3

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

Impact: MS Team scenario with ICE causes RTCP port with X when RTP is Y and when mux is supported. 

Root Cause: The SBC was not considering the SDP answer from the peer when setting the RTCP port value.

Steps to Replicate:

  1. SBX routes the INVITE to egress endpoint via egress TG. INVITE should have valid SDP including -

In SDP audio stream -
RTP and RTCP ICE candidates
a=rtcp-mux
a=rtcp: which has port number of audio rtp+1

2. SBX must send 180 and 200 OK to ingress endpoint and include valid SDP for audio stream.

3. Valid ACK received.

4. SBX routes the re-INVITE to egress endpoint via egress TG. re-INVITE should have valid SDP including -
In SDP audio stream -
RTP ICE candidates (no RTCP as egress has already agreed rtcp-mux)
a=rtcp-mux
a=rtcp: which has same port number as audio rtp (as this is not initial offer for this stream and rtcp-mux has already been agreed)

In SDP video stream -
RTP and RTCP ICE candidates (as this is initial offer for the video stream)
a=rtcp-mux
a=rtcp: which has port number of video rtp+1 (as this is initial offer for the video stream)

5. Call signaling completed and then call cleared.

Platform/Feature: SBC

The code is modified to send a=rtcp:<rtp port> when sending re-INVITE messages for streams previously agreed to support muxed behavior.
SBX-91273 1

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

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

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

Steps to Replicate:

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

Platform/Feature: SBC

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

Portfix SBX-91750: Observed a "SamProcess" core dump on an active box while running SIP-GW calls.

Impact: SBX may core if the GW Signaling Port configuration is disabled while the GW Signaling Link is up.

Root Cause: The core is caused by an attempted NULL pointer access.

Steps to Replicate: Disable the GW Signaling Port while the GW Signaling Link is up.

Platform/Feature: SBC

The code is modified to check for a NULL pointer to the GW Signaling Port before attempting to access this pointer.
SBX-923941

Multiple nodes switched over and caused outage.

Impact: Under certain conditions, the SBX sends out a duplicate OPEN_ACK, causing the receiving GW to crash.

Root Cause: Not reproducible.

Steps to Replicate: Steps are not reproducible.

Platform/Feature: SBC

The code is modified to only send out one OPEN_ACK per tcp/ip connection.
 SBX-75611 2

The service instant messages for "Call_Hold" and "Call_Retrieve" are not generated in some GW-GW scenarios.

Impact: When SIP-SBX-GW-GW-GSX-ISUP call is intercepted, if hold/retrieve is received from either side, the SBC is not sending service instant messages to the LI server.

Root Cause: The SBC is not sending service instant messages to the LI server.

Steps to Replicate:

Setup
SIP---GW(SBX)-----GW(GSX)-------ISUP
Description:
When call HOLD comes from called (egress), GSX does not send service instance to the intercept server.

Steps to Verify:
Ensure the setup above is active.
1. Start the LI server
2. Initiate SIP-ISUP call with HOLD from egress
3. Check LI server logs for service instance msg for hold and retrieve.

Platform/Feature: SBC

The code is modified to pass the Hold/Retrieve indications in GW-GW scenarios. Encode the service instant messages for Call_Hold and Call_Retrieve.
SBX-92625 / SBX-877273

Portfix SBX-87727: There was a SNMP-USER-BASED-SM-MIB Namespace Change.

Impact: The EMS cannot configure the SNMP-USER-BASED-SM-MIB through NETCONF.

Root Cause: The SNMP-USER-BASED-SM-MIB is not exposed to NETCONF.

Steps to Replicate: The steps cannot be replicated.

Platform/Feature: SBC

The SNMP-USER-BASED-SM-MIB is exposed to NETCONF for Administrator users.
SBX-926212

The BRM redundancy messages were filling up the DBG logs.

Impact: The BRM redundancy messages were filling up the DBG logs.

Root Cause: The redundancy messages were debug messages to help debug a resource leaking issue. The messages must be moved to lower level.

Steps to Replicate: The steps cannot be replicated.

Platform/Feature: SBC

The related BRM redundancy messages are downgraded to INFO/Minor level.


Resolved Issues in 07.02.02R000 Release 

The following issues are resolved in this release:


Resolved Issues

Issue IDSevProduct DescriptionResolution
SBX-861932

The D-SBC DFE module, which controls connections to the MSBC/TSBC, continues to read memory after being freed.

Platform/Feature: SBC

The code is modified to stop the timer when the gateway control block in DFE is freed so the timer does not expire and try to access the freed memory.
SBX-866841

The SCM Process cores when making a REFER call where more than two SCMs are present in an I-SBC configuration. When the scenario occurs, the SBC does not recognize the N:1 Slot and will not pick the changes.

Platform/Feature: SBC

The code is modified to pick N:1 changes for slot ID.
SBX-864802

The SCM may core due to memory corruption caused by processing Global PCDR Info received from the Policy Server.

Platform/Feature: SBC

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

During the write process to create a new policy status reporting file, the correct read privileges were not present to allow the successful completion of the status reporting session.

As a result, the status reporting process wrongly reported a sync in progress.

Platform/Feature: SBC: Application

The code is fixed to resolve this issue.
SBX-86667 / SBX-864682

Portfix SBX-86468: When the "Registration Expires in Expire Header" flag is enabled in the surrogate registration on Ingress TG IPSP, the de-registration is sent before the registration can refresh, which results in a call failure. (Originated in release 6.2.3F2)

Platform/Feature: SBC

The code is modified to pick up the correct expiration value from response PDU if "Registration Expires in Expire Header" flag is enabled for surrogate registration.
SBX-869991

The SBC added a REFER method in the Allow header when the condIncMethInAllowHdr was enabled, though REFER is set to Reject in TG methods instead of Allow Only.

Platform/Feature: SBC

REFER is set to Allow only if it is not rejected in the TG methods.
SBX-85144 / SBX 726932

PortFix SBX 72693: FPGA failures are observed on DSP cards. (Originated in release 8.0.0)

Platform/Feature: SBC: DSP

A server reboot is initiated to restore communication.
SBX-864933

When the SBC does not find the route information when adding the Max-Forwards header for an incoming call, the SBC rejects the call.

Platform/Feature: SBC

Avoid Max-Forwards header addition while forming the SIP response.
SBX-865231

When the PCRF is enabled, a SCM may core on switchover.

Platform/Feature: SBC

The code is modified to prevent the PCRF related SCM core on a switchover.
SBX-862462

The SBC reads the end of a memory block while processing DTLS signaling. This can result in invalid accessing of memory.

Platform/Feature: SBC


The code is modified to prevent the additional CR and LF (0x0d, 0x0a) characters at the end of an ISUP MIME body.
SBX-688582

The SBC CDR 'GMT' timestamps are skipping forward and backward in some call scenarios.

This issues causes call incorrect start/stop/duration timestamps in the CDRs.

Platform/Feature: SBC: CDR

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

Extra CR, LF (0x0d, 0x0a) characters are added at the end of an ISUP MIME body, immediately before the correct CR, LF is associated with the boundary line.

Platform/Feature: SBC: SIP

The code is modified so that extra CR, LF (0x0d, 0x0a) characters are no longer added at the end of an ISUP MIME body.


SBX-635712

The Active SBC may fail to synchronize ("Call/Registration Data" remains in syncInProgress) after an LSWU upgrade of the Standby SBC when using an IpPeer pathCheck profile.

Platform/Feature: SBC: Application


The RTM process is updated to handle pathCheck messages that may occur during LSWU.


SBX-873402

Transport is not correctly set while the SBC is sending an Authorization request.

Platform/Feature: SBC

The code is modified to set a correct transport type while sending an Authorization request.


SBX-876413
When copying a SIP Adaptor Profile in the EMA using the "Copy SIP Adaptor Profile" option, and the "advancedSMM" flag is enabled on the original SIP Adaptor Profile, the flag is not copied over once the new profile is saved (the flag stays disabled).
Platform/Feature: SBC
The code is modified to copy the flag state to the new profile.
SBX-734242
The CDR field 8 in START and STOP records always shows zero, even if there is a delay in the PSX response.
Platform/Feature: SBC: CDR
The code is modified to correctly calculate the delta for the setup message time and the PSX response time.
SBX-867481

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

Platform/Feature: SBC

Fixed the fragment timeout logic that was decrementing the wrong interface's current in-use count. This problem only impacts the SBC hardware. 
SBX-862392

The CDR connection timeouts greater than 127 seconds are not honored, as the TCP sessions times out after 127 seconds.

Platform/Feature: SBC

Changed the range for the connection timeout to a range of 15 to 120 seconds.
SBX-877081

In the AWS SBC, ssh keys stored in confd database are lost during the upgrade to 07.xx.xx.

Platform/Feature: SBC

The issue is resolved by having the standby undergoing upgrade request the confd.conf keys from the active before proceeding with the upgrade. 
SBX-879442

Blind transfer call fail due to DLRBT. The internal tone flag on leg B was not reset properly, as a result of the leg C fail to the cancel tone. 

Platform/Feature: SBC

Reset the tone flag when B is connected. 
SBX-880031

When the End to End PRACK is enabled and if call fails after sending 18x to Ingress before receiving PRACK or if any PRACK drops happens; there may be a memory leak.

Platform/Feature: SBC: SIP

The issue is resolved by releasing the memory while clearing call details for call failure.
SBX-858942

IPTABLES rules are incorrect on the SWE after an upgrade in the case where non-default addresses were configured for HA ports. If one of the configured HA addresses is the same as the default address, but the other is not, this may prevent the HA peers from communicating.

Platform/Feature: SBC

The code is modified to flush the “iptables” rules before adding the rules for the configured HA addresses.
SBX-879111
This issue occurred as routers respond to ARP probe request sent by the SBC with a GARP request and target MAC in that ARP request is set to a broadcast MAC. The SBC expects the target MAC in ARP response sent by router to contain the MAC address of the SBC port from which request was sent. The SBC was not treating the request as a valid response and resulted in reporting standby links as DOWN.
Platform/Feature: SBC
The issue is fixed by comparing the target IP address received in a ARP response to the destination IP configured in Link Monitor when target MAC comparison fails. In a GARP request/response, the target IP is be set to the IP of the router sending these packets. This change results in considering the GARP request sent by the router as valid response and reports link status correctly.
SBX-880613

When online validation only and both online and offline validation sessId and verId are zero in 200OK, SIPS fail to save the peer SDP.

Platform/Feature: SBC

Change the order of validating profile to ensure it return correctly.
SBX-88168 / SBX-876152

Portfix SBX-87615: After the announcement script is completed, the CC validates this as a multiparty call and transfer script and notifies ingress to connect the call.

Platform/Feature: SBC

After ann script is completed, the CC instructs the ingress to connect the call. 
SBX-87828 / SBX-869302

Portfix SBX-86930: e2e prack is not working if require header is present and no 100rel. (Originated in release 6.2.4)

Platform/Feature: SBC

If 100rel not in require header, it is validated in supported.
SBX-87826 / SBX-860992

Portfix SBX-86099: Minimize the logic suppressing the Update. (Originated in release 6.2.4)

Platform/Feature: SBC

The code is modified to send for the Update regardless of if the Minimize flag is set to ON.
SBX-860803

When multiple DM Nat tables are configured, calls which should have been sent to Direct Media are being media anchored through the SBC.

Platform/Feature: SBC

The code is modified to create the entries correctly.
SBX-87824 / SBX-860683

Portfix SBX-86068: reInvite after an authentication call is missing logic to copy the SMM scope variable data into a new message. (Originated in release 6.2.4)

Platform/Feature: SBC

Copied the SMM scope variable to new message so the SMM can apply the new logic.
SBX-880701

In case a call to sonusPeerUpload.expect is made and if the peer goes down then, there may be a waittime for the SCP connection, resulting in the application healthcheck timing out after 10 seconds, which causes the application to crash.

Platform/Feature: SBC

The SCP used times out in sonusPeerUpload.expect script to ensure that the wait time for the SCP connection to establish is no longer than 2 seconds.
SBX-880361

Because of the Anonymize flag, the host name will get updated with Egress SIP Sig port in an outgoing PAI header. When the Source host name size (SIP Sig IP) is bigger than destination, the host name size (an existing host name in PAI received on INGRESS) issue will appear.

Platform/Feature: SBC

The code is modified to reallocate memory before updating a host name value.
SBX-86920 / SBX-862363

Porfix SBX-86236: The SWe TPAD channel modify code had a bug that had a response sent to a different entity on the host (SWEA instead of DDH) and that resulted in DDH major log event. (Originated in release 8.0.0)

Platform/Feature: SBC: DSP

The code is modified to correct the behavior. 
SBX-886252

Shadow file copy is available to admin user after an upgrade.

Platform/Feature: SBC

The code is modified to remove the pre-upgrade shadow file saved during an upgrade.
SBX-885412

The SBC ignored the ACK and failed to relay it to the INGRESS peer. As a result, after 10 seconds, the OA-FSM timer expired on the egress call leg and the call was torn down. 

Platform/Feature: SBC

The code is modified so that the ACK can be relayed to the other call leg and the call can stay up.
SBX-873253

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

Platform/Feature: SBC

Perform a Defensive check for stEndpointAOR.puchUserName and to set the value to NULL after its freed to avoid double free.
SBX-886102

Possible memory leak when the parameter rewriteIdentities is enabled on a SIP trunk group.

Platform/Feature: SBC

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

When a E2E PRACK is disabled and PRACK is received from the caller with preconditions, the SBC does not relay the precondition changes to the callee.

Platform/Feature: SBC

The SBC sends an UPDATE towards egress to relay the preconditions to the callee.
SBX-881321

NAPT learning is broken if the following events occur:

RTP and RTCP NAPT learning are enabled when call comes up 
No packets are received within 1.5 seconds 
RTCP packet is received 
RTP packet is received 

In this scenario, the source IP address and RTCP port learn from the received RTCP packet, but any subsequent RTP packets (from same source IP address) are not learned. So, the RTP port is never learned.

Platform/Feature: SBC

The code is modified to add a NATL support to learn source IP address from an RTCP packet.
SBX-886522

When an Audio transcode is possible and below the line index is zero, all non-core streams are being removed even when multipleAudioStreamsSupport is enabled.

Platform/Feature: SBC: Media Resource Management

The code is modified by skipping the audio transcode for AUDIO/IMAGE streams under the multipleAudioStreamsSupport flag.
SBX-887152

The SBC was reading the end of a memory block while trying to play an announcement, due to pre-conditions interworking happening on the ingress call leg.

Platform/Feature: SBC

The code is modified to not copy more memory than required to hold the name of the announcement, to avoid reading invalid memory.
SBX-88596 / SBX-853352

Portfix SBX-85335: The SBC replaces custom EMA SSL certificate with a self-signed certificate during an upgrade. (Originated in release 8.1.0).

Platform/Feature: SBC: EMA

While restoring certificates (server certificate and client CA certificate for EMA TLS Profile) from the CDB to the cache, they now restore to /opt/sonus/ema/apache/.
SBX-883861

A second REFER comes in too fast when the previous referer has not completed the teardown. It sets the teardown in an invalid state.

Platform/Feature: SBC

Sending of ACK is delayed until the previous referer tears down. The subsequent REFER is accepted by the SBC.
SBX-885532

The logical implementation for the flag CondIncMethInAllow is incorrect. 

Platform/Feature: SBC

New logic is added to rework the CondIncMethInAllow flag
SBX-883272

Standby logs (/var/log/messages and syslog and user.log) are flooded with CpsShmAttach event log messages.

Platform/Feature: SBC

The standby code is modified to no longer call CpsShmAttach() unnecessarily.
SBX-88755 / SBX-721653

Portfix SBX-72165: The mandatory users (admin, guest, operator) in the SNMP users table are user removable. If removed, the SNMP commands may fail. (Originated in release 6.2.4).

Platform/Feature: SBC: CLI, EMA

Validation is added to ensure the mandatory users admin, guest, and operator are not removable.
SBX-88768 / SBX-885483

Portfix SBX-88548: For a non-SIP to SIP call, the transparency/relay flags are still in effect. (Originated in release 6.2.4)

Platform/Feature: SBC: SIP Applications

The code is modified to disable/ignore all transparency/relay flags for call flows that are not end-to-end SIP calls. 
SBX-883252

If a user enables/disables the audit system (auditd + kernel's audit system), the existing CLI command "set oam eventLog platformAuditLogs state <enabled/disabled>" will be used.

Platform/Feature: SBC

The code is modified to:

  • change the default state of the platformAuditLogs to enabled Stop audit system (auditd + Kernel audit system) for stopping auditd,
  • disable the audit system when platformAuditLogs's state is disabled and persists on restart.
SBX-889252

Software editions of the SBC use uninitialized values during the SmProcess startup.

Platform/Feature: SBC

The code is modified to initialize values on software editions.
SBX-890481

The SBC is not able to send 200OK to the Ingress due to tone playing and a "Send Update SDP in 200OK" flag.

Platform/Feature: SBC

Fixed the logical error so the SBC can send 200OK out.
SBX-892003

e2e PRACK is not working if the required header is present and 100rel is not.

Platform/Feature: SBC

Changed the logic to accommodate if 100rel is not in the required header, it is validated in supported header.
SBX-89320 / SBX-888822

Portfix SBX-88882: A 200 OK INVITE received immediately after a UPDATE/200 OK gets stuck and the call fails. (Originated in release 7.2.1)

Platform/Feature: SBC

The code is modified to avoid using a tone swap when a 200 OK INVITE is received immediately after a UPDATE/200 OK.
SBX-89288 / SBX-882202

Portfix SBX-88220: SBC system configuration: sysctl variables, hardening. (Originated in release 8.1.0)

Platform/Feature: SBC

Implemented security hardening measures to load the Yama security module at startup to block non-child tracing by ptrace.
SBX-886651

NAPT not learning due to a delay in media being received. NAPT is learning for 1sec for a re-INVITE and after the learning, the previously learned address is returned to NRMA (which does not work for end changes).

Platform/Feature: SBC

The code is modified to restart NAPT learning again after a timeout for re-INVITE.
SBX-89284 / SBX-892021

Portfix SBX-89202: When ISUP/QSIG message body is present in the OOD requests, the SCM coredump occurs since the hSipCallHandle will not be present. (Originated in release 8.1.0)

Platform/Feature: SBC

Added a Null check for hSipCallHandle.
SBX-889742
An OOD MESSAGE Request with the same CSeq and different from tag for a challenged request will be rejected with an 482 Loop Detected.
Platform/Feature: SBC
OOD MESSAGE Request with same CSeq and different from tag for a challenged request is processed automatically.
SBX-89336 / SBX-882212

Portfix SBX-88221: High auditd activity is causing disk issues and registration failures on the SWe. (Originated in release 6.2.4)

Platform/Feature: SBC

Added an audit rule to exclude MAC_IPSEC_EVENT messages from being logged by the auditd.
SBX-889891

R-URI userpart is incorrect when the ToHeader Transparency is on and with registration. 

Platform/Feature: SBC

The R-URI is based on contact received from an IAD registered end point.
SBX-893022

Application can fail to start if the name chosen for the SBC ends with "net".

Platform/Feature: SBC

The code is modified to handle the SBC names ending with "net".
SBX-887431

The SCM Process cores when receiving notifications from the PCRF, which does not exist on the Registration Control Block.

Platform/Feature: SBC

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

Portfix SBX-74470: SIP (LM) -> GW call (x-fer on this side) - call is torn down. (Originated in release 6.2.4)

Platform/Feature: SBC: Gw-Gw, Media Resource Management

The code is modified to define a new NRMA state, for conditional assignment of the state, and faking the answer when required, to avoid the timer expiry. 
SBX-89983 / SBX-899813

Portfix SBX-89981: Contact Transparency issue(HTP) for a Late Media Invite is not working as expected when excluded methods are configured. (Originated in release 8.1.0)

Platform/Feature: SBC

Added a fix for calling the parameters SipSgCheckAndSetContactHeaderTrasparency after SipSgCopyTransparencyContent.
SBX-90044 / SBX-759692

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

Platform/Feature: SBC: EMA, Security

The header is edited before sending the response from Apache 2 server.
SBX-866893

A change in the return code for Platform REST API calls for passwords mismatch.

Platform/Feature: SBC

To fix this issue, set the status code to 401 for authentication.
SBX-865862

SIPSG_GET_DMINFO_RPY_MSG is not sent when the DM Info is not sent. The SCM lookup times out after 1 second and the 200 OK is released after 1 second.

Platform/Feature: SBC

SIPSG_GET_DMINFO_RPY_MSG is sent irrespective of whether the DM Info is present or not.
SBX-893772

When the Enhanced Dynamic black list feature is configured for a Receipt of message event type, the ScmProcess leaks memory.

Platform/Feature: SBC

The code is modified to ensure the ScmProcess frees the memory allocated for the ICM Message carrying the Dynamic black list feature data.
SBX-900882

Subscription information is lost on an SBC switchover in a particular direction.

The NOTIFY request is rejected with a 489 Bad Event message after a double switchover.

Platform/Feature: SBC


The code is modified to allow a successful double switchover.
SBX-90128 / SBX-889963

Portfix SBX-88996: As, the single character search is an exhaustive search operation which would in turn consume more time and space , the browser witnesses Timeout Exception due to which the blank screen is rendered to the user. (Originated in release 6.2.4).

Platform/Feature: SBC: EMA

The code is modified to avoid and disallow single character search by rendering an appropriate error message to the user if the input does not match the criteria entered.
SBX-90204 / SBX-901953

Portfix SBX-90195: A transport parameter is transparently sent when the Request-URI transparency is enabled for all messages. (Originated in release 8.1.0).

Platform/Feature: SBC

The code is modified to remove the transport parameter in a request URI when request URI transparency is enabled.
SBX-90042 / SBX-763933

Portfix SBX-76393: The CPX process was timing out when requests were made for specific rows in an interval statistics table, only used to populate the statistics tar file. (Originated in release 6.2.4).

Platform/Feature: SBC: confd

The code is modified to return a request immediately with no data.
SBX-898771

For registration, the 200OK has the service-route, and the flag Stored service route enabled. If the Server sends multiple notifications without a record-route before the Subscribe is stable, the SBC may core due to duplicated freed memory. 

Platform/Feature: SBC

The code is modified to correctly initiate a NULL pointer after the memory is freed.
SBX-88048 / SBX-873211

Portfix SBX-87321: Sip Parser has predefined method length restriction set to 128 and a negative test case in Codenomicon test suite with a method including more than 128 characters is resulting in a coredump. (Originated in release 8.0.0).

Platform/Feature: SBC

Added software checks to enforce upper limit as well as NULL termination

SBX-92225 / SBX-757152

Portfix SBX-75715: The SCM reports a deadlock when multiple set operations are committed. The feature previously worked in earlier releases and does not work in 7.x releases. (Originated in release 8.0.0).

Platform/Feature: SBC: CLI

A check is added in the CPX to limit the maximum number of trunkGroups set per commit to 2 to avoid a SCM process core dump due to a healthcheck timeout.
SBX-881292

Registrations with a syntax error cause an incorrect REG counter.

Platform/Feature: SBC

The code is modified to update the TRM and SIPFE correctly.
SBX-89592 / SBX-892202

Portfix SBX-89220: The 200 OK is not being sent for call HOLD when the sdpAttributeRelay is enabled on the Trunk Group. (Originated in release 8.1.0).

Platform/Feature: SBC

The code is modified to reset the flag SIP_SDP_CTRL_IS_CHANGED_SDP when there is change in the Session Attributes.
SBX-882533

The PSX Name field is not being populated in CDR's.

Platform/Feature: SBC

The code is modified to include the PSX name in the CDRs.
SBX-902501

When "show status addressContext <addressContext_name> ipsec ipsecSaStatistics" and "show status addressContext <addressContext_name> ipsec ipsecSaStatus" commands are run and the IPSec is configured, the IKE Process will leak memory.

Platform/Feature: SBC: IPSec, SIP

The code is modified to ensure buffers are allocated once when generating the IPSec IKE statistics.
SBX-903641

[SMM] The Scm process core dumped while modifying the URI scheme.

Since the stHdrString is not MemZero and when we try to free the memory which is junk, coredump occurs.

Platform/Feature: SBC: Application

The code is modified to add a MemZero to the structures.
SBX-905102

The call setup time under the currentCallStatistics output was not calculated correctly.

Platform/Feature: SBC

The code is modified to simply keep a total of the number of ticks. For example, 100ths of a second for each call.
SBX-899963

In old scenario, using ':' for separation between attribute name and value.

Platform/Feature: SBC

Code was added to read the file properly if instead of ':', the file uses double quotes (") as a separator.
SBX-903931

When the saveCallFlows is enabled, and only Out of Dialog Messages are received, a memory leak occurs.

Platform/Feature: SBC

When the queue of packets exceeds the saveRecentCallFlowsInMemory maxMemoryUsage, the oldest entries are purged.
SBX-901801

When the SIPT library was returning a DISCARD_MSG event to SIPSG while trying to send out a message, it results in the call being released if the MIME disposition was required.

Platform/Feature: SBC

The code is updated to not release the call if the SIPT library returns DISCARD_MSG while sending out a message.
SBX-873421

During the long load run, a few 503 responses are seen from the SBC.

Platform/Feature: SBC

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

Portfix SBX-90379: Pathcheck process currently supports 32 DNS records, whereas the DNS client supports 100 so there was a mismatch and this pathcheck process crash was seen when there are more than 32 records. (Originated in release 8.1.0).

Platform/Feature: SBC

The Maximum records supported in a pathcheck is increased to 100, so that it will be in sync with a DNS client.
SBX-904253

During registration failures, and peer tries to register again, the SIPFE and SIPSG may become out of sync.

Platform/Feature: SBC

SIPS is no longer responsible to answer the re-transmissions and the application directly handles the answer to avoid an out of sync registration.

 
SBX-902312

The SCM may core while processing SIP INVITE headers.

Platform/Feature: SBC

A NULL pointer check is added to avoid a core dump when far end SIP endpoints are not following the standard.
SBX-856751

When invoking an API with an input param, the input params were not getting validated because the validation code was not present for the rest of the API input params.

Platform/Feature: SBC

A new class is added to validate all the API input params to fix this issue.
SBX-864252

The mgmtRedundancyRole is displaying Unknown instead of active/standby.

Platform/Feature: SBC

Make the SmaGetMgmtRedundancyRole() return to redundancyRole instead of rgmRedundancyRole.
SBX-865892

When there are multiple ipInterfaces in different subnets in an ipInterfaceGroup, the sipSigPort address can remain bound to an ipInterface with an unmatching subnet. The sipSigPort address does not move to an ipInterface with the matching subnet when the ipInterface with the matching subnet becomes enabled and in-service.

Platform/Feature: SBC

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

When the packets are logged as part of the SBC Packet Collector for Core Dump Analysis functionality, if there are SMM rules applied to those packets, the packets are not stored after the SMM rules have been applied.

Platform/Feature: SBC

The code is modified to save the packets after SMM rules have been applied.
SBX-856761

The user was able to read any file from the under-privilege REST user through a GET request.

Platform/Feature: SBC

The input sanitation is added to verify the REST call before executing the API.
SBX-76813 / SBX-708083

Portfix SBX-70808: It is not possible to use the EMA "Test SIP Adaptor Profile" or a CLI command "request profiles signaling sipAdaptorProfile getDigits testProfile" to test an SMM rule that manipulates an ISUP MIME body, because these mechanisms only support ASCII characters and the MIME body is binary. (Originated in release 8.0.0).

Platform/Feature: SBC

The CLI command is extended to allow processing of files contained binary MIME bodies. Processing of the inputPduString option and the EMA text screen is changed to only support the ASCII. 
SBX-862772

The packets are captured out of order. Though all packet data is present in memory, the packets are not stored in the proper order.

Platform/Feature: SBC

The code is modified to capture the packets in the correct order.
SBX-868522

/home/log/session directory has a record of the terminal session logs for all the users and the directory is world-writable without being set. 

Platform/Feature: SBC

The code is modified to set sticky bit for /home/log/session directory.
SBX-859972

A user is not able to create a group starting with '.'

Platform/Feature: SBC

The code is modified to not take groups starting with '.' as input, and to delete the groups staring with '.' at the time of the LSWU.
SBX-874473

The OS user linuxadmin was not getting the shortened lockout time of 10 seconds, when the OSAccountAging goes from being disabled to enabled.

Platform/Feature: SBC

The passwd.sh script is updated to correct the incorrect spelling.
SBX-871012

The Packet Loss Threshold is not set properly in the NP, so the NP will report a packet loss incorrectly.

Platform/Feature: SBC

Extract the pktLossThreshold setting from a proper location in the enable media API in the SWeNP code.
SBX-859883

When the To header transparency and call route by TN is on, the R-URI is uncorrected.

Platform/Feature: SBC

The code is modified to not treat R-URI as transparent.
SBX-874611

When the DRM (Application) is not receiving the response from the UXPAD for the health check messages, the DRM sends SIGABRT signal to the unresponsive UXPAD (using the UXPAD process number) to generate a coredump. 

Platform/Feature: SBC

Search for the exact match while the admin retrieves the PID of the Process.
SBX-858072

Privilege Escalation by www-data on the SBC (Runtime Diagnostics Test).

Platform/Feature: SBC

Updated the permission and ownership of /opt/sonus/sbx/diags/runDiagField.sh from the (-rwxr--r-- 1 sonusadmin sonus) to (-r-xr----- 1 root sonus) through the updateOwnerAndPermissions.sh.
SBX-874522

When the configuration for the connected realm (Address Context > Realm > Connected Realm) is created and the realm name used already exists, the code was reading off the end of a memory buffer.

Platform/Feature: SBC

The code is updated to use a string copy instead of a memory copy functions to avoid reading off the end of the memory buffer.
SBX-871401

First, a DNS query was getting initiated through the mgmt even if the IP was configured. The Patchchk process core dumps when the truncated DNS response is received from DNS server.

Platform/Feature: SBC

The Static route for the IP interface to the DNS server is provided, which solves the problem of the DNS query not going through the IP interface. 
SBX-878622

The SecureNAT does not learn the remote IP address.

Platform/Feature: SBC

The prefix match result of the received srcIP against the programmed srcIP is in Big Endian format, so it needed to be byte-swapped to Little Endian format.
SBX-881682

SIPS/SIPSG: The 200 Ok (connect) is not sent to the ingress, and ACK is not sent to the egress, when a call is handled using a custom call script.

After the announcement script run is completed, the CC confuses the script as a multiparty call transfer script and not telling the ingress to connect the call (send 200OK).

Platform/Feature: SBC

The code is modifed to allow the CC to inform the ingress to connect the call after the custom call script completes.
SBX-87527

The SBC allowed a user to use the same IP address for a route next hop that caused a loss of traffic to all off-net peers across the SBC interface.

Platform/Feature: SBC

The code is modified to validate that static route's next top IP address is not same as IP interface's altMediaIpAddress.
SBX-851322

For sRTP call, the SBC does not reset the ROC while doing an sRTP encryption, even if the SSRC changes. This may cause the remote decryption operation to fail on some 3rd party equipment.

Platform/Feature: SBC

The code is modified to remember the SSRC from the last RTP packet, and comparing it with the SSRC of current RTP packet before sRTP encryption is applied. If a change is detected, the ROC is reset to 0 before sRTP encryption is applied.
SBX-881972

An internal module's passphrase generation method was not strong.

Platform/Feature: SBC

The code is modified to use a stronger method.
SBX-888352

The SBC, while trying to create DM NAPT table (after retrieving the details from the Database), was trying to read the end of a memory block for some of the parameters in the table (such as table name, etc).

Platform/Feature: SBC

The code is modified to not copy more memory than required, to hold the table name of the DM NAPT table to then avoid reading invalid memory.
SBX-86712 / SBX-759432

Portfix SBX-75943: When an video+audio directmedia call with m=audio after m=video in the SDP is made (audio becomes the last stream), the LIF bandwidth is allocated though it is a DM call.(Originated in release 8.0.0).

Platform/Feature: SBC

A loop is added to save the streamId of the last non-audio stream. The code is modified to check if the audio is the last stream to be a part of this. An additional check is added to reset the session BW to 0 for the last non-audio stream for a direct media call, if the audio is found to be the last stream. 
SBX-89773 / SBX-890892

Portfix SBX-89089: If a name change operation is performed to swap any of the two system names (CE name or peer CE name), the SBC application may fail to start. (Originated in release 8.1.0).

Platform/Feature: SBC

The name change operation is enhanced to reject any name change operation that involves swapping any of the two system names (CE name or peer CE name).
SBX-864861

The I-SBC does not span across multiple vNUMA nodes, causing a SWe_NP failure to launch.

Platform/Feature: SBC

The SWe SBC software is updated to enforce I-SBC instances to run only with single vNUMA node in order to achieve deterministic performance.


SBX-89996 / SBX-895863

Portfix SBX-89586: Loading the TEAMS Template token from the EMA is not working. The Token load option does not load values into the template. No action is triggered even after clicking the Token load. (Originated in release 8.1.0).

Platform/Feature: SBC

Updated the code to successfully load the token and display the value corresponding to the attributes.
SBX-901573

The radiusSharedSecret may appear in plain text in the logs.

Platform/Feature: SBC

The code printing the plain text passphrase is removed.
SBX-90515 / SBX-902893

Portfix SBX-90289: The SBC cored after swapping a name (CE and System) and performing a clearDb action. (Originated in release 8.1.0).

Platform/Feature: SBC

The code is modified to compare all system names against each other before accepting a name change, and then generate a warning, when applicable.
SBX-904153

Currently, all filters are not displayed for tables such as Call Detail Status, Call Media Status, and Call Resource Detail Status.

Platform/Feature: SBC

The code is modified to display filters for all columns in the tables.
SBX-903231

In case of SUBSCRIBE Relay refresh, the the R-URI must be based on the last Contact received if the first route set has the lr parameter.

Platform/Feature: SBC

The logic is changed based on the RFC3261.
SBX-90789 / SBX-900854

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

Platform/Feature: SBC

The code is modified so the user can filter the called number data in CDR Viewer table, with numbers and few special characters such as #, *, +, -

SBX-883192

When history info header is received and International Nature of Address (NOA) Plus flag is enabled, the NOA printed in CDR log is incorrect. The NOA for the original called and redirecting number must be set to International.

Platform/Feature: SBC

The code is modified to check International NOA Plus flag before setting NOA for the original and redirecting number when the history info header is received.
SBX-903082

When LRBT is enabled for an ICE call and egress, the endpoint responds to initial INVITE with an 183 progress message with the SDP parameters followed by an 180 without the SDP and a 200 OK with the SDP. Following the local ring back tone, the SBC initiates re-INVITE to the egress endpoint that is missing ICE ufrag, password and RTCP candidate line in the SDP.

Platform/Feature: SBC

The software is modified to not clear the ICE information in this scenario.
SBX-858203

CDR records are broken into multiple syslog messages.

Platform/Feature: SBC

The code is modified to transfer a complete CDR as one syslog message.
SBX-907622

During SMM testing, the code for handling message scope variables could read off the end of a memory block while printing a debug statement.

Platform/Feature: SBC

The specific debug log line is deleted because there was a second debug line that is already printing from null terminated string.
SBX-901232

If a domain license is installed on the head end node, but the license is pushed out to another node more than an hour later, the push of the license is not successful.

Platform/Feature: SBC

The code is modified to allow the push of the domain licenses to other nodes, if it has been successfully installed on another node of the cluster before.
SBX-905102

The call setup time under the currentCallStatistics output was not calculated correctly.

Platform/Feature: SBC

The code is modified to keep a total of the number of ticks. (i.e. 100th's of a second for each call).
SBX-851362

Software Update fails if an snmp trapTarget with a name containing white-space characters is configured.

Platform/Feature: SBC

The LSWU code is modified to deal with trapTarget names containing whitespace.
SBX-900613

The function SipSgContinueCallProcessing() acquires pstCall using SipCallFromHandleAndLockCCBCmd() and after use, the function was not releasing pstCall, causing memory leaks.

Platform/Feature: SBC

The code is modified to release pstCall using SipUnLockAndReleaseCCBCmd() after a use.
SBX-914643

When the HA peer is upgraded, the upgrade screen shows an error pop up with "Internal Operation error session_start" content.

Platform/Feature: SBC

The code is modified to check to create cnxipm directory.
SBX-734512

SNMP v3 doesn't work after the upgrade/restore.

Platform/Feature: SBC: confd, Install/Upgrade Platform

The upgrade/restore version is applied after the SBX starts from the incoming configuration database.
SBX-914041

There is One way audio after call transfer is made on the SWe when Ring Back is enabled with SRTP towards the MS TEAM to relay it back to PSTN behind the SBC.

Platform/Feature: SBC

With these session modification flows, the NP code is modified to retain the enc contexts required for re-enabling so the endpoint can start accepting media.
SBX-913332

An Application on active may crash when the HA connection is frequently bouncing.

Platform/Feature: SBC

The SCP operation is completed in the background thread to ensure there is no timeout on the health check.
SBX-912242

The SBC is using the surrogate Registration hostPart as the target FQDN.

Platform/Feature: SBC

The code is modified to not over-write egress IpPeer fqdn(target route) with the surrogate hostPart.
SBX-91322 / SBX-894913

Portfix SBX-89491: If a split-brain occurs prior to the standby being up and being fully synced, selecting the former standby as the leader when coming out of a split-brain will result in a complete outage. (Originated in 8.1.0)

 Platform/Feature: SBC

The enhanced GR-HA leadership algorithm is updated to take the standby's sync state into account when deciding if the former standby is to be the post split-brain leader.
SBX-908972

The template form on the Configuration Script and Template Import page is not getting displayed due to some failure.

Platform/Feature: SBC

The code is modified to display the Configuration template form properly when a Configuration is chosen from the table. The Configurations list table is always displayed first when 'Create Configuration from Template' is clicked.
SBX-912262

Unable to upload configuration in the SBC in the Provision Management.

Platform/Feature: SBC

The code is modified to create export directory to store the configuration file.
SBX-911453

DSP card present status is not updated if the card is administratively disabled.

Platform/Feature: SBC

The code is modified to monitor the DSP card presence status every 10 seconds, irrespective of the card being disabled or enabled.
SBX-905812

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

Platform/Feature: SBC

The code is modified to correctly cope when a large volumes of pcap files are present.
SBX-911312

Serialization errors are logged in the SYS log for type 137603, which points to CPC_OP_TYPE_AC_ZONE_INFO, that in-turn caused the coredump.

Platform/Feature: SBC

The registration issue for CPC_OP_TYPE_AC_ZONE_INFO (137603) is fixed.
SBX-903882

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

Platform/Feature: SBC: Application, confd

Updated the NRS packet LIF status request processing routine to retrieve address context ID from a local cache instead of calling out to the CONFD.
SBX-90837 / SBX-899572

Portfix SBX-89957: In TR87 service (CSTA) call flow, INVITE transaction in SIP stack on ingress is not killed, the timer G expires and continues re-sending 200 OK to ingress. (Originated in release 6.2.4)

Platform/Feature: SBC

The code is modified to terminate the INVITE transaction on the receiving end of ACK.
SBX-91048 / SBX-908463

Portfix SBX-90846: Memory leak due to the use of the delete operator. (Originated in release 8.1.0).

Platform/Feature: SBC

Delete operator is used to deallocate the memory allocated via strdup() and is replaced by the delete operator with the free().
SBX-91779 / SBX-915942

Portfix SBX-91594: When SBC-7000 is under high call load with RTCP termination and unstable traffic (reaching 10Gb traffic instantaneously), the Network Processors cores stall. Media traffic stops and PRS coredump is generated. (Originated in release 6.2.4).

Platform/Feature: SBC: Firmware

Configure the work scheduler module so that UPF, DPF, UPP, DPP cores are guaranteed to have work occupy the in-unit work entry.
SBX-908752

A bug in GW Signaling code can cause a core when the GW Signaling Links are bouncing.

Platform/Feature: SBC

The GW Signaling code is modified to prevent a core .
SBX-909791

Apache server is not running.

Platform/Feature: SBC: Platform

Apache server app is rebuilt with the required library.
SBX-740333

When a logicalMgmtIpInterface is configured, and the useIpAddrAsSnmpSource is set to true. The source for snmp traps are the specified address in the logicalMgmtIpInterface ipAddress field. However, the source of the traps is not the correct address, and instead the address is of one of the management IP ports.

Platform/Feature: SBC: confd, Management, Platform

The flag snmpListenOnlyOnThisInterface is added to the logicalMgmtIpInterface configuration. The default value for this flag is set to false. When the flag is set to true, the confd daemon only listens on the address specified in the logicalMgmtIpInterface with useIpAddrAsSnmpSource set.
SBX-903661

AppContextId within NRMA_CALL_PTR is not being synced to standby after a switchover. As a result, Wile bridging calls NRMA identifies the Id as zero and crashes.

Platform/Feature: SBC

The code is modified to syncing AppContextId to standby.
SBX-908762

Gencom client sends a 481 for call park retrieval INVITE. When an incorrect tag in Replaces header, it is sent through the SBC.

Platform/Feature: SBC

The code is modified to merge an issue and egress lookup using the correct tags.
SBX-917383

If the LinkDetection interfaces are configured to use addresses specified in the systemMetaVariable dynamic table, those addresses are not properly read and LinkDetection is not activated.

Platform/Feature: SBC

The code is modified to properly read the addresses from the metaVariableDynamic table.
SBX-874411

The Broadsoft AS returns the 403 for a REFER Request due to From and To tags are swapped.

Platform/Feature: SBC

The SBC application code is modified to correctly populate the From tag and To tag values in outgoing REFER's replaces header section.
SBX-904422

ARM calculates the amount of memory that needs to be freed from the NP (Y has a multiple of certain number of fixed sized PNPS_ANN buffers) to fit in a new announcement the size of a WavFile_X. Due to design size, Y is not equal to size of WavFile_X.

Platform/Feature: SBC

The code is modified (Y is modified to Y') so that new announcements are added properly.
SBX-858581

The ACL rules in a non-default address context were not getting added back to the NP after a sbxrestart/reboot. Without this fix, the ACL rules configured in non-default address context do not work.

Platform/Feature: SBC

The code is modified to iterate the rules list in a correct fashion.
SBX-883381
The Policy Data is showing a sync in progress.
Platform/Feature: SBC
Stop the logrotate to remove this file.
SBX-91054 / SBX-887661

Portfix SBX-88766: The improper value for RFactor was displayed under the CLI command: trunkGroupQoeStatus. (Originated in release 7.2.1)

Platform/Feature: SBC

The wrong context was fetched to calculate the RFactor value. The code is modified for the RFactor calculation.
SBX-911861

In the case of status commands executed from the CLI, a request is sent to both active and standby nodes. An LVM running on active and standby nodes compares the CE name configured in the LDG with a server name and returns stats only for LDGs that are configured on that CE. However, there is no similar check in the case of a PF stat. Without the check for a PF stat,the statistics displayed for LDGs configured on standby node was not correct.

Platform/Feature: SBC

The code is modified to compare the CE name and return stats associated with the LDGs configured on the respective nodes.
SBX-914052

The cluster configuration for saveConfigStoreFile fails on the head end node due to a change of permission by keyKeeper.py. The sbcRegistration was not readable by the admin as a result of the configuration failure.

Platform/Feature: SBC

The code is modified and the admin is able to read the sbcRegistration.
SBX-911861

Failure stats are not being printed in the SBC stats file while it is showing in "show table addressContext default linkDetectionGroupStatistics". The LDGs are configured on both active and standby nodes. An LVM running on active and standby nodes compares the CE name configured in the LDG with server name, and returns stats only for the LDGs that are configured on that CE. However, there is not a similar check in case of PF stat. In response, the statistics displayed for the LDGs configured on standby node are not correct.

Platform/Feature: SBC

The code is modified to compare the CE name and return stats associated with the LDGs configured on the respective nodes.

SBX-911141

The SRTP enables calls in the SWe SBC and causes the NP_Work_2 to sporadically crash and core.

Platform/Feature: SBC

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

The SBC was not sending the ACK to the 200OK for an INVITE after the 4th switchover.

Platform/Feature: SBC

The syncing is done in all states for transferred calls to remove the issue.
SBX-89581 / SBX-870532

Portfix SBX-87053: The SBC fails to apply an ARS procedure on collecting a 503, with or without a Retry-After header when the FQDN is configured on the IP Peer. (Originated in release 8.0.0).

Platform/Feature: SBC

The code is modified to have the DNS resolved IP address on collecting a 503 when the FQDN configured in the IP peer.
SBX-890392

The System Diagnostics throws an error in Custom-> View Custom Perspectives through the xpath, which is incorrect.

Platform/Feature: SBC

The code is modified to point to the correct xpath.
SBX-889944

The status of the Routing Label Route in a table shows as out of service, even if it is In service when created. The out of service status shows when the code picks the wrong data for validating the status.

Platform/Feature: SBC

The code is modified to adjust the Routing Label Route Status, which was shown as Out of Service.
SBX-88860 / SBX-859022

Portfix SBX-85902: Whenever there is any SMM rule for a SDP body, the SMM will remove all linear white space before and after the “=” character from each SDP line.The removal of the white space before and after the "=" character results in a SIP parse error when valid lines "s= " or "l= ". (Originated in release 8.1.0).

Platform/Feature: SBC

The code is modified not to remove any spaces for an S and I Line when using the SMM.
SBX-887163

Remove the plainText EMS Passwords from the userData/MetaData files in cloud. EMS plain text password cannot be present in the SBC, it must be replaced with hashes.

Platform/Feature: SBC

The plain text password of EMS is replaced with encrypted passwords.
SBX-878832

A call is torn down if the SendOnlyPreferred enabled.

Platform/Feature: SBC

The code is modified to correctly set the receive and transmit payload type for the ULAW and ALAW. The ULAW and ALAW does not use an asymmetric payload type and is used for adding the logic.
SBX-88454 / SBX-872422

Portfix SBX-87242: When the DNS packets are received over a TCP, during the failure case (primarily when the length is less than 0 after a reading from the socket), there is no validation of the DNS TCB (Transaction Control Block) pointer while processing. (Originated in release 8.1.0).

Platform/Feature: SBC

A defensive check (to validate if the TCB pointer is NULL or not) is added before processing a connection failure.
SBX-757371

The Nessus scan found multiple vulnerabilities (1 critical, 3 high, 2 medium).

Platform/Feature: SBC: Application

The code is modified to upgrade the vulnerable packages.
SBX-87367 / SBX-871822

Portfix SBX-87182: There is an error while importing a perspective having " - " in the perspective name. (Originated in release 6.2.4).

Platform/Feature: SBC

The code is modified to implement the logic to verify and ensure that only valid characters are present in the file names.
SBX-87171 / SBX-865933

Portfix SBX-86593: An EMA Template fails to import the Config when Special Characters are present. (Originated in release 6.2.4).

Platform/Feature: SBC

The logic to escape HTML Characters is removed in the TemplateConfigServlet.java file.


Known Issues

Known Issues in 07.02.02R003 to 07.02.02R000

There are no known issues in this release.

Known Issues in 07.02.01R002 

The following issue exists in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-877402

LI call not working when standby MSBC is upgraded.

Platform/Feature: SBC

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

Workaround: No workaround available.

Known Issues in 07.02.01F001 and 07.02.1F002 Releases

There are no known issues in these releases.

Known Issues in 07.02.01R001 Release 

The following issue exists in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-880031

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

Platform/Feature: SBC

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

Workaround: No workaround available.

Known Issues in 07.02.01R000 Release 

The following issues exist in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-85825 2

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

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

Platform/Feature: SBC Core: EMA

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

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

SBX-863542

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

Platform/Feature: SBC Core: EMA

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

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

SBX-852282

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

Platform/Feature: SBC Cloud

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

Workaround: No workaround available.

Known Issues in 07.02.00R002 Release 

The following issues exist in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-850713

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

Platform/Feature: SBC

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

Workaround: Increase the maxPduSizeValue to 15k.

SBX-770542

An LSWU Upgrade from 7.0 to 7.1 failed.

Platform/Feature: SBC 5000/7000 Series: Application

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

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

SBX-86003

1

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

Platform/Feature: SBC Core: SIP Application

Impact: The peer may reject the call.

Workaround: No workaround available.

SBX-860942

Call fail after onhold and offhold.

Platform/Feature: SBC Core: SIP Application


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

Workaround: Enable E2E Update.


SBX-858592

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

Platform/Feature: SBC: DSBC

Impact: The SCM process may core dump.

Workaround: No workaround available.



Known Issues in 07.02.00R001 Release 

The following issues exist in this release:


Known Issues

Issue IDSevProblem DescriptionImpact/Workaround
SBX-760662

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

Platform/Feature: SBC CE: Application

Impact:

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

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

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

SBX-850713

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

Platform/Feature: SBC

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

Workaround: Increase the maxPduSizeValue to 15k.

SBX-770542

An LSWU Upgrade from 7.0 to 7.1 failed.

Platform/Feature: SBC 5000/7000 Series: Application

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

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


Known Issues in 07.02.00R000 Release

The following issues exist in this release:


Known Issues

Issue ID

Sev

Problem Description

Impact/Workaround

SBX-74179


1

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

Platform/Feature: SBC CE: Application, Platform

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

Workaround:

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

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

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

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

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

SBX-73218


 1

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

Platform/Feature: SBC CE: Application

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

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

SBX-73943


2

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

Platform/Feature: SBC Core: Application

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

Workaround: No workaround available.

SBX-74945

 4

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

Platform/Feature: SBC Core: CLI

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

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

SBX-73660


 2

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

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

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

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

SBX-725132

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

Platform/Feature: SBC SWe: SIP-Peering

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

Workaround: No workaround available.

SBX-713032

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

Platform/Feature: SBC CE: Application

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

Workaround: No workaround available.

SBX-727362

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

Platform/Feature: SBC 5000/7000 Series: SIP

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

Workaround: No workaround available.

SBX-72652


2

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

Platform/Feature: SBC CE: Application

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

Workaround: No workaround available.

SBX-745462

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

Platform/Feature: SBC CE: Application

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

Example:

Before updating sipSigPort with new dynamic metaVariable:

admin@vsbc1% show global servers lwresdProfile

lwresdProfile DEFAULT {

    description          DEFAULT;

    enumDomainNameLabel  DEFAULT_ZONE_LABEL;

    enableLwresdLog      disable;

    type                 signalingIp;

    addressContext       default;

    eDnsGlobalBufferSize 4096;

    eDnsMonitorInterval  120;

    zone                 ZONE_ING_V6;

    sipSigPort           3;

    ipInterfaceGroupName LIG_ING_V6;

}

admin@vsbc1% show addressContext default zone ZONE_ING_V6 sipSigPort

sipSigPort 3 {

    ipInterfaceGroupName      LIG_ING_V6;

    portNumber                5060;

    mode                      inService;

    state                     enabled;

    transportProtocolsAllowed sip-udp,sip-tcp;

    ipVarV6                   IF2.IPV6;

}

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

COMMAND     PID       USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME

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

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

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

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

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

After updating sipSigport to new dynamic metaVariable:

admin@vsbc1> show table system metaVariableDynamic

CE NAME              NAME     VALUE                 

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

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

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

admin@vsbc1% show addressContext default zone ZONE_ING_V6 sipSigPort

sipSigPort 3 {

    ipInterfaceGroupName      LIG_ING_V6;

    portNumber                5060;

    mode                      inService;

    state                     enabled;

    transportProtocolsAllowed sip-udp,sip-tcp;

    ipVarV6                   lpl_ing;

}

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

COMMAND     PID       USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME

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

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

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

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

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


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

Example:

Don't update the sipSigport to new metaVariable

admin@vsbc1% show addressContext default zone ZONE_ING_V6 sipSigPort

sipsigPort 3 {

    ipInterfaceGroupName      LIG_ING_V6;

    portNumber                5060;

    mode                      inService;

    state                     enabled;

    transportProtocolsAllowed sip-udp,sip-tcp

    ipVarV6                   IF2.IPV6;

}

SBX-756092

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

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

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

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

SBX-742692

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

Platform/Feature: SBC CE: Application

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

Example:

Before updating ipInterfaceGroup with dynamic metaVariable:

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

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

admin@vsbc1% show addressContext default ipInterfaceGroup LIG_ING_V6

ipInterface PKT_ING_V6 {

    ceName      SSBCACTIVE;

    portName    pkt0;

    mode        inService;

    state       enabled;

    ipVarV6     IF2.IPV6;

    prefixVarV6 IF2.PrefixV6;

    vlanTagVar  IF2.VlanId;

}

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

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

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

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

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

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

          collisions:0 txqueuelen:0

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

Creating dynamic metaVariable:

admin@vsbc1> show table system metaVariableDynamic

CE NAME              NAME  VALUE                 

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

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

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

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

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

admin@vsbc1% show addressContext default ipInterfaceGroup LIG_ING_V6

ipInterface PKT_ING_V6 {

    ceName      SSBCACTIVE;

    portName    pkt0;

    mode        inService;

    state       enabled;

    ipVarV6     lpl;

    prefixVarV6 IF2.PrefixV6;

    vlanTagVar  IF2.VlanId;

}

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

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

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

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

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

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

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

          collisions:0 txqueuelen:0

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


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

Example:

Delete the interface group:

 delete addressContext default ipInterfaceGroup LIG_ING_V6

Create interface group with new dynamic metaVariable:

admin@vsbc1% show addressContext default ipInterfaceGroup LIG_ING_V6

ipInterface PKT_ING_V6 {

    ceName      SSBCACTIVE;

    portName    pkt0;

    mode        inService;

    state       enabled;

    ipVarV6     lpl;

    prefixVarV6 IF2.PrefixV6;

    vlanTagVar  IF2.VlanId;

}

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

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

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

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

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

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

          collisions:0 txqueuelen:0

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

 Note: Similar procedure for IPV4.

SBX-758473

The RTCP port is not transparently passed in Direct Media.

Platform/Feature: SBC Core: Application

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

Workaround: Disable RTCP flag on Egress PSP.

set profiles media packetServiceProfile PSP_DM_DTLS rtcpOptions rtcp disabled


Known Limitations

The following limitations exist in this release:

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

  • The Access Control List (ACL) is not installed to configure SNMP traps for accepting traffic. A dynamic ACL is added to configure SNMP traps. An ACL must be installed for SNMP traps for accepting traffic.
  • 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 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 Ribbon Support immediately.

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

Performing Heat Stack Update when userdata is Updated with SSH Keys

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

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

Restricted Functionality with SBC

The following functionalities are not supported with SBC Microservices:

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

  • H323 support
  • GW signaling support

Network Licensing Limitations

After switchover during grace period, when the new standby SBC comes up and establishes itself as standby, there is a short period (a few minutes) when the standby is synchronized for normal operation, but the new standby has not yet completed establishing its licensing state using the grace license information. If there is a second SBC switchover during that window, the new active SBC (which became active before completing license state synchronization) 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.