Closed stazio closed 4 years ago
OK, I'm pushing a fix.
There is still something wrong here. libdatachannel now throws a "Incompatible roles with remote description" exception. I have attached a gist here of both the offer and the answer from the perspective of the browser.
Commenting out the offending exception produces no issues as far as I can tell.
This indicates a deeper problem as it means the local setup and the remote setup are the same. How do you end up in this situation?
How do you end up in this situation?
So I went to sleep, and woke up this morning and I can no longer reproduce the issue. This certainly has to do with the fact that both the browser and libdatachannel can produce an offer, though the signaling guarantees that only one offer is ever in progress at any time.
OK, I see. The API should behave a bit like the browser one so you have to either offer always from the same side or handle conflicts yourself using the signaling state. Please re-open if you encounter such an issue again.
It seems this bug is still present. The browser is failing to accept the remote answer with the warning
Failed to apply the description for m= section with mid='1': Failed to set SSL role for the transport.
wheremid:1
is the first mline in the description. Here is how to reproduce the issue: