897d08ef1b
There's some code that resets the ICE role on an ICE restart (behavior that's specified in ICE, but removed from ICEbis). And it wasn't taking into account that the remote endpoint may be an ICE lite endpoint, in which case the WebRTC endpoint's role should always be "controlling". BUG=chromium:710760 Review-Url: https://codereview.webrtc.org/2812173003 Cr-Commit-Position: refs/heads/master@{#17779}
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://chromium.googlesource.com/external/webrtc
- 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