Update STUN servers #1381
Merged
Update STUN servers #1381
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Commented out sipgate.net STUN server. Added Cloudflare STUN server.
|
cool, thanks, sure. My failures are typically NAT related to Safari, doubt this will help? But seems fine either way. |
|
Yeah, no, NAT issues are usually resolved using TURN |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why this PR?
After some testing, I discovered that the reason the WebRTC connection failed frequently for me was because the sipgate.net STUN server would fail with code 701.
I commented out the sipgate.net STUN server and added the Cloudflare STUN server.
Why Cloudflare?
I chose the Cloudflare STUN server because it is free to use and stable.
Changes:
Commented out sipgate.net STUN server.
Added Cloudflare STUN server.