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

[Alec Davis (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alec Davis updated ASTERISK-20442:
----------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

in 'make menuselect' if RADIO_RELAX is enabled and if 'relaxdtmf=yes' in chan_dadhi.conf, then REVERSE_TWIST is made even wider.

This may be enough to get 100% DTMF callerid recognition.

see values below for different settings already available:

DTMF_NORMAL_TWIST is always 6.3

with;
RADIO_RELAX disabled in make menuselect
   relaxdtmf=no in chan_dahdi.conf
     REVERSE_TWIST = 2.5
   relaxdtmf=yes in chan_dahdi.conf
     REVERSE_TWIST = 4.0

RADIO_RELAX enabled in make menuselect
   relaxdtmf=no in chan_dahdi.conf
     REVERSE_TWIST = 2.5
   relaxdtmf=yes in chan_dahdi.conf
     REVERSE_TWIST = 6.5

When disabling the TWIST tests altogether as I suggested as a test to see if it helped, I got false positvies DTMF on the inbound speech, and asterisk sends me a DTMF digit during speech, a bit annoying.

tbsky hasn't reported this yet.

So the TWIST tests need to stay there, but just a wider tolerance.

As to making this a configuration option, would we want a compile option in menuselect, a config option in chan_dahdi.conf, or some other method?

> 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