Do you want to use rtmps as fallback method of rtmp ?
That is not what we currently support.

We support rtmp + rtmpt as fallback
or
rtmps

So if you set useSSL to true it will first try on using rtmps connection.
Maybe if rtmps fails it might try rtmpt however rtmps should work

Your changes in hibRtmpConnection are not neccessary or have no effect actually.

Sebastian

2012/4/27 [email protected] <[email protected]>:
> Why do you change source code to set up rtmps ?
>
> 2012/4/27 Maxim Solodovnik <[email protected]>:
>> I set "restrictive" firewall on Ubuntu: all ports except for 22, 80 and 443
>> are closed
>> I set up apache to redirect all calls to ports 80 and 443 to appropriate OM
>> ports
>> I have modified config.xml and set
>>    <rtmpTunnelport>443</rtmpTunnelport> (to send all rtmpts traffic to
>> apache2 SSL port)
>>    <useSSL>yes</useSSL>
>>    <proxyType>best</proxyType>
>>
>> Modify hibRtmpConnection.lzx (under WebContent/src folder)
>> --- base/hibernate/hibRtmpConnection.lzx        (revision 1331341)
>> +++ base/hibernate/hibRtmpConnection.lzx        (working copy)
>> @@ -170,7 +170,7 @@
>>                  this.counterror=0;
>>                  this.connect();
>>              } else {
>> -                this.setAttribute('protocollName','rtmpt');
>> +                this.setAttribute('protocollName', canvas.useSSL ? 'rtmpts'
>> : 'rtmpt');
>>                  this.setAttribute('protocollPort',canvas.rtmpTunnelport);
>>                  var src = getUrl();
>>                  this.setAttribute('src',src);
>>
>> recompile and run
>>
>> according to the apache logs there were no request made to the 443 port.
>>
>> Everything work as expected in case I set up all parameters to use port 80
>> and "rtmpt"
>>
>>
>> On Fri, Apr 27, 2012 at 17:30, [email protected] <[email protected]>
>> wrote:
>>>
>>> Yes it should work.
>>> I think Stephen has tested this on his local machine too. There is no
>>> different between 1.9.x and 2.0 version regarding RTMP over native
>>> SSL.
>>>
>>> *set protocol to be "rtmpts" if useSSL is true and connection via
>>> rtmps is failed*
>>> => failed ?! What has failed to do with it?
>>>
>>> Edit red5/webapps/openmeetings/config.xml and set
>>> <rtmpsslport>5443</rtmpsslport> , <useSSL>yes</useSSL> and
>>> <proxyType>best</proxyType>
>>>
>>> proxyType to "best" is what makes the RTMPS connection use "native
>>> SSL" and NOT the old RTMPS implementation (which would be RTMP HTTP
>>> Tunneling over SSL)
>>>
>>> Sebastian
>>>
>>> 2012/4/27 Maxim Solodovnik <[email protected]>:
>>> > Hello Sebastian,
>>> >
>>> > I'm currently testing tunneling in OM (to set everything up on port 80
>>> > only)
>>> > while this testing I did the following:
>>> > set protocol to be "rtmpts" if useSSL is true and connection via
>>> > rtmps is
>>> > failed
>>> >
>>> > but unfortunately there seems to be no packets sent (according to the
>>> > apache2 logs)
>>> >
>>> > Do you know is rtmpts should work as expected in OM?
>>> >
>>> > --
>>> > WBR
>>> > Maxim aka solomax
>>>
>>>
>>>
>>> --
>>> Sebastian Wagner
>>> https://twitter.com/#!/dead_lock
>>> http://www.openmeetings.de
>>> http://www.webbase-design.de
>>> http://www.wagner-sebastian.com
>>> [email protected]
>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.openmeetings.de
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> [email protected]



-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
[email protected]

Reply via email to