p.host=0.0.0.0
>
> rtmp.port=1935
>
> ** **
>
> config.xml
>
> 1935
>
> ** **
>
> George.
>
> ** **
>
> *From:* Maxim Solodovnik [mailto:solomax...@gmail.com]
> *Sent:* Wednesday, 6 June 2012 8:18 PM
> *To:* openmeetings-user@incubat
rtmp.port=1935
config.xml
1935
George.
From: Maxim Solodovnik [mailto:solomax...@gmail.com]
Sent: Wednesday, 6 June 2012 8:18 PM
To: openmeetings-user@incubator.apache.org
Subject: Re: Need help with using alternate port for 1935
Only red5.properties need to be changed.
Additionally
Only red5.properties need to be changed.
Additionally restart might be necessary
On Jun 6, 2012 5:15 PM, "seba.wag...@gmail.com"
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
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
> Sebastian,
>
> is RTMPT still not working for you on demo.openmeetings.d
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, seba.wag...@gmail.com wrote:
> Hi George,
>
> the process is like that:
> First (try 0) rtmp
> try1 rtmpt
> try2 rtmpt
> try3 rtmpt
>
> So fir
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 an
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.
