Table of Contents
Ribbon SBC Edge Release 8.1.5 build 538.
About SBC Edge 1000/2000 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 the Ribbon SBC Edge 1000/2000.
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, open a Web browser and navigate to the Resource Library on the corporate website (https://ribboncommunications.com/company/get-help/resource-library).
Related Documentation
The Ribbon SBC Edge 1000/2000 documentation is located at the following Ribbon Wiki space: https://doc.rbbn.com/display/UXDOC81/Ribbon+SBC+Edge+Documentation
Release Notes Use and Distribution
Ribbon product 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 Announcements
To view/download Ribbon announcements, do the following:
- Log onto the Ribbon Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login).
- From the Quick Access menu, click and download the "Ribbon Support Portal User Guide," and navigate to the "ANNOUNCEMENTS tab" section for instructions on how to search for and view announcements.
Problems or Questions
For problems or questions, contact the 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 Edge 1000/2000
The SBC Edge platforms address the next-generation needs of SIP communications by delivering embedded media transcoding, robust security and advanced call routing in a high-performance, small form-factor device 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).
Interoperability
The table below shows interoperability between different Ribbon products. If you are upgrading from one SBC 1000/2000 to another, refer to the upgrade matrix at SBC Upgrade Path Matrix.
Sonus Product Releases Supporting Latest SBC Edge Features
| SBC SWe Lite |
|---|
7.0.0, 7.0.4, 8.0.3, 8.1.5 |
Compatible Ribbon Releases
When upgrading your network, ensure to upgrade each Ribbon product to the most current release to take advantage of the latest features, enhancements, and fixes.
For complete interoperability details between the various Ribbon products, including backwards compatibility, refer to Ribbon Product Interoperability.
For the latest and minimum compatible product versions of other Ribbon products supporting this release, refer to SBC 1000-2000-SWE Lite Interoperability Matrix.
Hardware and Software Requirements
This section provides information about any release-specific SBC Edge 1000/2000 hardware and software requirements.
Required Software Versions
The following software versions are required for this release and are available for download from the Customer Portal
| Product | Software/Update Package |
|---|---|
| SBC 1000 Software | sbc1000-release-8.1.5.build538.img |
| SBC 2000 Software | sbc2000-release-8.1.5.build538.img |
| SBC Comms | UXCOMMSVS-release-8.1.5.build538.zip |
Note
Due to an engineering/manufacturing update, alarm ID 5.32 ASM and SBC Firmware Mismatch may trigger after deploying a new SBC node. As a fix, ensure the SbcComms is updated.
How to Verify Currently Installed Software/Firmware Versions
Use the WebUI to verify the currently installed software version.
- Open the WebUI and the click the System tab.
- On the System page, click the Overview tab to view the the software version.
Upgrade Notes
This section contains specific upgrade notes for customers planning to upgrade to SBC Edge 1000/2000 8.1.5. For details on supported releases and upgrades, see 326376840.
SBC 1000/2000 Pre-Upgrade Requirements
Warning: Before You Upgrade
Before you upgrade the SBC, follow the Pre-Upgrade Requirements below. Failure to follow these instructions may lead to the SBC Edge becoming inoperative and requiring factory service.
Upgrade System Software Release 3.2 and prior
For details on upgrading earlier systems, see the following:
- SBC 1000-2000 3.2 Upgrade Notes
- SBC 1000-2000 3.1 Upgrade Notes
- SBC 1000-2000 3.0 Upgrade Notes
- SBC 1000-2000 2.2 Upgrade Notes
- SBC 1000-2000 2.1 Upgrade Notes
- SBC 1000-2000 2.0 Upgrade Notes
- SBC 1000-2000 1.3 Upgrade Notes
Upgrade Boot Image - Recommended
A new Boot Image upgrade (U-Boot 3.1.6o) is available with the release of the SBC 1000/2000 R3.1.0 b283 software.
Although upgrading the Boot Image is not mandatory, it is highly recommended. This release of the Boot Image remedies a known issue with resetting the SBC Edge to factory defaults.
Apply new SIP License (if required)
Running releases older than Release 3.0 require an upgraded SIP license key.
The new SIP license key must be applied before upgrading the system software.
All SIP-SIP call sessions now require a SIP license. Systems purchased before March 31, 2013 and provided with free SIP Licenses are grandfathered, and no purchase is necessary. Contact your Ribbon sales representative to acquire a new (free) SIP license key.
Only one call case requires a SIP call license. This is the case where both inbound and outbound channels are SIP. The exception for SIP calls to another SBC Edge 1000/2000, the Ribbon Tenor Series, or the Ribbon VX Series, however, still exists. If one or both of the call legs are to one of these devices,then a SIP call license will not be used.
Upgrade SBC 2000 eUSB Flash Drive - Automatic
The eUSB based flash drive may require a firmware update. This is an automatic process and is executed as a part of the internal upgrade process. If the eUSB firmware is upgraded, the SBC 2000 reboot process will run approximately one minute longer than usual.
This is applicable to the SBC 2000 only.
NOTE: Loss of Logs and Core Dumps
If the eUSB upgrade is executed, all logs and core dumps will be lost. However the SBC configuration will not be affected.
Upgrade SBC 1000/2000 System
Step 1: Backup Configuration - Mandatory
A configuration backup must be performed before proceeding with the SBC Edge upgrade. See Backing Up Data.
Step 2: Upgrade SBC Edge with Built-in ASM
For ASM Windows Support Specifications and Lync SBC Edge Versions which require different Operating Systems, please Log in to view Notes and Limitations.
Step 3: Upgrade the SBC Edge Communication Service
Upgrading the SBC Edge Communications Service is covered in the general SBC upgrade guide. Make sure that it is upgraded, then follow the remaining instructions here; extra steps are required to update the ASM Recovery Partition.
Step 4: Install Skype/Lync SBA Server Cumulative Updates
You may skip this section if your SBC 1000/2000 hardware is not configured with a built-in ASM deployed as a Skype/Lync SBA.
Microsoft has released the following Cumulative Updates for these respective Skype/Lync Server releases:
Unable to render {include} The included page could not be found.
Perform the following to apply this update to the Skype/Lync deployed ASM:
- Download the CU package from the Ribbon Support Portal.
- Follow the instructions outlined in Installing Cumulative Updates for Skype/Lync SBA.
Step 5: Install Windows Service Packs and Windows Updates Using ASM Roll-up Update
Windows Service Packs and Windows Updates are installed using the ASM Roll-up Update feature. Ribbon publishes Update Packs on a regular basis through the Ribbon Support Portal. The Update Packs work with Windows Update and other Non-Windows updates in order to keep the ASM up-to-date. The Update Packs contain tested and authorized Windows updates. Note that the Update Packs do not contain the actual Windows Service Packs and Updates. Once the Update Pack has been installed, the Windows Update State link in the Operational Status section will change to Updates Available - Install. The actual updates are installed using this link.
Below is the latest ASM Roll-up available:
Unable to render {include} The included page could not be found.
Step 6: Perform the Upgrade
Follow the general upgrade procedure outlined in Upgrading or Downgrading the SBC 1000/2000.
Additional Upgrade Notes
Self-Signed Server Certificate 5.0 and later - SHA2-256 Support
For Release 5.0 and later in the SBC Edge, the SHA-1 self-signed certificate is automatically replaced with the stronger SHA2-256 CA certificate (regardless of expiration). This adheres to Microsoft's plan policy announcement for Certificate Authorities (CAs) that deprecates the use of the SHA1 algorithm in SSL and code signing certificates, in favor of SHA2. For more information, see Microsoft's SHA1 Deprecation Policy.
Beginning in January 2017, Mozilla Firefox now supports SHA-1 certificates. To support this browser, the node must be upgraded to Release 5.0 or later to replace the existing self-signed certificate (SHA1) with an updated self-signed certificate (SHA 2-256).
SBC Upgrade Path
The following released versions have been validated with Release 8.1.5. If the version you currently use is not on this list, please contact your Ribbon representative for assistance.
ATTENTION
This release includes all bug fixes implemented in the release which are documented in the Supported Upgrade Paths. To view bug fixes in previous releases, refer to the release notes(s) of interest from the SBC 1000 - 2000 Documentation Home Page.
SBC Upgrade Paths
| Release | Upgrade to 8.1.5? |
|---|---|
| 7.0.x |  |
| 8.0.x | |
| 8.1.x | |
Important Note About Downgrades
SBC Edge 1000 software downgrades are not allowed on code prior to 6.1.0v450; the SBC 2000 is not affected.
This restriction does not apply to restoring a configuration (Configuration Restore) from an earlier version.
Resolved Issues
The following resolved issue exists in this release:
Resolved Issues
| Issue ID | Problem Description |
|---|---|
| SYM-27806 | SBC Handling of ReINVITE after Challenge Improvements. |
| SYM-27971 | Branch Tag Handling for Re-INVITE. |
| SYM-27989 | Call Routing Entries to Handle Parenthesis ( ) Characters. |
| SYM-27669 | Remove Limitation of Maximum Outbound Call SIP Dialogs. |
| SYM-28018 | Failed to Set Ethernet Port Redundancy State Correctly. |
| SYM-27978 | Audio Quality Issues Fixed for Silk Codec. |
| SYM-27977 | Allow to Import Two Different main certs. |
| SYM-28013 | SIP SG Down Due to Linked Peer SG down Could Still Process Incoming SIP Option. |
Known Issues
The following known issues exist in this release:
Known Issues
| Issue ID | Problem Description | Impact/Workaround |
|---|---|---|
| CHOR-5062 | Hold & Resume. Interoperability issue between SBC SWE Lite and Teams: Hold & Resume Call to Team from PSTN (Media Anchoring Internal) fails. Call Park. Interoperability issue between SBC SWE Lite and Teams: Call Park call to Teams from PSTN (Media Anchoring Internal) fails. | Impact: Impacts SBC 1000/2000 and SBC SWe Lite 8.1.5 and later, until resolved. Workaround: None. |
| SYM-28092 | Conference Call Failure in Central SBC 2000 When using the SBC 2000 as the Central SBC, conference calls fail. | Impact: Conference calls may also fail when using the SBC 2000 as the Proxy SBC. Impacts SBC 1000/2000 8.1.5 and later, until resolved. Workaround: Use the SBC SWe Lite as the Central SBC or Proxy SBC. |
| SYM-28118 | No Media between PSTN Endpoints after Consult Transfer in Central SBC 2000 When using the SBC 2000 as the Central SBC, there is no media between the PSTN endpoints after you perform a consult transfer to the second PSTN endpoint. | Impact: When using the SBC 2000 as the Proxy SBC, there may also be no media between the PSTN endpoints after you perform a consult transfer. Impacts SBC 1000/2000 8.1.5 and later, until resolved. Workaround: Use the SBC SWe Lite as the Central SBC or Proxy SBC. |
New Features in This Release
CHOR-2432 Local Media Optimization
The SBC Edge can be configured for Local Media Optimization for Microsoft Teams Direct Routing. Local Media Optimization allows the Microsoft Teams Direct Routing media flow to always use the shortest path to improve the SBC Edge's media quality and bandwidth usage. The Microsoft Teams Direct Routing media flow can be directly establish between the Teams client and the SBC, even if the SBC does not have Microsoft Teams Direct Routing connectivity.
For detailed information, refer to:
Overview
Content Tools