[cisco-voip] CCM log translator

[Wes Sisk]

so long as it is a not a SIP phone you can:

1. find the tcp handle of the phone you expect the call
2. follow that TCP handle through the logs watching events on the phone, 
they are pretty intuitive.  The biggest thing you need is a decoder for 
the call states:
typedef enum {
    TsOffHook = 1,
    TsOnHook = 2,
    TsRingOut = 3,
    TsRingIn = 4,
    TsConnected = 5,
    TsBusy = 6,
    TsCongestion = 7,
    TsHold = 8,
    TsCallWaiting = 9,
    TsCallTransfer = 10,
    TsCallPark = 11,
    TsProceed = 12,
    TsCallRemoteMultiline = 13,
    TsInvalidNumber = 14
} StationDCallState;


When the specific call (identified by callerid in the callinfo message) 
stops ringing, look just above that to see why the call was rerouted.

/Wes

Robert Kulagowski wrote:
> I'm trying to investigate a call issue after-the-fact.  The users at the 
> site reported that they were expecting a call to come in to reception, 
> which they then said "Did a half-ring, then went to VM"
>
> I've got CCM traces from that time period.  Is there a tool that will 
> take 4 MB of text files and in plain-English translate what actually 
> _happened_?  The log files are a mix of human readable text, hex codes, 
> etc, etc.  Add in that there are other calls going on at other sites at 
> the same time and it's practically impossible to follow the thread of 
> what's going on.
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>