Networking Requirements - PhenixRTS Docs
Networking Requirements
HTTP Connections
HTTP(S) is used for connecting to the Phenix PCast™ Platform and delivering live streams.
| Domain | Protocol | IP | Ports |
|---|---|---|---|
| phenixrts.com | HTTP/HTTPS | 107.178.248.156 | 80, 443 |
| pcast.phenixrts.com | HTTP/HTTPS | 107.178.248.156 | 80, 443 |
Persistent Connections
Our Native and Web SDKs establish dynamic HTTPS and persistent web socket connections with the closest Phenix PCast™ Point of Presence for low latency communication between clients.
| Domain | Protocol | IP | Ports |
|---|---|---|---|
| pcast-asia-east.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-asia-east2.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-asia-northeast.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-asia-south.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-asia-southeast.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-australia-southeast.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-europe-central.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-europe-central2.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-europe-north.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-europe-west.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-europe-west2.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-northamerica-northeast.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-southamerica-east.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-uk-southeast.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-us-central.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-us-east.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-us-northeast.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-us-southwest.phenixrts.com | TCP | Varies | 80, 443 |
| pcast-us-west.phenixrts.com | TCP | Varies | 80, 443 |
RTC Communication
For delivering real time stream, we rely on a combination of TCP and UDP connectivity.
| Protocol | Port |
|---|---|
| TCP | 80, 443*, 1935**, 3478, 3479 |
| UDP | 443, 1024 - 65535 |
| * | Port TCP/443 is used as a fallback with TURN. It is less optimal than UDP delivery in most cases. |
| ** | Port TCP/1935 is used for RTMP delivery for old browsers that do not support real-time standards. |
Firewall Settings
TURN on TCP/443 is used as a fallback in the case that UDP ports are blocked. While not optimal, the minimal requirement is to have port TCP/443 open for outgoing connections.
IP Address blocks
Download a text list of IP address blocks used by our servers. This list is updated daily.
STUN Servers
We use STUN servers for discovery of clients. It is incorporated for compatibility reasons for web browsers. Having no access to these servers will not impact using the phenix platform directly but it may impact (e.g. slow down or block) some browser from using the phenix platform effectively.
| Domain | Protocol | IP | Ports |
|---|---|---|---|
| stun.l.google.com | ICE | Varies | 19302 |
| stun1.l.google.com | ICE | Varies | 19302 |
| stun2.l.google.com | ICE | Varies | 19302 |
| stun3.l.google.com | ICE | Varies | 19302 |
| stun4.l.google.com | ICE | Varies | 19302 |
Firewall Settings
If you are blocking outgoing connections, please make sure the IPs and/or ports shown above are open in your firewall settings.