This is a port so that I remember where to find the scripts..
Shout out to the author:
This post is to outline the logging/tracing items for a MS Teams environment, most of the tracing will be from the Teams Client/Web App/etc.
It will hopefully be a "living" post that is updated when I find new things.
First Step - Get log files from the Client:
Teams Client, right click the icon in the task bar and select "Collect support files"
Time stamps in the log files are in epoch time:
What is epoch time?
The Unix epoch (or Unix time or POSIX time or Unix timestamp) is the number of seconds that have elapsed since January 1, 1970
"MSTeams Diagnostics Log <date><time>_calling.txt" has calls made received:
Trying to crate a "Resource Account" for a Teams CQ and/or AA, and came across an issue where via both TAC and Power Shell it would fail.
I had seen this before when the Teams/Skype Online was a Hybrid environment, but in this case the deployment has no on-premises Skype environment.
Turns out DNS is the issue, even when in a cloud only environment the Skype DNS entries are required.
This is a port so that I remember where to find the scripts.. https://github.com/mozziemozz/M365CallFlowVisualizer Shout out to the author: ...