Summary:	ASTERISK-29510: New pattern matcher matches invalid patterns
Reporter:	N A (InterLinked)	Labels:
Date Opened:	2021-07-06 08:20:16	Date Closed:	2021-07-06 08:26:38
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Core/PBX
Versions:	18.5.0	Frequency of Occurrence
Related Issues:	duplicates ASTERISK-19371 Incorrect matching with new pattern match engine enabled
Environment:		Attachments:
Description:	Thought I would give the new extenpatternmatcher a try, but it seems to be completely missing some pattern matches. As soon as I disable the new pattern matcher, everything works again. I don't know what the status of this new pattern matcher is today, and whether or not it is supposed to be ready for primetime, but this does seem like a pretty major bug with the PBX core. Here is debug 10: [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx_variables.c:377 ast_str_retrieve_variable: Result of 'EXTEN' is 'PJSIPATAxLB1' [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:2938 pbx_extension_helper: Launching 'Goto' [2021-07-06 13:06:30]     -- Executing [PJSIPATAxLB1@outgoing:1] Goto("Local/PJSIPATAxLB1@outgoing-0000058e;2", "PJSIP/ATAxLB1,1") in new stack [2021-07-06 13:06:30]     -- Goto (outgoing,PJSIP/ATAxLB1,1) [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1364 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1374 new_find_extension: return at end of func [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1369 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1370 new_find_extension: returning an exact match-- first found-- e [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1369 new_find_extension: Nothing strange about this match [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:1370 new_find_extension: returning an exact match-- first found-- e [2021-07-06 13:06:30] DEBUG[11600][C-00000283]: pbx.c:2938 pbx_extension_helper: Launching 'Goto' [2021-07-06 13:06:30]     -- Executing [e@outgoing:1] Goto("Local/PJSIPATAxLB1@outgoing-0000058e;2", "done,1") in new stack exten => _DAHDI[A-Za-z0-9].,1,Goto(DAHDI/${EXTEN:5},1) exten => _SIP[A-Za-z0-9].,1,Goto(SIP/${EXTEN:3},1) exten => _PJSIP[A-Za-z0-9].,1,Goto(PJSIP/${EXTEN:5},1) exten => _MGCP[A-Za-z0-9].,1,Goto(MGCP/${EXTEN:4},1) exten => _[A-Z].,1,Set(CDR_PROP(disable)=1) same => n,Answer() exten => e,1,Goto(done,1) It *should* be going to _[A-Z]. but is instead matching on e, which isn't even a valid match for the extension in the first place.
Comments:	By: Asterisk Team (asteriskteam) 2021-07-06 08:20:19.587-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].