Can I simplify WebRTC signalling for computers on the same private network? <p>WebRTC signalling is driving me crazy. My use-case is quite simple: a bidirectional audio intercom between a kiosk and to a control room webapp. Both computers are on the same network. Neither has internet access, all machines have known static IPs.</p> <p>Everything I read wants me to use STUN/TURN/ICE servers. The acronyms for this is endless, contributing to my migraine but if this were a standard application, I'd just open a port, tell the other client about it (I can do this via the webapp if I need to) and have the other connect.</p> <p>Can I do this with WebRTC? Without running a dozen signalling servers?</p> <p>For the sake of examples, how would you connect a browser running on 192.168.0.101 to one running on 192.168.0.102?</p>