similar to: Fwd: Goto(${PREV_CONTEXT},s,1) functionality?

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

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

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

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

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

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

Hello, I'm not understanding how to use GOSUB_RESULT in U() option from Dial app (I'm using 1.6.1) My extensions.ael is : context mylocal { 2 => { Dial(SIP/7530,,U(mynotify)); HangUp(); }; 3 => { Dial(SIP/7531); HangUp(); }; }; macro mynotify () { GOSUB_RESULT=ABORT; }; 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 >

Hello, we have an asterisk (1.4.21.2) with ZAP and mISDN channels, the mISDN are 2 incoming GSM Modems, each with 2 simcards. No, the mISDN line one and two are fine, but when I get a call on line 3 something with the time is wrong. Timeconditions fall through to off-hours even if the time of the call is clearly inside business hours, here a log excerpt: [Aug 26 11:04:36] VERBOSE[3112]

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 All, This question is probably more for the LDAP experienced users/developers as I'm sure it would work fine if I weren't using LDAP (but I am, and I'm almost there with the setup!!!). I've setup an extension with the following: AstExtension: 210 AstApplication: Macro AstApplicationData: call-ext,SIP/testuser&IAX2/testuser,210 When I dial this extension, I see the

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.

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?