Hello, We finally get the Red5 release, and everything should work as expected. Can you please check build #95 from here: https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.0.x/
Thanks in advance On Thu, Nov 6, 2014 at 10:35 AM, Maxim Solodovnik <solomax...@gmail.com> wrote: > Thanks > > Red5 team fixed this issue (I also add small patch to it) and currently we > are waiting for the release of red5-client > Here is the thread: > https://groups.google.com/d/topic/red5interest/27QHA62BvHQ/discussion > > On 6 November 2014 04:01, J H <jghsurf...@hotmail.com> wrote: > >> Hi Maxim, >> I reset the IP address for application.base.url configuration value as >> you suggested. Although you probably didn't expect it to make a difference >> with the screen sharing issue, I thought that I had better report what >> happened so we can rule it out as a possible solution. After the IP change, >> screen sharing still doesn't work >> >> Thank you for looking into this problem. If I can do any more testing, >> please let me know >> >> Regards, >> >> ------------------------------ >> Date: Mon, 3 Nov 2014 13:26:57 +0700 >> >> Subject: Re: Screen Sharing Concern >> From: solomax...@gmail.com >> To: user@openmeetings.apache.org >> >> yes, this better to be set to IP/server name available to every user in >> the system >> I'm trying to investigate the issue with screen sharing right now >> >> On 31 October 2014 20:54, J Hobbs <jghsurf...@hotmail.com> wrote: >> >> The value is: http://localhost:5080/openmeetings/ >> >> Does this need to be set to my outside IP address? >> >> Thanks again for your help >> >> ------------------------------ >> Date: Fri, 31 Oct 2014 16:50:05 +0700 >> >> Subject: Re: Screen Sharing Concern >> From: solomax...@gmail.com >> To: user@openmeetings.apache.org >> >> OM GUI >> login as admin >> go to Adminstration->Configuration >> application.base.url >> >> Going to test it on my servers (using latest 3.0.4-SNAPSHOT), what >> version are you using? >> >> On 31 October 2014 04:50, J Hobbs <jghsurf...@hotmail.com> wrote: >> >> Thank you for your suggestions. Here's the answers: >> >> << Could you check public_xx.jnlp what values it contains? (Host, port >> etc.) >> >> The host is correct and the port is 5080 which is open >> >> << Also there should be screensharing.log file on your machine >> >> The log file when screen sharing is attempted from the Internet produces >> this error: >> >> DEBUG 10-18 13:14:58.322 244 o.a.o.s.w.CoreScreenShare [AWT-EventQueue-2] >> - captureScreenStart >> INFO 10-18 13:14:58.322 254 o.r.c.n.r.BaseRTMPClientHandler >> [AWT-EventQueue-2] - rtmpt://##.##.#.##:5080/openmeetings/ >> *ERROR 10-18 13:14:58.612 73 o.a.o.s.w.RTMPTScreenShare [Thread-22] - >> null* >> WARN 10-18 13:15:00.682 281 o.a.o.s.w.g.ScreenSharerFrame >> [AWT-EventQueue-2] - Sharing action is already requested >> DEBUG 10-18 13:17:19.972 345 o.a.o.s.w.CoreScreenShare [AWT-EventQueue-2] >> - ScreenShare stopStream >> DEBUG 10-18 13:17:19.972 630 o.a.o.s.w.g.ScreenSharerFrame >> [AWT-EventQueue-2] - sharingActionRequested=true >> DEBUG 10-18 13:17:19.982 642 o.a.o.s.w.g.ScreenSharerFrame >> [AWT-EventQueue-2] - recordingActionRequested=false >> INFO 10-18 13:17:19.982 505 o.r.c.n.r.BaseRTMPClientHandler >> [AWT-EventQueue-2] - Connection was null >> >> The log file when screen sharing is attempted from within network >> produces no error: >> >> DEBUG 10-31 16:08:53.969 244 o.a.o.s.w.CoreScreenShare [AWT-EventQueue-2] >> - captureScreenStart >> INFO 10-31 16:08:54.054 254 o.r.c.n.r.BaseRTMPClientHandler >> [AWT-EventQueue-2] - rtmp://10.40.2.21:1935/openmeetings/ >> INFO 10-31 16:08:54.534 165 o.s.s.c.ThreadPoolTaskExecutor >> [NioProcessor-2] - Initializing ExecutorService >> INFO 10-31 16:08:55.175 159 o.r.s.n.r.RTMPHandshake [NioProcessor-2] - >> Processing server response for encryption >> INFO 10-31 16:08:55.176 186 o.r.s.n.r.RTMPHandshake [NioProcessor-2] - >> Type 0 digest comparison success >> INFO 10-31 16:08:55.203 251 o.r.s.n.r.RTMPHandshake [NioProcessor-2] - >> server response part 2 validation success, is Flash Player v9 handshake >> DEBUG 10-31 16:08:55.205 50 o.a.o.s.w.RTMPScreenShare [NioProcessor-2] - >> connection opened >> INFO 10-31 16:08:55.582 764 o.r.c.n.r.BaseRTMPClientHandler >> [ThreadPoolTaskExecutor-1] - No service provider / method not found; to >> handle calls >> like onBWCheck, add a service provider >> DEBUG 10-31 16:08:55.669 197 o.a.o.s.w.CoreScreenShare >> [ThreadPoolTaskExecutor-1] - ########## setConnectionAsSharingClient >> DEBUG 10-31 16:08:55.855 630 o.a.o.s.w.g.ScreenSharerFrame >> [ThreadPoolTaskExecutor-1] - sharingActionRequested=false >> DEBUG 10-31 16:08:55.881 658 o.a.o.s.w.CoreScreenShare >> [ThreadPoolTaskExecutor-1] - createPublishStream result stream id: 1; name: >> 7e34bc025dbf37e9ca675d9ff875c2b4 >> DEBUG 10-31 16:08:55.882 661 o.a.o.s.w.CoreScreenShare >> [ThreadPoolTaskExecutor-1] - setup capture thread spinnerWidth = 1600; >> spinnerHeight = >> 900; >> DEBUG 10-31 16:08:55.966 364 o.a.o.s.w.CoreScreenShare >> [ThreadPoolTaskExecutor-1] - onStreamEvent Invoke #0: Service: null Method: >> onStatus Num >> Params: 1 0: {clientid=1, level=status, >> details=7e34bc025dbf37e9ca675d9ff875c2b4, description=, >> code=NetStream.Publish.Start} >> DEBUG 10-31 16:08:55.966 371 o.a.o.s.w.CoreScreenShare >> [ThreadPoolTaskExecutor-1] - onStreamEvent Publish start >> INFO 10-31 16:08:55.967 764 o.r.c.n.r.BaseRTMPClientHandler >> [ThreadPoolTaskExecutor-1] - No service provider / method not found; to >> handle calls >> like onBWCheck, add a service provider >> DEBUG 10-31 16:09:21.460 345 o.a.o.s.w.CoreScreenShare [AWT-EventQueue-2] >> - ScreenShare stopStream >> DEBUG 10-31 16:09:21.461 630 o.a.o.s.w.g.ScreenSharerFrame >> [AWT-EventQueue-2] - sharingActionRequested=false >> DEBUG 10-31 16:09:21.465 642 o.a.o.s.w.g.ScreenSharerFrame >> [AWT-EventQueue-2] - recordingActionRequested=false >> DEBUG 10-31 16:09:21.465 57 o.a.o.s.w.RTMPScreenShare [NioProcessor-2] - >> connection closed >> INFO 10-31 16:09:21.527 203 o.s.s.c.ThreadPoolTaskExecutor >> [AWT-EventQueue-2] - Shutting down ExecutorService >> DEBUG 10-31 16:09:21.534 345 o.a.o.s.w.CoreScreenShare [NioProcessor-2] - >> ScreenShare stopStream >> DEBUG 10-31 16:09:21.534 630 o.a.o.s.w.g.ScreenSharerFrame >> [NioProcessor-2] - sharingActionRequested=false >> DEBUG 10-31 16:09:21.535 642 o.a.o.s.w.g.ScreenSharerFrame >> [NioProcessor-2] - recordingActionRequested=false >> >> << Also please check application.base.url configuration value >> >> I can't find the application.base.url file >> >> >> thanks again for your help >> ------------------------------ >> Date: Fri, 31 Oct 2014 01:24:51 +0700 >> Subject: Re: Screen Sharing Concern >> From: solomax...@gmail.com >> To: user@openmeetings.apache.org >> >> Could you check public_xx.jnlp what values it contains? (Host, port etc.) >> Also there should be screensharing.log file on your machine, maybe it >> contains anything useful. >> Also please check application.base.url configuration value >> >> WBR, Max (from mobile) >> On Oct 30, 2014 11:53 PM, "J Hobbs" <jghsurf...@hotmail.com> wrote: >> >> Hi All, >> I have a screen sharing concern. If I run screen sharing on my private >> network (within the firewall), >> everything works fine and I'm able to share my screen; however, when I >> try and run screen sharing from >> outside my network (from the Internet) the "Start sharing" button (on the >> "Desktop sharer" dialog >> screen) will not work - ie clicking the button does nothing. >> >> This is obviously a port issue so in addition to opening ports 5080 and >> 1935, I opened 843, 5443, >> 8443, 8088, 9999 and 9998 (all the OpenMeetings ports that I could find), >> but screen sharing still will not >> work from the Internet past the "Start sharing" button. >> >> Does anyone have any suggestions on how to fix this? >> >> >> >> >> -- >> WBR >> Maxim aka solomax >> >> >> >> >> -- >> WBR >> Maxim aka solomax >> > > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
