Quote
для полноценной работы нужен еще TURN сервер (релей), потому что по статистике до 10% пользователей живут за NATом, который не позволит UDP hole punching (а это не то же самое что UPnP)
Quote
одним STUN обойтись не получится как раз из-за этих 10%,
The standard listening port number for a STUN server is 3478 for UDP and TCP, and 5349 for TLS.
The standard listening port number for a STUN server is 3478 for UDP and TCP, and 5349 for TLS.
I’ve created a serverless-webrtc project on GitHub that decouples the “signaling server” exchange of connection information from the WebRTC code itself.
You’re really just using a different signaling server here — the IM chat or whatever else you’re using to transfer the SDP offers and answers. Sure, you could theoretically jot those down on a piece of paper and walk them to the person you’re trying to communicate with, in which case your body would be the signaling server
(A STUN server is still used to find out your external IP for NAT-busting. Leaking your IP address to a public STUN server is a privacy dealbreaker there.
Would it be possible to eliminate the need for a STUN server by using IPv6?)
You’re really just using a different signaling server here — the IM chat or whatever else you’re using to transfer the SDP offers and answers. Sure, you could theoretically jot those down on a piece of paper and walk them to the person you’re trying to communicate with, in which case your body would be the signaling server
(A STUN server is still used to find out your external IP for NAT-busting. Leaking your IP address to a public STUN server is a privacy dealbreaker there.
Would it be possible to eliminate the need for a STUN server by using IPv6?)