Are you forwarding port 80 to whatever the default RTMPT port is (I think it's 8088, check conf/red5.properties)? The little connectoid class I wrote tries RTMPS, then falls back to RTMP then RTMPT as connections fail and I've had it work perfectly behind even the most anal of corporate firewalls. All I use is an Apache server using mod_proxy to proxy certain URLs to Red5 (ie. ProxyPass /open http://red5.server:8088/open).
To everyone: I think it's straight forward enough, but would anyone benefit from me making a simple howto outlining how I got it working (if one doesn't already exist)? Jason Ben Wade wrote: > > I’ve ran into a problem where a user cannot stream from red5 servers > (He can stream with wowza and FMS servers). We’ve tried every config > variation and we currently have the config set to… rtmp (port 1935) > and rtmpt (port 80) and that doesn’t work. It might be on his end with > his router and isp, but when he uses rtmpt… port 80 should work for > him and it doesn’t, which means that some people are not able to > stream with red5. And it stinks to know that. J > > This link touched exactly on what we’re trying to get fixed but > doesn’t provide any fixes: > > http://jira.red5.org/browse/APPSERVER-124 > > Also, Alexandre was talking of stunnel (rtmps) in another email, but > that seems very complex to achieve at this point and it seems like > there should be a more reachable fix with rtmpt. Maybe not though. Any > thoughts or ideas would be extremely welcome! > > Regards, > > Ben Wade > > ------------------------------------------------------------------------ > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
