Yes it does. It allows me to match all dialled numbers with _. and then perform pre-dialling initialisation in the AGI script before the number is dialled. This can’t be done in extensions.conf.[/quote]
No, it does not. You must still match a dialed SIP extension (in this case the wildcad _. matching) before you may call an AGI/FastAGI in the first place. The same situation exists whether you use the logic of an extensions.conf dialplan or an AGI that forks from an extensions.conf dialplan, as the calling mechanism is still an extensions.conf dialplan.
You may also use the wildcard matching in conjunction with GotoIfs and string/variable manipulation within the extensions.conf dialplan to acheive this. You are not solving a pereived ‘limitation’.
[quote=“dgarstang”]sigh So, without the ability to include variables in #include statements, we have to do:
whereas with a variable we could have done…
which is substantially easier.[/quote]
This is not possible, nor is it necessary to acheive what you are looking for. As stated before, #includes are just a way of breaking down an extensions.conf into fragments to make them more modular/manageable and are all loaded at startup. You may do your stated requirements in various ways, including the use of the MySQL cmd within the dialplan itself, or using the internal Asterisk database.
As stated, the extensions.conf dialplan does have limitations, as does any scripting environment. The point is that the requirements you describe are all doable within extensions.conf, there are not limitations in this regard.
Further, it is possible to drop the extensions.conf into a database (using Realtime) to enhance the manageability, but using the same logic.
[quote=“dgarstang”]a) If someone had some decent documentation, this wouldn’t be the case, and
b) I’m doing fine with Asterisk. As I stated before, we’re performing quite advanced functions with it.[/quote]
Your two statements above are contradictory. First you say you don’t know it because you don’t have access to decent documentation, and then you say you know it just fine. Which is it?
It would appear from the posts that number one is more accurate, as you are describing limitations that only exist in your mind. There is plenty of documentation available online and in print form, none of it is perfect so to become fluent with Asterisk it requires a creative approach and willingness to learn through trial and error. This is an opensource community project afterall.