[asterisk-bugs] [Asterisk 0011329]: AEL macro argument variables aren't properly quoted when set

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=11329 
====================================================================== 
Reported By:                rain
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   11329
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.14  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 reopened
Fixed in Version:           
====================================================================== 
Date Submitted:             11-20-2007 15:40 CST
Last Modified:              01-11-2008 14:09 CST
====================================================================== 
Summary:                    AEL macro argument variables aren't properly quoted
when set
Description: 
When the dialplan code is generated to set a macro's variables, the
argument data isn't properly escaped, causing the loss of any quoting in
the macro.  For example, if the macro in the 'additional information' field
was called like so:

&foo(abc "def" geh);

...the following message would be logged:

I got [abc def geh] but I want it to look like [abc "def" geh]

The easiest fix is probably to wrap ${ARGn} inside a ${QUOTE()} in the
generated dialplan code.
====================================================================== 

---------------------------------------------------------------------- 
 murf - 01-11-08 14:09  
---------------------------------------------------------------------- 
Sorry, but if I change this now, we'll have an armed uprising.

It could easily cause some really unexpected, strange problems for users. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-11-08 14:09  murf           Status                   assigned => closed  
01-11-08 14:09  murf           Note Added: 0076739                          
======================================================================