| Summary: | ASTERISK-04582: ${MACRO_EXTEN} is not always | ||
| Reporter: | Johann Hoehn (johann) | Labels: | |
| Date Opened: | 2005-07-13 13:17:39 | Date Closed: | 2011-06-07 14:10:47 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | If a macro is called in an from an option that is chosen, then ${MACRO_EXTEN} is not being set. I was writing a macro to make some repeated checks a bit less cumbersome and wanted to be able to use ${MACRO_CONTEXT}, ${MACRO_EXTEN}, and ${MACRO_PRIORITY} to goto a slightly different point at the end depending on the results of the checks. To workaround it, I can just slap the return context/exten/priority as part of the agruments list. ****** ADDITIONAL INFORMATION ****** Example extensions.conf to trigger the problem: [macro-foo] exten => s,1,NoOp(Macro_Exten is ${MACRO_EXTEN}) [menu] exten => s,1,Background(somefile) exten => 1,1,NoOp(Exten is ${EXTEN}) exten => 1,2,Macro(foo) | ||
| Comments: | By: twisted (twisted) 2005-07-13 13:22:36 Can you please test this on 1.0.9? also on HEAD to see if the issue exists there? By: Johann Hoehn (johann) 2005-07-13 14:45:12 The above is a simplified version and is no longer having the problem. I checked with 1.0.8 and 1.0.9. The steps to reproduce are a bit more involved...double checking to see if might have been a error on my part. I recommened closing this bug for now. By: Russell Bryant (russell) 2005-07-13 15:19:07 closing for now at the request of the original poster | ||