XRAI Stream reaches visitors two ways: across the venue network to devices in the building, and through the XRAI cloud to browsers anywhere. This is what each path needs.
On the venue network
| Traffic | Address and port | Notes |
|---|---|---|
| Discovery | Multicast 224.0.0.255, UDP 55000 | Receivers find streams from these announcements. mDNS is an optional second route, for networks where the XRAI announcement is blocked but mDNS is not. |
| Captions | Multicast 224.0.0.255, UDP 55001 | A second publisher on the same network uses 55002, and so on. |
224.0.0.255 is in the Local Network Control Block: switches pass it to every port, so it gets through where other multicast is filtered, and routers never forward it. That means:
- The publisher and the receivers must be on one network segment. A guest network or a separate VLAN doesn't see the stream.
- Guest Wi-Fi with client isolation doesn't carry it.
- On a computer with more than one connection, such as Wi-Fi and Ethernet, or a VPN, XRAI Studio must send on the interface the audience is on. It has a Network interface setting for this.
Through the cloud
Browser viewers and the XRAI relay use ordinary outbound web access. Nothing inbound needs to be opened.
Phones and computers that receive
On iPhone, iPad and Mac, the XRAI app needs Local Network permission to find streams. Without it, discovery finds nothing and shows no error.
Venues with a licence can check what a computer on the network receives with Stream Agent. See Check the network with Stream Agent.