similar to: AEL and swap from macros to contexts

Hello, When reloading a diaplan (asterisk 1.6.1.X), I can see in console : [Apr 2 09:02:00] WARNING[2217]: ael/pval.c:2522 check_pval_item: Warning: file /etc/asterisk/extensions.ael, line 621-621: application call to Gosub affects flow of control, and needs to be re-written using AEL if, while, goto, etc. keywords instead! What is then the recommended substitution for Gosub() application

I'm trying to clarify my understand of gosub, macros and AEL. My understanding is that macros using the Macro() application, which is defined in extensions.conf by: [macro-foo] ... and called in extensions.conf with exten => _9NXXNXXXXXX.,n,Macro(fastbusy) is deprecated in favour of Gosub(). True so far? But then there are "macro"s defined in extensions.ael: macro foo() {

Hello, I am trying to alter the outbound callerID for extensions within a context I have created. I wrote the following: exten => _9.,2,ExecIf($[$["${REALCALLERIDNUM}" = "360"] | $["$ {REALCALLERIDNUM}" = "670"]]|Set|CALLERID(num)=581560) exten => _9.,3,ExecIf($[$["${REALCALLERIDNUM}" = "361"] | $["$

How do I include a file (not a context) in AEL? #include "filename" returns an error. Thanks, Jay

I have two offices sharing a phone system. They also share a common internal context because all of the employees of the second office also work for the first office. Each office has 4 outside lines and I have defined 2 channel groups in my zapata.conf. The second office needs all of their outgoing calls to go out over their lines so the people they call will have the correct callerID. I

I am building a new Asterisk server here at the office, and I'm wondering if there are any downsides to creating my dialplan with AEL. It seems more intuitive (to me), but I'm not sure if there are any pitfalls I need to be aware of first. We use this for internal extensions, 8 pots lines, and our answering service which gets about 500 incoming calls a day down our T1. Also, one more

Hi Everyone, Sorry, if this has been already discussed, but maybe someone encountered interesting issue. I have an * Dialplan configured with MySQL db. Everything works excellent, except, I can't specify the "ex-girlfriend logic". For example Context exten Priority app appdata Default 400 1 Wait 20 Default 400/100 1 Wait 10 So, it does not matter what is my callerid,

Hi, I've new to http://www.voip-info.org/wiki/view/Asterisk+AEL2 I'm using NoOp and Verbose functions inside extensions.ael. Strangely, NoOp is not printing anything in Asterisk console while Verbose is working. Am I missing something obvious ? Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL:

>>> Nobody has any information or opinions on any of this? Personally, I don't think MACROS are going anywhere any time soon, so I have not bothered looking into a substitution. As for ael; I've never used it. Doug

Almost two years ago, a change between how AEL code is built into Asterisk dialplan between minor versions made clear the need to provide a sane entry point into AEL subroutines and that's how AELSub() born. With Asterisk 11 release, they way [stdexten] at extensions.conf is invoked changed from Macro to Gosub using the 'missing context feature' and this caused that any stdexten

I just discover an "hidden" problem with AEL macro I want to have your feedback. If you use a macro to dial out, like &dialout(${EXTEN}), the leg extension will became ~~~~s~~~~ and if it happens you transfer the call, that will be the callerid appearing on the other phone display. I am just rewriting all the dialplan getting rid of the macro and using gosub, even if asterisk is

when i wnat to working with realtime and mysql for any context i have to insert (switch => Realtiem/context at extensions) statment into extensions.conf for example if i want to have 10 context, i have to insert these lines into extension.conf : [context1] switch => Realtiem/context1 at extensions [context2] switch => Realtiem/context2 at extensions [context3] switch =>

Hi, Is there some more thorough documentation of this change that has happened in 1.6? The upgrade.txt and changes.txt files mention it, but I have already seen details of this change that do not appear to be documented except in conversations on the mailing list... 1) It appears that it is no longer legal to have: [macro-contaxtA] ...stuff... [contextA] ...stuff... Is this true? Or have I

Hi, Am writing scripts to manage configuration management and Asterisk. I would like to be able to point the asterisk binary at config directory with an asterisk.conf in it, and for asterisk to run a pre- flight check. A bit like a pint check in php, 'apachectl configtest' and lots of other tools. asterisk will then exit with 0 on a safe config, and 1 on a bad config. I can

Hi, For some reason (outbound call tracking) I've got a few different outbound call process (using a macro for queuemetrics logging, or direct call) i wanted to factorise the routing process so i came up with something like the following. All in one it's working like expected, however every "ael reload" command trigger a lot of warning like that "application call

Hi all, I've just upgraded to latest 1.6.0 SVN from a few days ago and my Gosubs have stopped working. This is from the verbose logs: -- Executing [03333407271 at incoming-aaisp:4] GotoIf("IAX2/aaisp-3802", "1?5:7") in new stack -- Goto (incoming-aaisp,03333407271,5) -- Executing [03333407271 at incoming-aaisp:5] Gosub("IAX2/aaisp-3802",

Hi, I can't figure out what syntax to use with the Dial() "M" parameter for the AEL parser to interpret properly. Creating an AEL macro named "macro-screen()" partly works as a hack, but it must not turn into a gosub properly, so I get warnings about the "return;". Dial(...,tgM(&screen)) with the ael macro named "screen" does not work

Has any one used this? U(x[^arg[^...]]): x - Name of the subroutine to execute via Gosub arg - Arguments for the Gosub routine Execute via Gosub the routine <x> for the *called* channel before connecting to the calling channel. Arguments can be specified to the Gosub using '^' as a delimiter. The Gosub routine can set the variable ${GO

Greetings list, Over the last few days I've been gearing up to replace a couple of our servers with 1.6 as something of a testbed, but I'm encountering a few problems, and wondering if anyone can help... In extensions.conf, there are a number of contexts defined for each group of users, along the lines of: [groupa] [groupb] etc. In each of those, there's a command include =>

How does one go about accessing gosub arguments from Asterisk in extensions.lua? For example, I have the following in extensions.conf: exten => 1000,1,Wait(1) exten => 1000,n,Gosub(functions,mytest,1("123")) exten => 1000,n,Hangup And then the following in extensions.lua: extensions = { functions = { ["mytest"] = function()