screensharing at port 80
153 views
Skip to first unread message
frank
Apr 22, 2010, 8:51:02 AM4/22/10
to OpenMeetings User
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 openmeet...@googlegroups.com.
To unsubscribe from this group, send email to openmeetings-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
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 openmeet...@googlegroups.com.
To unsubscribe from this group, send email to openmeetings-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
Sebastian Wagner
Apr 22, 2010, 8:56:24 AM4/22/10
to openmeet...@googlegroups.com
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
--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
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 <frank.ei...@lisum.berlin-brandenburg.de>
--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
frank
Apr 22, 2010, 9:25:14 AM4/22/10
to OpenMeetings User
Hi Sebastian,
we used these instruction (http://groups.google.com/group/openmeetings-
user/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 <seba.wag...@gmail.com> 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 <frank.eichelb...@lisum.berlin-brandenburg.de>
> > .
we used these instruction (http://groups.google.com/group/openmeetings-
user/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 <seba.wag...@gmail.com> 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
>
>
>
>
> > 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 openmeet...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > openmeetings-u...@googlegroups.com<openmeetings-user%2Bunsu...@googlegroups.com>
>
>
> > 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 openmeet...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
> > 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
> seba.wag...@gmail.com
> >http://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> Sebastian Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://www.laszlo-forum.de
Sebastian Wagner
Apr 22, 2010, 9:31:30 AM4/22/10
to openmeet...@googlegroups.com
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
--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
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 <frank.ei...@lisum.berlin-brandenburg.de>
--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
frank
Apr 22, 2010, 9:55:23 AM4/22/10
to OpenMeetings User
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 <seba.wag...@gmail.com> 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 <frank.eichelb...@lisum.berlin-brandenburg.de>
> > user/msg/f73bd2ada345759d<http://groups.google.com/group/openmeetings-%0Auser/msg/f73bd2ada345759d>)
> > <openmeetings-user%2Bunsu...@googlegroups.com<openmeetings-user%252Buns...@googlegroups.com>
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 <seba.wag...@gmail.com> 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
>
> > user/msg/f73bd2ada345759d<http://groups.google.com/group/openmeetings-%0Auser/msg/f73bd2ada345759d>)
frank
Apr 27, 2010, 4:50:18 AM4/27/10
to OpenMeetings User
Hi Sebastian,
after many test with different ports for rtmp, rtmpt and http, i can
say it is not a port-problem.
If i use rtmp audio, video and screen-sharing are working.
But when i try it with rtmpt, only audio and video are working. I
think there is a failure in the screen-sharing application. The switch
to rtmpt is faulty.
Frank
On 22 Apr., 15:55, frank <frank.eichelb...@lisum.berlin-
> > Sebastian Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://...
after many test with different ports for rtmp, rtmpt and http, i can
say it is not a port-problem.
If i use rtmp audio, video and screen-sharing are working.
But when i try it with rtmpt, only audio and video are working. I
think there is a failure in the screen-sharing application. The switch
to rtmpt is faulty.
Frank
On 22 Apr., 15:55, frank <frank.eichelb...@lisum.berlin-
Sebastian Wagner
May 8, 2010, 9:06:42 AM5/8/10
to OpenMeetings User
Hi,
check with this revision:
http://code.google.com/p/openmeetings/source/detail?r=3242
Sebastina
On 27 Apr., 10:50, frank <frank.eichelb...@lisum.berlin-
brandenburg.de> wrote:
> Hi Sebastian,
>
> after many test with different ports for rtmp,rtmptand http, i can
> > > The Screen sharing should switch toRTMPT(so to port 80 in your case) if
> > > the user is connected to the application usingrtmpt. (In other words
> > > > > > openmeetings-u...@googlegroups.com<openmeetings-user%2Bunsubscr i...@googlegroups.com>
> > > > <openmeetings-user%2Bunsu...@googlegroups.com<openmeetings-user%252Buns ubsc...@googlegroups.com>
check with this revision:
http://code.google.com/p/openmeetings/source/detail?r=3242
Sebastina
On 27 Apr., 10:50, frank <frank.eichelb...@lisum.berlin-
brandenburg.de> wrote:
> Hi Sebastian,
>
> after many test with different ports for rtmp,rtmptand http, i can
> say it is not a port-problem.
> If i use rtmp audio, video and screen-sharing are working.
> But when i try it withrtmpt, only audio and video are working. I
> If i use rtmp audio, video and screen-sharing are working.
> think there is a failure in the screen-sharing application. The switch
> tortmptis faulty.
> > > the user is connected to the application usingrtmpt. (In other words
> > > > <openmeetings-user%2Bunsu...@googlegroups.com<openmeetings-user%252Buns ubsc...@googlegroups.com>
>
> > > > > > .
> > > > > > 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
> > > > > seba.wag...@gmail.com
>
> > > > > --
> > > > > You received this message because you are subscribed to the Google Groups
> > > > "OpenMeetings User" group.
> > > > > To post to this group, send email to openmeet...@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > > > openmeetings-u...@googlegroups.com<openmeetings-user%2Bunsubscr i...@googlegroups.com>
> > > > > > .
> > > > > > 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
> > > > > seba.wag...@gmail.com
>
> > > > > --
> > > > > You received this message because you are subscribed to the Google Groups
> > > > "OpenMeetings User" group.
> > > > > To post to this group, send email to openmeet...@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > > > .
> > > > > 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 openmeet...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > openmeetings-u...@googlegroups.com<openmeetings-user%2Bunsubscr i...@googlegroups.com>
> > > > > 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 openmeet...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
frank
May 10, 2010, 5:28:47 AM5/10/10
to OpenMeetings User
Hi Sebastian,
thanks, for your work. The screensharing from outside the firewall to
the computers behind the firewall works fine.
Over the rtmpt-connection i can starting the screensharing and i can
download the application and now <thats new> starts the screensharing-
window.
But thats all. Nothing happens, when i klick the the start- or the
record-button. (no entry in the logs)
The last lines:
2010-05-10 11:22:46,159 [TP-Processor35] INFO o.a.c.c.C.[.[.0.0.0.[/
openmeetings] - Velocity [info] VelocityViewServlet: Default
content-type is: text/html; charset=UTF-8
2010-05-10 11:22:46,234 [TP-Processor35] INFO o.a.c.c.C.[.[.0.0.0.[/
openmeetings] - Velocity [debug] ResourceManager : found
screenshare.vm with loader
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
Frank
thanks, for your work. The screensharing from outside the firewall to
the computers behind the firewall works fine.
Over the rtmpt-connection i can starting the screensharing and i can
download the application and now <thats new> starts the screensharing-
window.
But thats all. Nothing happens, when i klick the the start- or the
record-button. (no entry in the logs)
The last lines:
2010-05-10 11:22:46,159 [TP-Processor35] INFO o.a.c.c.C.[.[.0.0.0.[/
openmeetings] - Velocity [info] VelocityViewServlet: Default
content-type is: text/html; charset=UTF-8
2010-05-10 11:22:46,234 [TP-Processor35] INFO o.a.c.c.C.[.[.0.0.0.[/
openmeetings] - Velocity [debug] ResourceManager : found
screenshare.vm with loader
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
Frank
Sebastian Wagner
May 10, 2010, 5:34:20 AM5/10/10
to openmeet...@googlegroups.com
you do not test by sending the screensharing to yourself back again no?
You have to login with two users, sharing back to yourself is disabled.
Sebastian
2010/5/10 frank <frank.ei...@lisum.berlin-brandenburg.de>:
You have to login with two users, sharing back to yourself is disabled.
Sebastian
2010/5/10 frank <frank.ei...@lisum.berlin-brandenburg.de>:
--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
frank
May 10, 2010, 6:06:39 AM5/10/10
to OpenMeetings User
I test the screensharing with 2 computers as 2 different users in
differrent networks.
Now i see, there is an error-entry in the client-java-log:
[DEBUG] [AWT-EventQueue-0] org.red5.screen.webstart.ScreenShareRTMPT -
ScreenShare startStream
[DEBUG] [AWT-EventQueue-0]
org.red5.server.net.rtmp.BaseRTMPClientHandler - connect server:
onlife3.brandenburg.de port 80 application openmeetings/4
connectCallback org.red5.screen.webstart.ScreenShareRTMPT@eb7331
[DEBUG] [AWT-EventQueue-0]
org.red5.server.net.rtmp.BaseRTMPClientHandler - connect server:
onlife3.brandenburg.de port 80 connectionParams {objectEncoding=0,
app=openmeetings/4, flashVer=WIN 9,0,115,0, fpad=false, tcUrl=rtmpt://
onlife3.brandenburg.de:80/openmeetings/4, audioCodecs=1639,
videoFunction=1, pageUrl=null, path=openmeetings/4, capabilities=15,
swfUrl=null, videoCodecs=252} connectCallback
org.red5.screen.webstart.ScreenShareRTMPT@eb7331 conectCallArguments
null
[ERROR] [Thread-14] org.red5.screen.webstart.ScreenShareRTMPT - null
null
Frank
On 10 Mai, 11:34, Sebastian Wagner <seba.wag...@gmail.com> wrote:
> you do not test by sending the screensharing to yourself back again no?
> You have to login with two users, sharing back to yourself is disabled.
>
> Sebastian
>
> 2010/5/10 frank <frank.eichelb...@lisum.berlin-brandenburg.de>:
> ...
>
> Erfahren Sie mehr »
differrent networks.
Now i see, there is an error-entry in the client-java-log:
[DEBUG] [AWT-EventQueue-0] org.red5.screen.webstart.ScreenShareRTMPT -
ScreenShare startStream
[DEBUG] [AWT-EventQueue-0]
org.red5.server.net.rtmp.BaseRTMPClientHandler - connect server:
onlife3.brandenburg.de port 80 application openmeetings/4
connectCallback org.red5.screen.webstart.ScreenShareRTMPT@eb7331
[DEBUG] [AWT-EventQueue-0]
org.red5.server.net.rtmp.BaseRTMPClientHandler - connect server:
onlife3.brandenburg.de port 80 connectionParams {objectEncoding=0,
app=openmeetings/4, flashVer=WIN 9,0,115,0, fpad=false, tcUrl=rtmpt://
onlife3.brandenburg.de:80/openmeetings/4, audioCodecs=1639,
videoFunction=1, pageUrl=null, path=openmeetings/4, capabilities=15,
swfUrl=null, videoCodecs=252} connectCallback
org.red5.screen.webstart.ScreenShareRTMPT@eb7331 conectCallArguments
null
[ERROR] [Thread-14] org.red5.screen.webstart.ScreenShareRTMPT - null
null
Frank
On 10 Mai, 11:34, Sebastian Wagner <seba.wag...@gmail.com> wrote:
> you do not test by sending the screensharing to yourself back again no?
> You have to login with two users, sharing back to yourself is disabled.
>
> Sebastian
>
>
> Erfahren Sie mehr »
Sebastian Wagner
May 10, 2010, 7:20:29 AM5/10/10
to openmeet...@googlegroups.com
Hi Frank,
I have tested with rtmpt running on port 8088 with two machines and it
went well.
[ERROR] [Thread-14] org.red5.screen.webstart.ScreenShareRTMPT - null null
=> is there any message after that?
Sebastian
2010/5/10 frank <frank.ei...@lisum.berlin-brandenburg.de>:
I have tested with rtmpt running on port 8088 with two machines and it
went well.
[ERROR] [Thread-14] org.red5.screen.webstart.ScreenShareRTMPT - null null
Sebastian
2010/5/10 frank <frank.ei...@lisum.berlin-brandenburg.de>:
--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
frank
May 10, 2010, 8:08:19 AM5/10/10
to OpenMeetings User
Hi,
in the javaws.trace-log is no more message after that.
Here is the end of the jawaws.log:
<record>
<date>2010-05-10T13:41:59</date>
<millis>1273491719406</millis>
<sequence>26</sequence>
<logger>com.sun.deploy</logger>
<level>FINE</level>
<class>com.sun.deploy.util.LoggerTraceListener</class>
<method>print</method>
<thread>10</thread>
<message>[DEBUG] [AWT-EventQueue-0]
null
</message>
</record>
<record>
<date>2010-05-10T13:41:59</date>
<millis>1273491719500</millis>
<sequence>27</sequence>
<logger>com.sun.deploy</logger>
<level>FINE</level>
<class>com.sun.deploy.util.LoggerTraceListener</class>
<method>print</method>
<thread>10</thread>
<message>[ERROR] [Thread-12]
org.red5.screen.webstart.ScreenShareRTMPT - null
</message>
</record>
<record>
<date>2010-05-10T13:41:59</date>
<millis>1273491719500</millis>
<sequence>28</sequence>
<logger>com.sun.deploy</logger>
<level>FINE</level>
<class>com.sun.deploy.util.LoggerTraceListener</class>
<method>print</method>
<thread>10</thread>
<message>null
</message>
</record>
On port 80 with rtmpt it dosn't work.
Frank
in the javaws.trace-log is no more message after that.
Here is the end of the jawaws.log:
<record>
<date>2010-05-10T13:41:59</date>
<millis>1273491719406</millis>
<sequence>26</sequence>
<logger>com.sun.deploy</logger>
<level>FINE</level>
<class>com.sun.deploy.util.LoggerTraceListener</class>
<method>print</method>
<thread>10</thread>
<message>[DEBUG] [AWT-EventQueue-0]
org.red5.server.net.rtmp.BaseRTMPClientHandler - connect server:
onlife3.brandenburg.de port 80 connectionParams {objectEncoding=0,
app=openmeetings/4, flashVer=WIN 9,0,115,0, fpad=false, tcUrl=rtmpt://
onlife3.brandenburg.de:80/openmeetings/4, audioCodecs=1639,
videoFunction=1, pageUrl=null, path=openmeetings/4, capabilities=15,
swfUrl=null, videoCodecs=252} connectCallback
org.red5.screen.webstart.ScreenShareRTMPT@bf7916 conectCallArguments
onlife3.brandenburg.de port 80 connectionParams {objectEncoding=0,
app=openmeetings/4, flashVer=WIN 9,0,115,0, fpad=false, tcUrl=rtmpt://
onlife3.brandenburg.de:80/openmeetings/4, audioCodecs=1639,
videoFunction=1, pageUrl=null, path=openmeetings/4, capabilities=15,
swfUrl=null, videoCodecs=252} connectCallback
null
</message>
</record>
<record>
<date>2010-05-10T13:41:59</date>
<millis>1273491719500</millis>
<sequence>27</sequence>
<logger>com.sun.deploy</logger>
<level>FINE</level>
<class>com.sun.deploy.util.LoggerTraceListener</class>
<method>print</method>
<thread>10</thread>
<message>[ERROR] [Thread-12]
org.red5.screen.webstart.ScreenShareRTMPT - null
</message>
</record>
<record>
<date>2010-05-10T13:41:59</date>
<millis>1273491719500</millis>
<sequence>28</sequence>
<logger>com.sun.deploy</logger>
<level>FINE</level>
<class>com.sun.deploy.util.LoggerTraceListener</class>
<method>print</method>
<thread>10</thread>
<message>null
</message>
</record>
On port 80 with rtmpt it dosn't work.
Frank
> I have tested with rtmpt running on port 8088 with two machines and it
> went well.
>
> [ERROR] [Thread-14] org.red5.screen.webstart.ScreenShareRTMPT - null null
> => is there any message after that?
>
> Sebastian
>
> 2010/5/10 frank <frank.eichelb...@lisum.berlin-brandenburg.de>:
> went well.
>
> [ERROR] [Thread-14] org.red5.screen.webstart.ScreenShareRTMPT - null null
> => is there any message after that?
>
> Sebastian
>
Sebastian Wagner
May 10, 2010, 8:28:25 AM5/10/10
to openmeet...@googlegroups.com
You have correctly configured client + server to use rtmpt ?
Your Flash client that runs the screensharing is connected
via rtmpt?
Sebastian
2010/5/10 frank <frank.ei...@lisum.berlin-brandenburg.de>:
Your Flash client that runs the screensharing is connected
via rtmpt?
Sebastian
2010/5/10 frank <frank.ei...@lisum.berlin-brandenburg.de>:
--
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
seba....@gmail.com
frank
May 11, 2010, 3:38:11 AM5/11/10
to OpenMeetings User
Hi Sebastian,
i have tested the same configuration on an testserver. Only port 80
were open. All works fine.
But my productive -server ist behind a firewall that blocked ports and
the rtmp-protocoll. There the screensharing is not working. I think it
is a problem with the rtmp-protocoll, but where?
Best regards Frank
On 10 Mai, 14:28, Sebastian Wagner <seba.wag...@gmail.com> wrote:
> You have correctly configured client + server to use rtmpt ?
> Your Flash client that runs the screensharing is connected
> via rtmpt?
>
> Sebastian
>
> 2010/5/10 frank <frank.eichelb...@lisum.berlin-brandenburg.de>:
i have tested the same configuration on an testserver. Only port 80
were open. All works fine.
But my productive -server ist behind a firewall that blocked ports and
the rtmp-protocoll. There the screensharing is not working. I think it
is a problem with the rtmp-protocoll, but where?
Best regards Frank
On 10 Mai, 14:28, Sebastian Wagner <seba.wag...@gmail.com> wrote:
> You have correctly configured client + server to use rtmpt ?
> Your Flash client that runs the screensharing is connected
> via rtmpt?
>
> Sebastian
>
Reply all
Reply to author
Forward
0 new messages