Replies: 1 comment 3 replies
-
It is possible that you are behind a NAT that doesn't support address independent mapping/filtering. WebRTC for the Curious#Networking has a section explaining more. stun-nat-behaviour is a good tool to learn more also. I would run a TURN server and make it acessiable via TCP and UDP to support all networks. You could run your own or using a provider like Twillio. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
version:3.0.29
system:ubunbtu16.04
I have a camera And I using a PC to convert the camera signal to webrtc.
The stun is URLs: []string{"stun:stun.l.google.com:19302"}.
In the LAN very thing is OK. So I decide to make it in the internet.
The method is that:
Why the webrtc server doesn't response the client?
Beta Was this translation helpful? Give feedback.
All reactions