similar to: clarification on gosub, macros and AEL

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

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

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

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

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

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

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

Hi, I think this must be a bug introduced with 1.6.2.17.something. When I upgrade from asterisk-1.6.2.16.1 to asterisk-1.6.2.17.2 or 1.6.2.18, my AEL Dial() commands with the "U" options fail with the following error: [May 3 12:05:54] ERROR[6300] app_stack.c: Attempt to reach a non-existent destination for gosub: (Context:screen, Extension:s, Priority:1) Here are the segments

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

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

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

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, How can you use Dial application M(x) option from extensions.ael ? (As a reminder, this M(x) executes macro x when Dial called party answers). It seems to me that asterisk keeps looking for this macro in extensions.conf and not in extensions.ael. I tried both (and variations of those with ^ instead of ,) : Dial(Local/${EXTEN:1},,M(mymacro(${EXTEN}));

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

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

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! Since 1.6, when using AEL, macros are implemented using Gosub(). Is there workaround to have MACRO_EXTEN also in this case? regards Klaus PS: I know I could use something like context fromSip { 11 => &myMacro(${EXTEN}) } macro myMacro(MACRO_EXTEN) { } but isn't there some workaround to achieve compatibility with 1.4?

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