Call reporting UX lacks easy details

%3CLINGO-SUB%20id%3D%22lingo-sub-300434%22%20slang%3D%22en-US%22%3ECall%20reporting%20UX%20lacks%20easy%20details%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300434%22%20slang%3D%22en-US%22%3E%3CP%3ECall%20reporting%20UX%20lacks%20easy%20details%3C%2FP%3E%3CP%3EWhen%20attempting%20to%20troubleshoot%20dropped%20calls%20in%20Microsoft%20Teams%2C%20we%20frequently%20have%20to%20dig%20into%20the%20log%20details%20to%20find%20simple%20things%20like%26nbsp%3B%22meeting%20ended%22%20or%20%22call%20restarted%20because%20someone%20with%20an%20older%20device%20joined%22%20...%20also%20the%20basic%20reports%20do%20not%20have%20the%20details%20that%20the%20old%20reports%20did.%3C%2FP%3E%3CP%3EIs%20there%20any%20way%20the%20Admin%20experience%20will%20be%20improved%20to%20make%20it%20more%20functional%20for%20non-technical%20support%3F%26nbsp%3B%3C%2FP%3E%3CP%3EHaving%20senior%20or%20development%20staff%20pulled%20routinely%20for%20delving%20logs%2C%20running%20PowerShell%2C%20etc.%20is%20a%20waste%20of%20productivity.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-300434%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300670%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20reporting%20UX%20lacks%20easy%20details%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300670%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%26nbsp%3Bthe%26nbsp%3B%3CSPAN%3ECall%20Analytics%20capability%20is%20what%20we%20are%20trying%20to%20use.%20Participant%26nbsp%3Bnumbers%20are%20obfuscated.%26nbsp%3B%20Sessions%20dropped%20(or%20restarted)%20due%20to%20someone%20joining%20the%20call%20are%20typically%20not%20in%20the%20sessions%20list%20(only%20the%20new%20call%20forward)%20but%20can%20usually%20be%20found%20in%20the%20old%20PSTN%20usage%20details.%20Frequently%20digging%20into%20the%20DEBUG%20tab%20is%20only%20a%20first%20step%20to%20digging%20into%20the%20log.%20Maybe%20the%20data%20was%20just%20rolled%20up%20too%20high%20level%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20do%20have%20some%20tickets%20open%20for%20these%20issues%2C%20but%20it%20would%20be%20great%20to%20see%20overall%20improvement.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300555%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20reporting%20UX%20lacks%20easy%20details%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300555%22%20slang%3D%22en-US%22%3E%3CP%3EJames%20-%20thanks%20for%20the%20feedback%20here.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAre%20you%20using%20the%20Call%20Analytics%20capability%20in%20the%20Teams%20admin%20center%20(%3CA%20href%3D%22https%3A%2F%2Fadmin.teams.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fadmin.teams.microsoft.com%3C%2FA%3E)%20-%20search%20for%20a%20user%2C%20then%20click%20on%20the%20%22activity%22%20tab.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20goal%20of%20this%20capability%20is%20to%20absolutely%26nbsp%3Ballow%20IT%20Pros%20to%20understand%20what's%20going%20on%20with%26nbsp%3Bcalls%20and%20meetings%20without%20getting%20into%20the%20logs%20and%20surface%20issues%20like%20what%20you%20found.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20would%20be%20great%20to%20know%20what%26nbsp%3Bspecific%26nbsp%3Binformation%20we%20can%20surface%20more%20effectively%20for%20Teams.%26nbsp%3B%20We%20essentially%20took%20the%20Call%20Analytics%20capability%20from%20Skype%26nbsp%3Bfor%20Business%20and%20pumped%20the%20Teams%20calling%20and%20meetings%20media%20telemetry%20into%20that%20view.%26nbsp%3B%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Call reporting UX lacks easy details

When attempting to troubleshoot dropped calls in Microsoft Teams, we frequently have to dig into the log details to find simple things like "meeting ended" or "call restarted because someone with an older device joined" ... also the basic reports do not have the details that the old reports did.

Is there any way the Admin experience will be improved to make it more functional for non-technical support? 

Having senior or development staff pulled routinely for delving logs, running PowerShell, etc. is a waste of productivity.

2 Replies

James - thanks for the feedback here.

 

Are you using the Call Analytics capability in the Teams admin center (https://admin.teams.microsoft.com) - search for a user, then click on the "activity" tab.

 

The goal of this capability is to absolutely allow IT Pros to understand what's going on with calls and meetings without getting into the logs and surface issues like what you found.

 

It would be great to know what specific information we can surface more effectively for Teams.  We essentially took the Call Analytics capability from Skype for Business and pumped the Teams calling and meetings media telemetry into that view.  Thanks!

Yes, the Call Analytics capability is what we are trying to use. Participant numbers are obfuscated.  Sessions dropped (or restarted) due to someone joining the call are typically not in the sessions list (only the new call forward) but can usually be found in the old PSTN usage details. Frequently digging into the DEBUG tab is only a first step to digging into the log. Maybe the data was just rolled up too high level? 

We do have some tickets open for these issues, but it would be great to see overall improvement.