I can start the screensharing by clicking the button. Then begins the
download of the screensharing apllication.
Thats all. There is an exeption in the java-log, but only, if port
1935 is closed.
[ERROR] [javawsApplicationMain]
org.red5.screen.webstart.ScreenShareRTMPT - createWindow Exception:
java.lang.NullPointerException
at
org.red5.screen.webstart.gui.VirtualScreen.<init>(VirtualScreen.java:
34) [red5-screenshare.jar:na]
at
org.red5.screen.webstart.ScreenShareRTMPT.createWindow(ScreenShareRTMPT.java:
315) [red5-screenshare.jar:na]
at
org.red5.screen.webstart.ScreenShareRTMPT.main(ScreenShareRTMPT.java:
228) [red5-screenshare.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [na:
1.6.0_19]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [na:
1.6.0_19]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[na:1.6.0_19]
at java.lang.reflect.Method.invoke(Unknown Source) [na:1.6.0_19]
at com.sun.javaws.Launcher.executeApplication(Unknown Source) [na:na]
at com.sun.javaws.Launcher.executeMainClass(Unknown Source) [na:na]
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source) [na:na]
at com.sun.javaws.Launcher.run(Unknown Source) [na:na]
at java.lang.Thread.run(Unknown Source) [na:1.6.0_19]
java.lang.NullPointerException
at
org.red5.screen.webstart.gui.VirtualScreen.<init>(VirtualScreen.java:
34)
at
org.red5.screen.webstart.ScreenShareRTMPT.createWindow(ScreenShareRTMPT.java:
315)
at
org.red5.screen.webstart.ScreenShareRTMPT.main(ScreenShareRTMPT.java:
228)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
On 22 Apr., 15:31, Sebastian Wagner <[email protected]> wrote:
> What do you mean by does not work?
> The Screen sharing should switch to RTMPT (so to port 80 in your case) if
> the user is connected to the application using rtmpt. (In other words
> screensharing should always use the same as audio and video)
>
> As you maybe have seen: Initially the application it will try rtmp 3 times,
> if that fails it switches to rtmpt.
> If you then later start the screen sharing it will use the same settings as
> the main-connection (that is also used to broadcast audio/video).
> If it initially suceeds in connecting via rtmp of course screen sharing will
> also use rtmp.
>
> Sebastian
>
> 2010/4/22 frank <[email protected]>
>
>
>
> > Hi Sebastian,
> > we used these instruction (http://groups.google.com/group/openmeetings-
> > user/msg/f73bd2ada345759d<http://groups.google.com/group/openmeetings-%0Auser/msg/f73bd2ada345759d>)
> > and the follow ports:
>
> > config.xml
> > rtmpport 1935
> > rtmpTunnelport 80
> > httpport 80
>
> > red5.properties
> > rtmp.port=1935
> > rtmpt.port 80
>
> > How i say: audio and video are ok, but screensharing does'n work.
> > Frank
>
> > On 22 Apr., 14:56, Sebastian Wagner <[email protected]> wrote:
> > > Hi Frank,
>
> > > when you change in the red5.properties and config.xml
> > > the ports of rtmp and rtmpt
> > > audio + video and screensharing will use those.
>
> > > Screensharing does automatically use the same ports as audio and video.
>
> > > Sebastian
>
> > > 2010/4/22 frank <[email protected]>
>
> > > > Hi,
> > > > our openmeetings is running on port 80, so we can use it behind a
> > > > firewall. Audio and video are ok.
> > > > Only screensharing is not working (it works, when the firewallport
> > > > 1935 is open). Would it be possible to run screensharing on port 80.
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "OpenMeetings User" group.
> > > > To post to this group, send email to
> > [email protected].
> > > > To unsubscribe from this group, send email to
> > > > [email protected]<openmeetings-user%[email protected]>
> > <openmeetings-user%[email protected]<openmeetings-user%[email protected]>
>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/openmeetings-user?hl=en.
>
> > > --
> > > Sebastian
> > Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://
> >www.laszlo-forum.de
> > > [email protected]
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to
> > [email protected]<openmeetings-user%[email protected]>
> > .
> > > For more options, visit this group athttp://
> > groups.google.com/group/openmeetings-user?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<openmeetings-user%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> Sebastian
> Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://www.laszlo-forum.de
> [email protected]
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group
> athttp://groups.google.com/group/openmeetings-user?hl=en.
--
You received this message because you are subscribed to the Google Groups
"OpenMeetings User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/openmeetings-user?hl=en.
