More ShoreTel Troublehsooting

The TMSNCC logs the call accumulations recorded at the end of a call in the G-MST entry, this points to the RTP stream of the call with the following summary

Packet info

s: sent packets

r: received packets

l: lost packets

Jitter Buffer Info (call quality)

j: # of times jitter buffer had to adjust size trying to handle voice streams

u: # of times the jitter buffer did not get enough data to pass on a voice stream

o: # of times the jitter buffer received data outside of its maximum jitter buffer

09:11:49.557 ( 4184: 5288) G-MST: 200000BD "00070001-33cd-5927-c6e1-005056a27011" ("",""),(0, 0),0(Null),rsn:1,22:06:23.979 (UTC),pl:20,(s:16279, r:16279, l:0),(j:3,u:6435,o:11) flgs:0x00000000 "sip:@:5441",vpn:0

G-MST: 2 --> Relates to Network Side of the call

G-MST: 4 --> Relates to Trunk Side of the call

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.