What are the requirements to use HIVE for Kaltura MediaSpace?
Kaltura MediaSpace Requirements
Kaltura MediaSpace can be implemented in a variety of configurations, including on-premises implementations or as a managed cloud service.
- Support for Hive Streaming has been included in the Kaltura MediaSpace application from version 5.70 (based on Kaltura Player version 2.72).
Hive Streaming support varies based on the mode of deployment for Kaltura MediaSpace:
| Kaltura SaaS | Kaltura Regional Clouds | Kaltura MediaSpace On-Premises deployments |
|---|---|---|
 | Coming Soon | |
If you are unsure which version of Kaltura MediaSpace you have, please contact your Kaltura account team (see Release Notes)
Kaltura MediaSpace Requirements
Kaltura MediaSpace has its own live streaming requirements, detailed here.
Understanding Hive Streaming Requirements
HIVE WebRTC Endpoint Requirements
To support browser-based peer-to-peer distribution of live video, HIVE WebRTC requires a web browser that supports WebRTC data channels.
| Platform | Chrome | Firefox | Safari | Edge | Internet Explorer | Kaltura MediaSpace Go for iOS | Kaltura MediaSpace Go for Android |
|---|---|---|---|---|---|---|---|
| Windows | | | - | | Viewing Stats only | - | - |
| macOS | | | (Stats Only) | - | - | - | - |
| iOS | Viewing Stats only | - | Coming Soon | - | |||
| Android | | | - | - | - | - | Coming Soon |
Browsers that do not support WebRTC data channels may still view Kaltura MediaSpace events, but they will not benefit from peer-to-peer distribution.
HIVE WebRTC Networking Requirements
HIVE WebRTC typically functions optimally on enterprise networks without any additional configuration. However, IT Admins should review the following list to insure no required services are blocked.
Required or Optional | Protocol (Port) | Destination Address | Description | Comments |
|---|---|---|---|---|
| HTTPS & WSS (tcp/443) | *.hivestreaming.com | HIVE Cloud Services hosted on the Internet For plugins hosted by Hive, download.hivestreaming.com is a required endpoint and needs to be part of the firewall rules to bypass proxy services | HIVE Cloud Services are used for signaling, telemetry & logging only (no content) |
| WebRTC (udp/1025 thru udp/ 65535) | Browser-to-browser | Peer-to-peer transmission of encrypted video fragments and telemetry | UDP communication is not needed outbound, beyond the corporate firewall |
| STUN (tcp/3478 & udp/3478) | stun.hivestreaming.com | IP address & NAT discovery services (HIVE Cloud Services) hosted on the Internet | STUN is not required, but improves performance between connected sites. |
Legend |
|---|
|
|
Try It Out!
You can verify HIVE WebRTC is supported on your network by loading the HIVE WebRTC reference player. Share the URL https://webrtc.hivestreaming.com/kaltura with other workers in your network and watch the test video together for several minutes to verify your browsers are able to reach the Hive Streaming Cloud Services and connect with other browsers on the network to distribute video fragments. Click here for more information on the HIVE WebRTC reference player.
The HIVE Agent may be deployed by a Kaltura MediaSpace customer to enable more advanced use cases, including support for non-WebRTC compliant browsers, HIVE Silent Testing and custom network configurations.
HIVE Agent Endpoint Requirements
The HIVE Agent extends HIVE distribution support for Kaltura MediaSpace events to non-WebRTC web browsers, including Internet Explorer and Microsoft Edge. Installed HIVE Agents also support HIVE Silent Testing and custom network configurations.
| Windows | macOS |
|---|---|---|
HIVE Agent |
|
|
HIVE Agent Networking Requirements
HIVE Desktop Helper
The HIVE Agent uses the HIVE Desktop Helper process (HDH) to automatically connect to services on the Internet, including the HIVE Cloud Services and video content hosted on the video platform partner's CDN. If the HDH is not permitted or unable to transit your Internet infrastructure, manual network configuration steps are offered.
Required or Optional | Protocol (Port) | Destination Address | Description | Comments |
|---|---|---|---|---|
 | HTTPS (tcp/443) | 127.0.0.1 (local machine only) | The HIVE Agent must receive communications from the local web browser. The Agent "listens" on a special local machine address (commonly referred to as the loopback adapter). | Please ensure requests from installed web browsers to the local loopback adapter address (127.0.0.1) are not routed through a web proxy. This is typically configured in the Proxy Auto-Config (PAC) file. |
| HP2P (udp/1025 thru udp/ 65535) | Agent-to-Agent | The HIVE Agent must communicate with other HIVE Agents within the internal corporate network. | UDP communication is not needed outbound, beyond the corporate firewall. The specific UDP range utilized by HIVE Agents may be customized for a customer's network. |
Legend |
|---|
|
|