Add offer_extmap_allow_mixed to RTCConfiguration

Bug: webrtc:9986
Change-Id: I346e03a46f35c7d59d3ae769842e3aeec9d2d50d
Reviewed-on: https://webrtc-review.googlesource.com/c/110501
Commit-Queue: Johannes Kron <kron@webrtc.org>
Reviewed-by: Steve Anton <steveanton@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#25596}
This commit is contained in:
Johannes Kron
2018-11-12 10:25:48 +01:00
committed by Commit Bot
parent 5ae3a028c8
commit 89f874eb39
6 changed files with 36 additions and 5 deletions

View File

@ -597,6 +597,14 @@ class PeerConnectionInterface : public rtc::RefCountInterface {
// settings set in PeerConnectionFactory (which is deprecated).
absl::optional<CryptoOptions> crypto_options;
// Configure if we should include the SDP attribute extmap-allow-mixed in
// our offer. Although we currently do support this, it's not included in
// our offer by default due to a previous bug that caused the SDP parser to
// abort parsing if this attribute was present. This is fixed in Chrome 71.
// TODO(webrtc:9985): Change default to true once sufficient time has
// passed.
bool offer_extmap_allow_mixed = false;
//
// Don't forget to update operator== if adding something.
//