[asterisk-bugs] [Asterisk 0014267]: macro compatibility

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14267 
====================================================================== 
Reported By:                dimas
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14267
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 169153 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-18 16:27 CST
Last Modified:              2010-10-18 00:06 CDT
====================================================================== 
Summary:                    macro compatibility
Description: 
In 1.4 AEL used to generate macro- prefix for all macro contexts and
transform &m1() calls to Macro(m1). Now 1.6 Macro is deprcated and AEL
generates Gosub instead and does NOT generate macro- prefix.

The problem is that if your dialplan calls AEL macros from regular
dialplan - it will not work because AEL-generated macros do NOT have macro-
prefix while Macro application will add it. For the same reason features
like

myfeature => #,self,Macro,feature1

will not work anymore if feature1 is defined in the AEL.
====================================================================== 

---------------------------------------------------------------------- 
 (0128139) tilghman (administrator) - 2010-10-18 00:06
 https://issues.asterisk.org/view.php?id=14267#c128139 
---------------------------------------------------------------------- 
Please review the current configs/features.conf.sample.  There are 3
syntaxes currently for specifying application arguments in features.conf. 
I will include them here for brevity:

; The syntax for declaring a dynamic feature is any of the following:
;
;<FeatureName> =>
<DTMF_sequence>,<ActivateOn>[/<ActivatedBy>],<Application>[,<AppArguments>[,MOH_Class]]
;<FeatureName> =>
<DTMF_sequence>,<ActivateOn>[/<ActivatedBy>],<Application>[,"<AppArguments>"[,MOH_Class]]
;<FeatureName> =>
<DTMF_sequence>,<ActivateOn>[/<ActivatedBy>],<Application>([<AppArguments>])[,MOH_Class]

The second two syntaxes are designed to allow you to use commas between
arguments and not conflict with the commas in this configuration line.  Is
this the syntax you are using?  Does this not work for some reason? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-18 00:06 tilghman       Note Added: 0128139                          
======================================================================