Comms
Comms
Production intercom for the auditorium — the headset network that lets the
director, camera ops, lighting, projection and stage crew talk during a service.
It’s a Green-Go digital partyline, carried over Ethernet, with a
mobile-device bridge for phone/app users. The configuration is the single
Comm/Green-Go Configuration.gg5
(opened in the Green-Go editor).
Network
- VLAN 24, subnet
10.0.24.0/24, DHCP from the EdgeRouter, authoritative. See Networks. - The Green-Go bridge (
COMMS-BRIDGEX,10.0.24.1) lives in the AV room left rack. Stations sit around the room (e.g. a comms station in the switcher desk rack in the video control room). Green-Go carries both control and the intercom audio over the network.
Stations on 10.0.24.0/24
Named by role (see the network map):
| Address | Station |
|---|---|
10.0.24.1 |
BridgeX (mobile-device bridge); the only Comms device allowed out to the internet |
10.0.24.2 |
Lighting (LX) |
10.0.24.3 |
Projection |
10.0.24.4 |
Main camera |
10.0.24.7 |
Switcher |
10.0.24.8 |
Shading |
10.0.24.9 |
Audio stream |
Monitoring: red is the normal reading
Uptime Kuma monitors five stations by ping. Expect them all red outside a service. The Green-Go stations are service-time gear — they are powered up for a service and off the rest of the week — so a red Comms monitor on a Tuesday is the expected state, not an incident.
This only became a meaningful reading on 2026-09-17. Until then docker-server had no address on
VLAN 24, so the monitors were reporting a missing route and had never once recorded an up-beat.
Now the box holds 10.0.24.200, the EdgeRouter at 10.0.24.254 answers, and every station reports
ARP FAILED — a real negative rather than an unknown. See
the signage runbook for the full write-up.
If you need to know whether the network is healthy rather than the gear, ping 10.0.24.254 from
docker-server. That is the router on this VLAN and it answers whether or not any headset is on.
Where the config lives
The whole partyline — stations, channels and routing — is defined in the single
.gg5 file under Comm/. Edit it in the Green-Go editor and commit the result so
the configuration stays versioned.