9b2d4f5caa
This reverts commit 625efe6dfe5b5681a2d8d3d5ecaa0c5ac9edd6ee. Reason for revert: Speculative revert, possibly breaking downstream projects Original change's description: > Use also the related address in redundancy detection for candidates from > the any-address/wildcard ports. > > A TURN server can allocate different IPs for different allocation > requests from the same network interface, and a relayed candidate from a > wildcard port is not considered duplicate with another relayed candidate > using the same network interface in the current redundancy detection, if > their mapped addresses (as the "related address" for relayed candidates) > are different. Extra candidates would then be surfaced to the > application unnecessarily. > > Bug: webrtc:9469 > Change-Id: I504fde3b70cd727ef6ad4517072dcf37328a8380 > Reviewed-on: https://webrtc-review.googlesource.com/86181 > Commit-Queue: Qingsi Wang <qingsi@webrtc.org> > Reviewed-by: Steve Anton <steveanton@webrtc.org> > Reviewed-by: Qingsi Wang <qingsi@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#24108} TBR=steveanton@webrtc.org,tommi@webrtc.org,qingsi@google.com,qingsi@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Landing with NOTRY because ios64_sim_ios10_dbg bot is broken. Passing all other bots. NOTRY=True Bug: webrtc:9469 Change-Id: Ica382280be5b4470cb99d8cccadcd87d3e7d37bb Reviewed-on: https://webrtc-review.googlesource.com/95300 Commit-Queue: Qingsi Wang <qingsi@google.com> Reviewed-by: Qingsi Wang <qingsi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24371}
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