Hello, Alexey.
OpenMeetings use 3 ports:
5080 - for web content - flash application, pictures and others. This is
http traffic.
1935 - for video/audio steams. This is rtmp traffic.
8088 - for video/audio streams, that wrapped into http. This port is
used when it is impossible to transmit media data through 1935.
As I see you have configured only on port 5080.
What about 1935 or 8088?
Best regards,
Denis Kandrov
On 18.03.2013 21:03, Alexey Ghenov wrote:
This solution are similiar to apache2, i tried to make easy configuration
and deployment by one command using ant.
All that ant script doing is adding to yaws conf
<server localhost>
port = 8080
listen = 192.168.0.8
docroot = /home/alexey/comm.build/
singlewebapp/dist/yaws-1.95/var/yaws/www/testdir
# dir_listings = true
revproxy = / http://0.0.0.0:5080
partial_post_size = 65480
</server>
and reconfiguring openmeetings client to to use yaws proxy.
With best regards, Alexey.
