This document describes new features, the latest 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).
The SBC Core 07.02.xx documentation is located at the following Wiki space: SBC Core 7.2.x Documentation.
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.
The following Ribbon Bulletins are referenced in this release note:
To view/download Ribbon bulletins, do the following:
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
The SBC Core platforms address the next-generation needs of SIP communications by delivering media transcoding, robust security and advanced call routing, 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:
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.
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 backwards compatibility, refer to Ribbon Product Interoperability.
Refer to SBC 5000-7000-SWe Interoperability Matrices for the latest and minimum compatible product versions supporting the 07.02.00S400 release.
To instantiate the SBC instances, the following templates are used:
Prior to the 7.0 release, the default CLI admin user name and password for AWS SWe was admin/admin. Release 7.2 removes passwords for linuxadmin and admin users and enforces additional user account security practices for SBC SWe deployments in AWS.
The following significant changes are introduced in the SBC 07.02.00S400 instances on AWS:
support only SSH Key login for the “admin” and "linuxadmin" users
Sanity Checking - After AMI Instance Initiation
65GiB
of disk size.
Ribbon recommends m5.xlarge 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.
As of release 7.2S400, only following Instance types are supported for deployment in AWS:
m5.xlarge
m5.2xlarge
This release also provides Proof of Concept support for Google Cloud Platform (GCP) with Ribbon SBC.
The following SBC software versions are required for this release:
Use the EMA to verify the currently installed software versions.
Log on to the EMA, and from the main screen navigate to Monitoring > Dashboard > System and Software Info.
A software upgrade on SBC SWe should only be performed during periods of lower call activity. If the total number of active calls approaches the capacity limit of the SWe during upgrade, a double failure may occur tereby losing all active calls. If such a failure occurs, both active and standby SBC services will go down. Contact Ribbon Support immediately.
Release 7.2 of AWS requires that prior to upgrade you must update the user-data to include SSH keys for the admin account, and provide settings to enable creation of Linux cgroups to support 3rd Party application (cgroup only if needed). Please refer to the procedures in AWS SBC Software Upgrade Support.
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.
Once installed, resizing instances in AWS is not supported.
The following are the supported upgrade paths for this release.
The following features are included in the 07.02.00S400 Release.
For information on the features guide, refer to Feature Guides (7.2S400).
For more information on Public Cloud Performance Metrics, refer to Public Cloud Performance Metrics (7.2S400).
For features included in past releases, refer to:
For more information on Instantiating SBC SWe on Public Cloud, refer to Instantiating SBC SWe on Public Cloud (7.2S400).
For more information on Upgrading SBC SWe Public Cloud Instances, refer to Upgrading SBC SWe Public Cloud Instances (7.2S400)
The following issues are resolved in this release:
The following issues exist in this release:
The following limitations exist in this release:
m5.xlarge
m5.2xlarge
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 following functionalities are not supported with SBC Public Cloud:
Two stage calls
The following functionalities are not supported with SBC for AWS:
smarctl
disk status is not supported on Amazon instance.