similar to: Replacement of Macro() with Gosub()

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() {

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

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

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

Hello, I want that after client and queue member call would be established, cmd queue runs some 'procedures' . So I am using cmd Queue option 'gosub'. This is my example of ael : context QUEUE { _X. => { Ringing(); Wait(4); Answer(); Queue(${Queue},wr,,,60,,,check-record); Hangup(); }; }; macro check-record() {

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

Hi, according to discussion on asterisk IRC, where people said, that macros will be depracated, I tried to migrate from macros to contexts and Gosub but if I try to use gosub in extensions.ael, ael compiler complains, that I shouln't use Gosub app, but I can't find ael keyword, that will be Gosub equivalent, or can I ignore this ael warnings? thanks PJ LOG: lev:3 file:pval.c

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

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

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

Hi, I have recently run into the problem with macro implementation in AEL in Asterisk 1.6. I have some older AEL dialplan which runs on 1.4 but it does not on 1.6 and I'm not sure how to solve this correctly. Let me explain... For example, in Asterisk 1.4 I have a macro like this: macro read_digits(digits) { Set(playlist=${SHELL(${PYTHON} ${SCRIPTS}/read_digits.py

I have to design a dialplan for mulitple contexts (multiple companies) and I'm not sure how to go about it and I thought someone may offer help. Here is some background. There are three separate companies, let's say A, B and C. Each has their own context and each has their own set of numbers (these are just examples, not the actual config): [ContextA] exten =>

I'm trying to clarify contexts and their uses. I do have a good general understanding of them. My question is about "undeclared" and "non-existant" contexts. If I have a block somewhere (in sip.conf, for example), and it has no "context=thiscontext" field, does it just automatically use the "default" context? Or is this settable? (I see there is an

Hello, all. I've got a problem where we set up call pickup for a customer. If the Bob's extension rings and Bob is in Jim's office, Bob can press the button on his Snom 320 that says "Bob" and pick up his line. It works great for calls coming in from the outside but does not work for internal calls. Internal calls generate a app_directed_pickup.c:204 pickup_exec: No

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

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

hi!, Asterisk Version:1.6.1.20 OS: CentOS release 5.3 (Final) uname: 2.6.18-128.el5PAE #1 SMP Wed Jan 21 11:19:46 EST 2009 i686 i686 i386 GNU/Linux Application: Queue Specific Details: Obtain Acknowledgement from queue member before bridging the caller. Language: AEL Similar Example:http://www.voip-info.org/wiki/view/Asterisk+tips+Queue+Member+ackcall Scenario: 1. User calls in a General Number

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here's one that may be of interest to any upgraders. If you rely on the behavior of gosub you may want to make note of this change. I have an incoming call context: exten => _XXXX,n,GoSub(incoming,${EXTEN},1(${EXTEN})); that is supposed to gosub into the incoming extension at priority 1. Versions before 1.6.0.6 would drop into the

I have a caller screen queue setup. Basically a caller calls in, goes through a IVR, and before that caller is put into the queue, they get a sub ran on them first asking for them to say there name. That gets saved and they are entered into the queue using Queue(mainqueue,,,,300). In the queues.conf i have a list of members these are local/extension at external-default, there are two