Avaya SBC can use port 22 or port 222 to connect

When adding or editing Avaya Session Border Controller equipment,  the "SSH Connection" field now contains a drop down box to select either Port 22 or Port 222.

Bug Fixes

In Manage Equipment when using Test Access, inaccurate or confusing results were being displayed. Now you'll get the actual validation messages from the SSH and SNMP connections.

Only Genesys Cloud Alarms related to conversations now have a link to the related conversation record - Genesys Cloud Short Conversation, Genesys Cloud Poor Quality Conversation, Genesys Cloud Problematic Phone Call. 

Speed Test data was missing for users with VSMe client, after power resume. VSMe version1.0.99 has been deployed to Virsae and no further issue reported.

Dashboard Fixes

Note: All dashlet fixes are on the new dashlets only. Classic Dashlets have been deprecated and no fixes are being applied there.

SIP Response Summary dashlet - the chart did not render correctly, and values did not match when multiple equipment was selected. Data is now displayed correctly.

Microsoft Teams Call Summary dashlet - the call records for an individual Custom Site could sometimes display a value greater than the entire tenant. This has now been fixed.

On first load of the Alarms Summary dashlet, any VSM Everywhere related alarms could not be resolved for some users. This has now been fixed.

Alarms Summary dashlet column headers now sort correctly and can be filtered.