[asterisk-bugs] [JIRA] (ASTERISK-17329) [branch] DTMF on outbound call leg does not match inbound DTMF duration

[Olle Johansson (JIRA)]

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

Olle Johansson commented on ASTERISK-17329:
-------------------------------------------

The branch for 1.6 and 1.8 has been running in production for a long time and fixes a lot of issues with DTMF duration.

> [branch] DTMF on outbound call leg does not match inbound DTMF duration
> -----------------------------------------------------------------------
>
>                 Key: ASTERISK-17329
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17329
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Core/RTP
>            Reporter: Olle Johansson
>            Assignee: Olle Johansson
>            Severity: Minor
>         Attachments: dtmf-capture-1.pcap, dtmf.patch
>
>
> If two SIP phones is bridged over Asterisk, Asterisk will always have the wrong length to the DTMF audio. The primary causes are:
>  - DTMF duration is added with 160 ms for each BEGIN packet. The DTMF Begin is transmitted three times and should have the same duration
>  - One extra DTMF continue packet is generated directly after the BEGIN packets and adds another 160 ms
>  - The END packet shows the actual inbound duration + 160 since the CONT code adds 160 after sending
>  - For longer DTMF, we actually cut DTMF short since we cut DTMF off as soon as we received the DTMF END on the inbound channel.
> The attached patch solves these issues. 
> This seems to affect all released versions of Asterisk
> Branch: http://svn.digium.com/svn/asterisk/team/oej/rana-dtmf-rtp-duration-1.6.0



--
This message was sent by Atlassian JIRA
(v6.2#6252)