[asterisk-bugs] [Asterisk 0013357]: AEL doesn't like using dialplan function call as argument for 'jump' statement

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13357 
====================================================================== 
Reported By:                pj
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   13357
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 138442 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-08-21 10:57 CDT
Last Modified:              2008-09-04 18:05 CDT
====================================================================== 
Summary:                    AEL doesn't like using dialplan function call as
argument for 'jump' statement
Description: 
if I try to use function call to return value for jump statement, it fails
due to syntax error below...
if I call jump statement with variable as argument it's working fine

BAD:
jump ${DB(uri/${uri_string})};

OK:
Set(line=${DB(uri/${uri_string})});
jump ${line};

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013416 Function CUT doesn't work if passed as ...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-04 18:05 svnbot         Status                   assigned => resolved
2008-09-04 18:05 svnbot         Resolution               open => fixed       
======================================================================