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

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Sep 30 18:16:42 CDT 2010


The following issue requires your FEEDBACK. 
====================================================================== 
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-09-30 18:16 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?
====================================================================== 

---------------------------------------------------------------------- 
 (0127571) rmudgett (administrator) - 2010-09-30 18:16
 https://issues.asterisk.org/view.php?id=18077#c127571 
---------------------------------------------------------------------- 
What is the chan_misdn debug output when this happens?

Chan_misdn may be allowing an audio message to be played and letting the
caller to hangup the call after listening to it.

----

Cause No. 100 – Invalid information element contents
This cause code implies that there is something wrong with the ie coding
itself (as in protocol error) not the called number.

Would expect one of the following for an invalid called number:
Cause No. 1 – Unallocated (unassigned) number;
Cause No. 3 – No route to destination;
Cause No. 22 – Number changed;
Cause No. 28 – Invalid number format (address incomplete).
 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-30 18:16 rmudgett       Note Added: 0127571                          
2010-09-30 18:16 rmudgett       Status                   assigned => feedback
======================================================================




More information about the asterisk-bugs mailing list