Happy New Year and welcome to the first release of 2022. Since out the last release in December, our developers have been working on outstanding bugs from 2021to clear customer reported bugs.
In this release you will find the following fixes:
Identity Management
Identity Server (IS) will now check and change the branding functionality so that if the branding service errors, that error is handled gracefully. The VSM default branding will be used rather than a 500 error message.
New users are required to click on a link that should take them to the accept invite page. This was giving an http 500 error, but has now been fixed.
Locations and Equipment
The Description field was empty when viewed in Edit Location even though a description existed. (In many cases it contains the IP settings for the appliance host and this information is not found anywhere else in configuration as it is Collector specific.) The description field now shows.
On the Manage Equipment page there si is a button to export to csv. This file download was named 'Undefined' but now exports as 'Equipment_customer name'.
Tags
There were some tags where the associations with equipment were not in the database, and therefore didn't show up in the 'associations tree' and couldn't be removed. This has now been fixed.
Dashlets
On the Windows Server dashlet we have updated the tool tip , when hovering over the 'Free' values as it . The information format was misleading to the BP's/Customers in its previous form.
On the Calls In Progress dashlet, there was an intermittent fault where only the GWP@IP reference would show and the Extension name was missing. This has now been fixed.
Reports
The data in the csv export for the Trunk Group Call report did not match the data on the on-screen report. These now match and show correct data.
The filter in the CMS Call Trace Report for Calling Party was not always returning results. This has been fixed.
Alarm rules
In Alarm rules, the Activity Trace tab would just show continuously as 'loading' when there was no data. Users will now receive a message 'No data to display', if there is no data.
Occasionally, editing an alarm rule could make that rule invalid. The cause has been identified and you can no longer add an alarm rule where parent ID does not exist.