You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

MTR Health Status - alarms

Growth of video deployment for communications and collaboration has increased since COVID lockdown days. Microsoft Teams Rooms (online video conferencing) has become a key technology for driving better communication, collaboration and alliances.

Alarms generated for Microsoft Teams Rooms and Teams Devices will display in the Manage Alarms grid and the Alarms Summary dashlet. 

  • Teams Room
  • Surface Hub
  • Collaboration Bar
  • Teams Display
  • Touch Console
  • Teams Panel

Alarms will be generated if the status changes from Healthy.  If an alarm expires or a customer or Business Partner manually resolves an alarm, a new alarm will not be raised if the health status is the same as previous. We'll only raise an alarm if the health status is different from the last raised event.


Alarms Summary dashlet showing MTR health status alarms

MTR Health Summary dashlet

Our Microsoft Teams Room Health Summary dashlet, similar to our range of System Health Summary dashlets, is for our Business Partners and customers to have visibility of the state (health) of all software and hardware peripherals attached to the Microsoft Teams Room. The Microsoft Teams Room Health Summary dashlet shows details of the devices regardless of the manufacturer, such as hardware information (make and model), status (health and activity) and activity.

This dashlet is now available in a small size. We will build upon this functionality in future sprints. For more information refer to Microsoft Teams Rooms Health Summary dashlet

Microsoft Teams Rooms Health Summary dashlet - small size


Bug Fixes

When adding a new event in Change Calendar, an email will now be sent to the requestor when the "Send Notification of New Event" is selected. 

Dashboards - Preview bug fixes

The VSM-E alarms were incorrectly duplicated in the Alarm Summary dashlet, despite the database records not being duplicated. This only effected customer with VSM Everywhere. 

Some of the SIP generating equipment produce SIP messages re-using call id values for OPTIONS messages. which can overflow the record capacity from re-using call id values. We're no longer storing SIP OPTIONS messages from the SIP Processor service to avoid making Table Record full. This improves the efficiency of populating the SIP Response Summary dashlet.

Avaya Session Border Controller (ASBC) dashlet  - on the Network Interface section, the drill down now populate with data.

Avaya Application Enablement (AES) dashlet -  was not updating when under load with multiple dashboards open. We've made initial changes to improve performance.

Endpoint Data Summary dashlet - Expansion rows were missing drill down information and column alignment changed for improved readability.

Windows Server health dashlet would not allow navigation to the Processor, Memory and Disk reports even when subscribed. This has now been fixed.

Incorrect equipment types were selectable in the  Source Equipment field of the Active Streams, Mean Opinion Score and Calls In Progress dashlets. These no longer appear in the selection list for these dashlets.

 For the Active Streams, Mean Opinion Score and Calls In Progress dashlets, selecting 'All' equipment now populates these dashlets.











  • No labels