This week we have continued our work on Microsoft Teams and in this sprint have implemented an alarm for Teams Call Failure, as well as improving data reliability and some bugs fixes.

Teams Call Failure Alarm

If a Microsoft Teams Call Failure is reported by Microsoft then an alarm will now be generated in VSM.

  • The alarm will be shown by "stage" eg: midcall, call setup
  • The affected caller or callee is shown in the Administered-ID field
  • The default severity is 6 (Informational / warning level), but this can be changed as desired, for example making the alarm severity higher for the CEO or other executives

When selecting the alarm on the Alarms grid, the user is able to navigate to the Call record and

  • View the recorded Call Failure "stage" and "reason" (via mouseover on "?")
  • View the relevant data for voice quality (MOS, Latency, Jitter, Packet loss) and
  • View User Feedback if provided (star rating, selections and any comments)

Information from Microsoft about Teams Call Failure can be found here...


The Alarms grid above is found in Availability Manager > Manage Alarms and shows the unresolved alarms


MS Teams Call Records, drill down record on the user to trouble shoot the call failure 

Bug Fixes

On MS Teams, there was an issue caused by an API output change resulting in incorrect processing of raw data. This has now been fixed. 

We've changed the data collection time periods to improve data reliability for CPU, Memory and Network Interface data.

  • No labels