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.

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

For SBC SWe Lite

SWe Lite Release 7.0.4 is the current GA release; SWe Lite Release 8.0.0 will be available shortly.

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

The following is an Associated Ribbon Announcement for Release 8.0.1:

Warning-18-00028544. SBC Edge 1000/2000 Release 8.0 not reachable after initial configuration.
 

To view/download Ribbon announcements, do the following:

  1. Log on to the Ribbon Support Portal (https://ribboncommunications.com/services/ribbon-support-portal-login).
  2. From the Quick Access menu, click and download the "Ribbon Support Portal User Guide", and navigate to the "ANNOUNCEMENTS tab" section for instructions 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

EMS
 SBC 5000 Series
SBC 7000 Series
SBC SWE
SBC SWe Lite
V10.01.00R00004.02.03R00004.02.03R00004.02.03R000

6.1.x, 7.0.x

 

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 softare versions are required for this release and are available for download from the Customer Portal

ProductSoftware/Update Package
SBC 1000 Software

sbc1000-release-8.0.1.build508.img 

SBC 2000 Softwaresbc2000-release-8.0.1.build508.img
SBC CommsUXCOMMSVS-release-8.0.1.build508.zip

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.1. For details on supported releases and upgrades, see SBC Upgrade Path Matrix.

SBC 1000/2000 Pre-Upgrade Requirements

Warning: Before You Upgrade

Before you upgrading 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

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

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:

  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:

Unable to render {include} The included page could not be found.

Step 6: Perform the Upgrade

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

SBC Upgrade Paths

ReleaseUpgrade to 8.0.1?

4.1.x

(tick)
5.0.x(tick)
6.0.x(tick)
6.1.x(tick)
7.0.x(tick)
8.0.0(tick)

Important Note About Downgrades

SBC Edge 1000 software downgrades are not allowed on code prior to the versions 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.

  • 4.1.7v397
  • 5.0.5v417
  • 6.0.1v439
  • 6.1.0v450

Resolved Issues

All resolved issues in SBC SWe Releases 7.0.4 and SBC Edge 6.1.6 are included in Release 8.0.1.

Updates and Fixes

Issue IDProblem Description
SYM-24510Generate warning when TDM clock source changes
SYM-24880Easy Config: same DS1 port can be selected for both primary and secondary clock port
SYM-25098

When Early 183 is enabled Teams drops inboud calls in 15 seconds.

SYM-25106TEAMS Consultative Transfer fails to connect to PSTN with Media Bypass enabled
SYM-25130Call drops after 20 seconds when using Teams Relay candidate
SYM-25206WebUI: SMM - handle special chacter in Regex value
SYM-25239Non-numeric characters accepted by Payload Type field
SYM-25248System tab to identify SBC 1000 which has internal eUSB
SYM-25284REST API improvements for ACL
SYM-25320Cseq value in CANCEL is not the same as INVITE's value but uses PRACK's value
SYM-25330Allow Teams call transfer without SIP license
SYM-25336Easy config for Teams needs to set the ACL media port range based on chassis type
SYM-25377TLS connection is deleted at the end of call, although the reuse flag is enabled
SYM-25340SBC sets wrong IP address to c=line in INVITE for Teams Direct Routing
SYM-25343Populate CPU utilization in process table
SYM-25346IPSEC: SBC Edge not able to establish IPSEC tunnel with SBC Core tunnel Mode
SYM-25353SIP stack stability improvements
SYM-25355RBA menu is not displayed on the WebUI
SYM-25369Restart packet capture shows VLAN IP
SYM-25370Skype/Lync Presence Destination should only allow TLS Servers
SYM-25385MSFT Teams:No RingBack to PSTN when Teams blind transfers to another Teams/S4B user
SYM-25417SBC sets wrong IP address to host portion of From header in OPTIONS
SYM-25418Handle SMM rules for Fwd Reg after Local Processing
SYM-25419SBC Edge not allowing Remote SIP server IP Port 1002 to 1007, which is unassigned as per IANA
SYM-25444Support to allow more than 300 sec to T301 timer
SYM-25456Move the DTLS Profile resource URL mapping to commonHW

Security Updates and Fixes

Security Updates and Fixes in this release are listed below:

Security Updates and Fixes in this Release

Issue IDProblem Description
SYM-25362SBC Edge 1000/2000 Release 8.0 not reachable after initial configuration

New Features in This Release

SYM-25270 Support to covert Disconnect P1=8 to Progress

The SBC now supports the SBC sending a 183 with SDP when it receives a DISCONNECT with PI=1,8. In the ISDN Signaling Group, this new parameter Convert DISC PI=1,8 to Progress is available when the Play Inband Message Post-Disconnect fiels is set to Yes - Until Timer Expiry. For details, refer to Creating and Modifying ISDN Signaling Groups.