similar to: What happened to MACRO_EXTEN in AEL macros since 1.6?

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, 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}));

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

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

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

Hi, all. I'm making my first foray into AEL. I'm starting with a simple macro, but I've already encountered an odd behaviour. I'm wondering if someone can shed some insight: Asterisk 1.2.9.1 macro newPlaceCallPSTN { s => { TIMEOUT(absolute)=7200; NoOp(Analog Out List: ${ANALOGOUT}); ChanIsAvail(${ANALOGOUT}); NoOp(Available Out List:

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

hi list, i have a question about the args of queue: when we use Queue() app, there are some arguments than can use. help from CLI: Queue(queuename[,options[,URL[,announceoverride[,timeout[,AGI[,macro[,gosub[,rule]]]]]]]]) well.. i'm trying to identify who has taken the call on a queue, and, when agent conected, launch a macro with some args based on who takes the call i do: exten =>

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

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

Hei! I have a little problem with the subject. I use Asterisk CVS-HEAD-09/06/04-12:42:56 as a production *, but I do tests with a newer version Asterisk CVS-HEAD-11/18/04-10:01:32. Ok the problem is: in extension.conf I use macro for redirection, found on wiki pages: [macro-stdexten] ; ; Standard extension macro (with call forwarding): ; ${ARG1} - Extension(we could have used ${MACRO_EXTEN}

Hi! I use an "if" condition in extensions.ael to check if a channel variable is defined and if defined I add a certain header: context toNormaleRufe { _X. => { if (${NUMBER}) { SIPAddHeader(X-NUMBER: ${NUMBER}); }; ... }; This works fine, except NUMBER starts with the + sign. I tried using quotes but if