Summary: | ASTERISK-09518: MACRO_EXTEN, MACRO_... is empty in AEL | ||
Reporter: | Mike Anikienko (mike anikienko) | Labels: | |
Date Opened: | 2007-05-25 11:53:36 | Date Closed: | 2011-06-07 14:08:00 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | PBX/pbx_ael |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) ast-1.4.4.txt ( 1) ast-1.4.4-debug.txt ( 2) trunk-r66178M.txt ( 3) trunk-r66178M-debug.txt | |
Description: | In AEL ${MACRO_EXTEN} and other MACRO_... is emtpy: -- Executing [s@test-macros:3] NoOp("SIP/100-0825a0d8", "EXTEN=s MACRO_EXTEN=") in new stack But in the same dialplan in asterisk-1.4.4 this variable have properly value: -- Executing [s@macro-test-macros:3] NoOp("SIP/100-0823bfc0", "EXTEN=s MACRO_EXTEN=123") in new stack In attach all information what I cat catch. I dont know how to catch more. ****** ADDITIONAL INFORMATION ****** My context in extensions.conf: exten=> 2221,1,Goto(testmacros,123,1) My extensions.ael: context testmacros { 123 => { &test-macros(10,"test"); Hangup(); } } macro test-macros(var1,var2) { noop(EXTEN=${EXTEN} MACRO_EXTEN=${MACRO_EXTEN}); } | ||
Comments: | By: Steve Murphy (murf) 2007-05-25 12:41:20 The problem that's biting you here is that AEL in trunk, uses GOSUB instead of Macro to execute (and define) macros. In a gosub, you don't get the cool MACRO_EXTEN and friends. Note that in the trunk version, it didn't call MACRO, it called Gosub to go to the test-macros routines. Review the docs for Gosub and Macro, and somewhere in the release docs for trunk/1.4, I explain why I changed. If you can't find it, I'll regurgitate it in this bug. Reopen and demand an explanation, and I'll be happy to regurgitate the reasons for the change. By: Steve Murphy (murf) 2007-05-25 12:43:12 So, I'm closing this one now. See above. |