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

[Alec Davis (JIRA)]

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

Alec Davis commented on ASTERISK-20442:
---------------------------------------

Twist is caused by a non-uniform power loss across the frequency spectrum.  Normal twist is when low frequency power is greater than high frequency. Reverse twist is obviously the reverse condition.  The detector must be reject 8db and 4db for normal and reverse twist respectively.

Also found this describing a similar issue with REVERSE TWIST.
https://issues.asterisk.org/jira/browse/ZAP-181
ZAP-181 Some DTMF tones not detected at blind-transfer prompt dialtone


> 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: tbsky
>            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