[asterisk-bugs] [Asterisk 0012286]: [patch] immediate=yes treats s extension differently than others: doesn't return cause code 1 if doesn't exist

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=12286 
====================================================================== 
Reported By:                lmamane
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   12286
Category:                   Channels/chan_misdn
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.18 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-03-24 04:30 CDT
Last Modified:              2009-05-22 08:54 CDT
====================================================================== 
Summary:                    [patch] immediate=yes treats s extension differently
than others: doesn't return cause code 1 if doesn't exist
Description: 
On a TE PTP port, configured with immediate=yes, when the base number is
called and the "s" extension doesn't exist in the configured context,
chan-misdn jumps into the dialplan anyway, triggering the Asterisk fallback
to 'default' context machinery. If the "s" extension does not exist in the
'default' context either, chan-misdn returns ISDN cause code 16 (normal
call clearing) to the caller.

In contrast, if an extension is called and it doesn't exist in the
configured context, chan-misdn returns cause code 1 (that is, "this number
is not allocated"), without any fallback to "s" or the 'default' context.

I think the behaviour should be consistent, and always the second one
(cause code 1).
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-22 08:54 svnbot         Assigned To              rmudgett => file    
2009-05-22 08:54 svnbot         Status                   assigned => resolved
2009-05-22 08:54 svnbot         Resolution               open => fixed       
======================================================================