[asterisk-bugs] [Asterisk 0012298]: The new pattern matching does not work

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12298 
====================================================================== 
Reported By:                falves11
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   12298
Category:                   PBX/pbx_config
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 110615 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-26-2008 00:48 CDT
Last Modified:              04-15-2008 09:33 CDT
====================================================================== 
Summary:                    The new pattern matching does not work
Description: 
I have a lot of extensions, several thousands, and therefore I decided to
use the new patter-matching. It does not work at all. I send a call to my
cell at 19544447408, and it gets rejected with "not found". Please see the
dialplan and the SIP trace.
====================================================================== 

---------------------------------------------------------------------- 
 murf - 04-15-08 09:33  
---------------------------------------------------------------------- 
My apologies-- You are right-- I misinterpreted my notes here. 

I agree that the behavior of the new matching code should match the
behavior of the 'old'. That is my goal. I first have to understand why we
are not getting the same results. I thought I had the same stuff as you,
found the problem, and fixed it, but it looks like I don't have a grip on
reality.

In the meantime, I've found another bug in the pattern matcher, and in the
late hours last night, and in the early hours this morning, I managed to
track it down and make a fix. It has to do with a gap in the logic between
MATCH and SPAWN, and could easily be what's biting you. I will (in a few
hours) commit it to trunk and update this bug. So hang on-- and thanks for
taking the time to help perfect this code! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-15-08 09:33  murf           Note Added: 0085494                          
======================================================================