[asterisk-bugs] [Asterisk 0012082]: Dial plan pattern matching not working from odbc tables

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12082 
====================================================================== 
Reported By:                kactus
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12082
Category:                   Channels/chan_sip/DatabaseSupport
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0-beta4 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-26-2008 22:44 CST
Last Modified:              02-26-2008 23:40 CST
====================================================================== 
Summary:                    Dial plan pattern matching not working from odbc
tables
Description: 
It appears that pattern matching has either changed or is broken from 1.4
when reading dial information out of the database.

when using the flat files, ie extensions.conf, 

[from-sip3]
;switch => Realtime/from-sip3 at extensions
exten => _XXX,1,Dial(SIP/DestinationAccount)

this matches all 3 digit numbers such as 141 etc correctly. 

when using 

[from-sip3]
switch => Realtime/from-sip3 at extensions
;exten => _XXX,1,Dial(SIP/DestinationAccount)

with the database looking like:
context     exten         priority        app         appdata
from-sip3   _XXX          1               Dial       
SIP/DestinationAccount

the system throws a notice of:

[Feb 27 22:31:31] NOTICE[25133]: chan_sip.c:16314 handle_request_invite:
Call from 'OriginalDialingAccount' to extension '141' rejected because
extension not found.

and is unable to continue. Changing exten to 141 in the extensions
database table allows the call to proceed normally.

Please investigate
====================================================================== 

---------------------------------------------------------------------- 
 kactus - 02-26-08 23:40  
---------------------------------------------------------------------- 
Just some additional information from testing, it also does not match the
period wildcard '.'

ie _. or _X. do not get matched 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-26-08 23:40  kactus         Note Added: 0083005                          
======================================================================