[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:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   14122
Category:                   Applications/app_macro
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     ready for testing
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-02-10 16:23 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0099859) Corydon76 (administrator) - 2009-02-10 16:23
 http://bugs.digium.com/view.php?id=14122#c99859 
---------------------------------------------------------------------- 
That's very true, but it's a consequence of the Macro having exited.  I
don't think there's any way to change that. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-10 16:23 Corydon76      Note Added: 0099859                          
======================================================================