[asterisk-bugs] [Asterisk 0014411]: calling Gosub in macro does not work if the invalid extension is triggered

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14411 
====================================================================== 
Reported By:                klaus3000
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14411
Category:                   Applications/app_macro
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-02-05 05:39 CST
Last Modified:              2009-04-16 08:04 CDT
====================================================================== 
Summary:                    calling Gosub in macro does not work if the invalid
extension is triggered
Description: 
Hi!

Consider the following example:

macro blacklistMakro() {
  Gosub(blacklist_${BLACKLIST}|${MACRO_EXTEN}|1);
  return;
}

context blacklist_SIMPLE {
  _+49. => Hangup();
  i =>Return();
}

If the Gosub call inside the macro triggers the i extension, MACRO_DEPTH
is set to 0, the macro "forgets" that it is a macrom, and does not return
(auto fallthrough happens)


====================================================================== 

---------------------------------------------------------------------- 
 (0103306) lmadsen (administrator) - 2009-04-16 08:04
 http://bugs.digium.com/view.php?id=14411#c103306 
---------------------------------------------------------------------- 
Closed due to comments by klaus3000 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-16 08:04 lmadsen        Note Added: 0103306                          
2009-04-16 08:04 lmadsen        Status                   ready for testing =>
closed
2009-04-16 08:04 lmadsen        Resolution               open => no change
required
======================================================================