|
Home > Archive > Voice over IP Cisco > August 2007 > CCM log translator
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
CCM log translator
|
|
| Robert Kulagowski 2007-08-30, 1:12 pm |
| 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.
| |
| Kris Seraphine 2007-08-30, 1:12 pm |
| There's a couple of tools you could try.
http://www.employees.org/~tiryaki/tc/
If you have access to CCO downloads you can look for VLT (voice log
translator).
On 8/30/07, Robert Kulagowski <bob@smalltime.com> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
--
kris seraphine
| |
| Ted Nugent 2007-08-30, 1:12 pm |
| http://www.employees.org/~pgiralt/TranslatorX/
--- Robert Kulagowski <bob@smalltime.com> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
________________________________________
____
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
| |
| Wes Sisk 2007-08-30, 7:11 pm |
| 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
|
|
|
|
|