Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[Edge] ICE error: Wrong MESSAGE-INTEGRITY #498
In some cases, Edge cannot establish the ICE connection with JVB. The next screenshot shows:
The following screenshot shows the error response sent by JVB (Wrong MESSAGE-INTEGRITY):
So, it may happen that:
How to reproduce it
I cannot yet confirm that the issue just happens in the following scenario. However it may be related:
This scenario means that, at the beginning, Chrome and Firefox try a P2P connection and then they move to the SFU once Edge joins. From my point of view this should have zero impact in how Edge (or any other browser) performs the ICE procedures with JVB.
Said that, I've not seen any kind of ICE role conflict. The JVB sends the SDP offer so it becomes ICE controlling (as per RFC) and Edge receives the SDP offer so becomes ICE controlled. This is ok in the traces above.
I've ported copy&pasted the jitsi Edge
I've also seen a STUN 401 from mediasoup (wrong credentials) but just once and after doing many "page reloads" in the Edge tab. I will try to confirm this tomorrow so we can figure out whether this is a bug in Edge or in ice4j.
Amazing catch, @bgrozev !
However, I've never got this issue when connecting EDGE to mediasoup (with the very same
Anyhow, I cannot guarantee that this error does never happen with mediasoup because I've not done so many tests as with JVB.
I can directly report this error to people in Microsoft involved in Edge's ORTC. I will report it, ok?
Thanks a lot.
Oh no, I'm the author, and ICE parsing is strict and, in case of error, I log it:
Anyhow, the screenshots you have placed above clearly show a padding error in the USERNAME field, probably due to a wrong length value.
I'll report the issue and let you know.
Ah, alright, I didn't know that. Then there must be something in our code which triggers it.
Another thing: in your dump there are pairs of BRs with the same transaction ID, sent one after the other (without a timeout). This doesn't seem right either.
Reported in Edge Issue Tracker: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12332457/