Getting Call Quality Data in near real time

Occasional Contributor

Hi I am trying to get hold of call quality data as soon as possible after a call has finished via script.


I realize the CQD is delayed by a couple of days so thats not going to fit the need, but in the GUI when a call has finished its record appears just a few moments later for the user.  Can this be queried ?  I can see a beta API,, which looks like it might help, but you have to have the {id} property of the call, and if you dont know this how can you query for it ?  I can't see any other was of giving an input parameter ?


eg GET{id}







6 Replies

Here's an example PowerShell from the product team that will allow you to export call data for a time period



Thanks Steve that’s been really interesting, the get-csusersession that it’s using to get the data does return information for teams but interestingly - and frustratingly - the call quality data record isn’t there, it’s empty every time. This is populated somewhere because the gui has it a few minutes after a call is finished. So either you can pull it from another cmdlet or we are waiting for an updated api.

@MikeB1903 It might be worth sending an email to the author of the script, Jason, he was very helpful when we were using this script to extra RMC data from Skype. I doubt anyone knows much more about using these APIs.

MVP Ken Lasso just blogged on this very subject, largely confirming what you've found ...

Thanks Steve, thats really helpful.  I agree with both, I pinged steve on twitter and I see Ken is coming to the same conclusions.  Its a touch frustrating because the data clearly is there - it appears in call analytics just a few moments after the call - but we can't get to it.  Hopefully this will improve from MS.

@Steven Collier  Do you know if there is way to get CQD from data API. Like using below query ?




I am looking into this document and mainly for skype for business 2015.

I am not able to figure out how i can login with service principle and then to make call for accessing the data. Because documentation is not referring any way of login.