| Add_workflow_for_techpubs |
|---|
| AUTH2 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
|---|
| AUTH1 | UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'} |
|---|
| JIRAIDAUTH | TP-577 |
|---|
| REV5 | UserResourceIdentifier{userKey=8a00a0c866dc3dee0166ea60b86f0014, userName='null'} |
|---|
| REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
|---|
| REV3 | UserResourceIdentifier{userKey=8a00a0c8664c0be0016687d83fdb0025, userName='null'} |
|---|
| REV1 | UserResourceIdentifier{userKey=8a00a0c8601a1bc701602339d1190006, userName='null'} |
|---|
|
Table of Contents
About
16.1.0 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 documentation is located at the following Wiki space: EdgeView 16.1.0 Documentation Home .
Release Notes Use and Distribution
product release notes are protected under the copyright laws of the United States of America. This work contains proprietary information of , Use, disclosure, or reproduction in any form is strictly prohibited without prior authorization from .
Problems or Questions
For problems or questions, contact the Ribbon Support through telephone or fax:
- Ribbon Support Portal: https://ribboncommunications.com/services/ribbon-support-portal
- Voice: +1-833-RIBBON1 (1-833-742-2661)
- Japan Support Assistance Center: +81-3-6414-8550 (Japanese Language Support)
- Former Edgewater Networks Technical Assistance Center: +1-408-351-7200,#2 or +1-408-351-7255 (Americas), +44-203-769-0576 (EMEA)
About
offers a multi-tenant approach for remote configuration and central management of Intelligent Edges . The Service Control Center also offers auto-provisioning of VoIP phones without the overhead of running a complex software on separate hardware.
Using the software, enterprises and service providers can monitor and troubleshoot VoIP performance statistics from a central location, thus enhancing the support services provided to their customers. As a virtualized micro-services based appliance, offers excellent scale, high performance, agility, and cost-effectiveness providing a solid secure foundation for those enterprises and managed service providers considering hosted or managed, premise cloud or hybrid UCaaS offerings.
manages networks of all sizes. can be deployed as a standalone system or in a high-availability virtualized micro-service configuration for carrier-grade environments.
version 16.1.0 supports the following platforms:
- 302/304
- 2900
- 4550v2
- 4806v2
- 4808v2
- 6000
- 7304
Refer to EdgeView and EdgeMarc Interoperability Matrix for a detailed
interoperability matrix.
Required Software Versions
The following software versions are required for this release and are available for download from the Customer Portal:
| Product | Date | Software/Update Package |
|---|
EV 16.1.0 Software
| 12/18/220 | Filename : cluster-install-ev.sh Filesize: 26408
Filename: install-ev.sh Filesize: 26714
Filename: ev-fullpkg.tar.xz Filesize: 3492719423 |
How to Verify Currently Installed Software/Firmware Versions
Use the WebUI to verify the currently installed software version.
- Open the WebUI and click the Admin tab.
- On the Admin page, you can see the current software version under Software Version.
Upgrade Notes
This section contains specific upgrade notes for customers planning to upgrade to
16.1.0.
For details on supported releases and upgrades, see Upgrade EdgeView .
| Info |
|---|
For an Swap (eSWAP) use case, can be configured to automatically import legacy devices and collections from 14.x.x to 16.x.x. Once configured, any future 14.x.x modifications are automatically reflected on 16.x.x. To synchronize an 14 with an 16, refer to Synchronize EdgeView 14 with EdgeView 16.
|
Resolved Issues - Severity 1
There are no resolved issues of high severity in this release.
Resolved Issues - All Other Severities
| Issue ID | Case No. | Sev | Problem Description | Resolution |
|---|
| 1 | SCC-8133 | 201005-339131 | 2 | The container was not recovering from a container based interruption. | This has been fixed. |
| 2 | SCC-8111 | 200929-338234, 201016-341086, 201130-347809 | 2 | The GUI seems slow (when changing between devices in the 'Device List' page) as a result of the container being unhealthy. | This has been fixed. |
| 3 | SCC-8082 | - | 3 | Navigation Bar to only show what is Visible | The options in the top navigation bar are visible according to the user's provisioned roles. |
| 4 | SCC-7593 | 200519-317360 | 3 | High Availability clusters that were running inside of environments that prohibit direct root ssh access during cluster formation were unable to successfully form. | Alternative mechanisms were implemented to allow cluster formation and operations to occur on different ports without direct root ssh access between the cluster members. |
| 5 | SCC-8220 | 201026-342386, 201016-341086, 201130-347809 | 3 | Cassandra container was not healthy | Software improvements made to Cassandra configuration to address this. |
Known Issues - Severity 1
| Issue ID | Case No. | Sev | Problem Description | Resolution |
|---|
| 1 | SCC-8272 | - |
| Elastic indexing of cassandra SIP calls causes performance issue. Indexing each from/To DID SIP calls takes up lots of CPU time giving a slow performance. | For this release, the indexing is disabled. Other options are being explored to index the DIDs to achieve search by DIDs functionality without degrading the performance. |
| 1 | SCC-8465 | - |
| MOS and other call aggregation code is creating a huge load on the system. | TBD |
Known Issues - All Other Severities
| Issue ID | Case No. | Sev | Problem Description | Resolution |
|---|
| 1 | SCC-6842 | 201207-348809 | 3 | Add an to (primary VM) after HA deployment: - Login to .
- Select an from the Device > List page.
- Go to the Analysis page.
- Click on the TAKE SNAPSHOT button.
Once the action is completed, and you try to download the logs by clicking on the download icon, the following is observed: the "Snapshot doesn't exist" message is displayed in the , even though the Action log reported "Completed successfully". | To be Resolved post Release 16.1.0 |
| 2 | SCC-8028 | - | 3 | Inbound/Outbound call: - Log in to and navigate to the node.
- In , check Recent call logs under the System Analysis page - OUT MOS under Analysis page - Displays N/A.
| TBD |
| 3 | EM-25755 | 201201-347978 | 3 | VOS version 15.6.0 is the minimum VOS for this NEW 2900PoE when 15.x or 16.x is being deployed. in VOS 15.6.0 and earlier for the new 2900PoE, the /var/ewn_model parameter is not present, which is required by to display the correct model in the UI. 2900PoE RevB with VOS 15.6.0 or lower the displays incorrectly in . | 2900PoE RevB must have a minimum VOS of 15.6.0 for 16.0.4 or greater. The label located on the bottom of the system is 125-2900EPoE-01-B for identification purposes. |
| 4 | SCC-8328 | 201124-347101
| 3 | eSWAP process ends with “unsuccessful” error message w/ EV 16.0.2.
| Validate status of and ignore error message if the actual eSWAP was completed successfully. |
| 5 | - | 201207-348811 | - | Request for Feature: Unable to remove the corrupted (e.g. incompatible FW release) and start over w/ 16.0.2 & VOS 15.5.1. | Investigation started. |
| 6 | SCC-8438 | 201223-351336 | 3 | 16.0.4 has stopped to display an IP address of any model for an unknown reason. | Upgrade to 15.6.0 or later firmware. Older firmware like 15.5.1 does not send the NAT’ed IP to and only the public address. If an has been running 15.6.0 firmware, managed by and downgraded to 15.5.1, will continue to show that NAT’ed IP. |
| 7 | SCC-8009 | - | 4 | Unable to open SWe Lite and other devices immediately after registering to . | Wait 10 - 15 minutes and the system will open. |
| 8 | SCC-8436 | 201222-351330 | 2 | Password requirement for router is different when configured in EV16 vs directly on . | This is as designed. The System is a central management piece and always enforces the latest security requirements as intended to manage the latest VOS on all routers. |
New Features in This Release
SCC-7171 uses Unique Device Certificates for EMpath Communication
uses unique certificates to manage mutual authentication between s and .
SCC-8016 The Enhanced Collection card displays Rolled up Status from Devices within the Collection Hierarchy
The collection card displays rolled up details from devices within the collection hierarchy. The enhancements made to the collection card include:
- Search collection and enhanced collection details
- For Legacy collection, only the details are displayed and the Legacy label is shifted to the top-right.
- path warning is displayed for SBC devices as well.
- / with Active and Down device count 0 will display N/A in the donut.
- The collection name tooltip is displayed on the Collection name hover.
SCC-8017 Admin is able to change the Application Logo and Footer Text
The
admin is able to update the white label data and there is a button to restore the default white labelling data. The admin can:- see a separate section for branding with the required fields on the Configuration page.
- see the required information in the form of a tooltip when hovers the mouse over the information icon in the Branding section.
- can upload footer text and logo. The company logo at the bottom and the footer text are collectively known as the white labelling data.
- can restore the default logo and text by clicking the Restore Default button in the Branding section.
SCC-7674 provides Basic Inventory Report Enhancements
The basic inventory report is enhanced in order to cater to the requirements of small-scale customers. The inventory report now includes 's hostname, MAC, primary WAN IP, Reachability status, VOS version, age of reachability status, hardware model, uptime, and license status.
Reports are provided for pre-canned Total Calls and Peak Calls for and SweLite, and MOS Score for the devices viewable in the GUI. For reports more than 24hrs and CDR report, the users have to submit a reporting job and are able to see the status of it under the Report jobs list once complete. This report is for Device Inventory as well.
SCC-5957 Key Items to Run on 15 Report
Three critical items namely; Total calls, Peak calls and Average MOS are run on a daily basis from reports. It has the ability to run the report as well. The user needs to download the report and the downloaded report is in JSON format. Reports which are dependent on aggregation scripts such as Average MOS, Total Calls and Peak Calls report, only works for the call data generated on 16.1.0 and not for the old call data.
SCC-5737 Method Implemented to Export CDR from to a Third Party Server using Schedule Report
A new support feature is implemented to export CDR from an device to a third party server or supported and SWelite devices using Schedule Report. With this, the user can:
- Generate CDR report from Report jobs with search by collection level.
- Generate CDR report from Report jobs with search by device level.
- Download the completed CDR report files.
SCC-4116 An Option Included to get details using Export as JSON Option
An option is included to get details using Export as JSON. The JSON file contains the MAC address, platform details, firmware details, and vendor details of all connected devices. The u ser is able to retrieve Device Inventory details by submitting a report or calling -API .
SCC-8082, SCC-8157 The Navigation bar on displays only the Options that the Logged-In user can use
For a View-only user, the following options are hidden or disabled on the navigation bar:
- The Auto-Provision Devices and Policies option from the top navigation bar.
- The Add New Rule and Schedule A Job buttons at applicable places.
- The Add Recipients button and Active/Status checkboxes on the Rules List and Schedule Jobs List pages (including Collection rules and Jobs).
Under the Rules List and Schedule Jobs List pages, a view-only user can only see the User List or the 'Yes/No' option below Status. Also. a view-only user can navigate to Auto-Provision Devices page by selecting the Status option under the Provisioning tab.
SCC-8257 allows multiple replacements on the same legacy device
allows replacing the same legacy device multiple times to facilitate lab testing before rolling into production.