Great informational article regarding ShoreTel TMSNcc logs: http://www.netdungeon.com/articles/how-decipher-tmsncclog
Call Code Parameters:
|C-CE||Call Creation Event||Call Initiation.|
|L-CE||Leg Create Event||Follows a C-CE; Internal Transfers|
|L-IE||Leg Info Event||Provides information on other parties in the call.|
|C-SE||Call State Event||
State of call in progress; RingBack, Offering, 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 hung up.|
|G-MST||Media State Event||Media states for the terminated call leg.|
|Trunk Call Leg To PSTN||40000001|
|Internal Call Leg||20000023|
|PBX Responding to Party||ncc_media_ctl|
(s:1, r:378, l:0),(j:0,u:0,o:0)The above packet information lists sent and recieved packets, and jitter. This is very useful in understanding why calls fail. In many cases we will see issues with jitter readjustments during problem or dropped calls. The s:1 indicates 1 packet was sent, the r:378 indicates 378 packets were recieved. The second set of parentheses (j:0,u:0,o:0) describes the jitter buffer, and in this case was adjusted 0 times. This is more of an ideal scenario as problem calls will vary in their jitter and packet amounts.