Corporate networks, school networks and public Wi-Fi often block the connections an Eagle 3D Streaming stream needs. When that happens your app is fine — the network between it and your user is not.
The stream does not start, or starts and immediately stops. It usually works for you and fails for one customer, or works everywhere except one office — which is the pattern that identifies it. A fault in your app does not care which building the viewer is in.
Three things cause it, in rough order of likelihood:
Open the same stream from a different network — a phone on mobile data is the quickest test, since it shares nothing with the office network. If it works there, the app is fine and the network is the problem.
They can say why it is blocked, and whether the restriction is deliberate. Often it is a general category rule that was never aimed at you.
A specific, small request is far more likely to be granted than "please allow streaming". Give them the exact app URL, and ask that the hosts, ports and protocols in the table below are not blocked for it.
| Purpose | Host | Port and protocol |
|---|---|---|
| The stream page and its connection to the platform | connector.eagle3dstreaming.com (Linux apps:
connector_linux.eagle3dstreaming.com) |
TCP 443 (HTTPS and secure WebSocket) |
| Connection setup (STUN) and relay, used when a direct connection is not possible (TURN) | global.stun.twilio.com, global.turn.twilio.com;
as a fallback, coturn.eagle3dstreaming.com |
UDP and TCP 3478; TLS on TCP 443 (Twilio) or TCP 5349 (coturn) |
| Video, audio and input | The streaming machine, directly | UDP, on ports chosen for each session |
A network that allows only TCP 443 may still connect through the relay, but the picture and input lag will be worse than over UDP. Ask for UDP as well.
If the page says your IP address has been blocked, the network is not the cause — see blocked IP address (arriving with the next platform release).
Test from the venue's network, on the venue's Wi-Fi, before the day. A corporate guest network discovered an hour before a demo is not a problem anyone can solve in an hour.
The hardware side, if the network turns out not to be the cause.
Last updated