Teradek decoders and some apps and software clients require the following network ports for use with the Core management system.
Inbound Network Connections
In the standard scenario for using Teradek Decoders with Core, no incoming connections are needed from either the Core management system or a Sputnik server.
However, if you are sending a stream from an external Sputnik server to a standalone Teradek decoder or third party decoder using a supported streaming protocol (e.g. MPEG Transport Stream / MPEG-TS, or SRT) those connections would originate from the IP address of the Sputnik server and would need to reach the decoder on the custom port you have specified.
Be sure to configure firewalls and routers for any port forwarding needed in these circumstances.
Outbound Network Connections
Outbound connections are initiated by the Teradek decoder or app or software client, and arrive at the remote server on the indicated port.
If the Teradek decoder/app/software client is behind a firewall, and that firewall blocks or filters outbound traffic, the necessary ports must be open to allow communication and streaming.
- 80 (TCP) : Communication with the Core management system.
- 443 (TCP) : Communication with the Core management system.
- 5111 (TCP) : Communication with a Core-deployed Sputnik server, or a self-hosted Sputnik server using the default port.
- 5200-5299 (TCP) : This port range is used by default to pull down MPEG-TS video streams from a Core-deployed Sputnik server or a self-hosted Sputnik server. These ports are also used by apps like the Core app for iOS, or software clients like VLC Media Player or vMix or Wirecast to pull down the stream from a Sputnik server.
- 1024-65535 (TCP) : Communication and video streaming to an On Demand Sputnik server from devices and apps using the default TCP protocol. If On Demand Sputnik servers are not being used, this port range is optional. See this article for additional information.