Network Configuration to Stream with a Pixellot
Once your network has been configured according to the requirements below, we recommend downloading and running our Network Requirements Test Tool (click here) to verify*.
*NOTES: 1) For "Username" just put your name. 2) The tool does not factor in whitelisted domains and/or content filters, so please check those separately. 3) The tool must be run on the Pixellot computer.
We highly recommend adding the VPU (Pixellot computer) to a separate VLAN or a DMZ and assigning a static IP address.
VPUs use Google Public DNS 126.96.36.199 as the preferred server. Please use your internal DNS as the alternate. We also ask that Gateway SSL Decryption is bypassed and any Internet Sleep Schedules are disabled.
No inbound firewall rules are required as all connections are outbound. Inbound traffic will still be present, but only after an outbound connection is established. No services will ever connect directly to the host. To publish video and manage the server, the following ports must be open for outbound connections to all IPs:
|443*||TCP+UDP||Remote Management/video streaming||https, agent|
|123*||TCP||Clock synchronization||NTP-clock sync|
|2088*||UDP||Video streaming backup||
|5672||TCP+UDP||Graphics, Watermarks, etc.||Scoreboard Graphics Generation|
* 443 TCP must be open for a Pixellot unit to stream.
* 123 TCP is optional and not necessary.
* 443 UDP OR 2088 UDP must also be open.
The following ports are not required to broadcast but are highly recommended for keeping Sportzcast (scoreboard integration device) equipment/software up to date.
|1402||TCP||Sportzcast cloud connect|
|1403||TCP||Sportzcast remote support|
|1935||TCP||Remote Graphics support|
In addition, please whitelist the REQUIRED domains in any active content filters below:
*.nfhsnetwork.com - Communication to scheduling services
*.pixellot.stream - Communication to streaming services
*.pixellot.tv - Communication to streaming services
*.windows.com - Operating system updates
*.msecnd.net - Operating system configuration
*.microsoft.com - Operating system updates
*.video.google.com - Streaming configuration
*.intel.com - Driver configuration and updates
*.windowsupdate.com - Operating system updates
*.geforce.com - Driver configuration and updates
*.live.net - Operating system updates
*.internapcdn.net - System upgrades
*.globalsign.net - Certificate verification
*.verisign.net - Certificate verification
*.geotrust.com - Certificate verification
*.comodoca.com - Certificate verification
*.logmein.com - Remote control for troubleshooting
*.hpanalytics.com - System configuration and updates
*.cloudfront.net - Access to application updates
*.sportzcast.net - Scoreboard control
*.singular.live - Scoreboard graphics
Network Speed Requirements
We recommend an upload speed of at least 10 Mbps. As a reminder, the Pixellot system must be
plugged into a hard-line internet source (not wi-fi or cellular data). For more information about establishing a stable internet connection, please click here.
- DO NOT add any additional user accounts or change any user account settings
- DO NOT change the password
- DO NOT add the user to the school's domain
- Adding/changing user account information affects the system's ability to automatically login after a reboot, which may result in events not broadcasting
- DO NOT add the computer to the school domain
- DO NOT change firewall settings (or add additional firewall/antivirus software)
- Antivirus software consumes CPU resources and can disrupt network traffic
- DO NOT make the computer inaccessible
- Make sure you can access the machine if necessary
- DO NOT leave a monitor, keyboard, mouse, or any other external device plugged in
- Leaving these plugged in may affect our Support team's ability to remotely access the system for troubleshooting
- DO NOT use the computer for anything unless specifically directed by NFHS Network Support
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
For more information, see our Pixellot Network FAQ attached below.