[asterisk-bugs] [Asterisk 0011994]: Introducing en extension pattern matching variables similar to X or Z, but also recognizes the * and/or #
noreply at bugs.digium.com
noreply at bugs.digium.com
Fri Feb 15 17:21:06 CST 2008
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=11994
======================================================================
Reported By: buckersher
Assigned To: russell
======================================================================
Project: Asterisk
Issue ID: 11994
Category: Addons/General
Reproducibility: always
Severity: trivial
Priority: normal
Status: resolved
Asterisk Version: 1.4.14
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
Resolution: no change required
Fixed in Version:
======================================================================
Date Submitted: 02-14-2008 08:30 CST
Last Modified: 02-15-2008 17:21 CST
======================================================================
Summary: Introducing en extension pattern matching variables
similar to X or Z, but also recognizes the * and/or #
Description:
Asterisk has pattern matching mainly only for numerical digits, such as the
X or Z patterns. It would be useful if a pattern character can be
introduced that will also recognize the * or #, such as when a context
needs to redirect all the calls to another context. Although the wildcard
period pattern can be used in that case, it is not advisable to start a
pattern matching sequence with a period. Likewise, there are other useful
implementations for having this kind of pattern matching as well.
======================================================================
----------------------------------------------------------------------
russell - 02-15-08 17:21
----------------------------------------------------------------------
I'm closing this out since there is no patch and we don't accept feature
requests without patches on the bug tracker. However, like jsmith said,
you can already handle a pattern like this ...
Issue History
Date Modified Username Field Change
======================================================================
02-15-08 17:21 russell Status new => resolved
02-15-08 17:21 russell Resolution open => no change
required
02-15-08 17:21 russell Assigned To => russell
02-15-08 17:21 russell Note Added: 0082345
======================================================================
More information about the asterisk-bugs
mailing list