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.
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
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.
There are no Associated Ribbon Announcements with Release 8.0.
To view/download Ribbon announcements, do the following:
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
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).
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.00R000 | 04.02.03R000 | 04.02.03R000 | 04.02.03R000 | 6.1.0, 6.1.1, 6.1.2, 7.0.0
|
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.
This section provides information about any release-specific SBC Edge 1000/2000 hardware and software requirements.
The following softare 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.0.0.build502.img |
SBC 2000 Software | sbc2000-release-8.0.0.build502.img |
SBC Comms | UXCOMMSVS-release-8.0.0.build502.zip |
Use the WebUI to verify the currently installed software version.
This section contain specific upgrade notes for customers planning to upgrade to SBC Edge 1000/2000 8.0. For details on supported releases and upgrades, see SBC Upgrade Path Matrix.
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.
For details on upgrading earlier systems, see the following:
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.
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.
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.
If the eUSB upgrade is executed, all logs and core dumps will be lost. However the SBC configuration will not be affected.
A configuration backup must be performed before proceeding with the SBC Edge upgrade. See Backing Up Data.
For ASM Windows Support Specifications and Lync SBC Edge Versions which require different Operating Systems, please Log in to view Notes and Limitations.
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.
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:
Perform the following to apply this update to the Skype/Lync deployed ASM:
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:
Follow the general upgrade procedure outlined in Upgrading or Downgrading the SBC 1000/2000.
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).
The following previously released versions of SBC Edge can be upgraded to Release 8.0.0. 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.0? |
---|---|
4.1.x | |
5.0.x | |
6.0.x | |
6.1.x | |
7.0.x |
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.
All resolved issues in SBC SWe Releases 7.0.3 and SBC Edge 6.1.6 are included in Release 8.0.
The following known issues exist in this release:
Known Issues
Issue ID | Problem Description | Impact/Workaround |
---|---|---|
SYM-25106 | Teams Consultative Transfer fails to connect to PSTN (Media Bypass) A Microsoft consultative transfer issue causes call transfers to fail between a TEAMS client and the PSTN. | Impact: Call transfers fail. Workaround: None. |
SYM-25098 | When Early 183 is enabled Teams drops inbound calls in 15 seconds If Early Media is enabled, disable Early Media on the Teams Direct Routing SIP Signaling Group. This is a known Direct Routing issue until a fix is provided from Microsoft. | Impact: Inbound calls dropped after 15 seconds. Workaround: Disable Early Media. |
For Release 8.0, the SBC Edge, ASM, CCE and LX have been rebranded to reflect Ribbon.
An SBC 1000 or SBC 2000 device running Release 7.0.2 is certified to offer Microsoft Teams Direct Routing services for Non-Media Bypass call flows. Release 8.0 is at present a candidate software build for Direct Routing Media Bypass call flow-related certification in Q4 2018; upon successful certification, Ribbon and Microsoft will update the marketplace accordingly. For more information regarding SBC use cases and configuration in support of Non-Media Bypass and Media Bypass call flows, refer to:
Microsoft supports only certified devices (such as the Ribbon SBC Core and SBC Edge) to connect to the Phone System to accomplish Direct Routing. Refer to the List of Session Border Controllers certified for Direct Routing for information regarding the certification process, along with the benefits of deploying a certified SBC in support of Direct Routing.
Enables Real-time Transport Protocol (RTP/RTCP Multiplexing) for combining the two protocols' packets (RTP for data traffic and RTCP for control information) onto a single multiplexed UDP port. RTP/RTCP Multiplexing is supported according to RFC 5761, in which the SDP contains the value of a=rtcp-mux.
For more information, refer to:
Microsoft's Cumulative Updates include bug fixes and new features for the Skype for Business Server server (such as the SBA). Once Microsoft releases these updates, Ribbon validates them and creates an ASM_CU package (which includes the ASM Roll-up file), which is available via Ribbon Support Portal for installation. This new feature tracks the progress of the ASM Roll-up installation; the new progress bar signals that the upload is running in the background.
For more information, refer to:
Enables more security by supporting a TLS 1.2-Only configuration option (for supporting TLS 1.2 as described in RFC 5246), in addition to the TLS 1.0-1.2 configuration option.
For more information, refer to:
Time of Day enables the SBC to select a route for a call based on the local time and date; this option allows each specific route to optionally be selected based on the current local system time. The Time of Day tables define a group of Time of Day entries which specify times and days of the week.
For more information, refer to:
Polycom introduced on 5.8 firmware a feature called PSTN Failover. This feature allows creation of a Local Survivability configuration for Skype for Business users if Skype servers (for either Office 365 or On Premises) are unavailable. When Local Survivability is configured for Polycom VVX phones, phones can fall back to an appropriately configured SBC Edge if connectivity to Skype is lost. Refer to the following Best Practice for details:
Release 8.0 includes a set of tools that test port readiness for the services required for CCE or Microsoft Teams Direct Routing. Connectivity Check tools enable Ribbon Support to work with deployment teams to prevent service issues due to firewall configuration and other issues.
For more information, refer to Working with Connectivity Check -- Verifying Service and Port Requirements for CCE and Teams.
The Failover SIP Registration feature allows the SBC to handle registration to, and subsequent call processing to a secondary SIP server if the primary SIP server fails – for example, if the primary server, becomes unreachable, has registration expiration with re-registration failure, or refuses to accept registrations/calls for some other reason. Failover SIP registration is completed according to the Priority order of the SIP Servers. For more information, refer to:
During transformation table export, the WebUI displays a list of all transformation tables as you select one or more tables to export as XML-formatted files. For more information, refer to Importing and Exporting Transformation Tables.
After a packet capture is performed on an SBC 1000/2000, the WebUI includes an option for restarting or repeating the last packet capture performed. For more information, refer to Working with Packet Capture and Packet Capture - Best Practice.
The Easy Configuration Wizard for Microsoft Teams Direct Routing adds Easy Configuration templates for the following Provider-to-User configuration scenarios:
The IP PBX template that previously addressed user-side configuration only now provides easy configuration for both the User and Provider sides. In addition, the Microsoft UC scenario has been renamed to "Microsoft On Premises." For more information, refer to:
With the addition of the ICE (Interactive Connection Establishment) Lite Agent Support feature, the SBC 1000/2000 now supports both full and lite implementations of ICE as described in RFC 8445. ICE lite, for public Internet ICE agents, interfaces to the Microsoft TEAMS Direct Routing interface. The SBC 1000/2000 integrates Microsoft Teams clients by acting as an ICE lite agent endpoint for SIP calls involving Network Address Translators (NATs). This feature enables direct routing between an existing enterprise voice infrastructure (that is, the PSTN carrier and SIP trunks used for trunking services) and the Microsoft Phone System in Office 365. The SBC acts as a PSTN gateway; sessions for Microsoft Teams users can be routed directly to the PSTN through the SBC.
For more information, refer to:
The Datagram Transport Layer Security (DTLS) - Secure RTP (SRTP) Support feature extends the DTLS protocol as described in RFC 5764. DTLS-SRTP is used to negotiate SRTP keying between the SBC 1000/2000 and Microsoft Teams over the UDP media port. The negotiated keys are used for encryption and decryption of all media (RTP) packets being sent/received through the port used for DTLS-SRTP.
For more information, refer to:
Microsoft Edge is now included as a list of supported browsers in the SBC Edge.
For more information, refer to: