Suggestion about the tunnelling implementation.

[Alexey Ghenov]

Hello,

Now after 
OPENMEETINGS-576are
rejected, i am going to do this task with more acceptable way.(Looks
like i done mistake in understanding target of task in beginning). At least
in process of developing proposal i was learned many things about
openmeetings.

Looks like correct way to do this task are configuring red5 server. Are its
fine target? I am glad to receive any suggestions about that.

Also i planning to become more familiar with openmeetings source code, it
is be wonderful if someone give me staring point(related with tunneling
task) to start exploring.

And again source text from GSOC-2012.
>- proper traffic tunnelling (images and screensharing now use 5080 port,
SIP applet likely uses > different ports as well, while anything should be
happy with 80 port);
> - performance: getting rid of Apache httpd to improve openmeetings
hosting performance
> (Apache eats tons os megabytes - proper jetty configuration can be done
as a part of
> tunelling task);

With best regards, Alexey.

Suggestion about the tunnelling implementation.

[Alexey Ghenov]

Hello,

Now after 
OPENMEETINGS-576are
rejected, i am going to do this task with more acceptable way.(Looks
like i done mistake in understanding target of task in beginning). At least
in process of developing proposal i was learned many things about
openmeetings.

Looks like correct way to do this task are configuring red5 server. Are its
fine target? I am glad to receive any suggestions about that.

Also i planning to become more familiar with openmeetings source code, it
is be wonderful if someone give me staring point(related with tunneling
task) to start exploring.

And again source text from GSOC-2012.
>- proper traffic tunnelling (images and screensharing now use 5080 port,
SIP applet likely uses > different ports as well, while anything should be
happy with 80 port);
> - performance: getting rid of Apache httpd to improve openmeetings
hosting performance
> (Apache eats tons os megabytes - proper jetty configuration can be done
as a part of
> tunelling task);

With best regards, Alexey.

Re: Traffic tunneling

[Alexey Ghenov]

Hello,

Now after 
OPENMEETINGS-576are
rejected, i am going to do this task with more acceptable way.(Looks
like i done mistake in understanding target of task in beginning). At least
in process of developing proposal i was learned many things about
openmeetings.

Looks like correct way to do this task are configuring red5 server. Are its
fine target? I am glad to receive any suggestions about that.

Also i planning to become more familiar with openmeetings source code, it
is be wonderful if someone give me staring point(related with tunneling
task) to start exploring.

And again source text from GSOC-2012.
>- proper traffic tunnelling (images and screensharing now use 5080 port,
SIP applet likely uses > different ports as well, while anything should be
happy with 80 port);
> - performance: getting rid of Apache httpd to improve openmeetings
hosting performance
> (Apache eats tons os megabytes - proper jetty configuration can be done
as a part of
> tunelling task);

With best regards, Alexey.


2013/3/18 Denis Kandrov 

> Alexey,
> in Apache community to discuss issues is common to use the mailing lists.
> You are welcome to Apache Openmeetings community.
>
> Youpropose to use the yaws as a proxy server, which will perform tunneling
> traffic.
>
> As I understand yaws is distributed in most unix systems. In this case,
> there is no need to download the tarball and install any version is not
> clear yaws.
> A instruction for setting up and configure yaws and the necessary changes
> of config.xml will need.
>
> For apache2 web server I can give an existing solution, you just need
> enable the proxy module and add following lines toconfiguration file:
>
> ProxyPass /openmeetings 
> http://localhost:5080/**openmeetings
> ProxyPassReverse /openmeetings/ 
> http://localhost:5080/**openmeetings/
>
> ProxyPass /open http://localhost:8088/open
> ProxyPassReverse /open http://localhost:8088/open
>
> ProxyPass /send http://localhost:8088/send
> ProxyPassReverse /send http://localhost:8088/send
>
> ProxyPass /idle http://localhost:8088/idle
> ProxyPassReverse /idle http://localhost:8088/idle
>
> ProxyPass /close http://localhost:8088/close
> ProxyPassReverse /close http://localhost:8088/close
>
> But in this solution there is overhead with wrapping rtmp traffic to http.
>
> For me, it is not clear what your solution is different from the above?
>
> Best regards,
> Denis Kandrov.
>
>

Build failed in Jenkins: Openmeetings 2.1 #4

[Apache Jenkins Server]

See 

Changes:

[vdegtyarev] LabelID is corrected.

[vdegtyarev] Merge OPOPENMEETINGS-507 fix to brunch 2.1.

[vdegtyarev] Merge fix for OPENMEETING-503 to branch 2.1 (approved by Maxim)

[solomax] [OPENMEETINGS-537] context menu on saved WB is corrected

[solomax] Announce about new release is added to the news, Downloads headers 
and links are corrected

[solomax] [Release] Download links are updated

[solomax] [OPENMEETINGS-432] whiteboard is hidden for default video only room

[solomax] Debug URL is corrected in the docs

[solomax] Asterisk download URL was broken (fixed)

[solomax] version is bumped to be 2.1.1

[solomax] [OPENMEETINGS-589] mute/unmute hot key is added

[solomax] Release guide is updated with current release steps

[solomax] [OPENMEETINGS-587] "take exclusive audio" by hotkey is fixed

[iarkh] Site update: test plan for 2.1 pre-release testing has been added.

[solomax] Build: Screensharing under java7 was broken, fixed

[solomax] [OPENMEETINGS-460] typos are fixed

[solomax] [OPENMEETINGS-586] Import: ownerId is replaces with actual ownerId

[solomax] Release: CHANGELOG is updated

[solomax] SIP: updateSipTransport signature is changed to return current sip 
users count

[iarkh] [OPENMEETINGS-580]: Build system now uses recent smslib release 
(3.5.2). Fix for 2.1 branch.

[solomax] Release: License header is restored

[solomax] Release: classpath is updated after project renaming

[solomax] Release: project is renamed to avoid possible conflicts

[solomax] [OPENMEETINGS-583] Ability to disable enhanced microphone is added

--
[...truncated 2134 lines...]
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/delete_all.fla
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/pencil.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/doc_pre.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/ellipse.fla
AUWebContent/openmeetings/public/themes/basic-theme/whiteboard/uline.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/letter.fla
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/doc_next.fla
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/arrow_cursor_tool.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/cancel.png
AUWebContent/openmeetings/public/themes/basic-theme/whiteboard/line.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/delete_all.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/doc_first.fla
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/ellipse.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/page_delete.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/letter.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/pointerWhiteBoard_menu_rsc.fla
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/doc_next.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/menupointer.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/text_signature.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/doc_last.fla
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/lock_open.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/arrow_rotate_clockwise.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/doc_first.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/drawarrowicon.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/rectangle.fla
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/pointerWhiteBoard_menu_rsc.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/arrow_rotate_anticlockwise.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/doc_last.png
AUWebContent/openmeetings/public/themes/basic-theme/whiteboard/lock.png
AU
WebContent/openmeetings/public/themes/basic-theme/whiteboard/doc_pre.fla
A WebContent/openmeetings/public/themes/basic-theme/general
AU
WebContent/openmeetings/public/themes/basic-theme/general/cancel_icon.png
AU
WebContent/openmeetings/public/themes/basic-theme/general/resultset_up.png
AUWebContent/openmeetings/public/themes/basic-theme/general/style.png
AU
WebContent/openmeetings/public/themes/basic-theme/general/arrow_refresh_small.png
AUWebContent/openmeetings/public/themes/basic-theme/general/logo.png
AU
WebContent/openmeetings/public/themes/basic-theme/general/resultset_first.png
AU
WebContent/openmeetings/public/themes/basic-theme/general/cancel_icon_small.fla
AU

Openmeeting with Jabber support

[Premjith R Renjanan]

Dear Support,

Now I am testing Apachee openmeeting in my testing server. I tested most of
the features available in the Apache Openmeeting. I would like to use
Apache openmeeting in my work area. But I would like to know about jabber
support. Because I have an instance of openfire, which support jabber
service and I can able to connect IM client like Spark. Most my activities
and my users communicating by using this IM client.

So can u suggest one better way to integrate IM client like spark with
Apache Openmeeting ?


