When troubleshooting WebRTC connectivity issues, it is helpful to confirm whether or not the client can successfully reach the necessary STUN server. Having a proper connection to STUN is a critical component to advertising your public IP address and chosen port to our webRTC resources; especially in the case of NAT. If you’d like to learn more about STUN, this article is very informative.
This guide provides a quick set of instructions to validate reachability of a STUN server. There are two methods of testing; 'Using the Browser Console” and the “webrtc.github.io” method.
| Info |
|---|
Sharpen webRTC leverages the Google STUN servers accessible via stun.l.google.com:19302. The methods below test against the same endpoint Sharpen uses. |
webrtc.github.io
The following tool is not managed by Sharpen, so it should be noted that its usefulness may change.
...