586b19bdb6
To make this possible padding only packets will have the same timestamp as the previously sent media packet, as long as RTX is not enabled. This has the side effect that if we send only padding for a long time without sending media, a receive-side jitter buffer could potentially overflow. In practice this shouldn't be an issue, partly because RTX is recommended and used by default, but also because padding typically is terminated before being received by a client. It is also not an issue for bandwidth estimation as long as abs-send-time is used instead of toffset. BUG=chromium:425925 R=mflodman@webrtc.org, sprang@webrtc.org, tommi@webrtc.org Review URL: https://codereview.webrtc.org/1327933003 . Cr-Commit-Position: refs/heads/master@{#9984}
Name: WebRTC URL: http://www.webrtc.org Version: 90 License: BSD License File: LICENSE Description: WebRTC provides real time voice and video processing functionality to enable the implementation of PeerConnection/MediaStream. Third party code used in this project is described in the file LICENSE_THIRD_PARTY.