Calling createOffer twice generates different mids.
Reported by
mmalava...@twilio.com,
Jan 15
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: 1. Run https://jsfiddle.net/rnywtqL9/ in a new tab. 2. Open the browser console What is the expected behavior? mids in the two offers should be the same What went wrong? mids in the two offers are different Did this work before? N/A Does this work in other browsers? N/A Chrome version: 73.0.3671.3 Channel: canary OS Version: OS X 10.13.6 Flash Version: I was able to reproduce this in Firefox 64. Is this spec compliant behavior?
,
Jan 16
(6 days ago)
hbos@: Can you take a look or triage further?
,
Jan 16
(6 days ago)
,
Jan 16
(6 days ago)
Is this even a bug? You need to setLocalDescription() for the mids to be assigned. Is there anything in the spec that says that generating two offers without setting them must produce the same result for mids?
,
Jan 16
(6 days ago)
hbos@: Chrome 72 produces the same mids in multiple calls to createOffer(), but Chrome 73 produces different mids. I was wondering if I could get some insight about whether this change was implemented because it is specified in the spec somewhere?
,
Jan 16
(6 days ago)
Interesting. Steve did an awesome job patching SDP in 72 and 73. Steve, do you know which change caused this and if it’s intended?
,
Jan 16
(6 days ago)
Yes, this behavior was changed by this CL: https://webrtc-review.googlesource.com/c/src/+/116381 As far as I can tell there's no spec that says a=mid have to be stable if setLocalDescription is not called. In fact, this new behavior matches what Firefox has been doing. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Jan 15