similar to: Gosub replacement within AEL2 dialplans

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

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

Hello, I'm using AEL2 (in Asterisk 1.6.1.6) and I can't find a way to successfully come back into my dialplan. I've tried things like this (in features.conf) : toto => #9,peer,Goto,mylocal2,s,1 But typing #9 (from channel SIP/7275, in example bellow) I've got: -- Feature Found: toto exten: toto -- Started music on hold, class 'default', on SIP/7275-08b7fbe0

Hi, I'm using asterisk 1.6.1 and AEL2. I'm trying to find the best way to write my own custom functions ? At the moment, I'm using this pattern (extensions.ael) : context foo { 123 => { &myfunc(123456); NoOp(${GOSUB_RETVAL}); }; macro myfunc (arg) { Return (${arg}); } 1. First, I keep getting warnings like Warning: file /etc/asterisk/extensions.ael, line

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

Call to Action! For those who have the courage/ability, go grab an SVN copy of the asterisk release, the HEAD version, and my latest patch, from: http://bugs.digium.com/view.php?id=6021 Right now, the latest version of the patch is 0.10. apply it to the SVN head version, and do a "make". Read the Wiki on AEL2: http://www.voip-info.org/wiki/view/Asterisk+AEL2 Look at the examples

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

Does anyone know how to get CID working in AEL2 ? In extensions.conf you can do: exten => 111/666,1,PlayBack(demo-congrats) exten => 111/666,2,Hangup() exten => 111,1,PlayBack(demo-moreinfo) exten => 111,2,Hangup() and if callerid 666 dialed 111, they would get demo-congrats, everyone else gets demo-moreinfo. In AEL: 111 => { Playback(demo-moreinfo);

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

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

I just want to confirm but it seems that if-then-else is not permitted in case structure. It was not really documented but it seems to be the case. Can anyone confirm? switch(${DIALSTATUS}) { case NOANSWER: { // if-then-else not permitted If (${ael-var} = 1) { Playback(beep);

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

Where's Steve Murphy when you need him? :-) This doesn't seem to work in AEL2... Macro foo(arg1) { ..... Includes { Hangup; } } The error is: File: /etc/asterisk/extensions.ael, Line 59, Cols: 5-12: Error: syntax error, unexpected KW_INCLUDES, expecting '}' The same error does not occur when the includes is in a context. I need to

Hey all, I am very interested in using AEL2 (don't want to upgrade to 1.4 to get it though), but am having some problems upgrading/patching my asterisk system. I am following the instructions on the wiki: http://www.voip-info.org/wiki/view/Asterisk+AEL2#AEL2AnnouncementsandNews But get the following error:

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 am struggling to find out how to code hint in AEL2. I did hint(Custom:light1) and it keeps complaining about the : (colon). It works fine for SIP device like hint(SIP/439). Anyone who has tried it before?

Hi! All the AEL examples have a semicolon after the closing curly bracket, e.g: context test { 1 => Hangup(); }; but without ; it works fine too, e.g: context test { 1 => Hangup(); } So - what is the reason for the ; after the closing curly bracket? thanks klaus

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

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