[asterisk-bugs] [JIRA] (ASTERISK-19371) Incorrect matching with new pattern match engine enabled
Walter Doekes (JIRA)
noreply at issues.asterisk.org
Mon Sep 12 07:36:01 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-19371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Walter Doekes updated ASTERISK-19371:
-------------------------------------
Affects Version/s: 11.23.1
13.11.2
14.0.0-beta2
> 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)
More information about the asterisk-bugs
mailing list