[cisco-voip] Trying to track down a dropped call...

[Ed Leatherman]

Had a call center agent call in a report on a dropped call.. trying to
determine what happened to cause it to drop.

Since this has IPCC involved, I have less of a clue as to whats going on
than normal. The first messages that I see in the trace file when the call
dropped are:
03/28/2007 15:45:14.823 CCM|StationD(226): StationCtiD -
CtiLineCallDisconnectReq LH=5
03/28/2007 15:45:14.823 CCM|StationD(226): StationCtiD -
CtiLineCallDisconnectReq LH=5
03/28/2007 15:45:14.823 CCM|StationD(226): StationCtiD - StationOnHook
03/28/2007 15:45:14.823 CCM|StationD(226): StationCtiD - StationOnHook
This seems to tell me that either callmanager or ipcc is tearing down the
call rather than the agent bumping a button or something... or perhaps the
user is doing it via CAD somehow and doesnt know it. I don't see any reset
messages in callmanager for that phone to have lost connectivity.

Then some lines down,
03/28/2007 15:45:14.823 CCM|StationD:    (0000226) StopTone.
03/28/2007 15:45:14.823 CCM|StationD:    (0000226) SetLamp mode=1, stim=9
stimInst=1.
the the other normal stuff i've seen before when a call shuts down, closes
channel, stops transmission,etc.
Further down it closes out the gateway connection, the PRI message indicates
normal call clearing, and it looks like callmanager is closing the MGCP
connection.

Does anyone know if there is some place to look for the cause in an IPCC
express log? I looked through the MIVR log but nothing jumped out at me..
but i'm not sure what to look for either.

-- 
Ed Leatherman
Senior Voice Engineer
West Virginia University
Telecommunications and Network Operations
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070329/d4a8f82e/attachment.html