[Bug 785733] rtpbin: ntp-sync does no sanity checking for clock sync

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=785733

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #15 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
commit 3de02445320fcf880bc57f93e2abc34e4b28ea58 (HEAD -> master)
Author: Patrick Radizi <patrickr at axis.com>
Date:   Thu Sep 14 13:00:56 2017 +0200

    rtpbin: add option for sanity checking timestamp offset

    Timestamp offsets needs to be checked to detect unrealistic values
    caused for example by NTP clocks not in sync. The new parameter
    max-ts-offset lets the user decide an upper offset limit. There
    are two different cases for checking the offset based on if
    ntp-sync is used or not:
    1) ntp-sync enabled
       Only negative offsest are allowed since a positive offset would
       mean that the sender and receiver clocks are not in sync.
       Default vaule of max-ts-offset = 0 (disabled)
    2) ntp-sync disabled
       Both positive and negative offsets are allowed.
       Default vaule of max-ts-offset = 3000000000
    The reason for different default values is to be backwards
    compatible.

    https://bugzilla.gnome.org/show_bug.cgi?id=785733

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.