Hi Sebastian,

I thought that's what I had set up. I did change the source code and recompile. 
And looking at http://gregoire.org/2009/11/12/native-rtmps-in-red5/, that's 
pretty much what I did. Maybe a clarification is needed as to what the 
difference between RTMPS and native SSL is - I thought they were the same 
thing... even Nexus talks about "native RTMPS" in his mailing list posts from 
last year...

Holger

[cid:[email protected]]

, Oktober 2011 15:37
To: [email protected]
Subject: Re: [openmeetings-user] Re: RTMPS

Hallo Holger,

as Nexus did explain, he was using NATIVE SSL not RTMPS.
Also it does require to change source code and recompile that client.

Our guide will be quite similar to what Nexus has done.


Sebastian
2011/10/10 Holger Rabbach (ICT) 
<[email protected]<mailto:[email protected]>>
PS: I also tried running red5 RTMPS on port 443 instead of 8443, just to be 
sure that's not the problem...




-----Original Message-----
From: 
[email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>]
 On Behalf Of Holger Rabbach (ICT)
Sent: Montag, 10. Oktober 2011 15<tel:2011%2015>:18
To: 
[email protected]<mailto:[email protected]>
Subject: RE: [openmeetings-user] Re: RTMPS

Thanks, but that doesn't seem to work - I added the line, built a new 
distribution, installed it, ran the installer, then tried to connect from the 
client - doesn't even try port 8443. Emptied the browser cache as well, to be 
sure the old app isn't cached. Maybe this doesn't work anymore in 1.8.4?

Holger


-----Original Message-----
From: 
[email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>]
 On Behalf Of nexus
Sent: Samstag, 8. Oktober 2011 02<tel:2011%2002>:01
To: OpenMeetings User
Subject: [openmeetings-user] Re: RTMPS

[...]

I did a lot of work a while back using RTMPS with Openmeetings and it works 
well. Sounds like you have the Red5 side set up. In order to get native SSL 
RTMPS to work with Openmeetings you have to checkout and download the source 
and add the following bit of code to the following
file: WebContent\openmeetings\base\remote\rtmpConnection.lzx

          this._nc = new NetConnection();

           // local reference to rtmpconnection
           this._nc.t = this;

           this._nc.proxyType = "best";    --This is the line that
you have to add

After you add this line and build the app using the instructions on the build 
page, RTMPS will work.

In short, this line is necessary to tell the Flash player to try native SSL 
first before trying to go through other methods.

I have successfully used native SSL RTMPS using openmeetings with Windows, Mac, 
and Linux clients. It sounds like you have your keystore set up so this should 
be all you need.

I have been able to use the screensharer while using RTMPS but had to hard code 
the port in the source to use my RTMP port. So the screensharer has not been 
encrypted. I have recently been trying to build an RTMPS screensharer but have 
not been sucessful yet. I am looking forward to the guide mentioned as this 
should help with this quite a bit. I hope this is helpful.

--
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]<mailto:[email protected]>.
To unsubscribe from this group, send email to 
[email protected]<mailto:openmeetings-user%[email protected]>.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.


 OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3 
0JG - United Kingdom
 Charity reg no: 1112655 - Company reg no: 5649412<tel:5649412> (England and 
Wales)

--
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]<mailto:[email protected]>.
To unsubscribe from this group, send email to 
[email protected]<mailto:openmeetings-user%[email protected]>.
For more options, visit this group at 
http://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]<mailto:[email protected]>.
To unsubscribe from this group, send email to 
[email protected]<mailto:openmeetings-user%[email protected]>.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.



--
Sebastian Wagner
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
[email protected]<mailto:[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]<mailto:[email protected]>.
To unsubscribe from this group, send email to 
[email protected]<mailto:[email protected]>.
For more options, visit this group at 
http://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.

<<inline: image001.jpg>>

Reply via email to