[asterisk-bugs] [JIRA] Issue Comment Edited: (ASTERISK-20442) dtmf callerid regression

Alec Davis (JIRA) noreply at issues.asterisk.org
Thu Sep 20 03:04:27 CDT 2012


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

Alec Davis edited comment on ASTERISK-20442 at 9/20/12 3:04 AM:
----------------------------------------------------------------

This was most likely caused by ASTERISK-17493, and fixed in ASTERISK-19610.  You can try the patch 'review2085.diff3.txt' on that issue - the fix should be available in 1.8.17.0.

      was (Author: mjordan):
    This was most likely caused by ASTERISK-17493, and fixed in ASTERISK-19610.  You can try the patch on that issue - the fix should be available in 1.8.17.0.
  
> 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



More information about the asterisk-bugs mailing list