Table of Contents
This document describes new features, the latest hardware and software requirements, known limitations, and other pertinent release information for the latest release of Edge 8000 23.06.
The Edge 8000 23.06 documentation is located at the following Ribbon Wiki space: Edge 8000 23.06 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, 6500 Chase Oaks Blvd, Suite 100, Plano, TX 75023 U.S.A.. Use, disclosure, or reproduction in any form is strictly prohibited without prior authorization from Ribbon Communications.
For problems or questions, contact the Global Support Assistance Center:
Ribbon Support Portal: https://ribboncommunications.com/services/ribbon-support-portal
Voice: +1-833-RIBBON1 (1-833-742-2661)
Ribbon has built the Edge 8000 series from the ground-up, a newly designed platform that enables three of the most requested capabilities in a single edge device
A full-featured, Layer 3 edge router that can scale up to 10 Gbps, making it ideal for today’s cloud-first businesses that continually require greater bandwidth to optimize their cloud-based apps and storage.
Ribbon’s SBC SWe Edge software is co-resident on the platform to deliver market leading voice and video communications. The SBC capacity is licensed, making it cost effective for both small and large deployments.
All of these Edge 8000 features, functions and capabilities are built on top of a highly extensible and scalable Operating System (OS) that utilizes the combination of an industry hardened routing module from 6wind and equally industry hardened SWe Edge SBC functionality.
Release History
Release | Date | Purpose |
---|---|---|
Release 23.06 |
| Initial Release |
The following new features are included in this release:
Issue ID | Feature | Description |
---|---|---|
This is an initial release of the product. |
The following software versions are required for this release and are available for download from the Customer Portal:
Product | Date | File size | MD5 |
---|---|---|---|
Edge 8000 23.06 |
| 3050307584 | 86b090c15475e26dc6becbd7d668ee46 |
[root@e8000 e8k-data]# md5sum /e8k-data/CommonOs-alma.host-8.6-v23.6.0b20419-x86_64.iso
86b090c15475e26dc6becbd7d668ee46 /e8k-data/CommonOs-alma.host-8.6-v23.6.0b20419-x86_64.iso
Use the Edge 8000 WebUI to verify the currently installed software version.
Issue ID | Case No. | Sev | Problem Description | Resolution |
---|---|---|---|---|
This is an initial release of the product. |
Issue ID | Case No. | Sev | Problem Description | Resolution |
---|---|---|---|---|
This is an initial release of the product. |
There are no known issues of high severity in this release.
There are no known issues of other severity in this release.
Issue ID | Case No. | Sev | Problem Description | Resolution |
---|---|---|---|---|
AFN-1337 | 2 | [SWe Edge]:Have option to configure RAMP Server when tried to do upgrade with existing configuration | Should not have option to configure for RAMP Server in Edge8000_SweEdge under Settings->System->Node Level Settings. Workaround: Use the setupwizard to connect to the RAMP management platform. | |
AFN-1333 | 2 | Call functionality : Basic supplementary calls resulting in one-way audio issue | Issue occurs when CUCM is sending SRTP media to the Edge 8000. A call hold (MoH) when resumed can experience one-way audio. Workaround: Use RTP to allow the media to hairpin through the core SBC | |
AFN-1324 | 4 | [SWe Edge]:Alarms and Traps of SWe Edge are not visible on RAMP after doing partial factory Reset | A partial factory reset will not bring back the SNMP Target Address information automatically in the SWe Edge. Workaround: Set the SNMP Target Address information manually in the SWe Edge GUI. | |
AFN-1287 | 2 | G711U Proxy and G711U-G729 DSP load on 2VCPU | Up to 300 DSP calls supported | |
AFN-1216 | 2 | T38 Fax Calls: SWe Edge terminating new calls after first 60 calls are established | Only 60 T.38 sessions are supported with this release | |
AFN-1108 | 3 | SWe Edge (DSP mode) is not detecting fax tone when codec is g729 | Workaround: Use T.38 OR G.711 | |
AFN-1061 | 2 | Getting 503 service unavailable when the Signalling/Media IP is set to Auto in Signaling group. | Workaround: Configure the Signalling/Media IP as a static interface. | |
AFN-903 | 3 | Using SWe Edge both Extra interface were added & later one removed. SWe Edge shows Critical application Crashed and no interface appears for Extra interface 2 | Using the setupwizard to assign the interfaces be sure they are configured as required. Changing or deleting extra interfaces after the Swe Edge is configured to use this interface will result in unstable behavior. Workaround: If changes are require then remove then disable the Swe Edge interface, make the changes to the setupwizard and restart the system. Then re-enable the Swe Edge interface. | |
AFN-744 | 2 | Support for Reg-Info in contact header on Edge 8K | No workaround at this time. | |
AFN-685 | 2 | System cannot support 1000 concurrent Proxy calls due to RTP Packet Loss | Workaround: Up to 900 Proxy calls supported | |
AFN-628 | 2 | PRI overlap receive feature is not working | PRI Overlap is not supported for this release Workaround: none | |
AFN-468 | 2 | SWe Edge Wan Vlan : unable to get DHCP IP and ping wan side network - static IP fails too | SWe Edge Vlan is not supported for this release Workaround: Use untagged frames | |
AFN-1247 | 2 | After every Partial Reset/Reboot/Upgrade , routes are getting deleted , because of which UI's are unreachable | Workaround: A static route in Swe Edge maybe required | |
AFN-1341 | - | 2 | Internet is not working behind 8300 when any interface 'geX' is removed from BR4 members and separately configured for WAN interface | Using the setupwizard to configure the br4 settings and assigning a geX member when using DHCP type then re-configuring br4 with no interface members and disabling DHCP may not allow routing to work correctly. The system may still have the default gateway from DHCP in use. Workaround: Use the setupwizard default gateway menu to reapply the setting. |
Refer to component Release Notes for more information about component's new features, resolved issues, known issues and resolved security vulnerabilities.