search for: mymacro

...me[,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 => s,1,answer() exten => s,1,Queue(myQueue,,,,,,myMacro) but, there is no arguments there, right? what about use exten => s,1,answer() exten => s,1,Queue(myQueue,,,,,,myMacro,arg1) (remember that macro works like exten => s,n,Macro(myMacro,myArg1,myArg2), that means, concatenate args after macro name, separate with comas. but.... Queue t...

...(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})); Dial(Local/${EXTEN:1},,M(&mymacro,${EXTEN})); both lead to unexpected results: macro_exec: No such context 'macro-mymacro' for macro 'mymacro' As a workaround, I could write my macro in extensions.conf, but ... Regards -------------- next part -------------- An HT...

...e. I tested with SPA3102 and cisco2811 as gw and asterisk 1.8.26.1 as well as 11.8.1 Other end is analog number behind another cisco/asterisk, also tested calling a mobile number with the same result. What I did: dial is done like exten => s,n,Dial(SIP/<IP gw>/<dialed number>,,M(myMacro)), which tell Asterisk to execute myMacro when the call is answered by calling party. [myMacro] exten => s,1,NoOP(Executed when call is answered) same => n,AMD() same => n,NoOp(Dial status=${DIALSTATUS}) same => n,NoOp(AMD status=${AMDSTATUS} cause=${AMDCAUSE}) same => n,M...

...n 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})); > >> Dial(Local/${EXTEN:1},,M(&mymacro,${EXTEN})); > >> > >> both lead to unexpected results: > >> macro_exec: No such context 'macro-mymacro' for macro 'mymacro' > > > > I'd say use the U option instead of G. >...

Hi, I have defined a dialplan in lua and now would like to use "dial" with the macro M to implement some logic, when the callee-channel gets created. Working old style would be (extensions.conf) [default] exten => _X,1,dial(SIP/1,,M(mymacro^parameter)) [macro-mymacro] exten => s,1,verbose(${ARG1}) How to implement the same functionality using pbx_lua? Details: Asterisk 11.7 on Ubuntu 14.04 Kind regards Dennis Guse Quality and Usability Lab Telekom Innovation Laboratories TU Berlin Ernst-Reuter-Platz 7 D-10587 Berlin, Germany...

Bug or feature? I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, eg \mymacro{}: Error in tools::parse_Rd(fn) : Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but the error is not specific to this particular macro....

...hannel stops ringing/moh, and audio from the source is bridged into the destination. I have tried various options to the Read application, but none have altered the results. An example of the behaviour: Calling party on channel SIP/YYY dials XXX, hits dialplan: exten => XXX,1,Dial(SIP/ZZZ,,mM(mymacro)) Macro looks something like: [macro-mymacro] exten => s,1,Playback(somefile) ;This plays fine on channel SIP/ZZZ exten => s,n,Read(somevar,audioprompt) ;audioprompt plays fine, then immediately after playing the prompt, channel SIP/ZZZ starts hearing audio data from SIP/YYY, moh...

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?

I have built a dialplan which dial to someone with option M. Dial (SIP/1000,,M(MYMACRO)) Both parties are SIP phones. MYMACRO expects person on SIP/1000 dial 5 (using read) then exits - and doing so it bridges my phone (SIP/2000) with SIP/1000. If SIP/1000 hangs up before dial 5 - ok the call ends. if SIP/2000 hangs up before SIP/1000 dial 5 - the macro is unaware and keeps waiti...

...y arguments to macros (they will expand to an empty string, like in LaTeX). Best Tomas On 05/14/2018 11:23 PM, Georgi Boshnakov wrote: > Bug or feature? > > I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, > eg \mymacro{}: > > Error in tools::parse_Rd(fn) : > Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' > > A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but the error is not specific to...

...y arguments to macros (they will expand to an empty string, like in LaTeX). Best Tomas On 05/14/2018 11:23 PM, Georgi Boshnakov wrote: > Bug or feature? > > I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, > eg \mymacro{}: > > Error in tools::parse_Rd(fn) : > Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' > > A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but the error is not specific to...

Hello list ! This is my call to the macro : exten => 36,n,Macro(mymacro,${KNUMMER},yo) This is where {ARG1} and {ARG2} are used inside the macro : exten => s,n,Voicemail(${ARG1}@${ARG2},s) This the output on the CLI : VoiceMail("IAX2/zoiper-13958", "908001@|s") The variable ${KNUMMER} is set in the dialplan and well replaced by 908001. But {...

...d to an empty string, like in LaTeX). > > Best > Tomas > > On 05/14/2018 11:23 PM, Georgi Boshnakov wrote: >> Bug or feature? >> >> I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, >> eg \mymacro{}: >> >> Error in tools::parse_Rd(fn) : >> Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' >> >> A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but the err...