Always send RED headers if configured.

This shouldn't be needed, but because the receiver assumes RTX packets
contain RED if configured to receive them (due to an incompatibility
issue), we also have to make sure we send them for now.

BUG=webrtc:5675

Review-Url: https://codereview.webrtc.org/2033763002
Cr-Commit-Position: refs/heads/master@{#13024}
(cherry picked from commit 8f4c77fea10010b5879a01bf6fcd485318594a85)
TBR=stefan@webrtc.org

Review URL: https://codereview.webrtc.org/2061943003 .

Cr-Commit-Position: refs/branch-heads/52@{#5}
Cr-Branched-From: a376e70cf9d0df3c35d53533b454da542661775b-refs/heads/master@{#12798}
3 files changed
tree: e73cebb26d71f75e286a4361c2018c3127c9ffc3
  1. .clang-format
  2. .gitignore
  3. .gn
  4. AUTHORS
  5. BUILD.gn
  6. COPYING
  7. DEPS
  8. LICENSE
  9. LICENSE_THIRD_PARTY
  10. OWNERS
  11. PATENTS
  12. PRESUBMIT.py
  13. README.md
  14. WATCHLISTS
  15. all.gyp
  16. build_overrides/
  17. check_root_dir.py
  18. chromium/
  19. codereview.settings
  20. data/
  21. infra/
  22. license_template.txt
  23. pylintrc
  24. resources/
  25. setup_links.py
  26. sync_chromium.py
  27. talk/
  28. third_party/
  29. tools/
  30. webrtc/
README.md

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. This page is maintained by the Google Chrome team.

Development

See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.

More info