[asterisk-bugs] [Asterisk 0014941]: Using '@' to specify a context in AEL will cause parse errors

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14941 
====================================================================== 
Reported By:                bpgoldsb
Assigned To:                seanbright
====================================================================== 
Project:                    Asterisk
Issue ID:                   14941
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.1.0-rc4 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-04-20 14:01 CDT
Last Modified:              2009-04-20 15:58 CDT
====================================================================== 
Summary:                    Using '@' to specify a context in AEL will cause
parse errors
Description: 
The following code in the older style of dialplan will create a hint for
701 without errors:

exten => 701,1,ParkedCall(701)
exten => 701,hint,park:701 at parkedcalls 

The equivalent AEL code below will cause the AEL parser to throw a syntax
error:

hint(park:701 at parkedcalls) 701 => ParkedCall(701)
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-20 15:58 svnbot         Status                   new => assigned     
2009-04-20 15:58 svnbot         Assigned To               => seanbright      
2009-04-20 15:58 svnbot         Status                   assigned => resolved
2009-04-20 15:58 svnbot         Resolution               open => fixed       
======================================================================