Skip to content
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

Racing condition - ICE servers #740

Open
wardhanster opened this issue Aug 6, 2018 · 0 comments
Open

Racing condition - ICE servers #740

wardhanster opened this issue Aug 6, 2018 · 0 comments

Comments

@wardhanster
Copy link

wardhanster commented Aug 6, 2018

I have this weird condition where the peer creating the room is not able to get ICE server candidates from the signalling server, I do see the candidates appearing in the console, but they never get used (as per the chrome internals ). I am using Xirsys's fork of signalmaster.
At the moment I am populating the ICE server candidates using Xirsys's API call on the client end, which I believe is not the safest way to go ahead.

Although when another peer connected to the room, refreshes itself the needed ICE server candidates appear on the call initiator.

Any directions as why this might be happening ? and How I can resolve it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant