[asterisk-bugs] [Asterisk 0015421]: [patch] Serious problem in pattern matching

[Asterisk Bug Tracker]

The following issue is now READY FOR TESTING. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15421 
====================================================================== 
Reported By:                jsmith
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15421
Category:                   PBX/pbx_config
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Target Version:             1.6.0.19
Asterisk Version:           SVN 
JIRA:                       SWP-333 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-06-29 14:45 CDT
Last Modified:              2009-11-09 18:49 CST
====================================================================== 
Summary:                    [patch] Serious problem in pattern matching
Description: 
There appears to be a serious problem in the pattern matching in
Asterisk... for some reason, it thinks the following two extensions are
equivalent, when they're not.

exten => _N[2-4]X,1,NoOp(foo)
exten => _N[246]X,1,NoOp(bar)
====================================================================== 

---------------------------------------------------------------------- 
 (0113481) tilghman (administrator) - 2009-11-09 18:49
 https://issues.asterisk.org/view.php?id=15421#c113481 
---------------------------------------------------------------------- 
Back to testing.  David Brooks and I spent some time analyzing the problem,
and I came up with this patch which verifies differences in each character
class before continuing through the pattern.  This should also sort
correctly, with lower characters in the class (according to ASCII) sorting
before higher characters. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-09 18:49 tilghman       Note Added: 0113481                          
2009-11-09 18:49 tilghman       Status                   confirmed => ready for
testing
======================================================================