done: http://code.google.com/p/red5/issues/detail?id=227
On Wed, May 30, 2012 at 3:21 PM, [email protected] < [email protected]> wrote: > Yeah, > > as we are not yet sure if this is really the root of the issue we might > start a discussion there. > > Sebastian > > 2012/5/30 Maxim Solodovnik <[email protected]> > > > I didn't report the problem itself :( > > should I? > > > > > > On Wed, May 30, 2012 at 2:58 PM, [email protected] < > > [email protected]> wrote: > > > > > Did you report the possble fix for the rtmpt packet size to the red5 > devs > > > yet? > > > > > > Sebastian > > > > > > 2012/5/29 Maxim Solodovnik <[email protected]> > > > > > > > Issue 224 in red5: RTMPT client failed to connectis changed its > status > > to > > > > updated > > > > > > > > > > > > On Tue, May 29, 2012 at 11:11 PM, Maxim Solodovnik < > > [email protected] > > > > >wrote: > > > > > > > > > I failed to find the root cause analyzing logs etc. > > > > > So I start decreasing red5 version until it start working, then I > > find > > > > the > > > > > exact version it was broken and start analyzing diffs. > > > > > > > > > > After some time I notices that the packet size was decreased, I > tried > > > to > > > > > set it to 32K (as it was before) but it helps only partially. > > > > > Finally I have increased it to be 64K and it helps :) > > > > > > > > > > > > > > > On Tue, May 29, 2012 at 11:04 PM, [email protected] < > > > > > [email protected]> wrote: > > > > > > > > > >> Hi Maxim, > > > > >> > > > > >> thanks for the details, how did you came to that solution? > > > > >> Just by comparing rtmpt packets in old versions or ? > > > > >> > > > > >> > > > > >> Sebastian > > > > >> > > > > >> 2012/5/29 Maxim Solodovnik <[email protected]> > > > > >> > > > > >> > sorry for the brief response (was from my phone) > > > > >> > > > > > >> > please take a look at > > > > >> > > > > > >> > > > > > > > > > > http://svn.apache.org/repos/asf/incubator/openmeetings/trunk/singlewebapp/build.xml > > > > >> > line 729 > > > > >> > I did perform patching of red5.properties file: > > > > >> > rtmpt.target_reponse_size=65536 > > > > >> > was > > > > >> > rtmpt.target_reponse_size=8192 > > > > >> > > > > > >> > and it fixes the problem for me > > > > >> > > > > > >> > On Tue, May 29, 2012 at 7:01 PM, Maxim Solodovnik < > > > > [email protected] > > > > >> >wrote: > > > > >> > > > > > >> >> rtmpt in red5 with default settings did not works. > > > > >> >> I did modified the build to alter default red5 settings and > make > > > > rtmpt > > > > >> >> work > > > > >> >> Please try to: > > > > >> >> 1 delete build/red5/dist > > > > >> >> 2 ant dist > > > > >> >> Everything should work as expected. > > > > >> >> > > > > >> >> Please let me know how it works for you. > > > > >> >> I test it as follows: change rtmp port to be 11935 in > config.XML > > > and > > > > >> >> connect > > > > >> >> On May 29, 2012 6:48 PM, "[email protected]" < > > > > >> [email protected]> > > > > >> >> wrote: > > > > >> >> > > > > >> >>> Hi Maxim, > > > > >> >>> > > > > >> >>> you tried to explain it today several times but I did not > really > > > get > > > > >> it > > > > >> >>> (still). > > > > >> >>> > > > > >> >>> You said that rtmpt for Flash client works but RTMPTClient for > > > > >> >>> screensharing fails. Right? > > > > >> >>> From my perspective also the rtmpt connection for Flash > clients > > > > >> doesn't > > > > >> >>> work with r4374. > > > > >> >>> I somehow understood that you've said "There is a new revision > > > > >> available > > > > >> >>> that already fixes some of the rtmpt issues, but RTMPTClient > > > fails" > > > > >> >>> I might have misunderstood that. > > > > >> >>> r4374 is the latest revision and my tests shown that neither > > rtmpt > > > > for > > > > >> >>> the Flash Client nor the RTMPTClient for Screensharing works > for > > > > that > > > > >> >>> revision. > > > > >> >>> > > > > >> >>> Are we on the same page? > > > > >> >>> > > > > >> >>> Thanks > > > > >> >>> Sebastian > > > > >> >>> > > > > >> >>> -- > > > > >> >>> 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] > > > > > > > > > > > -- > > 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
