Intercom on phones and remote networks

Use the right access method

Phone browser access requires the documented trusted HTTPS host/link. A generated local desktop certificate is not automatically trusted by other devices. Hub-hosted conversations and independently hosted rooms have different connection setup; follow the workflow your crew host prepared.

Host and participant checks

1. Have the authorized host configure mobile access as documented, including the intended HTTPS address and any required certificate/proxy setup.
2. Share the private mobile link or QR only with intended crew members.
3. On the phone, open the supported browser link and allow microphone access. Choose the intended headset/audio route and tap the required Join/start control.
4. Keep the page visible and the phone unlocked during use. Test behavior before relying on a mobile browser during an event.
5. Confirm two-way speech with another crew member. Test switching audio devices and reconnecting after a network change.

Common remote failures

Untrusted certificates, blocked microphone permission, backgrounded pages, guest-network isolation and WebRTC network traversal can all affect communication. A webpage loading is not proof that the peer audio path works. Preserve the connection-health message and whether group talk, private calls or every mode fails.

Keep access private

Do not post a room invitation, mobile QR, private key or account token in a public support thread. End or revoke room access through the host's supported controls when the crew session is finished.