Network communication requirements for using standalone Hyperion servers

Overview

The tables below list the inbound / incoming and outbound / outgoing network connection requirements for using a standalone Hyperion server.

This covers the necessary ports and protocols needed for the following:

• Teradek encoder communication with the Hyperion server, as well as inbound video streaming to the Hyperion server.
• Teradek decoder communication with the Hyperion server, as well as decoders, apps or software clients to pull down the MPEG Transport Stream video hosted from the Hyperion server.
• Outgoing ports needed for a Hyperion server to send out video streams over RTMP to destinations like Facebook Live or YouTube Live, or over MPEG Transport Stream.

Inbound Network Connections

Inbound connections originate from outside the Hyperion server, and arrive at the Hyperion server on the indicated port.

If the self-hosted Hyperion server is behind a firewall, the necessary ports will need to be forwarded to the internal, private IP address of the Hyperion server.

• 22 (TCP) : SSH access to the Hyperion server; this is optional and not required in any way for streaming device operation. This is under user control, and is recommended that it is disabled unless proper security measures are in place for your self-hosted Hyperion server.
• 1957 (TCP) : HTTP communication with the Hyperion Dashboard / Web User Interface (Web UI).
• 1958 (TCP) : HTTPS communication with the Hyperion Dashboard / Web User Interface (Web UI).
• 5111 (TCP) : Communication port used by Teradek encoders and decoders to register with the Hyperion server. Also used as the inbound video port from Teradek encoders.
• 5111 (UDP) : Inbound video port used by Teradek encoders capable of using the UDP protocol for streaming video to a Hyperion server.
  • Streaming with the UDP protocol is available on a Cube + Bond (original), Bond II, Bond Pro, or 600 / 700 / 800 series encoders, and the streaming protocol is changed from the default TCP to UDP.
  • This does not apply to a standalone Cube (1st or 2nd gen), Slice encoder (1st gen), T-RAX encoder, or apps.
• 5000-5010 (TCP) : Video ports that are manually configured on a Teradek encoder to allow decoders or remote sources to pull down the video stream from the Hyperion server. The default port listed on encoders is 5000, and the default firewall range on pre-configured Hyperion servers sold by Teradek allows ports 5000 through 5010. If video streams are not being pulled down by decoders (e.g. only RTMP streaming is being used), these ports are optional.

Outbound Network Connections

Outbound connections are initiated by the Hyperion server, and arrive at the remote destination on the indicated port.

If firewalls are in place that block outbound traffic, the necessary destination ports must be permitted through those firewalls.

If firewalls are in place with content filtering, those content filters may block access to some sites categorized as related to social networking; content filter restrictions would need to be removed for the Hyperion server to be able to send out RTMP streams to those destinations.

• 80 (TCP) : RTMP streams sent over port 80 to either Facebook Live or Periscope. If RTMP streaming to Facebook Live or Periscope is not being used, this port is optional.
• 1935 (TCP) : RTMP streams sent to common online video platforms / CDNs like YouTube Live or Akamai. If RTMP streaming is not being used (e.g. only streaming between encoders and decoders), this port is optional.
  • NOTE : if RTMP streams are being sent to a third party device, server or hosted service on a port other than the default 1935, that port would likewise need to be permitted through any outbound firewalls that are filtering traffic based on the destination port.
• 9710 (TCP) : MPEG Transport Streams sent over the TCP protocol; this port is configurable on the encoder that is streaming into the Hyperion server, so if you're sending to a different port this must be allowed by any outbound firewalls. If you're not using outbound MPEG-TS streaming (e.g. only using RTMP or MPEG Transport Stream pulled down on ports 5000 through 5010) this port is optional.
• 9710 (UDP) : MPEG Transport Streams sent over the UDP protocol; this port is configurable on the encoder that is streaming into the Hyperion server, so if you're sending to a different port this must be allowed by any outbound firewalls. If you're not using outbound MPEG-TS streaming (e.g. only using RTMP or MPEG Transport Stream pulled down on ports 5000 through 5010) this port is optional.
  • NOTE : if MPEG Transport Streams are being sent to a third party device, server or hosted service on a different port, that port would likewise need to be permitted through any outbound firewalls that are filtering traffic based on the destination port.