With Thanks & Regards,
Premjith R

Re: Traffic tunneling

[Irina Arkhipets]

Hi Alexei,

Could you please clarify which help do you need more exactly?

Basically, you should start from the very beginning. I believe the first
step should be a look at the Openmeetings sources and development
environment setup:
http://openmeetings.apache.org/svn.html

Best regards,
Irina.



On Fri, Apr 12, 2013 at 3:08 PM, Alexey Ghenov  wrote:

> Hello,
>
> Now after OPENMEETINGS-576<
> https://issues.apache.org/jira/browse/OPENMEETINGS-576>are
> rejected, i am going to do this task with more acceptable way.(Looks
> like i done mistake in understanding target of task in beginning). At least
> in process of developing proposal i was learned many things about
> openmeetings.
>
> Looks like correct way to do this task are configuring red5 server. Are its
> fine target? I am glad to receive any suggestions about that.
>
> Also i planning to become more familiar with openmeetings source code, it
> is be wonderful if someone give me staring point(related with tunneling
> task) to start exploring.
>
> And again source text from GSOC-2012.
> >- proper traffic tunnelling (images and screensharing now use 5080 port,
> SIP applet likely uses > different ports as well, while anything should be
> happy with 80 port);
> > - performance: getting rid of Apache httpd to improve openmeetings
> hosting performance
> > (Apache eats tons os megabytes - proper jetty configuration can be done
> as a part of
> > tunelling task);
>
> With best regards, Alexey.
>
>
> 2013/3/18 Denis Kandrov 
>
> > Alexey,
> > in Apache community to discuss issues is common to use the mailing lists.
> > You are welcome to Apache Openmeetings community.
> >
> > Youpropose to use the yaws as a proxy server, which will perform
> tunneling
> > traffic.
> >
> > As I understand yaws is distributed in most unix systems. In this case,
> > there is no need to download the tarball and install any version is not
> > clear yaws.
> > A instruction for setting up and configure yaws and the necessary changes
> > of config.xml will need.
> >
> > For apache2 web server I can give an existing solution, you just need
> > enable the proxy module and add following lines toconfiguration file:
> >
> > ProxyPass /openmeetings http://localhost:5080/**openmeetings<
> http://localhost:5080/openmeetings>
> > ProxyPassReverse /openmeetings/ http://localhost:5080/**openmeetings/<
> http://localhost:5080/openmeetings/>
> >
> > ProxyPass /open http://localhost:8088/open
> > ProxyPassReverse /open http://localhost:8088/open
> >
> > ProxyPass /send http://localhost:8088/send
> > ProxyPassReverse /send http://localhost:8088/send
> >
> > ProxyPass /idle http://localhost:8088/idle
> > ProxyPassReverse /idle http://localhost:8088/idle
> >
> > ProxyPass /close http://localhost:8088/close
> > ProxyPassReverse /close http://localhost:8088/close
> >
> > But in this solution there is overhead with wrapping rtmp traffic to
> http.
> >
> > For me, it is not clear what your solution is different from the above?
> >
> > Best regards,
> > Denis Kandrov.
> >
> >
>

RTMPS

[Vieri]

Hi,

I'm trying out svn r1467194M but I'm unable to configure RTMPS/HTTPS as in 
http://openmeetings.apache.org/RTMPSAndHTTPS.html. I know it was broken at some 
point in svn but was wondering if it's going to be fixed or if it will be 
dropped.

Thanks,

Vieri

Re: RTMPS

[Maxim Solodovnik]

Hello Vieri,

trunk == 3.0 is going to be fixed
branch/2.1 should work as expected


On Fri, Apr 12, 2013 at 7:47 PM, Vieri  wrote:

> Hi,
>
> I'm trying out svn r1467194M but I'm unable to configure RTMPS/HTTPS as in
> http://openmeetings.apache.org/RTMPSAndHTTPS.html. I know it was broken
> at some point in svn but was wondering if it's going to be fixed or if it
> will be dropped.
>
> Thanks,
>
> Vieri
>
>
>


-- 
WBR
Maxim aka solomax