Plan your network

Tell the planner about your show. It works out what each phone and the server need, the data a phone uses in an hour, the ports to open, and which apps go on a computer at the venue.

Your show

Where ON Comms runs
Crew connect over
At the venue
12 on air, 2 talkingmeasured figures

Each phone, while talking

103 kbit/s up

Each phone, hearing 2 people at once

182 kbit/s down

A phone’s data, for an hour of that

88 MB

All the phones together, each on its own signal

345 kbit/s up2.0 Mbit/s down

Ports

Nothing to open at the venue: phones and computers connect out.

HTTPS on TCP 443, and audio on UDP 7882 — or TCP 7881, or the relay on UDP 3478, where UDP 7882 is blocked.

At the venue

Nothing else to install.

Where the figures come from

Measured on ON Comms itself, with two browsers on one network and a line talked on without a single pause — more than a real show sends, because speech pauses and Opus sends less in the pauses.

  • A line being talked on: 92.5 kbit/s up from the person talking, and 89.2 kbit/s down to each person hearing them. Opus is capped at 32 kbit/s; each packet also carries the frame before it, so a lost one is rebuilt, and the rest is headers.
  • A line nobody is talking on: 3.2 kbit/s — the silence Opus sends so the line is ready the moment a key goes down.
  • Signalling and control: about 4.3 kbit/s up and 3.6 down for each device.
  • On the wire, with AES-256-GCM, over IPv4 and UDP. Through a relay or over TCP, a little more.
  • The worst case: everyone talking is heard by everyone else. Crew who hear fewer lines use less.

Everything else a network needs to know is on the spec sheet.

See it on your own show.

We’ll walk your engineers through ON Comms on a call — your gallery, your network, your questions.

Book a walkthroughCreate an account