|Summary:||ASTERISK-15446: [patch] overlap dial should terminate when "ast_matchmore_extension" is false|
|Reporter:||Thomas Omerzu (t-o)||Labels:|
|Date Opened:||2010-01-16 15:44:12.000-0600||Date Closed:||2013-01-15 11:48:24.000-0600|
|Environment:||Attachments:||( 0) chan_misdn_overlapdial.patch|
|Description:||Overlap dialling in chan_misdn even waits for an timeout when this does not make any sense because we already have a valid extension and additional digits would only lead to invalid extensions.|
This is because the implementation currently ignores "ast_matchmore_extension" which could indicate this condition.
|Comments:||By: Thomas Omerzu (t-o) 2010-01-16 15:55:04.000-0600|
I would propose to use a patch similar to the one I just attached.
By: Birger "WIMPy" Harzenetter (wimpy) 2011-01-25 15:40:35.000-0600
What Asterisk version is this about?
I guess it's an older one. The patch is off by some thousand lines.
With the current chan_misdn I observe the opposite effect. It terminates on the first match, making overlapping extensions unreachable via overlap dialling, i.e. where chan_dahdi and chan_lcr automatically switch to timeout.
By: Thomas Omerzu (t-o) 2011-01-25 16:12:44.000-0600
You do not have to guess, just look into the issue history; I reported this as bug to 1.4.28.
By: Matt Jordan (mjordan) 2013-01-15 11:48:13.432-0600
So, it sounds like in Asterisk 1.8+ we have a different bug, as opposed to the one this patch was supposed to fix. Since Asterisk 1.4/1.6.2 are no longer supported, I'm going to close this issue out. If this is still a problem (or a bug report needs to be filed for the issue WIMPy described), please contact a bug marshal in #asterisk-bugs and/or open a new issue. Thanks!
By: Matt Jordan (mjordan) 2013-01-15 11:48:20.752-0600
Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions. After testing with Asterisk 1.8, if you find this problem has not been resolved, please open a new issue against Asterisk 1.8.