[asterisk-bugs] [Asterisk 0016903]: [patch] Incorrect pattern specificity in new dial pattern functions

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16903 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                bbryant
====================================================================== 
Project:                    Asterisk
Issue ID:                   16903
Category:                   PBX/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
JIRA:                       SWP-969 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-02-25 09:40 CST
Last Modified:              2010-09-09 20:49 CDT
====================================================================== 
Summary:                    [patch] Incorrect pattern specificity in new dial
pattern functions
Description: 
An error appears to have crept in when copying the specificity of X, Z and
N wildcards from the old dial pattern matching functions to the new ones.

In the old functions the specificity is:
X : 0x0A30
Z : 0x0931
N : 0x0832

which is the same as
[0-9] : 0x0A30
[1-9] : 0x0931
[2-9] : 0x0832

but in the new functions the specificity is:
X : 0x0A00
Z : 0x0901
N : 0x0802
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-09 20:49 svnbot         Status                   assigned => resolved
2010-09-09 20:49 svnbot         Resolution               open => fixed       
======================================================================