Only red5.properties need to be changed. Additionally restart might be necessary On Jun 6, 2012 5:15 PM, "[email protected]" <[email protected]> wrote:
> rtmpt does not work on demo.openmeetings.de > > Have there been changes since 03.06.2012 that require to update the > binaries or just changing packet size is enough to do the test ? > > Thanks > Sebastian > > 2012/6/6 Maxim Solodovnik <[email protected]> > >> Sebastian, >> >> is RTMPT still not working for you on demo.openmeetings.de? >> maybe you can try set packet size to 128K for it? >> >> >> On Wed, Jun 6, 2012 at 5:08 PM, [email protected] < >> [email protected]> wrote: >> >>> Hi George, >>> >>> the process is like that: >>> First (try 0) rtmp >>> try1 rtmpt >>> try2 rtmpt >>> try3 rtmpt >>> >>> So first it will try rtmp and then 3 times rtmpt. >>> Things are different if you configure rtmps. >>> >>> Currently RTMPT does not work at all with altest builds as there is an >>> issue with the underlaying Red5 server and RTMPT. >>> >>> Changing RTMPT to port 443 (if RTMPT is working again) should be best >>> for Firewall issues. Packets on port 443 are normally not blocked by >>> firewalls as 443 is normally HTTPS. >>> >>> Sebastian >>> >>> >>> 2012/6/5 George Kirkham <[email protected]> >>> >>>> Hi,**** >>>> >>>> ** ** >>>> >>>> We conference with people who are behind a firewall which blocks many >>>> ports, including 1935. Previously I had OpenMeetings working for them by >>>> using “rtmpt.port=8080” instead of the default port “rtmpt.port=8088”, >>>> and while this worked previously it has been failing for some time now. >>>> **** >>>> >>>> ** ** >>>> >>>> **1) **I think there is a fault in OpenMeetings in using the >>>> secondary ports, as I have been testing with my own installation by >>>> disabling port 1935 in our firewall and then doing an external test (which >>>> fails). I have tested this on the standard installation settings and with >>>> my modified 8080 port, both fail on Try 1 (because I use the firewall to >>>> block port 1935), Try 2 and Try 3. >>>> >>>> **** >>>> >>>> **2) **Can someone please explain to me how the port process >>>> works. My understanding is that if OpenMeetings cannot connect via “ >>>> rtmp.port=1935” for “try 1”, then it tries again on “rtmpt.port=8088” >>>> for try 2. I do not know what it attempts to use on try 3 (which is also >>>> failing for me). I believe that it is not trying the alternative ports >>>> >>>> **** >>>> >>>> **3) **Can someone please test for me, by blocking port 1935 in >>>> your firewall and see if external users can connect to your OpenMeetings? >>>> >>>> **** >>>> >>>> **4) **What is the repercussions if I were to change “ >>>> rtmp.port=1935” to “rtmp.port=8080” ? Does this affect performance in >>>> any way? >>>> >>>> **** >>>> >>>> **5) **The attached image is message I get after the three tries >>>> to connect all fail, when I block port 1935.**** >>>> >>>> ** ** >>>> >>>> **** >>>> >>>> ** ** >>>> >>>> Thanks,**** >>>> >>>> ** ** >>>> >>>> George Kirkham**** >>>> >>>> ** ** >>>> >>>> ** ** >>>> >>> >>> >>> >>> -- >>> 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] >
<<image003.png>>
