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.
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:
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.x, 7.0.x
|
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.1.build508.img |
SBC 2000 Software | sbc2000-release-8.0.1.build508.img |
SBC Comms | UXCOMMSVS-release-8.0.1.build508.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.1. 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, refer to the applicable Upgrade Notes: Production Releases.
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
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.1. 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.1? |
---|---|
4.1.x | |
5.0.x | |
6.0.x | |
6.1.x | |
7.0.x | |
8.0.0 |
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.4 and SBC Edge 6.1.6 are included in Release 8.0.1.
Updates and Fixes
Issue ID | Problem Description |
---|---|
SYM-24510 | Generate warning when TDM clock source changes |
SYM-24880 | Easy 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-25106 | TEAMS Consultative Transfer fails to connect to PSTN with Media Bypass enabled |
SYM-25130 | Call drops after 20 seconds when using Teams Relay candidate |
SYM-25206 | WebUI: SMM - handle special chacter in Regex value |
SYM-25239 | Non-numeric characters accepted by Payload Type field |
SYM-25248 | System tab to identify SBC 1000 which has internal eUSB |
SYM-25284 | REST API improvements for ACL |
SYM-25320 | Cseq value in CANCEL is not the same as INVITE's value but uses PRACK's value |
SYM-25330 | Allow Teams call transfer without SIP license |
SYM-25336 | Easy config for Teams needs to set the ACL media port range based on chassis type |
SYM-25377 | TLS connection is deleted at the end of call, although the reuse flag is enabled |
SYM-25340 | SBC sets wrong IP address to c=line in INVITE for Teams Direct Routing |
SYM-25343 | Populate CPU utilization in process table |
SYM-25346 | IPSEC: SBC Edge not able to establish IPSEC tunnel with SBC Core tunnel Mode |
SYM-25353 | SIP stack stability improvements |
SYM-25355 | RBA menu is not displayed on the WebUI |
SYM-25369 | Restart packet capture shows VLAN IP |
SYM-25370 | Skype/Lync Presence Destination should only allow TLS Servers |
SYM-25385 | MSFT Teams:No RingBack to PSTN when Teams blind transfers to another Teams/S4B user |
SYM-25417 | SBC sets wrong IP address to host portion of From header in OPTIONS |
SYM-25418 | Handle SMM rules for Fwd Reg after Local Processing |
SYM-25419 | SBC Edge not allowing Remote SIP server IP Port 1002 to 1007, which is unassigned as per IANA |
SYM-25444 | Support to allow more than 300 sec to T301 timer |
SYM-25456 | Move the DTLS Profile resource URL mapping to commonHW |
Security Updates and Fixes in this release are listed below:
Security Updates and Fixes in this Release
Issue ID | Problem Description |
---|---|
SYM-25362 | SBC Edge 1000/2000 Release 8.0 not reachable after initial configuration |
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.