Skip to end of metadata
Go to start of metadata

Table of Contents

About SBC Release Notes

This document describes new features, the latest hardware and software requirements, known limitations and other pertinent release information for the latest release of 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 (

Related Documentation

The SBC Core 07.01.xx documentation is located at the following Wiki space: SBC Core 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: LSWU for SBC SWe (running on VMWare or KVM) with greater than 10 vCPUs
  • Warning-18-00028165: SBC 5110 uses wrong encryption key intermittently SRTP
  • Warning-17-00022847: The DNS configuration parameters within the address contexts may cause certain configurations to fail during an upgrade to the SBC 6.2.0
  • Warning-17-00022689: Duplicate Trunk Group or Zone names can cause unexpected behavior
  • Warning-14-00020748: Verify system and databases are fully in sync prior to Live Software Upgrade (LSWU)

To view/download Ribbon bulletins, do the following:

  1. Log on to the Support Portal (
  2. Click Bulletins link from the menu bar. 
  3. Enter the bulletin number (last eight numbers) in the search field and press Return.

Problems or Questions

For problems or questions, contact Ribbon Support through telephone or fax: 

Worldwide Voice: 1 (978) 614-8589

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

Worldwide Fax: 1 (978) 614-8609

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.


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


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.


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

Compatibility with Ribbon Products


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


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

Refer to SBC 5000-7000-SWe Interoperability Matrices for the latest and minimum compatible product versions supporting the 07.01.00R000 (build 8) release.


SBC SWe Cloud Requirements for GCP

  • GCP SBC Swe requires a 4 VCPU instance profile with 15GiB memory.
  • GCP SBC Swe recommends an Intel Broadwell or later CPU.

Required Software and Firmware Versions

The following SBC 5000 series (51x0/52x0), SBC 5400 and SBC 7000 software and firmware versions are required for this release:

Table : Required Software and Firmware Versions




SBC Application



Operating System (OS) Version



SBC Application


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.

Upgrade Notes



Release 7.1 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.


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


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


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

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


The AWS version is currently available on an R7.0 branch. Customers should use the R7.0 branch or contact their local sales representative if they have a use case for AWS.


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.

07.01.00R000 (build 8) Upgrade Information


Prior to performing an upgrade to release 07.01.00R000 (build 8), usernames that do not conform to 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 user names consisting of digits only or not conforming to new user naming rules will be removed after performing a restore config in release 6.2.1R001. 


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

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


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

If you are upgrading from any SBC version with ePSX configuration to the 07.01.00R000 (build 8) release, execute the Method of Procedure, MOP to Re-configure SBC (with ePSX) to External PSX Prior to an Upgrade to 06.00.00R000 Release prior to performing an upgrade. For a list of supported LSWU paths, refer to Supported Upgrade Paths.

Support of maddr Post-Upgrade

When upgrading SBC Core to release 5.0.0 (and above) from a pre-4.2.4 release, 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 SBC is configured for registration access (where SBC sits between SIP phones and the Broadworks System. Otherwise, no new REGISTER is 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. Default is ‘disabled’.

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

See the following pages for configuration details:

New Features

New Features in 07.01.00R000 (Build 8) Release

SBX-74089 Support for Standalone SBX on GCP for PoC 

For information on support for a standalone SBC on GCP, refer to SBX-74089 POC MOP - Support for Standalone SBC on GCP (build 8).

Resolved Issues

Resolved Issues in 07.01.00R000 (Build 8) Release

There are no resolved issues in this release.

Resolved Issues in 07.01.00R000 Release 

The following issues are resolved in this release:

Table : Resolved Issues

Issue ID Sev Problem Description Resolution



SBC SWe/CE does not report when a call's Packet Loss exceeds the PktLossThreshold. This causes the PacketLoss to not be reported in the CDR, and to not generate a trap (if configured). 

Platform/Feature: SBC SWe, CE: Application

Missing code on the SWe platform that calculates and stores a semi-running value for the loss_rate (every 512 packets) was added.


SBX-51872 3

The generated MIB does not include segmentStatus or other statuses related to announcements.

Platform/Feature: SBC Core: confd

SNMP MIBS are loaded on SBX.
SBX-60238 2

Upgrade from 5.0F3 to 5.1.1R1 failed.

Platform/Feature: SBC 5000/7000 Series: LSWU

The active server core is addressed by SBX-62170, and the standby server issue is addressed by checking the local server state once the pre-installation checks complete or if the upgrade is aborted.

SBX-61949 / SBX-61938 / SBX-70920 2

11% per core performance degradation was observed between VMs that have less than 8 media cores or greater than 8 media cores.

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

Code was added to improve the estimation of transcoding.


SBX-66329 2

GPUStatus command does not display the health information of GPU.

Platform/Feature: SBC CE: Application, Documentation, Platform IP/Media Services

Changes were made regarding how the GPU statistics are displayed. With these changes, the telemetry data of GPU devices associated with the SBC instances can be viewed from the CLI command "show table system gpuStatus".


SBX-67534 2

ICMP port unreachable floods ICMP policer. ICMPV4 and ICMPV6 fill rate need to be increased.

Platform/Feature: SBC Core: Common Sonus Platform Services

The fill rate was increased from 50 to 350 packets per second.


SBX-67818 3

The First Call Setup Panel is displayed in the EMA Dashboard even after user completes the First Call Setup.

Platform/Feature: SBC Core: EMA

Code was added to check the status of First Call Setup completion. If found completed, then the "Getting Started with the SBC" panel will be hidden and this check will not run again. The user can enable it again in "dashboard settings".

SBX-68185 2

If the SBC received an error response after receiving a NOTIFY for an SBC initiated SUBSCRIPTION, the SBC was forwarding this to the application and trying to access a deleted subscription.

Platform/Feature: SBC 5000/7000 Series: Application

The code was modified so that the SBC does not forward to the application or try to access a deleted subscription.
SBX-68655 / SBX-68090 2

PortFix SBX-68090: A one-way audio call ensues when the SBC selects a local UDP port or 4500 for a media call. 

Platform/Feature: SBC Core: Platform

XRM was changed to not put UDP port 4500 (decimal) into the list of available media ports per local IP address. The default SIP signaling port and port 4500 are now avoided for media calls.
SBX-68785 2

Two active calls attempt to use the same bresId.

Platform/Feature: SBC Core: Media Resource Management, Platform

BRM standby support was improved to handle cases where RTM does not deallocate BRES resources on standby, and race condition where RTM delays deallocation of BRES resources on standby.
SBX-69005 / SBX-67665 2

PortFix SBX-67665: The PRS process leaks memory when the IPSEC feature is in use. 

Platform/Feature: SBC SWe: SIP Applications

The IPSEC code was modified to free the memory and prevent this leak.


SBX-69098 2

Nrma Deallocated BRES as it does not have Ingress NSD, thereby resulting in BRM IP Header Modify failure while updating port in the second 18x.

Platform/Feature: SBC Core: Media Resource Management, SIP

A dummy NSD was created in case of late media convert cases.


SBX-69187 / SBX-68976 2

PortFix SBX-68976: When only testPSX is configured, DS clients were not registering with DS and diamversion was not updated. Due to this, SBX is not able to send PSX query to testPSX.

Platform/Feature: SBC Core: Call Control

The code was modified so that when only the test PSX is configured, DS clients are getting registered and SBX is able to send PSX query to test PSX.
SBX-69239 / SBX-66869 2

PortFix SBX-66869: The Radius authentication feature resulted in exhaustion of thread resources in SWe_NP, causing external authentication requests to fail, forcing the external authentication through Radius server feature to go into a non-working state.

Platform/Feature: SBC SWe: Application

The thread resources on subroutine completion in SWe_NP were released, bringing the external authentication through Radius server back to a working state.

SBX-69407 / SBX-64576 2

PortFix SBX-64756: There was a core on a node of a geo-redundant HA system to trigger an unexpected switchover.

Platform/Feature: SBC 5000/7000 Series: Application, Redundancy

Code was added to support additional calls to the leader election after the the service is restarted.

SBX-69547 2

When the contact header in the incoming SUBSCRIBE/REGISTER does not have a username, the SBC was not including TGRP parameters in the outgoing SUBSCRIBE/REGISTER. 

Platform/Feature: SBC 7000 Series: Application

The code was modified to send TGRP parameters in the outgoing SUBSCRIBE/REGISTER even when the username is not present in the contact header of the incoming SUBSCRIBE/REGISTER.
SBX-69559 / SBX-69252 2

PortFix SBX-69252: ScmP cored when create path header was enabled in egress PSP.

Platform/Feature: SBC 7000 Series: Application

The code was modified so the logging function does not corrupt the stack.

SBX-69814 3

SMM is not writing specified data to CDR.

Platform/Feature: SBC Core: SIP

Support was added for SMM CDR write operation in Refer handling and relay cases.
SBX-69865 3

registrationInterval and registrationRefreshInterval fields need to be renamed.

Platform/Feature: SBC CE: CLI

The below attributes were renamed in the documentation.
  • accessScenario - renamed to isAccess 
  • registrationInterval - renamed to internalRefreshTimer and displayed only when isAccess='true' 
  • registrationRefreshInterval - renamed to externalRefreshTimer and displayed only when isAccess='true' 
  • natEnabled - not removed 
SBX-69943 / SBX-69708 2

PortFix SBX-69708: Check-in Requirement SBX-69629 for SIP-SIP Calls.

Platform/Feature: SBC Core: SIP

A flag was added in TG signaling to show whether to send PEM Header before Ingress Preconditions.


SBX-70088 / SBX-70013 2

PortFix SBX-70013: PSX globalconfig for switchOverMode does not work. When this is set and one PSX goes down then recovers, it should not come back as active until manually set, but it does comes back as active.

Platform/Feature: SBC Core: Common Sonus Platform Services

The datatype of pscsSwitchOverType was changed from BOOLEAN to USHORT.
SBX-70155 2

Multiple security vulnerabilities exist.

Platform/Feature: SBC 5000/7000 Series: Platform

Vulnerabilities were addressed by making changes to the apache configuration file which will set the X-Frame-Options header in the response and also limit the request header size by setting the LimitRequestFieldSize parameter.

SBX-70164 / SBX-57571 2

PortFix SBX-57571: EMA display for user is incorrect when RADIUS authentication is used.

Platform/Feature: SBC 5000/7000 Series: EMA

The code was modified so that the login user name displays instead of netconf user.
SBX-70202 1

SNMP based collection is failing under zone and sipTrunkGroup.

Platform/Feature: SBC 5000 Series, CE, SWE: Third Party

The sort order for zone and sipTrunkGroup was changed.
SBX-70323 / SBX-69380 2

PortFix SBX-69380: Unable to send SIP call via TLS. Ingress SBC was using the transport based on egress IPSP transport settings for the inter-SBC leg.

Platform/Feature: SBC Core: SIP

The code was modified so that ingress SBC uses the transport based on the Inter-Gateway Signaling Group or Signaling Gateway Group IPSP transport settings instead of the egress IPSP transport settings.
SBX-70385 2

Multiple Audio Stream is not working on a particular flow when AudioVideo call is downgraded to Audio only and another Audio Stream is added.

Platform/Feature: SBC Core: Application

Changes were made to comply with RFC.


SBX-70388 / SBX-67728 2

PortFix SBX-67728: The Retry-After header is getting added in Session-Expires headers with a large value.

Platform/Feature: SBC Core: Application

The code was modified to fix an initialization issue.

SBX-70389 / SBX-67242 3

PortFix SBX-67242: During downstream forking on Egress when peer2 answers SDP in 18x without 100rel, the SBC sends an UPDATE to peer2, causing call teardown.

Platform/Feature: SBC Core: SIP-Peering

The code was modified to suppress sending an UPDATE message to peer2.
SBX-70391 2

On Rx interface (PCRF), where Feature-List bitmask into the Feature-List-ID AVP is encoded, the Feature-List-ID can be 1 or 2. It is set to 19.

Platform/Feature: SBC Core: SIP

The code was modified to populate the Feature-List-Id with a valid value (1).


SBX-70416 / SBX-69779 2

PortFix SBX-69779: SBX policy DB oracle passwords are expiring.

Platform/Feature: SBC Core: Provisioning

The code was modified so that oracle DB passwords do not expire within 180 days.



SBX-70428 / SBX-53926 3

PortFix SBX-53926: SMM automatically being modified via GUI when no modification was done.

headerInfo field support is not present in the code for action operations related to regular expressions (like regsub, regdel, regappend etc..)

Platform/Feature: SBC Core: CLI

Support was added for the headerInfo field for regular expression operations.
SBX-70480 / SBX-69376 2

PortFix SBX-69376: The SBC cannot send the redirecting number in History info to PSX when the number of redirections is one time.

Platform/Feature: SBC 7000 Series: Call Control

The code was modified to send the Redirection Number to PSX even when the NNI flag is disabled.
SBX-70500 / SBX-70454 2

PortFix SBX-70454: The SMM is not storing the O line in an IPV6 case.

Platform/Feature: SBC Core: SIP Applications

The code was modified to store the O line if it contains the IPV6 Address.
SBX-70586 / SBX-70369 1

PortFix SBX-70369: A name change on the Platform Manager failed.

Platform/Feature: SBC 5000/7000 Series: Platform

The name change issue was fixed as ipinterface was changed to specify cename.
SBX-70637 2

The SBC should ignore Alternate configuration field while requesting EMS for configuration.

Platform/Feature: SBC CE: Application

The download config file name passed by the user was removed from the templates.

SBX-70670 / SBX-69029 3

PortFix SBX-69029: SFTP based CDR transfer needs to use an ephemeral local port.

Platform/Feature: SBC Core: Application

The CDR file transfer functionality was modified to use an ephemeral port instead of a fixed port. This was done to conform to the TCP/IP standard.
SBX-70673 / SBX-70131 2

PortFix SBX-70131: Application startup can fail post upgrade if password entry for a user is missing in CDB.

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

The code was modified to log the absence of missing password entry instead of it erroring out.
SBX-70680 2

Inconsistent processor capacity estimation in SWe platform.

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

The KVM Installation procedure was updated.
SBX-70779 / SBX-67565 2

PortFix SBX-67565: When incoming INVITE has reqURI with NPDI and RN and To header transparency is enabled, the SBC honors the To header transparency but reqURI is generated with same number as the To header

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

The code was modified to ensure the SBC generates the correct Req URI when To header transparency is enabled and incoming INVITE has NPDI and RN.
SBX-70780 2

When recording is enabled on a refer call flow, the SBC does not mirror call data for the main call leg correctly. This results in standby not able to reconstruct the main call block after switchover and results in no audio. 

Platform/Feature: SBC 5000/7000 Series: SIP

The code was modified to ensure the SBC mirrors the communication session information correctly to standby when calls are recorded.
SBX-70844 / SBX-70757 / SBX-68238 2

PortFix SBX-68238: The digit buffer was accessed improperly after 62 seconds. This resulted in an invalid memory access and caused memory protection fault. 

Platform/Feature: SBC Core: DSP

The code was modified so that the digit buffer is accessed only when it is valid. Also, previous digit detection flags in channel control structure are cleared while freeing the digit buffer.
SBX-70950 / SBX-69169 2

PortFix SBX-69169: reINVITE was not relayed to the ingress call leg due to tone being played.

Platform/Feature: SBC 7000 Series: Media Resource Management

The code was modified to fix the offer-answer issue.


SBX-70951 2

The SBC is not able to detect a syntax error for media image.

Platform/Feature: SBC Core: SIP

Code was added to validate the protocol and responses with the syntax error.
SBX-70952 / SBX-70445 3

PortFix SBX-70445: UPDATE is queued due to internal media lockdown after receiving 491 Request Pending. The logic of checking the state was incorrect.

Platform/Feature: SBC Core: SIP

The code was modified to check the proper state.
SBX-70955 3

Sub-system IDs are accepted in either upper case or lower case.

Platform/Feature: SBC 5000/7000 Series: Application

Subsystem IDsare changed to be case independent to avoid duplicate entries.
SBX-71011 / SBX-69608 3

PortFix SBX-69608: RTP Packet loss threshold detection is enabled when packetLossThreshold is set to 0 and peerAbsenceAction is set to peerAbsenceTrapAndDisconnect or peerAbsenceTrap.

Platform/Feature: SBC Core: Media

Code was added to validate the packet loss threshold when XRM receives RTP packet loss activity notification from NP. 

Code was added to validate packet loss threshold range and to disable packet loss on the media flow when threshold value is 0 to 399.

SBX-71012 / SBX-70592 2

PortFix SBX-70592: The standby SamP core dumps several times before all processes stop due to large configuration in N:1 redundancy.

Platform/Feature: SBC CE: Provisioning

The code was modified in SIPCM and SIPFE to disable healthchecks while restoring the configuration.

SBX-71049 / SBX-70864 2

PortFix SBX-70864: SIP NOTIFY relay behavior is not consistent across transport types and SBC SW versions. Notify fails to send to IAD via indialog Subscribe.

Platform/Feature: SBC Core: SIP Access

The issue was fixed by a code re-merge so that NOTIFY was able to send from AS to IAD after Subscribe through TLS.


SBX-71050 2

SIPREC is configured to trigger on egress TG, and to sends requests to 2 servers. INVITEs are seen to both servers, the first one completes the dialog; however, the second sends only a 100Trying.

Platform/Feature: SBC Core: SIP

The code was modified so that If SRS responds with 100 Trying to the INVITE with no further response, the transaction is terminated with CANCEL.
SBX-71162 / SBX-69791 3

PortFix SBX-69791: When a communication session is being recorded and re-INVITE is received from one of the endpoints with codec order altered, the SBC does not change the negotiated codec for communication session, but the negotiated codec for the recording session is changed.

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

The code was modified to ensure the SBC does not change the codec for the recording session if communication session codec is not changed after re-INVITE offer - answer.
SBX-71182 / SBX-70523 2

PortFix SBX-70523: A SIP-SIPI call hold interworking issue.

Platform/Feature: SBC Core: SIP

This issue was resolved by including GNO in IAM for SIP-I egress call if ingress INVITE had a-sendonly or a-inactive in SDP.
SBX-71200 / SBX-65892 3

PortFix SBX-69852: SBC ERE treats a DNS query that responds with “No Such Name” as a timeout, causing a 2-second delay.

Platform/Feature: SBC Core: ERE

The code was modified so that a "No Such Name" enum response is treated differently than Timeout and avoids PSX 2-second delay.


SBX-71243 / SBX-70180 3

PortFix SBX-70180: "Use Sip Domain in Request URI" is causing the RURI port number to not be included when the Diversion Header is present.

Platform/Feature: SBC Core: SIP

A port number was added in case of enum dip.
SBX-71383 / SBX-69838 3

PortFix SBX-69838: When receiving a port set to zero for audio in the offer, Answer does not come with the zero.

Platform/Feature: SBC 7000 Series: SIP

The SIPSG was updated to handle media port 0 case correctly in SDP.
SBX-71569 / SBX-68244 3

PortFix SBX-68244: When the secure IMS AKA TCP connection between UE port-s and SBC port-c is closed and then re-established by the SBC, the SBC initiates a connection from a non-secure ephemeral port instead of a secure port. Since the SBC is not sending messages on the secured port over IPsec towards UE, UE does not respond, causing SMS delivery to fail.

Platform/Feature: SBC SWe: SIP Access

The code was modified so that the SBC initiates the connection from secure port-c towards UE port-s over IPsec during re-establishment of the connection.
SBX-71760 / SBX-68300 3

PortFix SBX-68300: The SBC SWe discards fragmented signaling packets that are received on the port numbers from the media port range as rogueMedia.

Platform/Feature: SBC Core: SIP

The code was modified to allow IP frag reassembly of fragmented IP/UDP packets that are received on a SIP signaling port within the media port range, with the exception of the default SIP signaling port.


SBX-71763 / SBX-67028 3

PortFix SBX-67028: The SBC does not reject the SIP REFER when handleIpAddressesNotPresentInNetworkSelectorTableNst is set to rejectCall and the SIP REFER is received on the egress call leg.

Platform/Feature: SBC Core: SIP

The code was modified so that when the handleIpAddressesNotPresentInNetworkSelectorTableNst flag in ipSignalingProfile is set or modified in SBX CLI, both handleIpNotInNst and ingHandleIpNotInNst field are set to the same value.
SBX-71778 / SBX-71476 3

PortFix SBX-71476: NrmaDeallocCallLeg() update sent to NRM.

Platform/Feature: SBC Core: Call Control, Media Resource Management

The code was modified to not send the notification to NRM, when using a disconnect treatment profile to play a tone/announcement on call release.
SBX-71784 1

The SBC is not taking the "sweConfigProfileSelection" configuration changes from the configurator unless manually rebooted.

Platform/Feature: SBC CE: Application

The user needs to manually reboot the instances to activate the changes. A note is added to the relevant documentation.
SBX-71789 2

maxVMBandwidth needs to be renamed to maxProtectedPPS to estimate traffic profiles.

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

In sweTrafficProfiles, the maxVMBandwidth field was removed. 
In sweCapacityEstimate, estimatedProtectedLinkBandwidth was replaced by estimatedProtectedPPS.


SBX-71978 / SBX-71849 3

PortFix SBX-71849: When an IPsec tunnel is added, a core dump occurs as a result of an IP V6 address printed for debug logging that exceeded the print buffer size. This occurs only for fully populated IPV6 addresses.

Platform/Feature: SBC Core: Platform

The print buffer size was increased, and guarding against overwriting the buffer length was added.

SBX-71891 3

SBC provisioning limits are accepting 1 more record than the limit for ipInterfaceGroup and SIP TRUNK GROUP.

Platform/Feature: SBC SWe: Application, Platform

Limits for "small" configuration profile is updated to 129
SBX-72123 / SBX-71524 2

PortFix SBX-71524: When the authorization username and password was modified at IP Peer for surrogate registration, the change was not reflected in the REGISTER message sent from the SBC as a response to challenge. This happens when the surrogate registration profile is configured at IP Peer. 

Platform/Feature: SBC 5000/7000 Series: Application

The code was modified to ensure updates to the authorization username and password at IP Peer for surrogate registration are applied even when the surrogate registration profile is configured at IP Peer.
SBX-72168 3

To prevent Trace message loss with this level of call load, it is required to configure the diskThrottlingLimit to 25000.

Platform/Feature: SBC 5000/7000 Series: CLI


Allow diskThrottleLimit in typeAdmin CLI table to be general command.

Set diskThrottleLimit to 25000, to prevent message loss, when Trace logging is configured. 

SBX-72243 / SBX-72161 3

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

Platform/Feature: SBC 5000/7000 Series: EMA

The _ECHO command was added in alphabetical order in the sonusCommand file.
SBX-72279 / SBX-65833 3

PortFix SBX-65833: LSWU fails at postUpgradeChecks after the SBC Upgrade complete and application bring-up is complete.

Platform/Feature: SBC 5000/7000 Series: LSWU

The Policy Server code was modified to delay the active-standby policy data comparison on the standby server until after the active server is upgraded.

SBX-69374 2

Multiqueue problems are present.

Platform/Feature: SBC CE: Firmware

Multiqueue configuration on sriov ports is not applied.
SBX-70059 2

Support HOLD/RESUME INVITE from SIPREC SRS pauses and starts pumping media towards SRS.

Platform/Feature: SBC 5000/7000 Series: Application

Splitter API enhancements were added to support halt/resume of the tapped packet stream.
SBX-70633 2

OCSP does not contain a HOST Header. A client must include a HOST header field in all HTTP/1.1 request messages. Otherwise, the SBC indicates all OCSP queries to AIA are failing.

Platform/Feature: SBC Core: TLS

A HOST header field was added to the HTTP/1.0 OCSP Request message.
SBX-71486 / SBX-71098 3

PortFix: SBX-71098: In the case of Parse Failures, Reject Operation and Dialog Transparency, SMM Dialog Statefull variables are deleted without checking whether they are present in hash or not. This causes hash corruption and leads to coredump.

Platform/Feature: SBC Core: SIP

A check was added to see if the variables are present in the hash before freeing the SMM Dialog Statefull variables.

SBX-72158 2

Alternate names in EMA for registrationInterval, registrationRefreshInterval and accessScenario fields need to be displayed.

Platform/Feature: SBC SWe: CLI, EMA, EMA/EMS

 The following attributes were renamed/modified:
  • accessScenario - should be renamed to isAccess 
  • registrationInterval - should be renamed to internalRefreshTimer and displayed only when isAccess='true' 
  • registrationRefreshInterval - should be renamed to externalRefreshTimer and displayed only when isAccess='true' 
  • natEnabled - should not be removed
SBX-72303 2

RTP-EVENTS are not being intercepted at mediation server in a transcoded call.

Platform/Feature: SBC Core: Application

Code was added to pick the DTMF related configuration from the tapped leg, and configure it for the tap leg.
SBX-72351 1

Switchover failed after the LSWU from 7.0.0F001 to 7.1.0A20.

Platform/Feature: SBC SWe: LSWU

The ARP probe feature will no longer use the flag probeOnStandby which is enabled by default. The ARP probe feature will use a new flag probeOnStandbySWe to enable the ARP probe feature on the SWe platform, and this feature will be disabled by default. To use this feature, the user has to explicitly set probeOnStandbySWe enabled
The old flag probeOnStandby will only be visible for 4 pkt ports SWe instance where port redundancy is required, while flag probeOnStandbySWe will only be visible for 2 pkt ports SWe instance.
SBX-72388 2

Target: dhclient should not run on non-dhcp servers.

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

A function stopDhclients() in lca->modules-> was added.
stopDhclients() was called from lca->modules-> to kill dhclient.
SBX-72469 / SBX-71995 3

PortFix SBX-71995: When selecting the following: Address Context > choose Zone > select a Trunk Group > navigate to Ingress IP Prefix - EMA displays all Ingress IP Prefixes for all TG within the Zone.

 Platform/Feature: SBC Core: EMA

The code was modified so EMA displays Ingress IP Prefixes for the Sip Trunk Group selected.

SBX-72631 / SBX-72127 1

PortFix SBX-72127: During a reoccurring INVITE - 407 Proxy Authentication Required calls scenario, duplicate CPC_OP_STRs are inserted into the CPC_MSG_INFO, causing SCM to coredump.

Platform/Feature: SBC 5000/7000 Series: Platform

The code was modified to prevent duplicate CPC_OP_STRs from being inserted into the CPC_MSG_INFO during the reocurring INVITE - 407 Proxy Authentication Required calls scenario.

SBX-72675 / SBX-72103 3

PortFix SBX-72103: When a high number of unknown headers are configured on the SBC system transparency profile, an array overflow can occur, and the SBC may attempt to write into an invalid index in an array, causing a coredump.

Platform/Feature: SBC 7000 Series: Call Control

The code was modified to make sure the array index which holds the unknown header types is checked before writing an unknown header type.
SBX-72740 / SBX-72684 3

PortFix SBX-72684: IME from the re-invite is not being processed by SBC.

A call is answered on the Egress with 180 message with Remote Hold and SDP a=sendonly. 
This information is transmitted to the ingress call connects with one way audio.
The egress sent another Re-INVITE with a=sendrecv and ISUP Remote Retrieval.

But on the Ingress the SBC is sending the Re-INVITE with a=sendrecv without the ISUP message “Remote Retrieval”. Some ISUP equipment will stay in the one way audio state if it does not receive the “Remote Retrieval”

Platform/Feature: SBC 7000 Series: Application

This issue was fixed in SipSgReconfigureCallNfy to save mediaDirChange before calling SipSgConvertSdpToPsp. THe saved value was used to decide if callHold procesing should be invoked.

SBX-72814 2

This issue is specific to SBC-5400. On a standby SBC, the packet ports should not receive any packets. However, the NP was allowing ARP and packets matching ACL rules.

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

The code was modified to set the interface MAC address for pkt1 in yellowfin in order to support 2 10G interface.


SBX-72978 / SBX-54211 2

PortFix SBX-54211: The Allow header does not have NOTIFY in the Reponse.

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

 If no Allow header is received in 18x from Egress, then the Allow header received in the Initial Invite will be taken into consideration for 18x sent towards Ingress.


Known Issues

Known Issues in 07.01.00R000 (Build 8) Release

There are no known issues in this release. 

Known Issues in 07.01.00R000 Release

The following issues exist in this release:

Table : Known Issues

Issue ID


Problem Description


SBX-72861 3

During upgrade of an SBC SWe cloud instance where the VM RAM is greater than 18GB, the instance goes through an additional reboot when the Lifecycle Agent tries to bring up the instance as ACTIVE/STANDBY.

Platform/Feature: SBC CE: Application, LSWU

Impact: An additional reboot causes the instances to take more time to come up.

Workaround: No workaround available.

SBX-73054 3

If the standby node is selected as Headend, invalid configurations might be accepted on Headend, and activations on non-head nodes might fail.

Platform/Feature: SBC CE: Application

Impact: There is failure in activation of configuration.

Workaround: Upon starting a configuration edit on EMS, the user will make sure the head node role is Active. If it is not, restart the standby SBC (current Headnode), to force EMS to select another instance as Headnode.


Known Limitations

The following limitations exist in this release:

  • Only a standalone SBC is supported.
  • Only a four VCPU instance profile (with 15GiB memory and Intel Broadwell or later CPU) is supported.
  • For information on Performance for GCP 7.1.0R0 (build 8), refer to SBX-74089 POC MOP - Support for Standalone SBC on GCP (build 8)
  • 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.
  • 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.

Restricted Functionality with SBC

The following functionalities are not supported with SBC Microservices:

  • Far end NAT traversal
  • DTMF inter-working
  • RTCP termination for pass-through calls
  • Direct Media and Antitrombone 
  • Rx, Rf interfaces
  • Multimedia - MSRP, BFCP  
  • Fax detection
  • Two stage calls

  • H323 support
  • GW signaling support