[Home]

Summary:ASTERISK-07819: Fresh install on Debian won't launch - .ael file problems
Reporter:John Todd (jtodd)Labels:
Date Opened:2006-09-26 00:21:30Date Closed:2006-09-26 21:54:56
Priority:MinorRegression?No
Status:Closed/CompleteComponents:PBX/pbx_ael
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have just installed TRUNK on Debian (the OS was updated with a full apt-get update) and while the compile worked, it seems that the extensions.ael file from "make samples" gives some indigestion.  This is all 'right out of the box' so it is behaving in a way that is unexpected.  If this is user error, perhaps some better trapping can be done, but if it's code error I don't know where to start looking for it.

****** ADDITIONAL INFORMATION ******

ms1:/usr/src/asterisk# svn update

Fetching external item into 'menuselect'

Fetching external item into 'menuselect/mxml'
External at revision 3.

At revision 59.
At revision 43649.
ms1:/usr/src/asterisk# asterisk -vvvvgcd
Asterisk SVN-trunk-r43643, Copyright (C) 1999 - 2006 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'show license' for details.
=========================================================================
 == Parsing '/etc/asterisk/asterisk.conf': Parsing /etc/asterisk/asterisk.conf
Found

[blah blah blah]

 == Registered channel type 'Skinny' (Skinny Client Control Protocol (Skinny))
[Sep 26 06:09:08] NOTICE[24301]: pbx_ael.c:3799 pbx_load_module: Starting AEL load process.
[Sep 26 06:09:08] NOTICE[24301]: pbx_ael.c:3806 pbx_load_module: AEL load process: calculated config file name '/etc/asterisk/extensions.ael'.
[Sep 26 06:09:08] NOTICE[24301]: pbx_ael.c:3814 pbx_load_module: AEL load process: parsed config file name '/etc/asterisk/extensions.ael'.
[Sep 26 06:09:08] ERROR[24301]: pbx_ael.c:1236 check_goto: Error: file /etc/asterisk/extensions.ael, line 346-346: goto:  no context default could be found that matches the goto target!
[Sep 26 06:09:08] ERROR[24301]: pbx_ael.c:3827 pbx_load_module: Sorry, but 0 syntax errors and 1 semantic errors were detected. It doesn't make sense to compile.
ms1:/usr/src/asterisk# uname -a
Linux ms1 2.4.27-3-386 #1 Mon May 29 23:50:41 UTC 2006 i686 GNU/Linux
ms1:/usr/src/asterisk#


Comments:By: John Todd (jtodd) 2006-09-26 00:36:20

Moving extensions.ael to a different filename allows Asterisk to launch, but this is clearly not the Right Solution.
By: Steve Murphy (murf) 2006-09-26 09:59:59

I'll handle this one way or the other today. Either we'll not install this
by default, or we'll change the contexts to protect the innocent. But you are
right, if it is installed, it shouldn't create problems.

We will achieve the elusive "Right Solution"!!!


By: John Todd (jtodd) 2006-09-26 11:20:40

I see the SVN number has been changed to null, and this has been ticketd to 1-4-0-beta2.  Is that what I should be doing for SVN-TRUNK at this point?  (this is not specifically 'beta2' - this is just SVN-TRUNK, whatever rev that happens to be.)
By: Serge Vecher (serge-v) 2006-09-26 12:14:55

well, you should be making a determination where a bug needs to be fixed first as per following post by kpfleming http://lists.digium.com/pipermail/asterisk-dev/2006-September/023397.html

In the case of this report, the problem exists in 1.4-beta2, so it needs to be fixed there first, then automerged to trunk.
By: Steve Murphy (murf) 2006-09-26 21:50:10

Yes, this is a problem. Not only would the context & macro names collide with
the extensions.ael, but an edit to the file removed a context that was
referenced by a goto, which caused a fatal syntax error.
By: Steve Murphy (murf) 2006-09-26 21:53:57

I fixed the bugs in the .ael file, by renaming all the macros and contexts with a prefix of "ael-", and I fixed the goto by resurrecting its referenced context.

This would be r. 43739 for the 1.4 branch, and r43740 in the trunk.
By: Steve Murphy (murf) 2006-09-26 21:54:56

With this bug fixed in 1.4 and trunk, it's time to close it. If any further probs creap up, it can be reopened.