SBC Edge 1000/2000 8.0.3 Release Notes

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

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

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 Edge upgrade. See Backing Up Data.

Step 2: Upgrade SBC Edge with Built-in ASM

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

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

SBC Upgrade Paths

Release	Upgrade to 8.0.3?
4.1.x
5.0.x
6.0.x
6.1.x
7.0.x
8.0.0
8.0.1
8.0.2

Important Note About Downgrades

SBC Edge 1000 software downgrades are not allowed on code prior to 6.1.0v450; SBC 2000 is not affected.

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

New Features

The following features are included in Release 8.0.3:

SYM-27456 E911 Support for Teams Direct Routing

The Ribbon SBC Edge can be configured to handle emergency calls from Microsoft Teams Direct Routing. This feature supports all providers that are supported by the Microsoft Direct Routing E911 solution. Once the emergency call is received from Microsoft Teams Direct Routing, the SBC prioritizes the emergency call.

For detailed information, refer to:

• Best Practice - Configure Emergency Call for Microsoft Teams Direct Routing

SYM-22743 Support for Azure AD Integration

With the SBC Edge, you can configure Microsoft Azure AD to automatically route calls from a SIP Trunk or PSTN to Microsoft Teams Direct Routing at the same time you migrate to Microsoft Teams. In a network scenario, a call arrives from the carrier and the SBC Edge uses Azure AD information to detect if the called user had already been migrated to Microsoft Teams, and then routes the call.

For detailed information, refer to:

• Best Practice - How to Automate Migration to Microsoft Teams Direct Routing via Microsoft Azure AD

CHOR-2063 Edit Object within an Object

The new Edit Object within an Object is a new WebUI feature which enables you to configure an additional option without leaving the current configuration table. For example, if you add a SIP Signaling Group but have not yet added the Call Route Table, you can then click on an option to add the Call Route table without having to leave the SIP Signaling group.

The following configuration tables are affected:

• Creating and Modifying Entries to Call Routing Tables
• Creating and Modifying Action Configurations
• Creating and Modifying Entries to Action Set Tables
• Configuring the SBC Edge for RADIUS
• Creating and Modifying Entries in SIP Server Tables
• Creating and Modifying Media Lists
• Creating and Modifying SIP Signaling Groups

Resolved Issues

The following issues are resolved in Release 8.0.3:

Security Updates and Fixes

The following are security updates and fixes in Release 8.0.3: