Skip to content
Game Action 360 SPORTS
HUB
Menu
Application manual

Intercom: Install and connect

Operational reference for install and connect in Intercom.

Updated November 4, 2026 · 2 minute read · Application 1.0.23

Install and connect

  1. Install Intercom on each crew computer. Use Python 3.11+ with Tk, a current
  2. Chrome/Chromium browser, and a headset. The host also needs OpenSSL on PATH. On Mac, run Start-Mac.command; on Linux run bash install-linux.sh as your normal desktop user, then open Intercom from Applications or Workstation. Installation and account/license/update behavior follows the other GA360 apps.

  3. Connect your Workstation account and enable the Intercom application entitlement
  4. for crew accounts through Sports Hub plan/application access. Each app checks its own entitlement; room display names and invitations are separate from login.

  5. One person chooses Host room, enters their name/role and a room name, then
  6. confirms the host computer's LAN IP address or hostname. The suggested address may need replacing on computers with multiple network interfaces.

  7. Share the generated invitation privately. Each other person opens their local
  8. Intercom app, enters a name/role, pastes the invitation under Join room, and allows microphone access. Click Unmute microphone when ready.

  9. Use Private call on a crew card. The recipient accepts or declines. Incoming
  10. and outgoing pending calls pause your microphone; the group remains audible until a private call is accepted. Return to group ends the private call.

  11. In Hold to talk mode, first unmute, then hold the talk button or Space while
  12. focus is outside form controls. Releasing, changing windows or hiding the tab releases push-to-talk. Open-mic mode continues while you use other apps.

  13. The host keeps Intercom open for the event. End room & leave invalidates the
  14. invitation. Closing the host app also ends the room. Others can leave without ending the event. The host can remove a participant from the crew list.

No camera access is requested. The local UI uses port 8916. Host signaling uses TLS on port 8917; each invitation includes the exact host certificate fingerprint, which joining apps check before sending the room secret. Host keys are generated outside the installation under ~/.ga360-intercom and never included in exports. Room membership, invitations and signaling are in memory and end on restart. The app does not provide audio recording. Do not share an invitation publicly; removed participants can rejoin if they retain the current invitation.

Need more help with this?

Search a specific symptom, review related guides below, or prepare a report with the app version, operating system and exact error. Guides describe the documented release; installed versions and subscription access can differ.

Prepare a support report

Related guides

Troubleshooting · 2 min

Troubleshooting: start here

A reusable process for finding the failing layer and avoiding unnecessary reinstalls.

Application reference manuals · 2 min

Audio-to-NDI: Operation

Operational reference for operation in Audio-to-NDI.

Audio-to-NDI