The Hive Streaming service depends upon three types of communications:
- Outbound requests to the HIVE Cloud Services (signaling, telemetry & logging only)
- Internal network communication between HIVE endpoints (signaling & video fragments)
- Outbound requests to your chosen video platform provider's application and CDN (video fragments)
1. Outbound requests to the HIVE Cloud Services
For HIVE endpoints to function on your network, please bypass any web proxy or remove inspection, authentication and reputation lookup services for outbound HTTPS requests (including WebSockets) to the following domains:
Note: If wildcard access is prohibited or static IP addresses are needed for firewall configuration, additional details are available here.
2. Internal network communication between HIVE endpoints
HIVE endpoints must be able to communicate with one another across the internal corporate network:
- UDP communication must be permitted inside the corporate network. UDP communication is not needed outbound, beyond the corporate firewall.
- The HIVE Client "listens" on a special local machine address (commonly referred to as the loopback adapter). Please ensure requests from a local web browser to this local machine address bypass any web proxy (typically 127.0.0.1).
Note: The UDP port range used by the HIVE Client may be customized to prevent conflicts with other applications, contact your HIVE Technical Account Manager (TAM) for more information.
3. Outbound requests to your chosen video platform provider's application and CDN
Your chosen video platform provider may require additional rules to support access to their application(s) and CDN (Content Delivery Network). Contact your video platform provider for additional details.
Additional requirements for HIVE WebRTC
For HIVE WebRTC, our next-generation WebRTC-based distribution solution, we recommend two additional rules:
- Outbound TCP/3478 and UDP/3478 (STUN)
- Outbound UDP/53 (DNS)
NOTE: These are standard WebRTC communications that may already be enabled on your network (if you already use WebRTC applications)