[asterisk-bugs] [Asterisk 0018077]: Call hangs on causecode 100

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18077 
====================================================================== 
Reported By:                gkwmiddelkamp
Assigned To:                rmudgett
====================================================================== 
Project:                    Asterisk
Issue ID:                   18077
Category:                   Channels/chan_misdn
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.11 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-09-30 08:55 CDT
Last Modified:              2010-10-01 10:57 CDT
====================================================================== 
Summary:                    Call hangs on causecode 100
Description: 
When dialing a mISDN or Dahdi trunk, and there is an incomplete number
given. The dial hangs on causecode 100. (Incomplete information).

Is there a way asterisk will give a Busy on this call when this causecode
happens?
====================================================================== 

---------------------------------------------------------------------- 
 (0127588) rmudgett (administrator) - 2010-10-01 10:57
 https://issues.asterisk.org/view.php?id=18077#c127588 
---------------------------------------------------------------------- 
The cause value is coming from the STATUS message sent in response to the
SETUP message.  The switch is unhappy about something in the SETUP message.
 (I don't think the switch should be sending a STATUS message for an
incomplete called number, but that may be exactly what it is doing.)  The
switch then goes on to request more digits with the SETUP_ACKNOWLEDGE
message.

A STATUS message does not disconnect a call unless the indicated call
state is a non-existent call.  It should not cause a busy tone.

How are you collecting the called number digits?  You should be able to
write a dialplan that can collect enough digits to match a pattern. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-01 10:57 rmudgett       Note Added: 0127588                          
======================================================================