83d676bd15
A downstream bug ocurred because of a lack of symmetry when adding and removing a remote sender in Plan B that specifies SSRCs, but doesn't specify stream IDs. The issue when the first remote description is applied "default" for the stream ID on the remote sender, but the second time it's applied the current remote sender's "default" stream ID does not match the new remote description's empty stream ID. This was incorrectly interpreted as a new remote sender (which removed/added the sender). Bug: webrtc:7933 Change-Id: I87191b9e887b3450ef15111b5e867023c723a86e Reviewed-on: https://webrtc-review.googlesource.com/67191 Reviewed-by: Steve Anton <steveanton@webrtc.org> Reviewed-by: Noah Richards <noahric@chromium.org> Commit-Queue: Seth Hampson <shampson@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22760}
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.
Authoritative list of directories that contain the native API header files.
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