Thursday 12 May 2022

Teams Tracing/Logging

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:

Use log files to monitor and troubleshoot Microsoft Teams

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

Log files:

"MSTeams Diagnostics Log <date><time>_calling.txt" has calls made received:

Context Details:
SlashCommand           "/call <number>" in the search field
CentralDataLayer        Call from the dial-pad in Teams client

Time of call details:

State : 0 (Call Made)

State : 2

State : 9 (Ringing)

State : 3 (Call Answered)

State : 6 (Hang Up)

State : 7 (Call Cleared)

If anyone know what the exact state are, please drop a not in the comments, as this is what I have seen from making calls.

"MSTeams Diagnostics Log <date><time>.txt"

Phone number normalisation

The line above show that rule 4 of 11 was used to normalise the number via first the tenant dial-plan, then the global (AU) dial-plan.  The global (AU) dial-plan has three (3) entries, in the example above the tenant dial-plan has eight (8) entries.

Landis Attendant Console Install

Attempting to setup a test tenant with access to Landis Attendant Console, and was getting errors around granting access to the tenant. The ...