Replies: 2 comments
-
Ah, I can see more errors on refresh, looks like I do need working stun/turn servers after all: |
Beta Was this translation helpful? Give feedback.
0 replies
-
nvm, I installed and ran coturn, and provided a simple config: config: {
iceServers: [
{ url: 'stun:nestrischamps.local:3478' }
]
} And things are working now :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
(Apologies, for the noob question)
I thought that the turn server and ICE data were only needed to handle NAT, and that for a local setup, a vanilla peerjs server would suffice.
In my local setup, video is not working however. The chrome webrtc internals shows me this (on the receiver side):
but I'm not sure what to make of it 😢 . Do I need local stun/turn servers as well?
The signalling is working fine, I see this for the call negotiation:
Thanks in advance for any tips to put me in the right direction!
Tim
Beta Was this translation helpful? Give feedback.
All reactions