Specify the connection port

The Nimbb Player connects to our servers over different TCP ports. By default, the player tries all different ports in the following order: TCP 1935, TCP 80 and TCP 80 with HTTP tunneling. In most cases, the port TCP 1935 works and this is the fastest way to connect to our server, ensuring the best streaming speed. However, if your company's firewall is blocking the port TCP 1935, then the player will roll to another port (TCP 80 or tunneling) which is much slower and can cause low quality video. To test if your company's firewall is blocking a port outbound, you can try to force the port number to the player.

In this example, we are forcing usage of port TCP 1935. If you are able to record a video with the player below, then the port TCP 1935 is not blocked by your firewall. If you see the message "Problem connecting to server", then your firewall is blocking the port and you need to allow access to port TCP 1935 outbound.

This example requires you to specify your developer key (see tutorial).


HTML code

<object id="nimbb" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="320" height="240" codebase= "http://fpdownload.macromedia.com/get/flashplayer/current/swflash.cab">
<param name="movie" value="http://player.nimbb.com/nimbb.swf?mode=record&port=1935&key=XXXXXXXXXX&lang=en" />
<param name="allowScriptAccess" value="always" />
<embed name="nimbb" src="http://player.nimbb.com/nimbb.swf?mode=record&port=1935&key=XXXXXXXXXX&lang=en" width="320" height="240" allowScriptAccess="always" pluginspage="http://www.adobe.com/go/getflashplayer" type="application/x-shockwave-flash">

In the code, we specify the value 1935 to the parameter port. Note that other accepted values are 80, 80t (HTTP tunneling) and auto (default try-them-all).

Tip: if you want to enforce that your users get the best connectivity when using Nimbb, you can force usage of port TCP 1935.

View more tutorials.

SIGN UP NOW 7-day free trial

Check out our Developer guide to get started with Nimbb.