Comments on: RTMP being blocked by firewalls – Flash media server

By: Kristjan H Kristjansson

Kristjan H Kristjansson — Sun, 15 Aug 2010 09:19:53 +0000

Hi Avi – I found your article very good because I have had streaming video for a long time on my web and just found out last week that many can´t see it because of firewalls. I have therefore changed my videos into progressive at the media service provider. I was thinking about having files of different bitrates for auto-detection but that needs port 1935 and because you wrote: “1935 will probably always be blocked because it is not a known port and even simple routers often block it.” I will not do that. Best regards, Kristjan

Reply Quote

By: Avi Tzurel

Avi Tzurel — Thu, 22 Jul 2010 10:05:50 +0000

@Max: RTMPT behind the scenes is actually HTTP.
it could be that the proxy is blocking it.
if this is the case, I would go the extra mile and create an HTTP streaming.

Reply Quote

By: Max

Max — Mon, 19 Jul 2010 17:45:15 +0000

It seems that our company proxy blocks also RTMPT traffic and not only RTMP!!! (Of course it allows HTTP).
Is it possible or am I doing something wrong?!

Basically the .FLV is streamed via RTMPT through a .SWF file

Thank you very much!

Reply Quote

By: Webmaster

Webmaster — Thu, 10 Jun 2010 19:20:28 +0000

Hello! Please e-mail me your contacts. I have a question webmaster@bravto.ru” rel=”nofollow”>……

Thank you!!!…

By: Avi Tzurel

Avi Tzurel — Thu, 10 Jun 2010 14:06:45 +0000

@Ed: I didn’t post that code yet, it’s not only based on a timer, it’s also based on the failure of the first connection.

You don’t have to do any cleanup what so ever, you only assign a new value to the URL of the connection and connect again.

Reply Quote

By: Ed

Ed — Wed, 09 Jun 2010 20:42:38 +0000

Still curious if you’ve posted that code snippet yet. I’m guessing it uses an interval to define a timeout after which it gives up on the RTMP connection attempt and tries RTMPT. But I was wondering if you have to do anything special to cancel and cleanup after the 1st hanging connection attempt.

Reply Quote

By: Bruce

Bruce — Wed, 19 May 2010 16:30:41 +0000

@aj:
That’s because firewalls usually behave like so:
block any other port then 80 (meaning nothing will work)
block any other traffic other then http

So, falling back from port 1935 to port 80 is useless (usually)
falling back from rtmp to rtmpt is useful.

Reply Quote

By: Avi Tzurel

Avi Tzurel — Tue, 18 May 2010 21:37:59 +0000

@Ed:
No I didn’t post the code just yet, I will post it very very soon.

Thanks

Reply Quote

By: Avi Tzurel

Avi Tzurel — Tue, 18 May 2010 21:37:01 +0000

@aj:
That’s because firewalls usually behave like so:
block any other port then 80 (meaning nothing will work)
block any other traffic other then http

So, falling back from port 1935 to port 80 is useless (usually)
falling back from rtmp to rtmpt is useful.

Reply Quote

By: Ed

Ed — Tue, 18 May 2010 17:56:53 +0000

Did you ever post that fallback code?

Reply Quote

By: Ed

Ed — Tue, 18 May 2010 16:08:30 +0000

Did you ever post the fallback code somewhere?

Reply Quote

By: aj

aj — Tue, 23 Mar 2010 04:52:51 +0000

[quote]
DO NOT use any type of arrays of ports, simply use port 80, if the client can’t connect to RTMP on port 80, he will no be able to connect on RTMP no matter the port you are using.
[/quote]

What are the possible reason for this?

Reply Quote