[asterisk-bugs] [JIRA] (ASTERISK-22066) Analog phone digit delay when using cannot-complete-as-dialed catch-all in dialplan

[Justin Killen (JIRA)]

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

Justin Killen commented on ASTERISK-22066:
------------------------------------------

I agree that a custom extension seems overkill, but I thought it would be the simplest and least intrusive.

I don't think making them configurable solves the core problem.  The core problem here is that the catch-all is used for custom error reporting, not for 'valid' extension handling.  The only other way I could think of besides having a custom extension would be to somehow flag the catch-all pattern so that it uses the longer timeout (perhaps a custom timeout option on the pattern, like:  _X:notimeout or _X:nomatchtimeout or _X:senddigittimeout=matchdigittimeout ), which could be a hint as to what timeout to use for that specific match.
                
> Analog phone digit delay when using cannot-complete-as-dialed catch-all in dialplan
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22066
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22066
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 11.4.0
>         Environment: analog phones
>            Reporter: Justin Killen
>            Severity: Minor
>
> When an analog phone is picked up and a number is dialed, there are three associated timeouts (from chan_dahdi.c):
> firstdigittimeout = 1600
> gendigittimeout = 8000
> matchdigittimeout = 3000
> This creates reasonable timeouts.  However, it is a common occurrence to add a catch-all entry in the dialplan to provide a nice message when an invalid number is entered.  Because of this catch-all, all dahdi calls have a match, and the 3 second timeout is used instead of the intended 8 second timeout.
> It would be nice to have reasonable timeouts and nice messages not be mutually exclusive.  Perhaps a special extension target (like i and t) that gets used when there's no match?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira