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

Code smell in ICE candidate exchange process #46

Closed
elmarti opened this issue Sep 7, 2017 · 1 comment
Closed

Code smell in ICE candidate exchange process #46

elmarti opened this issue Sep 7, 2017 · 1 comment

Comments

@elmarti
Copy link
Owner

elmarti commented Sep 7, 2017

Certain devices never seem to receive ICE candidates and it unclear as to why. The WebRTC spec needs to be reviewed and the exchange process needs to be checked to ensure that ICE candidate exchanges are not being blocked by synchronous user interaction.

@elmarti
Copy link
Owner Author

elmarti commented Sep 7, 2017

Managed to throttle connection, it appears that the issue is that I am using publicly available STUN/TURN servers and often testing across a corporate firewall, making it hard to make a connection.

@elmarti elmarti closed this as completed Sep 7, 2017
@ghost ghost removed the ready label Sep 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant