[cisco-voip] Call hunting, ISDN code 0x66

[Mohit Saxena]

Try tweaking your isdn T310 timer on the isdn interface.

The default value is 10, try making it 30 or 40.

 

Br,

 

Mohit C. Saxena 
Sr. Network Administrator 
Starcomms Ltd. 
www.starcomms.com <blocked::http://www.starcomms.com>  
Mob: +234-702-800-0709

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Peter Grace
Sent: Thursday, August 07, 2008 4:21 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Call hunting, ISDN code 0x66

 

Hello list,

I have a situation where I am receiving a lot of ISDN 0x66 codes
(Recovery on timer expiry) in my calltracker output from one of our
AS5400's.  I think this is indicating to me that the cisco took too long
to find an acceptable destination for the call.  Is this correct?  If
so, is there a way to tweak the time before the thing gives up?  Do we
know how many times the cisco will try to hunt to the next SIP gateway
before it gives up and drops the call?

The reason why I was thinking it was taking too long is that almost all
of these 0x66 errors have the same symptoms, 0.00 conn time, and a total
call time of an average of 8.5 seconds long.  If I'm on the wrong track
please let me know; I'd like to resolve this issue.

Aug  6 19:55:34 psip02-mci.local 560071: Aug  6 23:55:34.124:
%CALLTRKR-6-CALL_RECORD: ct_hndl=559890, service=None, origin=Answer,
category=IsdnSync, DS0 slot/port/ds1/chan=1/0/3/1, called=XXXXX,
calling=XXXXX, resource slot/port=(n/a)/(n/a), userid=(n/a), ip=0.0.0.0,
account id=559909, setup=08/06/2008 23:54:48, conn=0.00, phys=0.00,
service=0.00, authen=0.00, init-rx/tx b-rate=0/0, rx/tx chars=0/0,
time=8.16, disc subsys=ISDN, disc code=0x66, disc text=Recovery on timer
expiry


Aug  6 19:55:34 psip02-mci.local 560075: Aug  6 23:55:34.124:
%CALLTRKR-6-CALL_RECORD: ct_hndl=559894, service=None, origin=Answer,
category=IsdnSync, DS0 slot/port/ds1/chan=1/0/3/8, called=XXXXX,
calling=XXXXX, resource slot/port=(n/a)/(n/a), userid=(n/a), ip=0.0.0.0,
account id=559913, setup=08/06/2008 23:54:52, conn=0.00, phys=0.00,
service=0.00, authen=0.00, init-rx/tx b-rate=0/0, rx/tx chars=0/0,
time=8.24, disc subsys=ISDN, disc code=0x66, disc text=Recovery on timer
expiry


Aug  6 19:55:34 psip02-mci.local 560076: Aug  6 23:55:34.124:
%CALLTRKR-6-CALL_RECORD: ct_hndl=559895, service=None, origin=Answer,
category=IsdnSync, DS0 slot/port/ds1/chan=1/0/3/10, called=XXXXX,
calling=XXXXX, resource slot/port=(n/a)/(n/a), userid=(n/a), ip=0.0.0.0,
account id=559914, setup=08/06/2008 23:54:53, conn=0.00, phys=0.00,
service=0.00, authen=0.00, init-rx/tx b-rate=0/0, rx/tx chars=0/0,
time=8.04, disc subsys=ISDN, disc code=0x66, disc text=Recovery on timer
expiry


Thanks, 
Pete



DISCLAIMER: The information contained in this message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and permanently delete this message and any attachments from your system. Any form of dissemination, use, review, distribution, printing or copying of this message in whole or in part is strictly prohibited if you are not the intended recipient of this e-mail. Please note that e-mails are susceptible to change. STARCOMMS PLC shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. STARCOMMS PLC does not guarantee that the integrity of this communication has been maintained or that this communication is free of viruses, interceptions or interferences. STARCOMMS PLC reserves the right to monitor all e-mail communications, whether related to the business of STARCOMMS or not, through its internal or external networks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080807/ca660b9c/attachment.html>