<br><br><div class="gmail_quote">On Tue, Jul 14, 2009 at 11:47 AM, Tilghman Lesher <span dir="ltr"><<a href="mailto:tilghman@mail.jeffandtilghman.com">tilghman@mail.jeffandtilghman.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Monday 13 July 2009 17:19:15 Philipp Kempgen wrote:<br>
> Tilghman Lesher schrieb:<br>
> > On Monday 13 July 2009 01:03:48 pm Philipp Kempgen wrote:<br>
> >> Philipp Kempgen schrieb:<br>
> >> > Is Asterisk supposed to evaluate #exec's in an #include'd file?<br>
> ><br>
> > The directive "#exec" is not permitted in an AEL configuration file.<br>
><br>
> I see, that would explain why it doesn't work. :-)<br>
><br>
> But in that case it's a documentation issue. The extensions.conf<br>
> sample says: "The #exec command works on all asterisk configuration<br>
> files." I guess it should read "The #exec command works on all<br>
> asterisk *.conf files except for asterisk.conf."<br>
><br>
> Is there a specific reason not to permit #exec in AEL files? <br></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
<br>
</div>It wasn't coded that way, and it's parsed in a completely different way than<br>
any other Asterisk configuration file. I don't know the reason Murf didn't<br>
do '#exec' specifically, but I suspect it has to do with the complexity<br>
thereof.</blockquote><div><br>I didn't "exclude" the #exec for any particular reason. I think it just wasn't in the<br>original AEL (1.2) code, so I missed it... (or it escaped my all-powerful eyes somehow).<br>
If someone files a bug, I might be able to code up something to handle it in future releases.<br>(just as a reminder for me). I guess you could, for the time being, put your #exec stuff<br>in an extensions.conf file, and use the modules.conf tricks to preload the extensions.conf<br>
file first, if that is a requirement, as previously suggested...<br><br>murf<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div class="im"><br>
> Is any *.conf file (which permits #exec) guaranteed to be read before<br>
> extensions.ael? It would then be possible to (ab)use an #exec in there<br>
> to trigger my generator script (which must not output anything then of<br>
> course). extconfig.conf? logger.conf? modules.conf? Ugly workaround<br>
> but doable.<br>
<br>
</div>No, but you can force it by doing an explicit load of a particular module in<br>
modules.conf. Explicitly loaded modules are loaded before all<br>
automatically-loaded modules.<br>
<font color="#888888"><br>
--<br>
Tilghman & Teryl<br>
with Peter, Cottontail, Midnight, Thumper, & Johnny (bunnies)<br>
and Harry, BB, & George (dogs)<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Steve Murphy<br>ParseTree Corp<br><br>