Can I simplify WebRTC signalling for computers on the same private network?

STUN/TURN is different from signaling.
STUN/TURN in WebRTC are used to gather ICE candidates. Signaling is used to transmit between these two PCs the session description (offer and answer).
You can use free STUN server (like stun.l.google.com or stun.services.mozilla.org). There are also free TURN servers, but not too many (these are resource expensive). One is numb.vigenie.ca.

Now there’s no signaling server, because these are custom and can be done in many ways. Here’s an article that I wrote. I ended up using Stomp now on client side and Spring on server side.

I guess you can tamper with SDP and inject the ICE candidates statically, but you’ll still need to exchange SDP (and that’s dinamycally generated each session) between these two PCs somehow. Even though, taking into account that the configuration will not change, I guess you can exchange it once (through the means of copy-paste 🙂 ), stored it somewhere and use it every time.

Leave a Comment