Note about my confusing way of using the word "fallback": We do NOT use the auto-fallback that the NetConnection has build in.
So whenever I use the word "fallback", what I mean is: 1) If an event _different_ from "NetConnection.Connect.Success" the rtmpConnection was detected, the lzx class rtmpConnection throws an "onerror" event 2) I have an handler defined in hibRtmpConnection that catches the "onerror" event, counts the number of times connected and reconnects (Line 170) What Adobe Documentation ( http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/NetConnection.html) means by "fallback" is that you can set in the NetConnection ActionScript object a fallback method to switch automatically the protocol. We don't do this, we programmatically catch errors and implement our own "fallback" Sebastian 2012/4/27 [email protected] <[email protected]> > No there is not rtmpts > There are two different rtmps implementations in the Flash Player, > RTMP HTTP Tunneling over SSL > RTMP over native SSL. > Both implementations have the connection string "rtmps". > To switch between those you set proxyType=best to use "native SSL" > > RTMP HTTP Tunneling over SSL > => We do not provide configuration docs for that, it is not recommended to > use it at all. It is buggy and not supported on MacOSX and Linux (at least > in the past). > RTMP over native SSL works on those devices (I personally could verify at > least OSX with rtmp over native SSL successfully) > > So the three possible connection ways are: > rtmp, rtmpt, rtmps(with proxyType=best) > > RTMP will fallback to rtmpt if failed. > RTMPS has no fallback defined (at least I never tested that) > > To check if the various profiles do work the easiest thing is to modify > the config.xml and change the port settings. > > Proxytype: > > http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/NetConnection.html#proxyType > > Sebastian > > 2012/4/27 Maxim Solodovnik <[email protected]>: > > My bad > > there is no such thing as rtmpts > > > > sorry for that > > > > > > On Fri, Apr 27, 2012 at 17:57, Maxim Solodovnik <[email protected]> > > wrote: > >> > >> I'm trying to test if all rtmp* are working. > >> So I'm > >> Checking if NOT secure version is working > >> 1) disable firewall open OM flash application: OM connects to rtmp > >> [success] > >> 2) enable firewall open OM flash application: OM connects to rtmpt > >> [success] > >> > >> Checking if secure version is working > >> 3) disable firewall open OM flash application: OM connects to rtmps > >> [success] > >> 4) enable firewall and would like to check if tunneled secure > rtmpts works > >> as expected. > >> > >> or there is no rtmpts? > >> would requests be secure in case if useSSL is set to "yes" and tunneling > >> is on duty? > >> > >> > >> On Fri, Apr 27, 2012 at 17:44, [email protected] > >> <[email protected]> wrote: > >>> > >>> 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] > >> > >> > >> > >> > >> -- > >> WBR > >> Maxim aka solomax > > > > > > > > > > -- > > 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]
