21c4b1e9ca
This makes relay candidates identifiable in scenarios where the TURN server is behind another entity and the peer sees a different ip address: client -> turn -> relay address -> third party relay + address -> peer In those cases, the relay candidate will become peer-reflexive since the peer sends the third party relay's address in the xor-mapped address and it is currently not easily possible to determine this is a relay candidate anymore. BUG=webrtc:13392 Change-Id: I6787339d0abdc735f8a43f636a676cccd8cadcda Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/237561 Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com> Cr-Commit-Position: refs/heads/main@{#35346}
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 here 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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation