[asterisk-bugs] [JIRA] (ASTERISK-20355) Provide an entry point for stdexten written in AEL from pbx_config.c

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-20355:
-------------------------------------

    Assignee: Asterisk Team  (was: Octavio Ruiz)
      Status: Open  (was: Waiting for Feedback)

> Provide an entry point for stdexten written in AEL from pbx_config.c
> --------------------------------------------------------------------
>
>                 Key: ASTERISK-20355
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20355
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Core/Configuration, PBX/pbx_ael, PBX/pbx_config
>    Affects Versions: SVN, 11.0.0-beta1, SVN, 11.0.0-beta1
>         Environment: Centos 5, Centos 6
>            Reporter: Octavio Ruiz
>            Assignee: Asterisk Team
>            Severity: Minor
>              Labels: AEL, AELSub, Gosub, Macro, asterisk
>         Attachments: aelsub-stdexten.patch
>
>
> ASTERISK-18809 and ASTERISK-19457 changed the way pbx_config.c invokes the stdexten subroutine from Macro to Gosub, providing examples at extensions.conf and without a means of backwards compatibility.
> Since this change, any stdexten written in AEL would be not reachable by the Gosub application when configuring pbx_config.so to do so due the new approach of how stdexten through Gosub is called (explained in extensions.conf.sample).
> Being not able to define arbitrary priorities in AEL there is no way to re implement stdexten in this language having to fall back to Macro application loosing the benefit of better nesting and the   Gosub use trend.



--
This message was sent by Atlassian JIRA
(v6.2#6252)