[asterisk-bugs] [Asterisk 0011086]: avoid nonexistent context warnings when loading AEL

noreply at bugs.digium.com noreply at bugs.digium.com
Thu Oct 25 17:32:18 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11086 
====================================================================== 
Reported By:                dimas
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   11086
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-25-2007 11:25 CDT
Last Modified:              10-25-2007 17:32 CDT
====================================================================== 
Summary:                    avoid nonexistent context warnings when loading AEL
Description: 
When AEL loads its configuration, it produces alot of warnings like

[Oct 25 19:59:26] WARNING[2457] pbx.c: Context 'FOO' tries includes
nonexistent context 'BAR'

This happens because BAR context is defined later than FOO context. When
you have really many context, they are most likely spread across multiple
files and it is not always possible to organize files in a way that
included context are always loaded before including ones.
====================================================================== 

---------------------------------------------------------------------- 
 dimas - 10-25-07 17:32  
---------------------------------------------------------------------- 
You are right. AEL perfectly handles contexts in any order they defined.
The problem is caused as you are saying by presence of empty contexts.
Which will probably lead me to filling another issue depending on IRC
conversation :)

Sorry for confusion. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-25-07 17:32  dimas          Note Added: 0072525                          
======================================================================




More information about the asterisk-bugs mailing list