[asterisk-bugs] [Asterisk 0015910]: new exten pattern matching not correctly prioritizing extensions by CID

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Aug 31 14:58:53 CDT 2010


The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=15910 
====================================================================== 
Reported By:                dbrooks
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15910
Category:                   Core/PBX
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Target Version:             1.6.2.13
Asterisk Version:           SVN 
JIRA:                       SWP-1763 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
Resolution:                 unable to reproduce
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-09-17 11:45 CDT
Last Modified:              2010-08-31 14:58 CDT
====================================================================== 
Summary:                    new exten pattern matching not correctly
prioritizing extensions by CID
Description: 
If extenpatternmatchnew == true, the pattern-matching trie is utilized, but
CID matching does not work. It seems that any extension with a CID pattern
is considered an invalid extension.
====================================================================== 

---------------------------------------------------------------------- 
 (0126502) tilghman (administrator) - 2010-08-31 14:58
 https://issues.asterisk.org/view.php?id=15910#c126502 
---------------------------------------------------------------------- 
This would appear to be already fixed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-31 14:58 tilghman       Note Added: 0126502                          
2010-08-31 14:58 tilghman       Status                   acknowledged => closed
2010-08-31 14:58 tilghman       Resolution               open => unable to
reproduce
======================================================================




More information about the asterisk-bugs mailing list