commit | e98954c35e97dfe4d50fe6bd75587b14ffb6568e | [log] [tgz] |
---|---|---|
author | Jakob Ivarsson <jakobi@webrtc.org> | Wed Feb 06 14:37:50 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Feb 06 15:30:54 2019 |
tree | 6049eca40a6c83d31f6afb3bee2cafb7eb2b42b2 | |
parent | 9025bd5142b0d356049bd23cbf1562ca8709d23b [diff] |
Prevent updating state in the delay manager if the packet was reordered. Currently, if the last packet was reordered (e.g. due to retransmission) then the next packet's inter-arrival time will be estimated incorrectly due to the jump in sequence numbers. This change prevents that by not resetting the stopwatch on reordered packets. This will also better estimate inter-arrival times when we have multiple reordered packets in a burst. Currently we would only measure the iat of the first reordered packet correctly and not the ones coming after it. There is a slight risk introducing this: If we would receive an out of order packet far into the future (in sequence numbers) and then continue getting packets in the normal order, then we would not update the current sequence number for these and incorrectly estimate their inter-arrival times since they would all be considered reordered. Change-Id: Ic938a37cbddf1cb9c30b610218f56794568d3d01 Bug: webrtc:10178 Reviewed-on: https://webrtc-review.googlesource.com/c/119949 Reviewed-by: Minyue Li <minyue@webrtc.org> Reviewed-by: Henrik Lundin <henrik.lundin@webrtc.org> Commit-Queue: Jakob Ivarsson‎ <jakobi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26572}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.