[cisco-voip] Odd hunting issue
Wes Sisk
wsisk at cisco.com
Tue Aug 9 16:47:53 EDT 2011
I don't want to jump to conclusions but this comes to mind:
CSCto78441 7962 phones are going off-hook and then on-hook 400
milliseconds later
Regards,
Wes
On 8/9/2011 4:18 PM, Robert Singleton wrote:
> On 08/09/2011 01:12 PM, Wes Sisk wrote:
>> Sounds like an anomaly with the device or the user of the device.
>> What type of is it?
> All instruments at the site are 7962G hardware revision 12.0. Switch
> is WS-C3560-24PS running 12.2(25)SEB2; router is 2811 running 12.4(9)T1.
>> If you're seeing it in CDR that means the call either got connected
>> or disconnected with an abnormal cause code. What was the cause code
>> and origin of the cause code in CDR?
> I'm sorry, I meant to mention that in my posting... all these calls
> show normal codes, always code 0 on origin and 16 on the destination.
> The duration is usually 0 (XX below) but about one in seven showed 1
> second. Ring and talk time always add up to 1 second.
>
> orig dest date time ring talk orginator destination
> 0 16 Tue Aug 9 10:57:20 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 10:57:31 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 10:57:41 0 1 NPANXXNNNN 2083000
> 0 16 Tue Aug 9 10:57:48 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 10:59:33 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 10:59:37 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:03:03 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:04:17 0 1 NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:05:49 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:07:39 0 1 NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:08:26 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:08:26 2 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:08:45 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:08:53 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:08:58 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:12:06 9 XX 2033001 2083000
> 0 16 Tue Aug 9 11:12:37 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:12:41 0 1 NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:13:12 1 XX 2000785 2083000
> 0 16 Tue Aug 9 11:13:54 1 XX NPANXXNNNN 2083000
> 0 16 Tue Aug 9 11:15:00 0 1 NPANXXNNNN 2083000
>
> Also, just in case I didn't make it clear, pulling the one device out
> of the line group stopped the issue, even after putting the device
> back in the the line group. It is not doing it at all now.
>
> I should have turned on traces while it was happening, but that didn't
> occur to me at the time :/
>
> Robert
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
More information about the cisco-voip
mailing list