Network Configuration to Stream with a PIXELLOT
If you have a Pixellot, you must:
Whitelist all outbound HTTP/S traffic to pixellot.tv.
Whitelist all outbound HTTP/S traffic to logmein.com.
No inbound firewall rules are required. No services will ever connect directly to the host. However, to publish video and manage the server, we need these ports open for outbound traffic to all IPs:
|443||TCP||Remote Management||https, agent|
|123||TCP+UDP||Clock synchronization||NTP-clock sync|
|80||TCP||Event control (stop / start)||RabbitMQClient (Coordinator in Production/Necessary for Graphics)|
|2077||UDP||Video streaming||ZIXI broadcaster|
|53||TCP+UDP||DNS Name management||
|1401||TCP||Sportzcast (Score data integration tool)|
Network Configuration to Watch Video
Open all TCP traffic on ports 80 and 443 for nfhsnetwork.com and all subdomains.
Open all TCP traffic on ports 80 and 443 for w.sharethis.com.
You may need to disable any content filters or filtering applications for the VPU's IP address.
Video Stream/Data Transmission
- All video data is transferred from Pixellot to the NFHS Network Servers using Real-Time Messaging Protocol (RTMP)
- The NFHS Network Servers are all hosted using Amazon Web Services (AWS) in the North Virginia (US East) Data Centers
- Once received by the NFHS Network, the video data is transcoded using automated servers (no human involvement), and then stored in the AWS S3 Storage Buckets (again hosted on AWS North Virginia)
- The video is distributed to consumers using HTTP Live Streaming (HLS) using the AWS CloudFront Content Distribution Network