On Demand Sputnik servers are used differently by Teradek devices compared to a dedicated Sputnik server that is hosted by Core or deployed manually and linked to a Core account.
Network port ranges and IP addresses used by the On Demand Sputnik can change between each use of the service. Teradek devices are able to automatically obtain the current IP address and port for the On Demand Sputnik region when the device is powered on and makes a connection to Core.
In comparison, a dedicated Sputnik server allows a consistent IP address and range of ports to always be available.
Core Subscription Levels
Since the IP address and ports used with an On Demand Sputnik server can change, there are some scenarios where it may not be possible to use an On Demand Sputnik server. For example:
- If there are stringent security requirements on a network -- for example, a static IP address or limited port range must be approved for outbound connections through a business firewall.
- Another use case which would require a dedicated Sputnik server is the use of 3rd party streaming software like Telestream Wirecast or vMix. Third party products cannot determine the On Demand Sputnik server's address or ports, and are not supported on the Starter subscription level.
If you have similar requirements, you cannot use the Starter subscription plan; the Starter plan is limited to using an On Demand Sputnik server.
Instead, choose the Basic level subscription plan or higher and create a dedicated Sputnik server.
Network Port Requirements
The following port ranges must be allowed for connections to an On Demand Sputnik server:
- outbound port range 1024 through 65535/TCP. This is used in the following:
- Outbound streaming from an Encoder to the On Demand Sputnik server using the TCP protocol.
- Receiving / pulling down the stream to a Decoder from the On Demand Sputnik server. This type of pulled connection always uses the TCP protocol.
- outbound port range 1024 through 65535/UDP : This is used for streaming from an Encoder to the On Demand Sputnik server using the UDP protocol.
- Streaming with the UDP protocol is available on a Cube + Bond (original), Bond II, Bond Pro, or Cube 600 / 700 / 800 series, and the streaming protocol is changed from the default TCP to UDP.
- This does not apply to a standalone Cube, or to a Teradek Decoder.
If these outbound port ranges are blocked then it may not be possible for the encoder or decoder to make a connection to the On Demand Sputnik server on that particular network interface (Ethernet, USB modem, or Wi-Fi).
Outbound port blocking may be encountered on shared network connections at public venues (hotels, airports, coffee shops) or at facilities with restrictive security settings such as school, government, or business networks.