Why would you add the rtmpt in the connection string? When it works right, RTMPT should be transparent. If a client can't connect using rtmp, it tries rtmpt on port 80. This works perfectly under the jetty install as long as you leave the default http port on 5080 and change the rtmpt port to 80 in the red5.properties file.
Bill vlad wrote: > On 5/23/07, *Interalab* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > No. I've never been able to get it to work. I remember seeing the > section you talk about in jetty, so I'll copy it and see if I can help > get rtmpt to work. > > > Thank you! it is worth trying it, of course, but.. > > My initial question was how to listen to RTMPT commands _without_ that > embedded tomcat on a different port. > I saw that servlet-mapping in the .war's web.xml with "/rtmp" that > basically says > > <servlet> > <servlet-name>rtmpt</servlet-name> > <servlet-class> > org.red5.server.net.rtmpt.RTMPTServlet > </servlet-class> > <load-on-startup>2</load-on-startup> > </servlet> > <servlet-mapping> > <servlet-name>rtmpt</servlet-name> > <url-pattern>/rtmpt</url-pattern> > </servlet-mapping> > > Does this work? how can I use it, if URLs like > "rtmpt://localhost:8080/red5/rtmpt/ApplicationName" > fail because of the implied "application name" as the first token > after :8080/ ? > > Thank you for your patience, > Vlad > ------------------------------------------------------------------------ > > _______________________________________________ > 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
