Resources - Videos

How to Dive Deep into Detailed Microsoft Teams and Skype for Business Analytics

Most organizations have already made the shift to Microsoft Teams or Skype for Business. But just because it has been deployed and adopted doesn’t mean service and management can be forgotten. This video dives into our Call Explorer dashboard software and details how to surface micro-level metrics which help to improve your Teams and Skype for Business services. We provide insight into personalized operations reviews, service recommendations, and customized reporting.


This short video will focus on our PowerSuite Call Explorer Solution. Call Explorer lets you create a functional histogram of your SDM data by diving deep and searching your call records for new insights to drive increased Skype for Business health. Call explorer offers both a set of prepackaged reports, devices, conferences, voice and video quality, call failures, sharing functionality, and more, as well as an easy UI for creating customized queries to find information that isn’t exposed in other PowerSuite solutions. In addition, our PowerSuite dashboard includes a Call Explorer query button for all results that allows you to dive deeper into problems impacting your Skype for Business deployment. Here, we have one such query where operations dashboard has told us about a site that has poor call quality for wired users. It’s good to have insight into a site performance. but what is even more powerful is knowing the root symptom that caused these calls to be marked as bad. So I’ve added the source field to the query and now I can see that the most common network condition that caused my calls to be marked poor was round-trip time. This allows me to have a more informed discussion with my network team. If I want to take a proactive look at errors that are occurring in my environment outside of what PowerSuite monitoring is reporting to me, I can easily create a query that allows me to look at unexpected errors. I can organize the results by the source pool of the air and then group the MS diag code. This could help me find numerous things like users who are configured for enterprise voice, but never enabled. As final example, I may want to evaluate the quality of devices deployed in my org in a more micro fashion. I can look for things like echo percent send which tells us how much echo made it past the device’s DSP and into the call. Here, I’ve grouped by capture device and now I can see an average or max echo score for various devices. I could easily add the from URI the user’s address who are sending the echo to my report and instantly I know not only what devices are having lots of echo issues but which users are using those devices, so I can reach out to them proactively.

Check Out Our Additional Videos

Shopping Basket