Forum Discussion
Increasing issues with Skype for Business which resolve themselves.
I'm getting a few customers on Skype for Buisness PSTN online who are consistantly running into one off issues. Issues such as calls failing to go through call queues or calls that are being dropped throughout the day for different users. During these situations we reach out to MS to troubleshoot this further but by the time we get a remote session in place. The issue clears up or no longer happens. Is there a global logging setting I can turn for a tenant that would include errors or logs for calls going through call queues. Or more detailed reports on calls for users to pinpoint dropped calls for online users only? Long story short, I'd like to be able to troubleshoot this faster in a real time manner while waiting for Microsoft support to call me back to start troubleshooting.
2 Replies
Have you looked at the Advanced Call Analytics: https://adminportal.services.skypeforbusiness.com/ ?
I also wrote a PowerShell GUI for the get-csusersession cmdlet: http://realtimeuc.com/2016/10/get-csusersessiongui/
Another option is to view the client traces:
- This can be done by opening the .UccApilog file from the client’s Tracing folder (https://support.office.com/en-us/article/Turn-on-error-logs-in-Skype-for-Business-4892fe33-ef40-48e2-9070-5308d2a57c7e) with a text editor or Snooper. Snooper is part of the Skype for Business Server 2015 Debugging Tools (https://www.microsoft.com/en-us/download/details.aspx?id=47263).
That. Is. Awesome! Thanks for the insight on that.
I knew about the Advanced call portion but I thought you had to manually turn that feature on because it's a preview. My mistake for not even thinking about that before posting this, but I didn't realize how far it breaks it down until now when i did a deep dive into the logs. This will surely help speed up troubleshooting issues with the system.
The powershell Gui seems rather impressive. Nice work!
I've dived into the trace logs, but sometimes we were not able to recreate the issue or the issue went away on the user before we can get the trace logs. This is still a very handy method of finding out what happened with the application and calls through it.
Cheers!
