[asterisk-bugs] [Asterisk 0016903]: Incorrect pattern specificity in new dial pattern functions
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Feb 25 10:01:02 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16903
======================================================================
Reported By: Nick_Lewis
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16903
Category: PBX/General
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-02-25 09:40 CST
Last Modified: 2010-02-25 10:01 CST
======================================================================
Summary: 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
======================================================================
----------------------------------------------------------------------
(0118546) Nick_Lewis (reporter) - 2010-02-25 10:01
https://issues.asterisk.org/view.php?id=16903#c118546
----------------------------------------------------------------------
In both the new and old functions the char set cardinality is set
incorrectly to 0x00 for . and ! wildcards. These wildcards permit all ascii
values from 0x00 to 0x7F so the cardinality should therefore be set to
0x80. This problem with . and ! does not cause symptoms at the moment but
will prevent correct pattern ordering with the introduction of some
proposed future wildcards
Issue History
Date Modified Username Field Change
======================================================================
2010-02-25 10:01 Nick_Lewis Note Added: 0118546
======================================================================
More information about the asterisk-bugs
mailing list