1c34974d6f
The first argument of FindMatchingCodec is supposed to be the list that contains the codec to be found, specifically to handle RTX codecs that point to other codecs. But this wasn't being done everywhere, and wasn't noticed because *most of the time* it just results in adding the RTX codec in a different location, which isn't an issue. But, it's still not standards-compliant. And it sometimes is an issue when talking to older endpoints. Adding a regression test, and DCHECK in FindMatchingCodec to ensure this doesn't happen by accident again. Bug: webrtc:8332 Change-Id: I5def056b245c6d00a49a59d429f1dee303fb7cef Reviewed-on: https://webrtc-review.googlesource.com/6240 Reviewed-by: Justin Uberti <juberti@webrtc.org> Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20130}
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.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct