By default Red5 listens for RTMP connections on port 1935 and RTMPT connections on port 8080. Unless we want to change Red5 to listen for RTMPT connections on port 80 (and get into the hassle and security issues of running it as root), this means that we must explicitly code our clients to fall back to port 8080 instead of relying on the built-in Flash Player fallback mechanism (which falls back to RTMP tunneling through port 80).
So far so good. My question is this: does this actually solve anything? If a client is behind a firewall that blocks outgoing connections on non-standard ports, 8080 will be blocked too. Or is this simply intended to solve the case where the firewall is filtering by protocol rather than port? I'd like to hear how others are dealing with the fallback to RTMPT issue. Thanks, Ryan _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
