[asterisk-bugs] [Asterisk 0018910]: After update from asterisk-1.6.2.14 to asterisk-1.6.2.17 Gosub(macro, s, 1(args)) stopped working
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Mar 3 16:36:08 CST 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18910
======================================================================
Reported By: alexandrekeller
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18910
Category: PBX/pbx_ael
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.6.2.17
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-03-02 18:31 CST
Last Modified: 2011-03-03 16:36 CST
======================================================================
Summary: After update from asterisk-1.6.2.14 to
asterisk-1.6.2.17 Gosub(macro,s,1(args)) stopped working
Description:
After update from asterisk-1.6.2.14 to asterisk-1.6.2.17
Gosub(macro,s,1(args)) stopped working.
Then I realized all my AEL macros wasn't created with extension s, instead
there is a ~~s~~ extension, which has broken my entire dialplan.
What happened? How to solve that?
Thanks
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0018480 [patch] Contexts with a 'switch' statem...
======================================================================
----------------------------------------------------------------------
(0132614) tilghman (manager) - 2011-03-03 16:36
https://issues.asterisk.org/view.php?id=18910#c132614
----------------------------------------------------------------------
Given that subroutines have changed before, we find it odd that you're
adamant that such implementation details don't change. However, we're
discussing creating an application called something like CallAEL(), that
will allow you to call a particular routine built in AEL, whose redirection
will remain stable, even if the internals change. We believe this would
meet your requirements. What do you think?
Issue History
Date Modified Username Field Change
======================================================================
2011-03-03 16:36 tilghman Note Added: 0132614
======================================================================
More information about the asterisk-bugs
mailing list