Intercom: Networks and remote crews

Networks and remote crews

Start on the same wired or Wi-Fi network with client isolation disabled. Permit host TCP port 8917 and peer WebRTC UDP connectivity. Each computer opens its own localhost UI so microphone permissions work without installing a trusted web certificate on every crew computer. Audio is encrypted by WebRTC and travels between the crew endpoints (or via a configured TURN relay), not through the Hub.

For different networks, use a reachable host address and suitable STUN/TURN settings supplied by your network administrator, or connect through a VPN that permits peer audio. Expand Remote network settings when hosting and enter ICE server JSON, for example:

[{"urls":"turn:relay.example.com:3478","username":"crew-user","credential":"YOUR_TURN_CREDENTIAL"}]

Require TURN relay forces media through TURN and requires a TURN URL. No public TURN service, credentials, managed cloud hosting, mobile app or internet relay is included. Do not paste ICE settings or invites into broadcasts. Remote operation must be tested on the crew's actual networks before the event.