similar to: Asterisk 1.6 AEL Macro vs GoSub

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

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

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

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

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

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

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

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

2008/12/2 Philipp Kempgen <philipp.kempgen at amooma.de> > Philipp Kempgen schrieb: > > Olivier schrieb: > > > >> 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 >

Hi I'm using a macro to dial in a AEL dialplan. The problem is the macro do not set the field CDR(dst), showing only ~~s~~. I tried various configurations, but without solutions. This is the macro: macro dial-out(destno,dialstring,route_descr,interno) { __TRANSFER_CONTEXT=ipbx; if(${interno} = 1) { Set(__PICKUPMARK=${destno}); if(${ODBC_verify_user(${CALLERID(num)})} > 0) { t = tT; }

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 I'm using a macro to dial in a AEL dialplan. The problem is the macro do not set the field CDR(dst), showing only ~~s~~. I tried various configurations, but without solutions. This is the macro: macro dial-out(destno,dialstring,route_descr,interno) { __TRANSFER_CONTEXT=ipbx; if(${interno} = 1) { Set(__PICKUPMARK=${destno}); if(${ODBC_verify_user(${CALLERID(num)})} > 0) { t = tT; }

How consistent has the syntax for extensions.ael been from version to version? extensions.conf has annoyed me in this regard. i.e.: commas to pipes, pipes back to commas, macro to gosub, etc etc.

Hello-- It's been a while since I wrote any updates about AEL/AEL2 to the users list, and I thought it might be worthwhile to update everyone on what is going on in respects to AEL. What the heck is AEL? The Asterisk Extension Language. A higher level language for extensions.conf, which will appear in the config file, extensions.ael, in the /etc/asterisk/ (or equiv) directory. It provides

Hello, How can you parse a comma separated list using function CUT and AEL ? I've tried but it displays error message (though is seems to find the correct value) : STRING=101,102 VAL=${CUT(STRING,\,,1)}; NoOp(VAL is ${VAL}); Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL:

2009/12/3 Olivier <oza-4h07 at myamail.com> > Hello, > > How can you parse a comma separated list using function CUT and AEL ? > > I've tried but it displays error message (though is seems to find the > correct value) : > > STRING=101,102 > VAL=${CUT(STRING,\,,1)}; > NoOp(VAL is ${VAL}); > > Cheers > Sorry for the noise but I mixed up with another