[asterisk-bugs] [Asterisk 0014122]: [patch] Macro execution doesn't get to "h" extension

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14122 
====================================================================== 
Reported By:                wetwired
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   14122
Category:                   Applications/app_macro
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     feedback
Target Version:             1.4.24
Asterisk Version:           1.4.23-rc3 
Regression:                 Yes 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-12-22 06:13 CST
Last Modified:              2009-01-21 19:08 CST
====================================================================== 
Summary:                    [patch] Macro execution doesn't get to  "h"
extension
Description: 
In asterisk-1.4.23-rc3 (and in SVN 1.4 branch) execution of macro context
interrupted by hangup never gets to "h" context defined by "catch h =>".
Instead of this, execution returns to "h" extension of calling context. In
asterisk-1.4.23-rc2 and earlier, execution was finishing in macro "catch h
=>" branch.
====================================================================== 

---------------------------------------------------------------------- 
 (0098402) Corydon76 (administrator) - 2009-01-21 19:08
 http://bugs.digium.com/view.php?id=14122#c98402 
---------------------------------------------------------------------- 
andrew:  have you checked to see if the deepest macro is still executing
when the call is hungup?  The code will only execute the "h" extension in a
macro which is still executing.  If it exited, and the next macro up
doesn't contain an "h" extension, then it is expected that the "h"
extension would run from the main context, since it could not find it in
the context where it hungup. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-21 19:08 Corydon76      Note Added: 0098402                          
======================================================================