[asterisk-bugs] [JIRA] (ASTERISK-18271) Pattern matching with res_config_mysql extensions does not behave as expected
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Tue Sep 22 10:46:33 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-18271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227649#comment-227649 ]
Matt Jordan commented on ASTERISK-18271:
----------------------------------------
Relevant conversation from #asterisk:
{quote}
<catphish> i'm sad this has never been accepted, i have to keep this as a local patch: https://issues.asterisk.org/jira/browse/ASTERISK-18271
* darkbasic (~quassel at niko.linuxsystems.it) has joined #asterisk
* darkbasic_ has quit (Ping timeout: 250 seconds)
<mjordan> catphish: no one put it up for review, or attached it as a valid patch.
<mjordan> The fact that someone did it inline is actually quite bad, as there's no CLA for inline patches. Which means I now have to go remove it.
* cyford (~support at c-73-137-1-6.hsd1.ga.comcast.net) has joined #asterisk
<mjordan> Particularly since res_config_mysql is a community supported module.
<mjordan> So... yeah.
{quote}
I'm going to put the relevant instructions for participating in a peer review on this issue. If someone would like to submit a patch for this issue that fixes it, that'd be greatly appreciated. Thanks!
> Pattern matching with res_config_mysql extensions does not behave as expected
> -----------------------------------------------------------------------------
>
> Key: ASTERISK-18271
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-18271
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Addons/res_config_mysql
> Affects Versions: 1.8.5.0
> Reporter: Charlie Smurthwaite
>
> When using RealTime extensions from MySQL with res_config_mysql and overlapping pattern extensions, selection of an extension does not work as expected. Test case:
> Extensions in mysql with appropriate context:
> _800.
> _80.
> Dialed number: 8001
> Expected behaviour:
> _800. matches number because it is the most explicit match
> Actual behaviour:
> _80. matches number because it is the first matching extension in the mysql resultset (query is ordered by extension)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list