| commit | 925324030525f9174b50a321a78da00cad163087 | [log] [tgz] |
|---|---|---|
| author | Per K <perkj@webrtc.org> | Mon Jan 02 15:57:18 2023 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 04 11:35:19 2023 |
| tree | 0b241f8a4e54b787a5be7b11b012892924d043e8 | |
| parent | 7a5de444553b98715873b93390b2daf8c68a08e2 [diff] |
Reland "Remove use of ReceiveStreamRtpConfig:transport_cc" This is a reland of commit 97ba853295578975a04fc504315cccd465f9f0bd This cl did not cause the regression in Chrome rolls https://chromium-review.googlesource.com/c/chromium/src/+/4132644?tab=checks. Real culprit reverted in https://webrtc-review.googlesource.com/c/src/+/290502. Original change's description: > Remove use of ReceiveStreamRtpConfig:transport_cc > > With this change, webrtc will send RTCP transport feedback for all received packets that have a transport sequence number, if the header extension > http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions is negotiated. > I.e the SDP attribute a=rtcp-fb:96 transport-cc is ignored. > > > Change-Id: I95d8d4405dc86a2f872f7883b7bafd623d5f7841 > > Bug: webrtc:14802 > Change-Id: I95d8d4405dc86a2f872f7883b7bafd623d5f7841 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/290403 > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> > Commit-Queue: Per Kjellander <perkj@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#38980} Bug: webrtc:14802 Change-Id: Ib98e61413161d462da60144942cdb0140e12bc42 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/290503 Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Commit-Queue: Per Kjellander <perkj@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#38997}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.