[asterisk-dev] h extension not considered within a macro for Asterisk 1.6.0.6 and later

[Alec Davis]

Ok, but before we change to GOSUBs, is it valid to execute an 'h' extension
within a GOSUB?

Alec
 

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Tilghman Lesher
Sent: Wednesday, 8 April 2009 04:10 a.m.
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev]h extension not considered within a macro for
Asterisk 1.6.0.6 and later

On Tuesday 07 April 2009 00:35:51 Alec Davis wrote:
> I've filed a very similar bug http://bugs.digium.com/view.php?id=14757
>
> Even though I've described it to work using a GOSUB not MACRO, were 
> not happy with the workaround.

That's because it was actually a BUG.  The "h" extension never should have
executed within the macro context.  It was always documented that the "h"
extension only executes within the main context, where the Macro was called.

We fixed that bug, but with the understanding that people depended upon this
buggy behavior, we made the "h" extension check within the Macro for an "h"
extension, before going to the main context.

This, by the way, is the same reason why fixing CDRs is so difficult.
Everytime we fix a bug, people complain that we "broke" CDRs, because they
depended upon buggy behavior!

--
Tilghman

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev