-
Notifications
You must be signed in to change notification settings - Fork 77
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
Not connecting clients from different networks #9
Comments
Can you tell me where you are running it? |
I noticed the demo won't work with separate networks either, so I'm guessing this is the missing piece of the puzzle. Maybe this is a configuration issue in the service hosting the TURN server? |
Yes, it can be. I'll be investigating this during this week. Last week it was possible to do a call Poland-Korea. Something stopped working or got updated. I also considering that I am using free stun and turn servers and right now the use of those servers have increased |
I'm noticing the same problem with other webrtc demos out there. |
I'm running on heroku |
Yes I'm having the same problem but I think that is something related to turn and stun server not with the application itself. I also asked about that on simple-peer repository because I saw that other applications are having the same problem. |
I was able to solve it by testing my stun and turn servers here https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ I deployed the updated version check it out |
@diegogurgel I am having issue in video chat. When two clients connected to same network, it working fine. But having issue on connecting with different client. I am running you example code. Anything extra configuration I need to do
Originally posted by @donny08 in #7 (comment)
The text was updated successfully, but these errors were encountered: