[asterisk-bugs] [JIRA] (ASTERISK-26500) res_rtp_asterisk: DTMF RFC2833 with timestamp 0 are ignored

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26500:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> res_rtp_asterisk: DTMF RFC2833 with timestamp 0 are ignored
> -----------------------------------------------------------
>
>                 Key: ASTERISK-26500
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26500
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 1.8.32.3, 14.0.2
>            Reporter: Thomas Sevestre
>            Assignee: Thomas Sevestre
>
> In function process_dtmf_rfc2833, the "Dropping out of order DTMF frame" test drops all DTMF with timestamp 0. Some equipments always send the first DTMF with timestamp 0. This leads to drop the first DTMF of each call.
> I've fixed the problem by changing this :
> {code:title=From res_rtp_asterisk.c}
> if ((rtp->last_seqno > seqno && rtp->last_seqno - seqno < 50)
> 	|| timestamp <= rtp->last_end_timestamp) {
> {code}
> into this:
> {code}
> if ((rtp->last_seqno > seqno && rtp->last_seqno - seqno < 50)
> 	|| (timestamp != 0 && timestamp <= rtp->last_end_timestamp)) {
> {code}



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