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

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

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

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

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

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.1.0. If the version you currently use is not on this list, please contact your Ribbon representative for assistance.

Note
title 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 SWe Lite Documentation Home Page.

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

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

Info
All resolved issues in SBC SWe Releases 7.0.3 and SBC Edge 6.1.6 are included in Release 8.1.

Caption
0 Table 1 Updates and Fixes
Issue ID Problem Description SYM-24154 Support for Multiple SAN entries when creating a CSR SYM-24940 Simplified Teams Direct Routing Carrier support through the Transformation table SYM-27422 The  Spacevars 0 longproduct have DSPs that support asymmetric codec handling, which means these SBCs can handle both the SDP answer and SDP offer that contain multiple codecs. The  Spacevars 0 product3 has virtual DSPs that do not support the handling of asymmetric codecs, so the  Spacevars 0 product3 has implemented the ability to lockdown on a single codec to avoid asymmetric codec handling. Asymmetric codec handling can cause potential issues for audio handling, so the SBC must have consistent behavior between the Spacevars 0 longproduct and the Spacevars 0 product3 . To resolve this issue, the Spacevars 0 longproduct have a single codec lockdown functionality that allows the Spacevars 0 longproduct to lockdown on a single codec (first match) when responding to an SDP offer from a peer, and send a re-Invite with a single codec on receiving an SDP answer that contains multiple codecs from the peer.

Known Issues

The following known issues exist in this release:

Caption
0 Table 1 Known Issues 3 Known Issues
Issue ID Problem Description Impact/Workaround SYM-27702 Call Counter not Accurately Displaying Call Count When Call Fails due to Unavailable License For example, the Global Call Counters table incorrectly displays that 51 calls succeed when 50 SILK licenses and a larger number of DSP licenses are available, and you make 51 calls that require SILK. Since there is no license, call 51 fails. Impact: There are potentially incorrect global call statistics when the SBC rejects calls that require SILK because there is no license. Workaround: None.

New Features in This Release

SYM-9096 Add SILK - Super Wideband Audio Codec to SBC Edge Products

The SBC 1000/2000 supports the SILK audio codec. Skype designates SILK as an internet wideband audio codec for use in VoIP. During the call setup for SILK transcoded calls, the SBC Edge obtains the DSP Transcoding license and SILK Transcoding licenses.

For details, refer to:

• Protocols and Functions Supported
• Creating and Modifying Voice Codec Profiles
• Working with Licenses

SYM-21115 Additional Confirmation Warning Added

For the SBC 2000, the ethernet port must be enabled for continued access to the management interface. If you attempt to disable the Ethernet Port with the status of "Up," a warning message is displayed.

For details, refer to:

• Configuring Ethernet Ports on the SBC Edge 2000
• Managing Ethernet Ports

SYM-23201 Support SCOM for 2016

The SBC Edge supports SCOM (Microsoft System Center Operations Manager) 2016. The SCOM Management Pack allows customers in a Microsoft Server Environment to monitor the health of the SBC Edge system using SCOM.

For details, refer to:

• Working with SCOM

SYM-23703 Ribbon Protect "Bad Number" Table Added

Protect uses the CDRs/logs generated by the SBC Edge to identify bad actors. These bad actors are blocked from accessing the SBC Edge through a dynamic black listing mechanism. The REST Interface helps Protect to enable these actors to be blacklisted by SBC Edge.

For details, refer to:

• Configuring SBC Edge to Create Bad Actors from Protect Data

SYM-25157 Easy Configuration Wizard for the SoftBank "ConnecTalk"

The Easy Configuration Wizard adds the SoftBank ConnecTalk option to the SIP Trunk field for SIP Trunk applications.

For details, refer to:

• Configure SIP Trunk with Microsoft On Premises
• Configure SIP Trunk with ISDN PBX
• Configure SIP Trunk with IP Phones
• Configure a SIP Trunk With IP PBX
• Configure SIP Trunk with Microsoft Teams

SYM-25442 Display Last Login on Top Banner

The last login time/date is displayed on the WebUI login screen.

For details, refer to:

• Logging into the SBC Edge

SYM-25429 Option to Acknowledge the Pre-Login Message before logging into the WebUI

A new Acknowledge Pre-Login Message appears on the WebUI login screen; this checkbox enables the user to acknowledge the Pre-Login message before entering the system.

For details, refer to:

• Managing Global Security Options

SYM-27016 RASO: Allow Domain Controllers to be Disabled

This feature allows the user to enable or disable the domain controller.

For details, refer to:

• Managing Domain Controllers
• Adding and Modifying Domain Controllers
• Configuring the SBC Edge for Active Directory User Domain Access

SYM-27201 Implement Multiple Certificate Support

The SBC 1000/2000 supports multiple certificates to migrate from one enterprise to another. The Web UI updates the SBC Edge Certificate screen name to SBC Primary Certificate and adds the SBC Supplementary Certificates screen. The Create TLS Profile window adds the Certificate drop-down menu in the Client Attributes and Server Attribute sections.

Info
title Note
The SBC 1000/2000 can use multiple certificates to support multiple enterprises that require the mutual authentication and verification of certificates to use the certificates with each enterprise.

For details, refer to:

• Creating and Modifying TLS Profiles
• Managing Supplementary Certificates
• Managing Primary Certificates
• Connect SBC Edge to Microsoft Teams Direct Routing for Enterprises with Skype for Business On-Premises
• Connect SBC Edge to Microsoft Teams Direct Routing for Enterprises with Cloud PBX