| commit | 3ae59d33a310280e2f21ed4c53849950171e48e8 | [log] [tgz] |
|---|---|---|
| author | Qingsi Wang <qingsi@webrtc.org> | Fri Jul 12 04:53:45 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Jul 12 05:38:20 2019 |
| tree | 58c2615bd568c6afe51d5a1029a025d02c90912c | |
| parent | 58388aa07c17bb0d3ea2aa284651934c147de3e6 [diff] |
Use the dummy address 0.0.0.0:9 in the c= and the m= lines if the default connection address is a hostname candidate. Using a FQDN in the c= line has caused an inter-op issue with Firefox when hostname candidates are the only candidates gathered when forming the media sections. To address this issue, we use 0.0.0.0:9 when a hostname candidate would be used to populate the c= and the m= lines. The SDP grammar related to ICE candidates has been moved out of RFC8445, and is currently defined in draft-ietf-mmusic-ice-sip-sdp. A FQDN address must not be used in the connection address attribute per the latest draft, if the ICE agent generates local candidates. Also, the wildcard addresses (0.0.0.0 or ::) with port 9 are given the exception as the connection address that will not result in an ICE mismatch. We thus adopt the aforementioned solution after combining these considerations. Bug: chromium:927309, chromium:982108 Change-Id: I3df2db0f154276da39f99650289cf81baa677e74 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/145280 Commit-Queue: Qingsi Wang <qingsi@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28547}
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.
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.