[asterisk-bugs] [JIRA] (ASTERISK-28303) res_rtp_asterisk: Interaction between smoother and DTMF can cause out of order timestamps

[Kevin Harwell (JIRA)]

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

Kevin Harwell updated ASTERISK-28303:
-------------------------------------

    Target Release Version/s: 16.3.0

> res_rtp_asterisk: Interaction between smoother and DTMF can cause out of order timestamps
> -----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28303
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28303
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 13.20.0
>            Reporter: Torrey Searle
>            Assignee: Torrey Searle
>      Target Release: 13.26.0, 16.3.0
>
>         Attachments: full.txt, timestamp_issue.tgz, wrong_timestamp.pcap.pcapng
>
>
> When the smoother is non-empty, it infers the delivery time based on the number of samples removed from it.
> However while a dtmf (RFC4744) is being generated, no samples are being removed from the smoother, so it's delivery timestamp falls behind current time.
> When the next dtmf is being generated, this triggers a large jump forward in time in calc_txstamp as the dtmf functions use now() instead of delivery time.  This causes a jump forward in rtp timestamps of audio packets w/o timing info (the ones generated by the smoother).
> However once the smoother becomes empty again, then timing will get passed once more from the calling leg to the called leg, and the above issue will manifest itself as a jump backwards in rtp timestamps



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