[
https://issues.apache.org/jira/browse/OPENMEETINGS-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238627#comment-15238627
]
Manohar Kotapati commented on OPENMEETINGS-1358:
------------------------------------------------
Thank you for your help, Maxim.
I changed the keystore name as keystore.screen and now I am able to open the
screen sharing window.
But the sharing is not happening on click of screen share button.
I observed the screenshare.log file and I suspect the problem is with the URL
which is connecting as rtmp instead of rtmps
*(rtmp://openpractice.cs.ttu.edu:5443/openmeetings/4)*
------------------------------------------------------------------------------------------------
DEBUG 04-12 22:36:17.024 170 o.a.o.s.w.CoreScreenShare [javawsApplicationMain]
- host: openpractice.cs.ttu.edu, app: 5443, port: openmeetings/4, publish:
a86654b2673aaf48950620ff449245a5
DEBUG 04-12 22:36:17.354 196 o.a.o.s.w.CoreScreenShare [javawsApplicationMain]
- initialized
DEBUG 04-12 22:36:19.557 288 o.a.o.s.w.CoreScreenShare [AWT-EventQueue-2] -
captureScreenStart
INFO 04-12 22:36:19.561 254 o.r.c.n.r.BaseRTMPClientHandler [AWT-EventQueue-2]
- *rtmp://openpractice.cs.ttu.edu:5443/openmeetings/4*
INFO 04-12 22:36:19.818 165 o.s.s.c.ThreadPoolTaskExecutor [NioProcessor-2] -
Initializing ExecutorService
DEBUG 04-12 22:36:20.145 62 o.a.o.s.w.RTMPSScreenShare [NioProcessor-2] -
connection closed
DEBUG 04-12 22:36:20.149 62 o.a.o.s.w.RTMPSScreenShare [NioProcessor-2] -
connection closed
DEBUG 04-12 22:36:20.156 391 o.a.o.s.w.CoreScreenShare [NioProcessor-2] -
ScreenShare stopStream
-------------------------------------------------------------------------------------------------
Is that the reason for screen share failure?
If yes, am I missing any setup to make that connecting URL as rtmps? Or is it
hard coded one?
I am attaching the original screensharing.log file to this issue. Please check
it once.
Many Thanks,
Manohar
> RTMPS SSHHandshakeFailed error in 3.0.7 and working fine with 3.0.4
> --------------------------------------------------------------------
>
> Key: OPENMEETINGS-1358
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1358
> Project: Openmeetings
> Issue Type: Bug
> Components: HTML5/Room
> Affects Versions: 3.0.7
> Environment: OS: Windows
> Issue replicated in OpenMeetings 3.0.7
> Working fine with OpenMeetings 3.0.4
> Reporter: Manohar Kotapati
> Assignee: Maxim Solodovnik
> Priority: Blocker
> Labels: easyfix, patch
> Fix For: 3.1.2
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I am working with Openmeetings 3.0.7. I fallowed all the steps mentioned in
> the http://openmeetings.apache.org/RTMPSAndHTTPS.html for for RTMPS, HTTPS
> configuration.
> And the certificates are also signed by valid CA. While entering the room and
> at the time of network testing, the rtmps connection is not establishing with
> port 8443. And in the log the status is as follows.
> ------------------------------------------------------------------------
> Port: : start test...
> rtmps://openpractice.cs.ttu.edu:8443/speechtherapy/hibernate
> *** debug ***
> devRtmpConnection/registerMethods()
> devrtmpconnection «<rtmpConnection>#0| /@testsView/@portTest/@rtmp» _onStatus
> NetConnection.Connect.SSLHandshakeFailed
> Port: RTMP connect status - NetConnection.Connect.SSLHandshakeFailed
> Port: connection error - null
> ----------------------------------------------------------------
> It is working fine in OpenMeetings 3.0.4 with the same configurations and
> keystores.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
