Summary:	ASTERISK-25491: extenpatternmatchnew=yes breaks with hint and pattern match extension in the same context
Reporter:	Sebastian Denz (denz)	Labels:
Date Opened:	2015-10-23 04:54:50	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	Core/PBX
Versions:	13.1.0	Frequency of Occurrence	Constant
Related Issues:	is related to ASTERISK-29170 Conflict hints with extenpatternmatchnew=true
Environment:	Debian Jessie, certified-asterisk-13.1-cert2	Attachments:
Description:	While testing Asterisk 13 i tried the new pattern matcher. With extenpatternmatchnew=yes i was not able to call the extensions anymore, after creating a hint with the same pattern like the dial-extension (_XXX). {code} [general] static=yes writeprotect=yes autofallthrough=yes extenpatternmatchnew=yes clearglobalvars=yes [from-internal] exten => _XXX,1,NoOp(internal call from ${CALLERID(all)} to ${EXTEN}) same => n,SIPAddHeader(Alert-Info: Auto Answer) same => n,Dial(${PJSIP_DIAL_CONTACTS(${EXTEN})},,tT) exten => _XXX,hint,PJSIP/${EXTEN} {code} As long as the hint is not created (because no subscription was done) everything works fine. But when the hint was created the patternmatcher does not find the extension with priority 1 anymore: {code} asterisk13-test*CLI> dialplan show 401@from-internal [ Context 'from-internal' created by 'pbx_config' ]  '_XXX' =>         hint: PJSIP/${EXTEN}                          [pbx_config]                    1. NoOp(internal call from ${CALLERID(all)} to ${EXTEN}) [pbx_config]                    2. SIPAddHeader(Alert-Info: Auto Answer)      [pbx_config]                    3. Dial(${PJSIP_DIAL_CONTACTS(${EXTEN})},,tT) [pbx_config] -= 2 extensions (5 priorities) in 1 context. =- asterisk13-test*CLI> core show version Asterisk 13.1-cert2 built by root @ asterisk-test on a x86_64 running Linux on 2015-10-20 14:34:57 UTC [Oct 23 11:12:41] NOTICE[1056]: res_pjsip_session.c:1587 new_invite: Call from '401' (UDP:10.3.66.108:5070) to extension '402' rejected because extension not found in context 'from-internal'. asterisk13-test*CLI> {code} After extenpatternmatchnew=no everything works as exepected.
Comments:	By: Asterisk Team (asteriskteam) 2015-10-23 04:54:52.556-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].