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

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-22066:
----------------------------------------

Fair enough on the use of the {{i}} extension. I'm going to go ahead and ack this issue.

Since this is a minor bug/improvement (I'd classify at as a bug, as having to recompile or otherwise modify the source to get this to work in an environment is really a bug), a patch that sends the call to the {{i}} extension would help get the issue resolved faster.
                
> 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