[Home]

Summary:ASTERISK-27950: Context Visability between AEL and Extensions
Reporter:Mark Murawski (kobaz)Labels:
Date Opened:2018-07-02 14:21:17Date Closed:2020-01-14 11:13:53.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Applications/General
Versions:13.21.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Mixed extensions.conf / aelAttachments:( 0) patch-13-feb6768
Description:Given the following extensions.conf configuration
{noformat}
[foo]
exten => 1234,1,NoOp(stuff)
same => n,Hangup()
{noformat}

Given the following ael configuration:
{noformat}
extend context foo {
 11223344 => {
   NoOp(AEL);
 }
}

context bar {
 s => {
   goto foo, 1234, 1;
 }
}
{noformat}

The following generated dialplan should be created
{noformat}
[ Context 'bar' created by 'pbx_ael' ]
 's' =>            1. Goto(foo,1234,1)                           [pbx_ael]

[ Context 'foo' created by 'pbx_ael' ]
 '11223344' =>     1. NoOp(AEL)                                  [pbx_ael]
 '1234' =>         1. NoOp(stuff)                                [pbx_config]
                   2. Hangup()                                   [pbx_config]
{noformat}

Instead, we get the following error:
{noformat}
check_abstract_reference: Warning: file /etc/asterisk/extensions.ael, line 6-10: Couldn't find a reference to this abstract context (foo) in any other context!
check_goto: Error: file /etc/asterisk/extensions.ael, line 14-14: goto:  no label 1234|1 exists in the context foo or its inclusions!
pbx_load_module: Sorry, but 0 syntax errors and 1 semantic errors were detected. It doesn't make sense to compile.
{noformat}

The applied patch fixes the issue with goto, and will allow the ael to load.  It does not yet however, fix the warning about the context reference
Comments:By: Asterisk Team (asteriskteam) 2018-07-02 14:21:17.840-0500

The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process.
By: Asterisk Team (asteriskteam) 2018-07-02 14:21:18.170-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Kevin Harwell (kharwell) 2018-07-03 09:50:51.351-0500

[~kobaz] Are you thinking you'll try (get a chance) to push the patch(es) up to gerrit?
By: Asterisk Team (asteriskteam) 2018-07-17 12:00:03.202-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines