[asterisk-bugs] [Asterisk 0019111]: When using extenpatternmatchnew=yes, dialplan-based callerid fails using forward slash

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19111 
====================================================================== 
Reported By:                amessina
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19111
Category:                   PBX/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.8.3.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-04-13 01:48 CDT
Last Modified:              2011-04-13 11:03 CDT
====================================================================== 
Summary:                    When using extenpatternmatchnew=yes, dialplan-based
callerid fails using forward slash
Description: 
[mss]
exten => 333/2201,1,SayDigits(${CALLERID(num)})

Phone dials 333...

NOTICE[23160]: chan_sip.c:21358 handle_request_invite: Call from 'sip1' to
extension '*333' rejected because extension not found in context 'mss'.

This 'feature' worked previously in 1.6.2.17
====================================================================== 

---------------------------------------------------------------------- 
 (0133718) amessina (reporter) - 2011-04-13 11:03
 https://issues.asterisk.org/view.php?id=19111#c133718 
---------------------------------------------------------------------- 
Sorry.  Yes, in 1.6.2.17, with extenpatternmatchnew=yes, the forward slash
callerid matching worked properly.

In addition, subscriptions to dynamic hints are affected as well.  With
the following:

; Toggle per-extension call recording
exten => *72,1,Goto(${EXTEN}${CALLERID(num)},1)
exten => _*7222XX,1,NoCDR()
same => n,Set(RECORD=${DB(RECORD/${CALLERID(num)})})
same => n,ExecIf($["${RECORD}" =
"0"]?Set(DB(RECORD/${CALLERID(num)})=1):Set(DB(RECORD/${CALLERID(num)})=0))
same => n,ExecIf($["${RECORD}" =
"0"]?Set(DEVICE_STATE(Custom:RECORD-${CALLERID(num)})=INUSE):Set(DEVICE_STATE(Custom:RECORD-${CALLERID(num)})=UNAVAILABLE))
same => n,ExecIf($["${RECORD}" =
"0"]?Playback(dictate/record_mode&on&vm-goodbye):Playback(dictate/record_mode&ha/off&vm-goodbye))
same => n,Hangup()

Using extenpatternmatchnew=yes in 1.8.3.2, when a phone attempts to
subscribe to the hint:
WARNING[8640] pbx.c: Unable to register extension '*722201', priority -1
in 'hints', already in use

Using extenpatternmatchnew=no in 1.8.3.2, the phone subscribes properly.

Using extenpatternmatchnew=yes (or no) in 1.6.2.17: the phone subscribes
properly. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-13 11:03 amessina       Note Added: 0133718                          
======================================================================