[asterisk-bugs] [JIRA] (ASTERISK-28421) Wrong type used for timestamp in res_rtp_asterisk

Asterisk Team (JIRA) noreply at issues.asterisk.org
Tue May 21 09:06:47 CDT 2019


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

Asterisk Team commented on ASTERISK-28421:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> Wrong type used for timestamp in res_rtp_asterisk
> -------------------------------------------------
>
>                 Key: ASTERISK-28421
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28421
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 16.3.0
>            Reporter: Morten Tryfoss
>            Severity: Minor
>
> int is used instead of unsigned int in ast_rtp_interpret. Values above max of an int causes (at least) the adaptive jitterbuffer to stop working because of negative timestamp value in the packet.
> Suggested fix:
> --- a/res/res_rtp_asterisk.c
> +++ b/res/res_rtp_asterisk.c
> @@ -6326,7 +6326,8 @@ static struct ast_frame *ast_rtp_interpret(struct ast_rtp_instance *instance, st
>         unsigned int *rtpheader = (unsigned int*)(read_area);
>         struct ast_rtp *rtp = ast_rtp_instance_get_data(instance);
>         struct ast_rtp_instance *instance1;
> -       int res = length, hdrlen = 12, seqno, timestamp, payloadtype, padding, mark, ext, cc;
> +       int res = length, hdrlen = 12, seqno, payloadtype, padding, mark, ext, cc;
> +       unsigned int timestamp;
>         RAII_VAR(struct ast_rtp_payload_type *, payload, NULL, ao2_cleanup);
>         struct frame_list frames;
>  



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



More information about the asterisk-bugs mailing list