Hello Sebastian, RTMPT configuration was changed according to the Paul's comments: [1] Since then there is no need in additional port for RTMPT (OM HTTP port is always used, and can be redirected via Apache or changed to be 80 in red5.properties)
RTMP client is broken in red5: [2] RTMPT is working if started from the debugger (with the Exceptions you have described, already reported to Paul) The issue I ask you to take a look at is: In case user enters the room using RTMPT *.jnlp file is failed to be created since room_id == null [1] https://groups.google.com/d/topic/red5interest/14I7Ya2WjgQ/discussion [2] https://groups.google.com/d/topic/red5interest/2_JuBOY8WhU/discussion On Thu, Aug 1, 2013 at 2:34 PM, [email protected] <[email protected] > wrote: > I can see in the source code that the RTMPT port is no more configurable. > Actually setting rtmpt to port 443 was a common way to solve 99% of all > Firewall issues. > How would you do that now? You have to set the http port to 443 ? > > And I don't know how stable the RTMPT Servlet is. There have been issue > with it in the past. > What was the reason for that change ? > > And screenharing over RTMPT does not work for me at all. Same as RTMP.But > the behaviour is slightly different. > RTMP version throws handshake error. > > RTMPT does not but it has other exceptions. In the console of the RTMPT > JavaWebStart application you can find lots of exceptions throws like this: > > ERROR 08-01 19:28:26.894 RTMPProtocolEncoder.java 34725 111 > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder [Thread-19] - Error > encoding > java.lang.NullPointerException: null > at > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder.dropMessage(RTMPProtocolEncoder.java:225) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder.encodePacket(RTMPProtocolEncoder.java:133) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder.encode(RTMPProtocolEncoder.java:109) > ~[red5-server.jar:na] > at > org.red5.client.net.rtmpt.BaseRTMPTConnection.write(BaseRTMPTConnection.java:240) > ~[red5-client-1.0.2-RC1.jar:1.0.2-RC1] > at org.red5.server.net.rtmp.Channel.write(Channel.java:138) > ~[red5-server.jar:na] > at org.red5.server.net.rtmp.Channel.write(Channel.java:107) > ~[red5-server.jar:na] > at > org.red5.server.stream.consumer.ConnectionConsumer.pushMessage(ConnectionConsumer.java:183) > ~[red5-server.jar:na] > at > org.red5.client.net.rtmp.BaseRTMPClientHandler.publishStreamData(BaseRTMPClientHandler.java:565) > ~[red5-client-1.0.2-RC1.jar:1.0.2-RC1] > at > org.apache.openmeetings.screen.webstart.CaptureScreen.pushVideo(CaptureScreen.java:130) > ~[openmeetings-screenshare-3.0.0-SNAPSHOT.jar:na] > at > org.apache.openmeetings.screen.webstart.CaptureScreen.run(CaptureScreen.java:87) > ~[openmeetings-screenshare-3.0.0-SNAPSHOT.jar:na] > ERROR 08-01 19:28:29.412 RTMPProtocolEncoder.java 37243 111 > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder [Thread-19] - Error > encoding > java.lang.NullPointerException: null > at > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder.encodeCommand(RTMPProtocolEncoder.java:763) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmpt.codec.RTMPTProtocolEncoder.encodeCommand(RTMPTProtocolEncoder.java:49) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder.encodeCommand(RTMPProtocolEncoder.java:731) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder.encodeInvoke(RTMPProtocolEncoder.java:719) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder.encodeMessage(RTMPProtocolEncoder.java:499) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder.encodePacket(RTMPProtocolEncoder.java:134) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.codec.RTMPProtocolEncoder.encode(RTMPProtocolEncoder.java:109) > ~[red5-server.jar:na] > at > org.red5.client.net.rtmpt.BaseRTMPTConnection.write(BaseRTMPTConnection.java:240) > ~[red5-client-1.0.2-RC1.jar:1.0.2-RC1] > at org.red5.server.net.rtmp.Channel.write(Channel.java:138) > ~[red5-server.jar:na] > at org.red5.server.net.rtmp.Channel.write(Channel.java:107) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.RTMPConnection.invoke(RTMPConnection.java:953) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.RTMPConnection.invoke(RTMPConnection.java:922) > ~[red5-server.jar:na] > at > org.red5.server.net.rtmp.RTMPConnection.invoke(RTMPConnection.java:977) > ~[red5-server.jar:na] > at > org.red5.client.net.rtmp.BaseRTMPClientHandler.invoke(BaseRTMPClientHandler.java:487) > ~[red5-client-1.0.2-RC1.jar:1.0.2-RC1] > at > org.apache.openmeetings.screen.webstart.CoreScreenShare.sendCursorStatus(CoreScreenShare.java:178) > ~[openmeetings-screenshare-3.0.0-SNAPSHOT.jar:na] > at > org.apache.openmeetings.screen.webstart.CaptureScreen.run(CaptureScreen.java:94) > ~[openmeetings-screenshare-3.0.0-SNAPSHOT.jar:na] > > > > > > 2013/8/1 Maxim Solodovnik <[email protected]> > >> Hello Sebastian, >> >> I'm currently trying to test RTMPT screensharing (the only one working >> right now somehow) and found weird issue: If client trying to start >> screensharing and is connected via RTMPT he/she has room_id == null in >> Client. >> >> if RTMP is used room_id is set to the proper value. >> The behavior above is observed in both: "SWF login then open the room" >> and "Wicket enter the room". >> >> Can you please take a look at this issue? >> Thanks in advance! >> >> >> -- >> WBR >> Maxim aka solomax >> > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected] > -- WBR Maxim aka solomax
