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 (https://ribboncommunications.com/company/get-help/resource-library).

Related Documentation

The SBC Core 07.00.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 (https://ribboncommunications.com/services/ribbon-support-portal-login)
  2. Click Bulletins link from the menu bar. 
  3. Enter the bulletin number (last eight numbers) in the search field and press Return.

Problems or Questions

For problems or questions, contact 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.

Interoperability

The SBC Core software interoperates with the following:

  • 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.


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 Compatibilities.

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

Sample CFN Templates Included in This Release

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

Table : Templates

TemplateDescription
AWS_Stand_Alone_template.jsonOrchestration of Standalone SBC.
AWS_HFE_HA_template_auto_subnet.jsonHA with High-Availability Front End (HFE) and HFE subnet auto created.
AWS_HFE_HA_template.jsonHA with HFE and HFE subnet. Not auto created, and user choice of subnet selection.

SBC SWe Cloud Requirements for AWS

Note

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

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

Note

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

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

Required Software and Firmware Versions

The following SBC software versions are required for this release:

Table : Required Software and Firmware Versions

Components

Software/Firmware

Version

SBC Application

 

 

Operating System (OS) Version

V06.00.00-S404
SonusDB

V07.00.00-S404

SBC Application

V07.00.00-S404
EMAV07.00.00-S404

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

Warning

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

Note

Once the installation or upgrade completes on 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.

Note

As an SBC Core password security enhancement, user passwords automatically expire after upgrading to 7.0.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.0.0 Release
Customers using Legacy mode will stay on the Legacy mode after upgrade to SBC 7.0.0 Release. Once upgraded to SBC 7.0.0 Release, the customer will not be able to set Network License mode.

Note

Once installed, resizing instances in AWS is not supported.

 

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

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

See the following pages for configuration details:

Instantiating SBC SWe on AWS

To instantiate the SBC SWe on AWS, refer to the Instantiating SBC SWe on AWS procedure.

Instance Types Supported for Amazon Web Services on SBC SWe

ReleaseInstance Types SupportedRecommended Default Instance TypeComments
7.0.x SBC SWe in AWS"m4.xlarge",
"m5.xlarge",
"m5.2xlarge",
"c3.2xlarge",
"c3.4xlarge",
"c3.8xlarge",
"c4.2xlarge",
"c4.4xlarge",
"c4.8xlarge",
"c5.2xlarge",
"c5.4xlarge",
"c5.9xlarge",
“ g3.4xlarge”
  • M5 and C5 instances are cheaper compared to M4 and C4 instances of previous generation
  • M5 instance for Passthrough
  • C5 instance for Transcode and Crypto call scenarios

Note: If you change the instance type from M4 to M5 or C4 to C5 you will need to contact Ribbon for appropriate licensing.

  • G3 instances for Transcode only workloads/call scenarios
  • Largest instance type supported is c5.9xlarge

Newer generation M5 and C5 instance underlying Hypervisor is KVM Nitrox and Networking is ENA.

New Features

New Features in 07.00.00S404 Release

SBX-72000 Monitoring the HFE Node

For information, refer to Monitoring the HFE Node.

SBX-72598 Create a Script to Pin Third-Party Software to Particular Set of Cores in SBC SWe

For information, refer to Create a Script to Pin Third-Party Software to Particular Set of Cores in SBC SWe.

SBX-60478 MOP - Replacement Upgrade for AWS

For information, refer to Replacement Upgrade for AWS

SBX-72811 Route53 with Cloud Watch Support with VPC Endpoint Deployment

For information, refer to Route 53 Configuration With Cloud Watch.

SBX-72745 Create NTP configurable for the SBC SWe in Cloud

For information, refer to Creating NTP configurable for the SBC SWe in Cloud (S404).

SBX-67691 Creating an SBC SWe Snapshot in AWS

For information, refer to Creating an SBC SWe Snapshot in AWS.

Creating Security Groups on AWS

For information, refer to Creating Security Groups on AWS.

SBX-63311 SBC SWe Monitoring Using VoIPmonitor - Proof of Concept (404)

For enhancements made to this proof of concept, refer to SBC SWe Monitoring Using VoIPmonitor - Proof of Concept.

SBX-69157 / SBX-69386 / SBX-70936

For enhancements made to the Performance Metrics, refer to AWS Performance Metrics.

SBX-69227 

For enhancements made to the REST API Performance Benchmarks, refer to REST API Performance Benchmark.

SBX-71197

For enhancements made to this MOP to provide an HFE Node, refer to SBX-60481 AND SBX-71197 MOP to Provide an HFE Node for AWS.

New Features in Previous Releases

For new features in previous releases, refer to:


Resolved Issues

Resolved Issues in 07.00.00S404 Release

The following issues are resolved in this release:

Table : Resolved Issues

Issue ID Sev Problem Description Resolution
SBX-72282 2

SWe cannot route telephony calls.

Platform/Feature: SBC CE: HA

This was resolved as part of the S402 delivery and is included in GA.

Resolved Issues in 07.00.00S402 Release

The following issues are resolved in this release:

Table : Resolved Issues

Issue ID Sev Problem Description Resolution
SBX-70216 2

The Alternate IP feature in AWS has issues during HA, and the secondary IP’s are jumbled when the metadata is obtained from AWS. As a result the secondary IP to EIP mapping goes for toss leading to inconsistent config in active-standby setup and resulting in issues with HA of the SBC.

Platform/Feature: SBC CE: Application, Platform

The code was modified in HFE, SBC and the Cloud formation template to support this feature.
SBX-72749 2

HFE Private subnet is auto created.

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

Instead of auto create, a choice is provided to select from an existing list of subnets that were created earlier.
SBX-72609 3

Upon reboot the tap_dpdk interface for monitoring is down and needs to be brought up manually.

Platform/Feature: SBC CE: Platform

The issue is addressed and tap_dpdk interface is up on reboots.
SBX-72794 2

The command formats have changed causing an issue during install of HA with HFE.

Platform/Feature: SBC CE: Platform

Linux ifconfig tool changed data representation, so the 'ifconfig' was giving a different output on different versions of AWS-Linux. 

HFE code was modified to support both types of output.

Resolved Issues in 07.00.00S400 Release

The following issues are resolved in this release:

Table : Resolved Issues

Issue ID Sev Problem Description Resolution
SBX-70374 2

AWS rate limits and throttles the number of API's sent by the SBC during switchover, causing IP movement to not take place and therefore causing unsuccessful switchover and media outage.

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

The code was modified to get local port from range '2026 to 2226" to send queries to AWS API server for IP switchover.
SBX-70115 1

EMA takes 3-5 minutes to load the trunk group configuration and Alarm page.

Platform/Feature: SBC CE: EMA

This was resolved as part of the re-anchor to 7.0R000 build, through EMA and stability fixes.
SBX-70016 3

Configuration of AWS SBC using EMA failed.

Platform/Feature: SBC Core: Application

The correct config which enabled the configuration of SBC via EMA was shared.

SBX-69700 3

The default instances types for each of the SBC SWe releases was not documented, causing confusion for choosing the right instance types for SBC releases.

Platform/Feature: SBC SWe, CE: Documentation

The documentation was updated with the instance types for SBC releases and the need to use M5 for passthrough and C5 for crypto and transcoded calls.

SBX-70117 2

Without the EIP and internet access to mgt interface HA failover for secondary IP and EIP does not function, and this requirement was not documented.

Platform/Feature: SBC CE: Documentation

The documentation was updated to convey the need for internet access for management interface for HA failover.

 

Resolved Issues in 07.00.00A019 Release

The following issues are resolved in this release:

Table : Resolved Issues

Issue ID Sev Problem Description Resolution
SBX-68154 2

When SWeNP is crashing at boot time, its core dump is not getting collected or saved by the system.

Platform/Feature: SBC SWe: Media

The code was changed so that the SWeNP memory initialization accessing out of allocated boundary for US processing blocks was corrected.
SBX-68445 1

The configuration database is not synchronized with the loading XML from Standby.

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

The code was modified in ChmProcess to synchronize the configuration database and the loading XML from Standby.

Resolved Issues in 07.00.00R000 Release

The following issues are resolved in this release:

Table : Resolved Issues

Issue ID Sev Problem Description Resolution
SBX-33099 2

The EMA Web server presents the EMA server certificate to only the TLS peer even when the server certificate was a signed CA certificate. The EMA Web server should send the entire certificate chain when the server certificate is not a self-signed certificate.

Platform/Feature: SBC Core: EMA

EmaTlsProfile's ClientCaCert is used to specify "remote" certificates to verify peer's certs, and to build an EMA server chain.

The EMA Web server certificate presents entire certificate chain to the TLS peer when the server certificate is signed by Certificate Authority (CA) certificate. The certificate chain is an ordered list for certificates containing the EMA server certificate, intermediate CA certificates, and the root CA certificate.

SBX-42093 3

The SBC does not support conversion from RTP to a SRTP call if the original SDP offer contained DTLS.

Platform/Feature: SBC Core: SIP

The code was modified to support Call Flow from DTLS-SRTP and vice versa.

SBX-62479 / SBX-66804 2

SBX reports an event when call failures due to DSP failures exceeds a configured limit. This was being incorrectly reported even if xcodeFreeTransparency flag was enabled.

Platform/Feature: SBC 5000/7000 Series: Platform

The code was modified to fix the incorrect reporting.
SBX-62806 2

New GPU status/stats need to be implemented.

Platform/Feature: SBC CE (Cloud Edition): Platform IP/Media Services

New CLI transcoding commands are added. For more information, see SBX-62806 Implement GPU status/stats.
SBX-63382 2

If there are 3 or more sysdumps in /opt/sonus/external, the user is prevented from continuing with sysDump collection.

Platform/Feature: SBC Core: Common Sonus Platform Services

Sysdump is restricted when there are 3 or more sysdumps in /opt/sonus/external.

 

SBX-63744 3

The SBC fails to start the DTLS SRTP server when dtlsCryptoSuiteProfile has two identical crypto suites configured. As a result, the call is torn down. In ICE enabled environments, the call continues but DTLS never negotiates since the SBC cannot find the DTLS session on which the DTLS packet was received.

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

Added a NULL check to handle resource allocation failure.
SBX-64593 3

User is unable to change the mode to outOfService when state was enabled.

Platform/Feature: SBC Core: EMA/EMS

The code was modified to handle state disable/enable as part of sipSigPort update/delete. sipSigPort fields can now be updated or deleted without modifying the state.
SBX-64725 / SBX-64068 2

PortFix SBX-64068: The Standby instance is not running the 10 minute-timer.

Platform/Feature: SBC Core: Application

The code was modified to set the 10 minute-timer even in standby mode.
SBX-64736 3

In the EMA search tab, entering a single letter character will result in no search output.

Platform/Feature: SBC 5000/7000 Series: EMA

The code was modified so that the EMA search tab is disabled unless the search text is a minimum of 2 characters.


SBX-64819 3

The Runtime Diagnostic tool it does not show the % of test cases completed or the status of the operation.

Platform/Feature: SBC Core: EMA

The code was modified to handle non-ascii value and to delete the log file.
SBX-65327 2

When there is an ongoing SIP recording in progress based on the recording criteria set to the calling party, and the SBC receives a REFER request to transfer the call, upon successful call transfer, the existing SIP recording session is stopped.

Platform/Feature: SBC Core: SIP

The code was modified to keep the ongoing SIPREC session active upon successful call transfer.
SBX-65772 / SBX-61870 2

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

Platform/Feature: SBC 7000 Series: Application

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

PortFix SBX-60281: MINOR GWCM errors are flooding the SYS logs.

Platform/Feature: SBC 7000 series: Gw-Gw

The SBC code was modified to log the messages at the INFO level instead of the MINOR level. 
SBX-65963 / SBX-65966 / SBX-62093 2

PortFix SBX-62093: In an IMS AKA scenario, the SBC cores if a health check timeout occurs because a socket connection function takes longer than normal to complete.

Platform/Feature: SBC SWe: SIP/TLS

The SBC code was modified to prevent the health check timeout by unlocking the socket connection structure in cases when the socket connection function does not return SUCCESS. 
SBX-66330  

Need to maintain 2 sets of MC level thresholds for SWe, one for default profile (with 65%, 75%, 85% thresholds), and another for non-default profile (with 85%, 90%, and 95% thresholds). Based on the traffic profile activated, the overload thresholds need to be set accordingly.

Platform/Feature: SBC SWe: Platform/Feature

The MC levels are set the same as hardware for non-default traffic profiles.

New overload profiles are introduced for SWe.

For more information, refer to:

SBX-66432 / SBX-63845 2

PortFix SBX-63845: Geographical redundancy HA mode is disabled after upgrade to release 5.1.1.

Platform/Feature: SBC 5000/7000 Series: Redundancy

The SBC code was modified to ensure the geographical redundancy status is retained when upgrading from 5.0.2 SBC versions.
SBX-67006 2

During switchover on AWS HA SWe instances, movement of IPs to the new active SWe instance failed.  The root cause of this issue was that the SBC failed to get IAM role credentials from the metadata server.

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

To fix this issue, the code was modified to restart the SBC application if the SBC does not get IAM role credentials. 
SBX-67240 / SBX-66969 2

PortFix SBX-66969: An invalid parameter value is being passed from the function CpcDiamRetrieveGenericDigits() to the function StrNCpyZ(), causing StrNCpyZ() to generate a System Error in which the stack trace is being written to the log. This is happening repeatedly – causing the disk to fill up and ultimately causing the system to switchover. 

Platform/Feature: SBC 5000/7000 Series: Application

The code has been modified to prevent the invalid parameter value from being passed to the function.
SBX-67316 2

PortFix SBX-66761: In a preconditions interworking scenario, the SBC is resending the SDP from the initial INVITE request in a preconditions UPDATE message rather than basing the SDP on the 18x response it received.

Platform/Feature: SBC 7000 Series: Call Control

The code was modified to send the codecs received in the 18x response in the preconditions UPDATE message.
SBX-67317 / SBX-66682 2

PortFix SBX-66682:The SBC is sending Require:100Rel in the outgoing INVITE request when preconditions is set to required.

Platform/Feature: SBC 7000 Series: SIP

The code was modified to send Supported:100Rel in the initial INVITE when preconditions is set to required.
SBX-67356 2

BMC will lose or reset user configuration on unexpected power outage. BMC will be reset with the default user configuration.

Platform/Feature: SBC 5000/7000 Series: BMC

system configuration is restored. If configuration is not recoverable, at minimum, user specific information is restored.
SBX-67360 / SBX-67329 2

PortFix SBX-67329: Test Call Number Profile only allows numeric characters, and does not allow "+". Therefore, it does not match if the username in the "from" header contains a "+" and cannot query to test PSX.

Platform/Feature: SBC 7000 Series: Call Control

The code was modified to allow “+” in the test call number.
SBX-67540 1

The flag names needs to be changed for lastProvResponse to lastReceivedSdp for the forking scenarios.

Platform/Feature: SBC 7000 Series: LSWU, SIP

The new flag name is set addressContext ADDR_CONTEXT_1 zone ZONE_AS sipTrunkGroup MVELE_TG_SBX_EGRESS media earlyMedia forkingBehaviour lastReceivedSdp 
SBX-67570 2

SIPREC was not designed and implemented with mediaPortRange functionality.

Platform/Feature: SBC SWe: SIP

Functionality was added to get mediaPortRange configuration from sipTrunkGroup and use it when allocating resources for SIPREC.
SBX-67658 / SBX-65577 2

PortFix SBX-65577: After the SR-IOV ports connected to the SBC running in a cloud environment were physically removed and plugged back in, the SBC failed to communicate using the Virtual Function (VF) assigned.

Platform/Feature: SBC SWe Cloud: Platform

The code was enhanced with an auto-recovery mechanism for the SBC VF link to address the case when a link is physically removed and then plugged in again. This change makes sure that the link on the SBC works correctly again as soon as the physical link comes up.
SBX-67698 / SBX-67634 2

PortFix SBX-67634: The SBC does not send an egress preconditions update when the initial INVITE is received with the data path mode set to send-only/recv-only.

Platform/Feature: SBC 7000 Series: SIP

A check was added to send a preconditions update even if the initial invite is received with the data path mode as send-only/recv-only.
SBX-67935 2

In the EMA interface, scrolling down the left panel causes the principal panel to also scroll. The two panels should not be synchronized.

Platform/Feature: SBC Core: EMA

The left panel and principal panel were de-synchronized, and a PrimeNG ScrollBar panel was added around the left navigation tree.
SBX-67969 3

The EMA Log Management screen needs to provide T-shark logs for downloading purposes.

Platform/Feature: SBC Core: EMA

The code was modified to list out T-shark log files on the Log Management screen.
SBX-68232 / SBX-67038 3

PortFix SBX-67038: A commands to detect a DSP card that was powered on interfered with adding User ACL on the hardware ACL module, which caused a timeout on the add ACL command. This then caused PRS to coredump.

Platform/Feature: SBC 7000 Series: Application

The command was modified to detect the DSP card that was powered on so that it does not interfere with adding User ACLs.
SBX-68351 / SBX-65235 2

PortFix SBX-65235: When incoming calls are received from an unregistered endpoint and the supressNonRouteInviteResponse flag is enabled, the SBC does not release memory allocated for the SIPSG CCB structure. When a high number of these calls are received, the SBC may not process further calls. As per the supressNonRouteInviteReponse feature functionality, the SBC does not respond with a 100 Trying message to the unregistered endpoint.

Platform/Feature: SBC 5000 Series / SWe: Call Control

The code was modified to fix the SIPSG CCB structure leak when the suppressNonRouteInviteResponse flag is enabled.
SBX-68366 3

sonusCpLicenseServerName is present in the VARIABLES list sonusCpLicenseAcquireFailed trap, but is absent from the corresponding clearing trap, sonusCpLicenseAcquireSucceeded. Therefore, sonusCpLicenseAcquireFailed will not be cleared.

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

A new parameter, sonusCpLicenseServerName is added to the sonusCpLicenseAcquireSucceeded trap.
SBX-68400 2

In the unity explorer, the user role drop-down is missing under Administration> User and Application Management > New User, causing creation of a new user to fail.

Platform/Feature: SBC CE (Cloud Edition): EMA

The user role drop-down is now present under Administration > User and Application Management > New User configuration after merging 6.2 software branch with 7.0 release.  
SBX-68401 3

EMA SMM rule name displays as unknown characters when the name contains the special symbol @, as the @ symbol was not decoded in the UI javascript code.

Platform/Feature: SBC Core: EMA

The UI javascript code was modified to decode the @ character, therefore correctly displaying the SMM rule name.
SBX-68430 / SBX-67440 3

PortFix SBX-67440: The logs are being filled by a per-call GWSG log message.

Platform/Feature: SBC 7000 Series: Application

An unnecessary SYS_ERR and a MAJOR level log message logged by GWSG were removed.

The MAJOR log message was replaced with an INFO level DBG log message.

SBX-68654 / SBX-68090 2
PortFix SBX-68090: One-way audio call occurs when local UDP port 4500 is chosen for a media call.

Platform/Feature: SBC Core: Platform
The code was modified to remove UDP port 4500 from the available media ports because it is reserved for IPSec ESP packet UDP encoding.
SBX-68677 / SBX-68363 2

PortFix SBX-68363: WebRTC ICE/DTLS call never reaches stage 2 ESTABLISHED state although DTLS negotiates properly.

Platform/Feature: SBC Core: SIP

 

A check was added to ensure that RTP and RTCP addresses match when UC response is received.
SBX-69204 / SBX-69033 2

PortFix SBX-69033: The SBC is transmitting 183 after PRACK/200, causing call failure.

Platform/Feature: SBC Core: SIP

Retransmission Logic is added for 18x responses without SDP.
SBX-69237 2

Dsbc parameters are not supporting partial configuration.

Platform/Feature: SBC CE (Cloud Edition): Application, Provisioning

The code was modified to support delta update on Dsbc parameters.
SBX-69272 / 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 was released, bring the external authentication through Radius server back to a working state.
SBX-69362 / SBX-69298 2

PortFix SBX-69298: ScmP coredumps because of SMM corruption.

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

The SMM corruption is fixed by using vsnprintf in case of SipsMmUtilDebug, in case of a SMM Criterion Failure.
SBX-69406 / SBX-64756 2

PortFix SBX-64756: Inconsistent data in determining which node should be active caused the process to crash.

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

The source was updated to prevent the data from becoming inconsistent.

Known Issues

Known Issues in 07.00.00S404 Release

The following issue exists in this release:

Table : Known Issues

Issue ID Sev Problem Description Impact/Workaround
SBX-68445 1

standbyInstance is not accessible on spawning/upgrading instances.

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

Impact: Standby management IP is not reachable.

Workaround: On an HA setup, run clear DB on standby continuously, or repeat the SBC installation till the issue is reproduced.

Known Issues in 07.00.00S402 Release

The following issues exist in this release:

Table : Known Issues

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

When amf_Process is killed in an HA with HFE solution, switchover is not triggered.

Platform/Feature: SBC CE: HA

Impact: As part of HA stability tests if the AMF process of SBC is killed manually, existing calls and registrations are impacted. Stable calls are released.

Workaround: No workaround available.

SBX-69734 3

IPsec calls from a public to private network are failing.

Platform/Feature: SBC CE: HA

Impact: IPSEC for signaling is not supported in AWS. This feature is unsupported for SBC SWe in Openstack and AWS environments.

Workaround: No workaround available.

Known Issues in 07.00.00S400 Release

The following issues exist in this release:

Table : Known Issues

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

Media is not encrypted during TLS-SRTP call

Platform/Feature: SBC CE: Application, Platform

Impact: : For TLS-SRTP calls via SBC SWe in AWS, media is not encrypted, causing the media to be unsecure.

Workaround: No workaround available.

SBX-69734 3

IPsec calls from a public to private network are failing.

Platform/Feature: SBC CE: Application, Platform

Impact: IPSEC for signaling is not supported in AWS. This feature is unsupported for SBC SWe in Openstack and AWS environments.

Workaround: No workaround available.

SBX-70298 2

When amf_Process is killed in an HA with HFE solution, switchover is not triggered.

Platform/Feature: SBC CE: HA

Impact: As part of HA stability tests if the AMF process of SBC is killed manually, existing calls and registrations are impacted. Stable calls are released.

Workaround: No workaround available.

SBX-70216

2

 

The Alternate IP feature in AWS has issues during HA, and the secondary IP’s are jumbled when the metadata is obtained from AWS. As a result the secondary IP to EIP mapping goes for toss leading to inconsistent config in active-standby setup and resulting in issues with HA of the SBC.

Platform/Feature: SBC CE: Application, Platform

Impact: Inconsistent config in active standby setup resulting in issues with HA of the SBC.

Workaround: No workaround available.

SBX-70080 2

The config for HFE node is stored in AWS S3. If the location for the script of HFE Node is invalid, the SBC HA pair and HFE Node would come up, but calls from Public to Private do not work.

Platform/Feature: SBC CE: Platform

Impact: Calls from Public to Private are impacted.

Workaround: Manually download the script and apply the config.


Known Issues in 07.00.00A019 Release

The following issues exist in this release:

 

Table : Known Issues

Issue ID

Sev

Problem Description

Impact/Workaround

SBX-69366

2

A random core was observed on an active instance.

Platform/Feature: SBC CE (Cloud Edition): CLI, Platform

Impact: The SBC needs a minimum disk I/O for call processing and functioning. Whenever the AWS disk I/O speed drops (for reasons unknown), the SBC application will encounter issues and timeouts, resulting in impacted calls.

Workaround: No workaround available. SBX service will restart after core dump, and HA will ensure call continuity after 15-18 seconds.

SBX-69367

A core dump is observed on the active instance after the following procedure:

  1. SBXSTOP on installed active - current standby.

  2. SBXSTOP on installed standby - current active.

  3. clearDB on installed standby.

  4. sbxrestart on installed active.

Platform/Feature: SBC CE (Cloud Edition): CLI, Platform

Impact: The SBC needs a minimum disk I/O for call processing and functioning. Whenever the AWS disk I/O speed drops (for reasons unknown), the SBC application will encounter issues and timeouts, resulting in impacted calls.

Workaround: No workaround available. SBX service will restart after core dump, and HA should ensure call continuity after 15-18 seconds.

 

Known Issues in 07.00.00R000 Release

The following issues exist in this release:

Table : Known Issues

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

.001% call failures observed while running transcoded call load for 10 hours.

Platform/Feature: SBC CE (Cloud Edition): Application

Impact: .001% of calls fail.

 Workaround: No workaround available.

SBX-68314 2

When Media SBC (M-SBC) is running with a call load (around 34k calls), if the CLI based switchover is triggered, media switchover (the time at which switchover is triggered on an active node to the time media is restored on standby node) will take around 1.5 seconds.

Platform/Feature: SBC CE (Cloud Edition): Platform

Impact: During the media switchover, all the media packets will be dropped and no media will flow. Media/calls will be restored after the media switchover.

Workaround: No workaround available.

SBX-68726 2

If the process SWe_NP crashes, there will be media loss for around 1.3 seconds.

Platform/Feature: SBC SWe: SIP Applications

Impact: Media switchover time will be high when SWe_NP crashes. Media will be restored afterwards. No calls will drop.

Workaround: No workaround available.

SBX-58903 2

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

Platform/Feature: SBC 7000 Series: SIP

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

Workaround: None


Known Limitations

The following limitations exist in this release:

  • The Access Control List (ACL) is not installed to configure SNMP traps for accepting traffic. A dynamic ACL is added to configure SNMP traps. An ACL must be installed for SNMP traps for accepting traffic.
  • The physical NIC connectivity must be in active state at the hypervisor level before starting the SWe instance on the SBC SWe platforms. In case of SWe instance with SR-IOV interfaces, manual restart of the SWe instance is required if physical NIC connectivity goes down while the instance is in progress.
  • The HA interface must not be configured with link local address or subnet. For example, do not configure it with 169.254.0.0/16 subnet. 

  • The Antitrombone feature is not supported on the D-SBC.
  • EMS identifies the nodes based on the VNFC-ID. While instantiating SBC/PSX cloud nodes, ensure that you use a unique VNFC-ID only. If you reuse an existing VNFC-ID, EMS treats this as a re-registration request and overwrites the existing data on the cloud node.
  • While configuring the SBC SWe Cloud instances, the CLIs commits successfully even if any metaVariable provided is incorrect. The SBC SWe Cloud instance cannot validate the CLIs, as the CDB configuration file is stored in the SBC Configurator and is shared among all the other SBC SWe Cloud instances in the cluster.
  • Editing IP Interface is not reflected in the if configuration (ifConfig). This behavior is observed only on the S-SBC when action is set to "dryup" mode on the IP Interface. The IP address changes are not updated in the kernel and will not be displayed when ifconfig linux command is executed. In case of S-SBC, if the ipInterface configuration needs to be modified and if the action is set to "dryup" in ipInterface configuration, it must be set to "force" before disabling the ipInterface and making any changes.
  • A LSWU on an SBC 7000 should only be performed when the total number of active calls on the system is below 18,000. If the criteria is not met, a double failure during the upgrade may occur thereby losing all active calls. If such a failure occurs, both active and standby SBC services will go down.  Contact TAC immediately.
  • Multiple-IP Support on AWS - For the SBC (SWe) supported instance types in AWS, there is a limit of 7 Maximum number of IP's per interface. This is because AWS currently only supports up to 7 IPs to be moved from active to standby in a single request. This stops us from supporting more than 7 IPs in HFE and non-HFE based HA solution. 
  • Troubleshooting tools CDR viewer and Elastic Search are not supported on AWS SBC SWe instances. 

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

Restricted Functionality with SBC for AWS

The following functionalities are not supported with SBC for AWS:

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