New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ICE gathering starts too early #116
Comments
Mh, the gathering process is being started when applying the description, so I can't quite follow you. Can you provide a call graph of relevant RAWRTC functions and event handlers? A |
Here's the backtrace for the
And here's one for the
So, if I'm reading this right |
I see. Yeah, this is a bug and I think we could queue a task to start the gathering process delayed (need to check if we can start the other transports regardless). This is not completely trivial to fix and I'm a little bit busy at the moment. However, for now you should be able to send the offer directly after creating it. Just make sure you call |
According to https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-24#section-4.1.9 the ICE gathering process should only start after the local description has been set. However, in my application after calling
rawrtc_peer_connection_create
, therawrtc_peer_connection_local_candidate_handler
is called before thenegotiation_needed_handler
, which is where I set the local description and send an offer to the remote peer. Since I am using trickle ICE, therawrtc_peer_connection_local_candidate_handler
just sends the ICE candidates to the remote immediately.This is a problem, because the remote needs to receive the offer as well as create and set the answer description locally, before remote ICE candidates can be added. (The remote is Firefox 60.0.1)
The text was updated successfully, but these errors were encountered: