I think to solve this issue we should analyse the case. I have the following configuration: Linux Debian Etch 2.6.18-4-amd64 Java Sun 1.6.0-b105 Apache Tomcat/5.5 Apache 2.2.4 Mod_Jk Red5 0.6.2 stable WAR
The thing is the RTMPT service doesn't listen on the 8088 port as it's set up in the red.properties and classes/red5.properties I don't think it's a problem of the Tomcat container as I saw someone saying here in the discussion since if I run a standalone version a use nmap to scan the ports I get the following: Port 1935 - open/rtmp Port 8088 - open/unknown This shows in the standalone version the RTMPT service is listening on port 8088 and using the port tester I can connect to it localhost:8088 If I run the nmap on a WAR version I get the following: Port 1935 - open/rtmp Port 8088 - closed/unknown This shows the RTMP service is listening on the 1935 port regardless the Tomcat container in which it runs listens on port 8080 and 8009(jk_mod), so I guess it should be the same for the RTMPT service listening on 8088, then when we solve why it's not working on this port we can go on with the Mod_jk redirection(I've got this working for Apache2/Tomcat). I see Lenny and Joachim are the only people that got the RTMPT working in the WAR version. I've read this mailing list and tutorials on the net and Red5 wiki, done test, but this is the point where I got, I can redirect trafic to port 80 to the Tomcat, but since the RTMPT service is just not listening on its port I'm not getting any further with setting up the RTMPT :(. Any help largely appreciated Thanks David Engelmaier _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
