Table of Contents |
---|
New Alarms for VSM Everywhere
...
users
Table of Contents |
---|
VSM-E vProbe updated
An updated version of the probe is now available VSM Everywhere users with probe version 1.0.53. This support the customizable Speed Test frequency.
...
56 can receive the following Wi-Fi alarms:
Unsecure Wi-Fi
You can now immediately identify when users are connected to unsecure Wi-Fi with the following two alarms, thus reducing vulnerability to security breach:
- Wi-Fi Authentication Unsecure
- User is connected to unsecure Wi-Fi network
- Wi-Fi Encryption Unsecure
- User is connected to an unencrypted Wi-Fi network
Poor Wi-Fi
You can now identify users that are having Wi-Fi quality issues and trouble shoot when it's happening with the following three alarms:
- Poor Wi-Fi
- Wi-Fi signal strength and Link Quality combination is lower than the recommended value for voice and non-HD Video calls - recommended Signal Strength value of -67 dBm or greater AND Link Quality of 41 dB or greater.
- Low Wi-Fi Signal Strength
- Wi-Fi signal strength is lower than the recommended value for voice and non-HD Video calls - recommended value is -67 dBm or greater.
- Low Wi-Fi Link Quality
- Wi-Fi link quality is lower than the recommended value for voice and non-HD Video calls - recommended value is 41 dB or greater.
Bug Fixes
Microsoft Teams Call Records - a record containing an external user could not be expanded. This has now been fixed.
Roles and access Access - when selecting equipment, the equipment list was not rendering correctly. This now renders correctly.
Roles and Access - deleted users were not being removed from the User 'count' on the Roles and Access page. The number of users in a Role is now correct.
Reports - some reports incorrectly included Location as a selection on the +Schedule report page. This has been fixed.
Network Topology Configuration - selecting Edit did not produce the pop-up modal to edit a selected Network device. This has now been fixed.
The File Upload Transaction Log was failing to load. We've implemented a temporary fix, so you'll get data for the last 7 days.
SIP Session Trace records were not available for the last hour, for some customers. This has now been fixed.