[asterisk-users] #exec in #include'd file

[Philipp Kempgen]

Tilghman Lesher schrieb:
> On Monday 13 July 2009 01:03:48 pm Philipp Kempgen wrote:
>> Philipp Kempgen schrieb:
>> > Is Asterisk supposed to evaluate #exec's in an #include'd file?

> The directive "#exec" is not permitted in an AEL configuration file.

I see, that would explain why it doesn't work. :-)

But in that case it's a documentation issue. The extensions.conf
sample says: "The #exec command works on all asterisk configuration
files." I guess it should read "The #exec command works on all
asterisk *.conf files except for asterisk.conf."

Is there a specific reason not to permit #exec in AEL files?

BTW: That's a good example of something to run in
/etc/asterisk/startup.d/*.sh. Thread:
http://lists.digium.com/pipermail/asterisk-users/2009-May/232318.html
http://lists.digium.com/pipermail/asterisk-users/2009-May/232709.html
The story is that I already have a script which recursively evaluates
#include's and #exec's in AEL files and then writes extensions.ael.
I wanted to get rid of the script because there's no clean way to have
it run automatically before asterisk is about to be started but now I
can't.

Is any *.conf file (which permits #exec) guaranteed to be read before
extensions.ael? It would then be possible to (ab)use an #exec in there
to trigger my generator script (which must not output anything then of
course). extconfig.conf? logger.conf? modules.conf? Ugly workaround
but doable.


    Philipp Kempgen
-- 
AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied  ->  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de
Videos of the AMOOCON VoIP conference 2009 ->  http://www.amoocon.de
--