Page History

Table of Contents

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.

Related Documentation

The Ribbon SBC Edge 1000/2000 documentation is located at the following Ribbon Wiki space: https://doc.rbbn.com/display/UXDOC80/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 

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.

Compatible Ribbon Releases

For complete interoperability details between the various Ribbon products, including backwards compatibility, refer to Ribbon Product CompatibilitiesInteroperability.

For the latest and minimum compatible product versions of other Ribbon products supporting this release, refer to SBC 1000-2000-SWE Lite Interoperability Matrix.

Required Software and Firmware Versions

This section provides information about any release-specific SBC Edge 1000/2000 firmware and software requirements.

The following software versions are required for this release and are available for download from the Customer Portal.

Software/Update Packages

How to Verify Currently Installed Software/Firmware Versions

Use the WebUI to verify the currently installed software version.

1. Open the WebUI and the click the System tab.
   
   
2. On the System page, click the Overview tab to view the the software version.

Upgrade Notes

This section contain specific upgrade notes for customers planning to upgrade to SBC Edge 1000/2000 8.0.2. For details on supported releases and upgrades, see SBC Upgrade Path Matrix.

Anchor
Prerequisites for Upgrades Prerequisites for Upgrades

SBC 1000/2000 Pre-Upgrade Requirements

Upgrade System Software Release 3.2 and prior

For details on upgrading earlier systems, refer to the applicable Upgrade Notes: Production Releases.

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.

Apply new SIP License (if required)

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

Upgrade SBC 1000/2000 System

Step 1: Backup Configuration - Mandatory

A configuration backup must be performed before proceeding with the SBC Edgeupgrade. See Backing Up Data.

Step 2: Upgrade SBC Edgewith Built-in ASM

Step 3: Upgrade the SBC EdgeCommunication 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

Microsoft has released the following Cumulative Updates for these respective Skype/Lync Server releases:

Perform the following to apply this update to the Skype/Lync deployed ASM:

1. Download the CU package from the Ribbon Support Portal.
2. 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:

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 

, 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).

Anchor
SBC Upgrade Path Matrix SBC Upgrade Path Matrix

SBC Upgrade Path

The following previously released versions of SBC Edge can be upgraded to Release 8.0.1. If the version you currently use is not on this list, please contact your Ribbon representative for assistance.

Caption
0 Table 1 SBC Upgrade Paths
Release Upgrade to 8.0.2? 4.1.x 5.0.x 6.0.x 6.1.x 7.0.x 8.0.0 8.0.1

Important Note About Downgrades

SBC Edge 1000 software downgrades are not allowed on code prior to the version listed below in order to prevent issues that could cause significant problems. Older SBC Edge 1000s, and all SBC Edge 2000s, are not affected.

This restriction does not apply to restoring a configuration (Configuration Restore) from an earlier version.

• 6.1.0v450

New Features

The following features are included in Release 8.0.2:

SYM-27208 Add Media Bypass Support Behind NAT

The SBC 1000/2000 is supported behind a NAT device in Microsoft Teams Direct Routing; this feature enables the SBC to use the IP of the NAT device as the source IP for all outgoing messages.

For detailed information, refer to:

• Best Practice - How to Configure the SBC Edge behind the NAT in Microsoft Teams Direct Routing
• Configure ISDN PSTN with Microsoft Teams
• Configure SIP Trunk with Microsoft Teams
• Configure an IP PBX with Microsoft Teams

Info
Microsoft Teams' Call Park and Shared Line Appearance (SLA) features are supported in release 8.0.2 and higher.

Resolved Issues

The following issues are resolved in Release 8.0.2:

Info
All resolved issues in SBC SWe Releases 7.0.x and SBC Edge 6.1.x are included in Release 8.0.2.

Caption
0 Table 1 Updates and Fixes
Issue Description SYM-25184 Call Handling improvements with Call forking SYM-25365 Handling of different Payload Type for Telephone-events SYM-25391 Message Translation Table Column Size Fix SYM-25462 SIP Server Failover improvements SYM-25506 Handling of early UPDATE when Call Setup in Progress SYM-25507 Handle larger referred-by headers from Teams SYM-25522 Call Control robustness improvements SYM-25530 Teams initiated call with two m-line with video SYM-25533 Annual Time Zone update 2018 SYM-25539 NTTDocomo with Teams Easy Config wizard scenario improvements SYM-25540 KDDI Easy Config fix for Split DNS SYM-25542 REGISTER requests handling improvements at the time of WAN recovery SYM-25548 Correct help link for DTLS-SRTP page SYM-25553 Handling the Retry-After header for calls SYM-25557 Teams support with SBC behind NAT SYM-25561 Easy config Wizard fix for KDDI SIP Trunk SYM-25563 Call Control stability improvements SYM-25569 Fix for NAT signalling public mask field SYM-25570 Update OpenSSL for CVE-2019-1559 fix SYM-25571 SBC uses the last codec negotiated instead of the configured codec list in SIP response SYM-25572 DNS SRV should use same connection for all messages SYM-25576 Call cleanup race condition handling SYM-27015 Correct help link for ASM operational status SYM-27018 Re-INvite handling on Server fail over improvements SYM-27026 SIP Trunk IOT testing at Telekom in Germany SYM-27027 DNS SRV FQDN changes and handling REGISTER enhancements SYM-27028 Fix for SBA Certificate Export SYM-27029 Offer/Answer enhancements for T38 parameters. SYM-27034 Call Forking handling enhancements SYM-27047 SBC sends REGISTER messages to endpoints alternately when multiple endpoints are configured in SIP server table SYM-27057 Send SIP PDU at INFO level for Ribbon Protect SYM-27076 SIP robustness improvements SYM-27162 Support SBC behind NAT along with SYM-25557 SYM-27175 Remove Diversion header from ACK message if present in original INVITE SYM-27204 Easy Config Wizard for Teams for SBC behind NAT SYM-27206 Handle race condition in FailOver feature when invite and register fails on same server SYM-27223 Fix applying SMM to Notify method SYM-27230 SBC sets the refresher parameter incorrectly while responding 200 OK of UPDATE SYM-27242 Call Control stability enhancements SYM-27300 Handle PRACK call flows for 181 responses