[asterisk-bugs] [JIRA] (ASTERISK-19371) Incorrect matching with new pattern match engine enabled

[Walter Doekes (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232245#comment-232245 ] 

Walter Doekes commented on ASTERISK-19371:
------------------------------------------

Yeap. Ran into this just now.

In my case I had:
{noformat}
exten => +31NUMBER1,1,Goto(specific-action1)
exten => +31NUMBER2,1,Goto(specific-action2)
exten => _+Z,1,Goto(fallback-action)
{noformat}
Here I always get the fallback action, quite useless. (Prepending a {{_}} to the two specific patterns makes it work obviously.)

It appears that the extenpatternmatchnew is not used that much or we'd see this bug being referenced more often.

> Incorrect matching with new pattern match engine enabled
> --------------------------------------------------------
>
>                 Key: ASTERISK-19371
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19371
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/pbx_config
>    Affects Versions: 10.1.2, 11.23.1, 13.11.2, 14.0.0-beta2
>            Reporter: Kinsey Moore
>            Severity: Minor
>
> When executing dialplan with extenpatternmatchnew=yes set, some patterns do not match the same as they did with the old dialplan engine.  The example that I came across:
> exten => 7,1,goto(100,1)
> exten => 100,1,noop(Dialplan chose correctly)
> exten => _1X[0-5],1,noop(Dialplan chose WRONG)
> Under the old dialplan engine, the 100 extension would be chosen (correctly since it is more specific).  Under the new engine, _1X[0-5] is chosen instead.  This is not a major issue since the new engine is disabled by default.



--
This message was sent by Atlassian JIRA
(v6.2#6252)