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

[Alec Davis]

But is GOSUB going to stay that way? Or is it also considered a BUG that
works, and has yet to be fixed.

Please read carefully the output from 'core show application macro', if the
help is wrong, please correct it.

Below the output from 'core show application macro':
"This means that if a hangup occurs, for instance, that the macro will be
searched for an 'h' extension, NOT the context from which the macro was
called.
So, make sure to define all appropriate extensions in your macro! (Note: AEL
does not use macros)"

Which I interpret as:
	If the macro has an 'h' extension defined it will executed.

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 07:00 a.m.
To: Asterisk Developers Mailing List
Subject: Re:
[asterisk-dev]=?ansi_x3.4-1968?q?h_extension_not_considered_with?==?ansi_x3.
4-1968?q?in_a_macro=09for_Asterisk_1=2E6=2E0=2E6_and_lat?==?ansi_x3.4-1968?q
?er?=

On Tuesday 07 April 2009 13:36:26 Alec Davis wrote:
> Ok, but before we change to GOSUBs, is it valid to execute an 'h' 
> extension within a GOSUB?

Yes, it is.  Gosub works differently.

--
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