[asterisk-bugs] [Asterisk 0014941]: Using '@' to specify a context in AEL will cause parse errors
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Apr 20 15:37:33 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14941
======================================================================
Reported By: bpgoldsb
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14941
Category: PBX/pbx_ael
Reproducibility: always
Severity: minor
Priority: normal
Status: new
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:
======================================================================
Date Submitted: 2009-04-20 14:01 CDT
Last Modified: 2009-04-20 15:37 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)
======================================================================
----------------------------------------------------------------------
(0103488) bpgoldsb (reporter) - 2009-04-20 15:37
http://bugs.digium.com/view.php?id=14941#c103488
----------------------------------------------------------------------
Tested on a clean source and works great.
Issue History
Date Modified Username Field Change
======================================================================
2009-04-20 15:37 bpgoldsb Note Added: 0103488
======================================================================
More information about the asterisk-bugs
mailing list