[asterisk-bugs] [Asterisk 0014141]: Pattern matching for extensions with ranges is broken

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14141 
====================================================================== 
Reported By:                dimas
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   14141
Category:                   PBX/pbx_ael
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 166771 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-12-25 14:56 CST
Last Modified:              2009-01-15 18:19 CST
====================================================================== 
Summary:                    Pattern matching for extensions with ranges is
broken
Description: 
It looks like something has broken in extension pattern matching since
1.4.21.2
My dialplans which used to work there do not work with latest 1.4 branch.
After spending some time I nailed problem down to:

context ctxa {

        _[1-7]XXX => {
                NoOp;
        };
};

context ctxb {

        includes {
                ctxa;
        }

        12 =>   jump 4012 at ctxa;

};

This dialplan does not load producing:

voip1*CLI> ael reload 
...
[Dec 25 23:47:14] ERROR[10868]: pbx_ael.c:1284 check_goto: Error: file
/etc/asterisk/ael/local/test.ael, line 15-15: goto:  no label 4012|1 exists
in the context ctxa or its inclusions!
[Dec 25 23:47:14] ERROR[10868]: pbx_ael.c:4498 pbx_load_module: Sorry, but
0 syntax errors and 1 semantic errors were detected. It doesn't make sense
to compile.
voip1*CLI> 
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-15 18:19 svnbot         Status                   assigned => resolved
2009-01-15 18:19 svnbot         Resolution               open => fixed       
======================================================================