Errors on IP Outputs

RTMP Client Mode

Issue	Cause	Solutions
Improper URI	The URI configured in the IP output profile is malformed.	On the StreamHub, deactivate the IP output, then go to the IP Output Profiles configuration page and type a valid URI (e.g., a valid URI does not end with a slash character "/").
DNS issue	No DNS server configured on the StreamHub server.	Go to the StreamHub server's Settings menu to check whether a DNS server is configured or not. If not, configure a DNS server (please refer to the StreamHub Installation & Configuration Guide ).
	The DNS server does not send any address for the domain name.	The StreamHub tries to establish a connection every 30 seconds. If the problem persists: On the StreamHub, deactivate the IP output. Go to the IP Output Profiles configuration page and check that the domain name included in the URI is correct. Use the `ping` command from a computer with the same network configuration as the StreamHub server (i.e., which is on the same LAN, with the same gateway, and the same DNS server configured) to check whether the domain name does exist on the DNS server.
	The DNS server does not exist or it is not responding.	The DNS server may be temporarily not responding, for instance if an update is in progress. To check the availability of the DNS server configured on the StreamHub server: Go to the StreamHub server's Settings menu (please refer to the StreamHub Installation & Configuration Guide) to check the DNS server configuration. Use the `ping` command, from a computer with the same network configuration as the StreamHub server (i.e., which is on the same LAN, with the same gateway and the same DNS server configured) to check whether the DNS server responds or not.
Connection timed out	No ICMP response received after the RTMP connection request of the StreamHub client.	The StreamHub tries to establish a connection every 30 seconds. If the problem persists: Check the network, especially if a firewall or a proxy server could block the stream without sending any ICMP message.
Host unreachable	The RTMP server cannot be reached.	The StreamHub tries to establish a connection every 30 seconds. If the problem persists: Use the `ping` or `trace route` command, from a computer with the same network configuration as the StreamHub server (i.e., which is on the same LAN and with the same gateway configured) to check the network. If possible, check whether the RTMP server is started or not.
Connection refused	The domain name or the IP address configured in the URI is incorrect (e.g., it can be another server).	On the StreamHub, deactivate the IP output and then go to the IP Output Profiles configuration page and check that the IP address and domain name are those of the RTMP server to which the stream should be directed. See Configuring IP Output Profiles.
	The distant server is started, however the RTMP service is not started.	Start the RTMP service on the distant server.
	Port issue	Check the port configured on the RTMP server for the RTMP service. On the StreamHub, deactivate the IP output. If the port configured on the RTMP server is not the default one (i.e., TCP 1935), go to the IP Output Profiles configuration page of the StreamHub and modify the URI in order to reference the port in it (please see Configuring IP Output Profiles).
Not RTMP server	A service does exist for the URI (address and port), however it is probably not an RTMP service.	On the StreamHub, deactivate the IP output. Go to the IP Output Profiles configuration page of the StreamHub and check the URI configured for this RTMP server, it may be the URI of another server and/or the port included in the URI is incorrect. For instance, if the RTMP server with the hostname "youtube.com" has: a HTTP web service using TCP port 8888 an RTMP service using TCP port 1935 The URI "rtmp://youtube.com :8888/live/stream" would direct towards the web service of the server (because the port 8888 is dedicated to the HTTP service and not to the RTMP service). In this example, to fix the issue delete the port number (":8888") from the URI, or replace it with the port corresponding to the RTMP service, which, in this instance, is ":1935".
RTMP stream refused	The stream key is already used (e.g., trying to publish a stream that is already published on a Wowza server configured with the option "Duplicate Stream Keys").	Stop the other client using the stream key.
	The stream key/ application name / instance name is incorrect (on Youtube Live for instance).	Check the RTMP URI: the instance name (if any), the application name, and the stream key.
	Problem with the login and/or password.	Check the authentication of the IP output.
Connection lost	The TCP connection between the StreamHub server and the RTMP server has been lost during the transmission.	Look at the error code returned on next connection: the connection error message appears about 30 seconds after the message "connection lost".
Overrun error	The RTMP connection does not have a sufficient network bitrate to transmit the incoming stream to its clients.	StreamHub tries to establish a connection every 30 seconds. If the problem persists: If the Live profile configured on the field unit is on VBR mode, lower the video bitrate using the control slider "capped bitrate" which is on the page of StreamHub. See Capping the Video Bitrate. If the Live profile configured on the field unit is on CBR mode, stop the Live transmission on the field unit and select another Live profile configured with a lower video bitrate. Then, restart the Live transmission on the field unit. Increase the bitrate of the Internet connection: download speed of the RTMP server and/or the upload speed of the StreamHub. Find a potential network disrupting element (for instance, another traffic such as a TS stream consuming the bandwidth).

TS over IP

Issue

Cause

Solutions

The video freezes (client side)

The latency is too low.

On the StreamHub, disable the IP output.
In the Output section, open the TS output parameters and increase the TS bitrate for the TS output.

Many dropped packets on the TS output

The incoming stream bitrate is too high regarding the TS bitrate configured on the TS output settings.

If the incoming live directed to the TS output is configured with the VBR bitrate mode, you can lower the video bitrate from the input page using the control slider.

On the StreamHub, deactivate the IP output.
Go to the IP Output Profiles configuration page of the StreamHub and increase the TS bitrate and/or the Delay for the TS output. To set the TS bitrate, please read the recommendations about Creating a TS output profile on Configuring IP Output Profiles.

Network is overloaded

Check the whole chain, from the field unit to the StreamHub and from the StreamHub to the IRD, to try to identify a potential network disrupting element (for instance, other traffic consuming the bandwidth).
Ensure that the upload speed of the StreamHub is sufficient (for more details, please refer to the StreamHub Installation & Configuration Guide).
Ensure that the download speed of the IRD is sufficient to receive the stream.

RTSP

Issue

Cause

Solutions

No video on the player

There is a proxy, gateway or firewall on the LAN to which is connected the client appliance

Configure the player to request RTSP over TCP (interleave mode).

For instance, on VLC: go to Tools > Preferences > (Show all settings) > Input / codecs > Demuxers > RTP/RTSP and enable "Use RTP over RTSP (TCP)".

SST

Issue

Cause

Solutions

Input is busy

The input of the receiving StreamHub is already used.

Select another input that is not already used.

Input is disabled

The input of the receiving StreamHub is not set with a SafeStream protocol.

Select another input that is set with the SafeStream protocol.
Set the input on the receiving with the SafeStream protocol.

Host unreachable

The Destination server cannot be reached

Check the IP address and the Manager Port configured for the Host server:

In the Host server Web interface, go to Settings > General > and check the Manager Port.
In the receiver server Web interface, go to Settings > IP Output Profiles and select the SST Profile assigned to the Host Server. Check that the IP Address and the Manager Port are the same as in the Host server Web interface.