[cisco-voip] Unexpected ISDN disconnect cause code.

Erick Bergquist erickbe at yahoo.com
Thu Oct 12 23:23:35 EDT 2006


Do you have fwd hunt busy/noanswer set on the hunt pilot? If not, set them to fwd the calls to another phone or maybe an autoattendent or VM when they are all busy? 

It sounds from the info given so far, that the gateway tries to send the call the call manager (voip dialpeer) and it is busy, then tries the next dial-peer which hairpins it back out PRI causing the channels to be used and causing the congestion cause code perhaps. it may be cycling through all the channels quickly. 
Do you have huntstop on your last voip dialpeer, to prevent it from going back out PRI (unless you want that and if there are matching dialpeers that send it that way)?

Can you send more details and a full debug isdn q931 of a call from start to finish?

----- Original Message ----
From: Alex A. Pavlenko <lex at sandy.ru>
To: cisco-voip at puck.nether.net
Sent: Wednesday, October 11, 2006 10:42:03 AM
Subject: [cisco-voip] Unexpected ISDN disconnect cause code.

Colleagues,

please consider the call flow:
PSTN-(PRI)->Cisco AS5350-(IP/H323)->Callmanager 4.0
Called number is routed through hunt pilot with single hunt list in it.
Hunt list includes single line group. The problem is when all phones in a
line group are busy PSTN user hears reorder tone, not busy signal.
In debug isdn q931 on AS5350 I see 
ISDN Se3/1:15 Q931: TX -> DISCONNECT pd = 8  callref = 0xEC00 
      Cause i = 0x80AA - Switching equipment congestion
I've broken my brains already, please help.

--
Alex Pavlenko
System Administrator
Sandy Info

_______________________________________________
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