[asterisk-bugs] [JIRA] Commented: (ASTERISK-20442) dtmf callerid regression

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-20442:
----------------------------------------

My thoughts on this:

It feels like 'relaxdtmf' was the wrong approach.  This doesn't seem to be a 'yes/no' option.  It feels like these values could be tweaked in chan_dahdi - and that while we should sanitize inputs to make sure they don't exceed potential values, we should probably expose that at some level.  (With a caveat in the .conf file that if you don't know what these things are, you shouldn't tweak them)

I'm not normally an advocate for having more config options, but in this case, that feels appropriate.  When you have different devices, different locales, all demanding different things - config options are the way to go.

> dtmf callerid regression 
> -------------------------
>
>                 Key: ASTERISK-20442
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20442
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: 1.8.16.0
>         Environment: with TDM400P FXO card
>            Reporter: tbsky
>            Assignee: Alec Davis
>            Severity: Minor
>
> hi:
>    when I use asterisk 1.8.9. the DTMF CallerID works 90% correct. (sometime it will drop 1 or 2 digits). but when I upgrade to 1.8.10 or 1.8.16, it can only detect 1 or 2 digits for every call (so drop 7 or 8 digits for every call). I think there are something change between 1.8.9 and 1.8.10 but I don't know what.
>    can you tell me what to test or provide what information to fix the bug?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira