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

https://www.epochconverter.com/

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

ShoreTel Contact Centre Log Monitor

The Contact Center Log Monitor tool is found in the following directory:

C:\Program Files (x86)\ShoreTel\ShoreTel Contact Center Server\Bin

The executable is called:
BswLogMon.exe

This is what the tool looks like with all setting enabled..

TMSncc Logs

This will be a living post of call codes from the TMSncc logs from ShoreTel:

C-CE: Call Creation Event - Call Initiation
L-CE: Leg Create Event - Follows a C-CE for every call setup. Internal blind transfers C-CE may be skipped.
L-IE: Leg Info Event - Follows a C-CE, L-CE. Leg Info; Provides info on other parties in the call.
C-SE: Call State Event - State of call in progress; all parties. RingBack, Offering, Established, etc.
L-SE: Leg State Event - Follows a C-SE to inform the leg state changes.
L-DE: Leg Destroy Event - Call tear down; Leg is destroyed.
C-DE: Call Destroy Event - Call destroyed by user or system.
G-MST: - Media State Event - Media state for the terminated call leg. Every RTP stream also has a media state.

Some more details:
http://wayback.archive.org/web/20150731055525/http://netdungeon.com/decipher-tmsncc-log

Logging/Tracing in Lync Server 2013

In Lync Server 2013 the way to enable tracing has changed there is no longer GUI to enable the tracing, its done via command line.

The command is “ClsController.exe” and is located in “C:\Program Files\Common Files\Microsoft Lync Server 2013\ClsAgent\” on the Lync 2013 Server, in Lync 2010 you ran the “Lync logging Tool” and selected components that you wished to trace, started the trace and re-created the problem, stopped the trace and then “Analysed” the trace with the snooper tool.

Lync 2013 doesn’t allow you to select the components that you wish to trace, you now select a scenario that you wish to trace/

The flow is now:

• ClsController.exe -start –scenario –pools
• Reproduce the Issue
• ClsController.exe -stop –scenario –pools
• ClsController.exe -flush –pools
• ClsController.exe -search –pools –components –loglevel

 Today I came across this post by Richard Brynteson at MasteringLync.com

http://masteringlync.com/2012/08/02/centralized-logging-in-lync-2013/

The output file is created on the desktop of the user logged in running the bat file, then you can use snooper from the Lync Debug Tools to open the file

All Lync Server 2013 have the ClsAgent running on them, so you only need to run the ClsController.exe once and it will collect from all servers in the pool identified.