date:20200516

I'm using use-auth-secret without user in coturn's configuration and with
empty p:turnUser in OM's applicationContext.xml.
I haven't tried to configure user auth through applicationContext.xml...I
only tried user auth by not touching applicationContext.xml at all and by
configuring it in KMS's WebRtcEndpoint.conf.ini. That way it worked but
most users had trouble to prolong their sessions on turn and so had
disconnects by channel-lifetime (by default 10 minutes).

Looking at
https://github.com/apache/openmeetings/blob/master/openmeetings-core/src/main/java/org/apache/openmeetings/core/remote/KurentoHandler.java#L335
if
you want to try user auth you need to set p:TurnMode="",
p:TurnUser="username" and p:turnSecret="password"

сб, 16 мая 2020 г. в 20:39, Juan Antonio Moreno Carmona :

> Hi Konstantin
>
> Then, what mechanism do you use? user or use-auth-secret?
>
> And how do you fill applicationContext.xml file. I tried to comment
> use-auth-secret and static-auth-secret in turnserver.conf file.
> Furthermore, I leave p:turnSecret option empty in applicationContext.xml
> file.
>
> But then I get following error in catalina.out and I can't get
> camera/audio working
>
> ERROR 05-16 18:57:36.864 o.a.w.DefaultExceptionMapper:170
> [-apr-443-exec-6] - Unexpected error occurred
> java.lang.IllegalArgumentException: Empty key
>
> Regards.
> El 16/5/20 a las 16:22, Konstantin Kuzov escribió:
>
> Hi there, I have a few suggestions about tutorials.
>
> 1) I don't really understand the purpose for setting both user and
> use-auth-secret in coturn. According to documentation they are both
> exclusive:
> # Be aware that use-auth-secret overrides some parts of lt-cred-mech.
> # The use-auth-secret feature depends internally on lt-cred-mech, so if
> you set
> # this option then it automatically enables lt-cred-mech internally
> # as if you had enabled both.
> # Note that you can use only one auth mechanism at the same time! This is
> because,
> # both mechanisms conduct username and password validation in different
> ways.
> # Use either lt-cred-mech or use-auth-secret in the conf
> # to avoid any confusion.
>
> 2) Also for coturn I don't see the fingerprint option. Isn't it required
> for webrtc?
> 3) What the point for installing to something obscure like /opt/open504
> and using open504 as database name? IMHO it would just complicate upgrading
> procedure for users.later on.
> 4) Please use openmeetings.service on distributions which use systemd.
> 5) User need to be aware that tomcat won't reload to new certificates upon
> renewal and will keep using old certificates until full restart. So
> typically after 3 month clients will be greated with expired certificate in
> case of let's encrypt. If user don't want to restart tomcat every now and
> then and terminate by that all currently active connections user need send
> to it reloadSslHostConfig(host) or reloadSslHostConfigs() via jmx or
> manager. But it is not something simple like in case of nginx which only
> require SIGHUP signal to the process. And nor jmx or manager is shipped
> with OM distribution anyway. As one solution to the problem on my test OM
> installation VM with let's encrypt I'm using acme-tiny instead of certbot
> (matter of preference) and this custom protocol
> https://github.com/CkNoSFeRaTU/tomcat-reloadprotocol which will
> automatically reload it for me every configured interval.
>
> сб, 16 мая 2020 г. в 13:22, Alvaro :
>
>> ...in Russian mailing-list, Konstantin gives an idea about
>> help to solve the reconnection in Turn server:
>>
>> "stale-nonce=0" (at /etc/turnserver.conf)
>>
>> ...'ve added this parameter to the tutorials:
>>
>>
>> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
>> CentOS 7-8.pdf
>>
>> ...and
>>
>> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
>> Ubuntu 18.04.pdf
>>
>>
>> ...and reuploaded to:
>>
>>
>>
>> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
>>
>>
>> There it is at your disposal.
>>
>>
>> Thanks to Maxim to comment it.
>>
>>
>> Regards
>>
>> Alvaro
>>
>>
>> 
>>
>> El jue, 23-04-2020 a las 18:18 +0200, Alvaro escribió:
>>
>>
>> Hello,
>>
>> It is at your disposal two new tutorials called:
>>
>>
>> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
>> CentOS 7-8.pdf
>>
>> ...and
>>
>> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
>> Ubuntu 18.04.pdf
>>
>>
>> It is tested with an OpenMeetings 5.0.0-M4 server installed on a pc
>> at home, after NAT router; and each in the room saw and heard the others
>> cameras and your own correctly.
>> Also in the tests done, we have uploaded files, recorded video
>> and shared desktop without any error.
>>
>> You can find them here:
>>
>>
>>
>> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
>>
>>
>> Best regards
>>
>> Alvaro
>>
>> .
>>

Re: New tutorials Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4

Hi Konstantin

Then, what mechanism do you use? user or use-auth-secret?

And how do you fill applicationContext.xml file. I tried to comment
use-auth-secret and static-auth-secret in turnserver.conf file.
Furthermore, I leave p:turnSecret option empty in applicationContext.xml
file.

But then I get following error in catalina.out and I can't get
camera/audio working

ERROR 05-16 18:57:36.864 o.a.w.DefaultExceptionMapper:170
[-apr-443-exec-6] - Unexpected error occurred

java.lang.IllegalArgumentException: Empty key

Regards.

El 16/5/20 a las 16:22, Konstantin Kuzov escribió:

Hi there, I have a few suggestions about tutorials.

1) I don't really understand the purpose for setting both user and
use-auth-secret in coturn. According to documentation they are both
exclusive:

# Be aware that use-auth-secret overrides some parts of lt-cred-mech.
# The use-auth-secret feature depends internally on lt-cred-mech, so
if you set

# this option then it automatically enables lt-cred-mech internally
# as if you had enabled both.
# Note that you can use only one auth mechanism at the same time! This
is because,
# both mechanisms conduct username and password validation in
different ways.

# Use either lt-cred-mech or use-auth-secret in the conf
# to avoid any confusion.

2) Also for coturn I don't see the fingerprint option. Isn't it
required for webrtc?
3) What the point for installing to something obscure like
/opt/open504 and using open504 as database name? IMHO it would just
complicate upgrading procedure for users.later on.

4) Please use openmeetings.service on distributions which use systemd.
5) User need to be aware that tomcat won't reload to new certificates
upon renewal and will keep using old certificates until full restart.
So typically after 3 month clients will be greated with expired
certificate in case of let's encrypt. If user don't want to restart
tomcat every now and then and terminate by that all currently active
connections user need send to it reloadSslHostConfig(host) or
reloadSslHostConfigs() via jmx or manager. But it is not something
simple like in case of nginx which only require SIGHUP signal to the
process. And nor jmx or manager is shipped with OM distribution
anyway. As one solution to the problem on my test OM installation VM
with let's encrypt I'm using acme-tiny instead of certbot (matter of
preference) and this custom protocol
https://github.com/CkNoSFeRaTU/tomcat-reloadprotocol which will
automatically reload it for me every configured interval.

сб, 16 мая 2020 г. в 13:22, Alvaro >:

...in Russian mailing-list, Konstantin gives an idea about
help to solve the reconnection in Turn server:

"stale-nonce=0" (at /etc/turnserver.conf)

...'ve added this parameter to the tutorials:

Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4
on CentOS 7-8.pdf

...and

Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4
on Ubuntu 18.04.pdf

...and reuploaded to:

https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools

There it is at your disposal.

Thanks to Maxim to comment it.

Regards

Alvaro

El jue, 23-04-2020 a las 18:18 +0200, Alvaro escribió:

Hello,

It is at your disposal two new tutorials called:

Installation SSL certificates and Coturn for OpenMeetings
5.0.0-M4 on CentOS 7-8.pdf

...and

Installation SSL certificates and Coturn for OpenMeetings
5.0.0-M4 on Ubuntu 18.04.pdf

It is tested with an OpenMeetings 5.0.0-M4 server installed on a pc
at home, after NAT router; and each in the room saw and heard the
others
cameras and your own correctly.
Also in the tests done, we have uploaded files, recorded video
and shared desktop without any error.

You can find them here:

https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools

Best regards

Alvaro

Re: different langauges

2020-05-16 Thread Tom Luo

Thanks a lot!

On Sat, May 16, 2020 at 10:23 AM K. Kamhamea 
wrote:

> https://localhost:5443/openmeetings/#admin/lang
>
> You may want to replace localhost with your domain.
> Hope this helps
> K.
>
> Am Sa., 16. Mai 2020 um 16:00 Uhr schrieb Tom Luo :
>
>> Do you have a link?
>>
>> On Sat, May 16, 2020 at 9:56 AM Maxim Solodovnik 
>> wrote:
>>
>>> sure :)
>>>
>>> On Sat, 16 May 2020 at 20:50, Tom Luo  wrote:
>>>
 Hi,

 Does Openmeetings have different language translations?

 Thanks,

 Tom


>>>
>>> --
>>> Best regards,
>>> Maxim
>>>
>>

Re: New tutorials Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4

Hi there,
The only thing that i can say is...it works for me as was.


..


El sáb, 16-05-2020 a las 17:22 +0300, Konstantin Kuzov escribió:
> Hi there, I have a few suggestions about tutorials.
> 
> 1) I don't really understand the purpose for setting both user and 
> 
> use-auth-secret in coturn. According to documentation they are both
> exclusive:
> # Be aware that use-auth-secret overrides some parts of lt-cred-mech.
> # The use-auth-secret feature depends internally on lt-cred-mech, so
> if you set
> # this option then it automatically enables lt-cred-mech internally
> # as if you had enabled both.
> # Note that you can use only one auth mechanism at the same time!
> This is because,
> # both mechanisms conduct username and password validation in
> different ways.
> # Use either lt-cred-mech or use-auth-secret in the conf
> # to avoid any confusion.
> 
> 2) Also for coturn I don't see the fingerprint option. Isn't it
> required for webrtc?
> 3) What the point for installing to something obscure like
> /opt/open504 and using open504 as database name? IMHO it would just
> complicate upgrading procedure for users.later on.
> 4) Please use openmeetings.service on distributions which use
> systemd.
> 5) User need to be aware that tomcat won't reload to new certificates
> upon renewal and will keep using old certificates until full restart.
> So typically after 3 month clients will be greated with expired
> certificate in case of let's encrypt. If user don't want to restart
> tomcat every now and then and terminate by that all currently active
> connections user need send to it reloadSslHostConfig(host) or
> reloadSslHostConfigs() via jmx or manager. But it is not something
> simple like in case of nginx which only require SIGHUP signal to the
> process. And nor jmx or manager is shipped with OM distribution
> anyway. As one solution to the problem on my test OM installation VM
> with let's encrypt I'm using acme-tiny instead of certbot (matter of
> preference) and this custom protocol https://github.com/CkNoSFeRaTU/t
> omcat-reloadprotocol which will automatically reload it for me every
> configured interval.
> 
> сб, 16 мая 2020 г. в 13:22, Alvaro :
> > ...in Russian mailing-list, Konstantin gives an idea abouthelp to
> > solve the reconnection in Turn server:
> > "stale-nonce=0" (at /etc/turnserver.conf)
> > ...'ve added this parameter to the tutorials:
> > 
> > Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4
> > on CentOS 7-8.pdf
> > ...and
> > Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4
> > on Ubuntu 18.04.pdf
> > 
> > ...and reuploaded to:
> > 
> > https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+
> > for+installing+OpenMeetings+and+Tools
> > 
> > There it is at your disposal.
> > 
> > Thanks to Maxim to comment it.
> > 
> > Regards
> > Alvaro
> > 
> > 
> > El jue, 23-04-2020 a las 18:18 +0200, Alvaro escribió:
> > > Hello,
> > > 
> > > It is at your disposal two new tutorials called:
> > > 
> > > 
> > > Installation SSL certificates and Coturn for OpenMeetings 5.0.0-
> > > M4 on CentOS 7-8.pdf
> > > 
> > > ...and
> > > 
> > > Installation SSL certificates and Coturn for OpenMeetings 5.0.0-
> > > M4 on Ubuntu 18.04.pdf
> > > 
> > > 
> > > It is tested with an OpenMeetings 5.0.0-M4 server installed on a
> > > pc
> > > at home, after NAT router; and each in the room saw and heard the
> > > others
> > > cameras and your own correctly.
> > > Also in the tests done, we have uploaded files, recorded video
> > > and shared desktop without any error.
> > > 
> > > You can find them here:
> > > 
> > > 
> > > https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorial
> > > s+for+installing+OpenMeetings+and+Tools
> > > 
> > > 
> > > Best regards
> > > 
> > > Alvaro
> > > 
> > > .
> > >

Re: New tutorials Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4

Also better to use domain name in p:turnUrl if user have one and port
number can be omitted if it is default 3478.

сб, 16 мая 2020 г. в 17:22, Konstantin Kuzov :

> Hi there, I have a few suggestions about tutorials.
>
> 1) I don't really understand the purpose for setting both user and
> use-auth-secret in coturn. According to documentation they are both
> exclusive:
> # Be aware that use-auth-secret overrides some parts of lt-cred-mech.
> # The use-auth-secret feature depends internally on lt-cred-mech, so if
> you set
> # this option then it automatically enables lt-cred-mech internally
> # as if you had enabled both.
> # Note that you can use only one auth mechanism at the same time! This is
> because,
> # both mechanisms conduct username and password validation in different
> ways.
> # Use either lt-cred-mech or use-auth-secret in the conf
> # to avoid any confusion.
>
> 2) Also for coturn I don't see the fingerprint option. Isn't it required
> for webrtc?
> 3) What the point for installing to something obscure like /opt/open504
> and using open504 as database name? IMHO it would just complicate upgrading
> procedure for users.later on.
> 4) Please use openmeetings.service on distributions which use systemd.
> 5) User need to be aware that tomcat won't reload to new certificates upon
> renewal and will keep using old certificates until full restart. So
> typically after 3 month clients will be greated with expired certificate in
> case of let's encrypt. If user don't want to restart tomcat every now and
> then and terminate by that all currently active connections user need send
> to it reloadSslHostConfig(host) or reloadSslHostConfigs() via jmx or
> manager. But it is not something simple like in case of nginx which only
> require SIGHUP signal to the process. And nor jmx or manager is shipped
> with OM distribution anyway. As one solution to the problem on my test OM
> installation VM with let's encrypt I'm using acme-tiny instead of certbot
> (matter of preference) and this custom protocol
> https://github.com/CkNoSFeRaTU/tomcat-reloadprotocol which will
> automatically reload it for me every configured interval.
>
>>
>>

Re: New Features: "very fast conference" and more

The only thing Jitsi does regarding to ports in default configuration is
using nginx's APLN map feature (
http://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html) to hide
default stun/turn ports behind nginx https port. But be aware that this
feature can break secure websocket for some browsers like chrome.

)сб, 16 мая 2020 г. в 17:36, Maxim Solodovnik :

> This service uses Jitsi
> I'm still not sure if it is possible to configure WebRTC to use less ports
> AFAIK it is impossible
>
>

Re: Restricting Recording in OM

Sure,

room has correspondent option Admin->Conference Rooms

On Sat, 16 May 2020 at 21:35, OpenMeetings User <
openmeeti...@sportingnetgain.com> wrote:

> Greetings:
>
> Is it possible to configure OpenMeetings so that attendees cannot record
> the meeting?
>
> Thanks,
> Owen
>


-- 
Best regards,
Maxim

Re: New Features: "very fast conference" and more

On Sat, 16 May 2020 at 00:14, R. Scholz 
wrote:

> Hello,
>
> today we had a online-conference from our marketing-company.
> They have their own conference-system.
>
> Total easy to login and runs very nice.
> All members (without exception) have no problems to enter the
> conference-room and use their microphone
> and, the notebook-user, their camera.
>
> I must admit freely: Not bad.
>
> I think there are some features we shpuld have a deeper look on it - and
> implement in our OM.
>
> - No problems with ports: All members, including the members  from
> official institutions, can login without problems and no changes with
> their firewall.
> (I asked one (or two) weeks ago that question.) And use the microphone
> and camera.
> Essential point: It seems it is possible to make a
> video/audio-conference with all peoples, including this one who are
> behind a "Great firewall".
>

This service uses Jitsi
I'm still not sure if it is possible to configure WebRTC to use less ports
AFAIK it is impossible


>
> - The handling -> New OM-feature: "Quick-conference":
> 1.) Calling a URL
> 2.) Enter a Name
> Thats all.
> (That was the only information we got from the marketing-company.) And
> it works.
>

You can generate URL send it to your parties
they will enter the name on enter
can participate :)

Our current registration form is a little bigger than one field :))


>
> (We must use Google-Chrome. It was recommended.)
>
> - a very tidy desktop: a few icons and all work very good, including
> sharing desktop.
>
> - OK, security is not a focus here. But that is a "Quick-conference".
>
> ...
>
> If anybody wants to try:
> https://besprechung.konferenzen.online
>
> With best regards,
>
> René
>
>
>
>
>

-- 
Best regards,
Maxim

Restricting Recording in OM

2020-05-16 Thread OpenMeetings User

Greetings:
Is it possible to configure OpenMeetings so that attendees cannot record the 
meeting?
Thanks,Owen

Re: different langauges

2020-05-16 Thread K. Kamhamea

https://localhost:5443/openmeetings/#admin/lang

You may want to replace localhost with your domain.
Hope this helps
K.

Am Sa., 16. Mai 2020 um 16:00 Uhr schrieb Tom Luo :

> Do you have a link?
>
> On Sat, May 16, 2020 at 9:56 AM Maxim Solodovnik 
> wrote:
>
>> sure :)
>>
>> On Sat, 16 May 2020 at 20:50, Tom Luo  wrote:
>>
>>> Hi,
>>>
>>> Does Openmeetings have different language translations?
>>>
>>> Thanks,
>>>
>>> Tom
>>>
>>>
>>
>> --
>> Best regards,
>> Maxim
>>
>

Re: different langauges

Sure,

please join us in translation :))
https://poeditor.com/join/project/6UF8Mhql61

On Sat, 16 May 2020 at 21:00, Tom Luo  wrote:

> Do you have a link?
>
> On Sat, May 16, 2020 at 9:56 AM Maxim Solodovnik 
> wrote:
>
>> sure :)
>>
>> On Sat, 16 May 2020 at 20:50, Tom Luo  wrote:
>>
>>> Hi,
>>>
>>> Does Openmeetings have different language translations?
>>>
>>> Thanks,
>>>
>>> Tom
>>>
>>>
>>
>> --
>> Best regards,
>> Maxim
>>
>

-- 
Best regards,
Maxim

Re: New tutorials Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4

Hi there, I have a few suggestions about tutorials.

1) I don't really understand the purpose for setting both user and
use-auth-secret in coturn. According to documentation they are both
exclusive:
# Be aware that use-auth-secret overrides some parts of lt-cred-mech.
# The use-auth-secret feature depends internally on lt-cred-mech, so if you
set
# this option then it automatically enables lt-cred-mech internally
# as if you had enabled both.
# Note that you can use only one auth mechanism at the same time! This is
because,
# both mechanisms conduct username and password validation in different
ways.
# Use either lt-cred-mech or use-auth-secret in the conf
# to avoid any confusion.

2) Also for coturn I don't see the fingerprint option. Isn't it required
for webrtc?
3) What the point for installing to something obscure like /opt/open504 and
using open504 as database name? IMHO it would just complicate upgrading
procedure for users.later on.
4) Please use openmeetings.service on distributions which use systemd.
5) User need to be aware that tomcat won't reload to new certificates upon
renewal and will keep using old certificates until full restart. So
typically after 3 month clients will be greated with expired certificate in
case of let's encrypt. If user don't want to restart tomcat every now and
then and terminate by that all currently active connections user need send
to it reloadSslHostConfig(host) or reloadSslHostConfigs() via jmx or
manager. But it is not something simple like in case of nginx which only
require SIGHUP signal to the process. And nor jmx or manager is shipped
with OM distribution anyway. As one solution to the problem on my test OM
installation VM with let's encrypt I'm using acme-tiny instead of certbot
(matter of preference) and this custom protocol
https://github.com/CkNoSFeRaTU/tomcat-reloadprotocol which will
automatically reload it for me every configured interval.

сб, 16 мая 2020 г. в 13:22, Alvaro :

> ...in Russian mailing-list, Konstantin gives an idea about
> help to solve the reconnection in Turn server:
>
> "stale-nonce=0" (at /etc/turnserver.conf)
>
> ...'ve added this parameter to the tutorials:
>
>
> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
> CentOS 7-8.pdf
>
> ...and
>
> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
> Ubuntu 18.04.pdf
>
>
> ...and reuploaded to:
>
>
>
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
>
>
> There it is at your disposal.
>
>
> Thanks to Maxim to comment it.
>
>
> Regards
>
> Alvaro
>
>
> 
>
> El jue, 23-04-2020 a las 18:18 +0200, Alvaro escribió:
>
>
> Hello,
>
> It is at your disposal two new tutorials called:
>
>
> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
> CentOS 7-8.pdf
>
> ...and
>
> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
> Ubuntu 18.04.pdf
>
>
> It is tested with an OpenMeetings 5.0.0-M4 server installed on a pc
> at home, after NAT router; and each in the room saw and heard the others
> cameras and your own correctly.
> Also in the tests done, we have uploaded files, recorded video
> and shared desktop without any error.
>
> You can find them here:
>
>
>
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
>
>
> Best regards
>
> Alvaro
>
> .
>
>

Re: different langauges

2020-05-16 Thread Tom Luo

Do you have a link?

On Sat, May 16, 2020 at 9:56 AM Maxim Solodovnik 
wrote:

> sure :)
>
> On Sat, 16 May 2020 at 20:50, Tom Luo  wrote:
>
>> Hi,
>>
>> Does Openmeetings have different language translations?
>>
>> Thanks,
>>
>> Tom
>>
>>
>
> --
> Best regards,
> Maxim
>

Re: different langauges

sure :)

On Sat, 16 May 2020 at 20:50, Tom Luo  wrote:

> Hi,
>
> Does Openmeetings have different language translations?
>
> Thanks,
>
> Tom
>
>

-- 
Best regards,
Maxim

different langauges

2020-05-16 Thread Tom Luo

Hi,

Does Openmeetings have different language translations?

Thanks,

Tom

Re: OM 505 Problem reconnect Stream

On Sat, 16 May 2020 at 14:48, Peter Dähn  wrote:

> Hi Maxim,
>
> I added this parameter to coturn... I hope this helps...
>
> You asked for
>
> *ERROR 05-15 17:24:26.348 o.a.o.c.r.KurentoHandler:201 [ntLoopGroup-2-1] -
> Unexpected error while clean-up*
>
>
> Can I see stack-trace for this exception?
>
>
> This was after restart kms. As I said: No connection possible after
> restart of kms.
>
> *DEBUG 05-15 17:24:04.532 o.a.o.w.c.OmWebSocketPanel:88 [io-5082-exec-10]
> - Sending WebSocket PING*
> *DEBUG 05-15 17:24:12.317 o.a.o.w.c.OmWebSocketPanel:88 [io-5082-exec-12]
> - Sending WebSocket PING*
> *INFO  05-15 17:24:26.156 o.k.j.c.JsonRpcClientNettyWebSocket:275
> [ntLoopGroup-2-1] -  channel closed*
> *INFO  05-15 17:24:26.156 o.k.j.c.JsonRpcClientNettyWebSocket:275
> [ntLoopGroup-5-1] -  channel closed*
> *DEBUG 05-15 17:24:26.241 o.a.o.c.r.KurentoHandler:150 [ntLoopGroup-2-1] -
> JsonRpcWsClient disconnected from ws://127.0.0.1:/kurento because
> Channel closed.*
> *DEBUG 05-15 17:24:26.241 o.a.o.c.r.KurentoHandler:150 [ntLoopGroup-5-1] -
> JsonRpcWsClient disconnected from ws://127.0.0.1:/kurento because
> Channel closed.*
> *INFO  05-15 17:24:26.275 o.a.o.c.r.KurentoHandler:141 [ntLoopGroup-2-1] -
> !!! Kurento disconnected*
> *INFO  05-15 17:24:26.276 o.a.o.c.r.KurentoHandler:141 [ntLoopGroup-5-1] -
> !!! Kurento disconnected*
>

For whatever reason the messages are doubled ...


>
> *DEBUG 05-15 17:24:26.276 o.a.o.c.r.KurentoHandler:190 [ntLoopGroup-2-1] -
> Client will destroyed ...*
> *WARN  05-15 17:24:26.276 o.a.o.c.r.KurentoHandler:117 [Thread-88202] -
> Media Server is not accessible*
> *DEBUG 05-15 17:24:26.307 o.a.o.d.d.r.PollDao:104 [Thread-88202] -  ::
> hasPoll :: 12561*
> *DEBUG 05-15 17:24:26.310 o.a.o.d.d.r.PollDao:98 [Thread-88202] -  ::
> getArchived :: 12561*
> *WARN  05-15 17:24:26.312 o.k.j.c.JsonRpcClientNettyWebSocket:308
> [ntLoopGroup-2-1] -  Trying to close a JsonRpcClientNettyWebSocket with
> channel == null*
> *WARN  05-15 17:24:26.312 o.k.j.c.JsonRpcClientNettyWebSocket:291
> [ntLoopGroup-2-1] -  Trying to close a JsonRpcClientNettyWebSocket with
> group == null*
> *DEBUG 05-15 17:24:26.312 o.a.o.c.r.KurentoHandler:192 [ntLoopGroup-2-1] -
>  Client is destroyed*
> *WARN  05-15 17:24:26.312 o.a.o.c.r.KurentoHandler:117 [Thread-88202] -
> Media Server is not accessible*
> *ERROR 05-15 17:24:26.348 o.a.o.c.r.KurentoHandler:201 [ntLoopGroup-2-1] -
> Unexpected error while clean-up*
> *WARN  05-15 17:24:26.349 o.a.o.c.r.KurentoHandler:117 [Thread-88202] -
> Media Server is not accessible*
> *WARN  05-15 17:24:26.355 o.a.o.c.r.KurentoHandler:117 [Thread-88203] -
> Media Server is not accessible*
> *DEBUG 05-15 17:24:26.355 o.a.o.d.d.r.PollDao:104 [Thread-88203] -  ::
> hasPoll :: 12561*
> *WARN  05-15 17:24:26.355 o.a.o.c.r.KurentoHandler:117 [Thread-88202] -
> Media Server is not accessible*
>

Is there "!!! Kurento connected" later in the logs?


>
>
> Greetings Peter
>
> Am 16.05.20 um 05:35 schrieb Maxim Solodovnik:
>
> Hello Peter,
>
> On Fri, 15 May 2020 at 23:21, Peter Dähn   
> wrote:
>
>
> Hi Maxim,
>
> 1st: I meant is there a way to prevent those reconnection?
>
>
> Yesterday there was a thread in Russian 
> mailing-listhttps://markmail.org/message/camwly4nwmyot67o
> Konstantin point out "stale-nonce=0" TURN parameter might be required
> (otherwise default timeout of 600 seconds will happen on TURN server)
> I have added this parameter to my coturn config
>
> this might help
> hard to say if this is the only reason :(((
>
> re-connections were added due to multiple user requests
> I believe auto-recover after error is something good :)))
>
>
>
> 2nd: yes restart was successful and it didn't help...
>
> Today it happens again.. some of my "findings"
>
>
>
> Below errors are expected during multiple re-connections
> I will add some guards so it will not pollute the logs
>
>
>
> *sudo grep ERROR /OM_HOME/logs/catalina.out*
> *ERROR 05-15 17:14:42.505 o.a.c.i.AbstractFaultChainInitiatorObserver:114
> [nio-5082-exec-6] - An unexpected error occurred during error handling. No
> further error processing will occur.*
> *ERROR 05-15 17:21:38.308 o.a.o.w.c.OmWebSocketPanel:144 [nio-5082-exec-3]
> - Error while processing incoming message*
> *ERROR 05-15 17:21:38.352 o.a.o.w.c.OmWebSocketPanel:144 [nio-5082-exec-3]
> - Error while processing incoming message*
> *ERROR 05-15 17:21:38.356 o.a.o.w.c.OmWebSocketPanel:144 [nio-5082-exec-3]
> - Error while processing incoming message*
> *ERROR 05-15 17:21:38.398 o.a.o.w.c.OmWebSocketPanel:144 [nio-5082-exec-3]
> - Error while processing incoming message*
> *ERROR 05-15 17:21:38.401 o.a.o.w.c.OmWebSocketPanel:144 [nio-5082-exec-3]
> - Error while processing incoming message*
> *ERROR 05-15 17:21:38.405 o.a.o.w.c.OmWebSocketPanel:144 [nio-5082-exec-3]
> - Error while processing incoming message*
> *ERROR 05-15 17:21:38.408 o.a.o.w.c.OmWebSocketPanel:144 [nio-5082-exec-3]
> - Error while processing incoming message*
>

Re: About invitation

Hello,

Yes, I guess so


On Sat, 16 May 2020 at 17:03, Juan Antonio Moreno Carmona 
wrote:

> Is it okay to send an invitation to this mailing list so that multiple
> users can make use of that invitation to attend the room?
>
> Greetings.
>
>

-- 
Best regards,
Maxim

Testing presentation room


Ok, I'm going to try.

Re: New tutorials Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4

...in Russian mailing-list, Konstantin gives an idea abouthelp to solve
the reconnection in Turn server:
"stale-nonce=0" (at /etc/turnserver.conf)
...'ve added this parameter to the tutorials:

Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
CentOS 7-8.pdf
...and
Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
Ubuntu 18.04.pdf

...and reuploaded to:

https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+
installing+OpenMeetings+and+Tools

There it is at your disposal.

Thanks to Maxim to comment it.

Regards
Alvaro


El jue, 23-04-2020 a las 18:18 +0200, Alvaro escribió:
> Hello,
> 
> It is at your disposal two new tutorials called:
> 
> 
> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
> CentOS 7-8.pdf
> 
> ...and
> 
> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
> Ubuntu 18.04.pdf
> 
> 
> It is tested with an OpenMeetings 5.0.0-M4 server installed on a pc
> at home, after NAT router; and each in the room saw and heard the
> others
> cameras and your own correctly.
> Also in the tests done, we have uploaded files, recorded video
> and shared desktop without any error.
> 
> You can find them here:
> 
> 
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+fo
> r+installing+OpenMeetings+and+Tools
> 
> 
> Best regards
> 
> Alvaro
> 
> .
>

Re: [openmeetings-en-espanol] Nuevos tutoriales instalacion de certificados SSL y Coturn para OpenMeetings 5.0.0-M4

...en la lista-foro ruso, Konstantin ha dado una idea paraayudar acerca
de la reconexion del servidor Turn:
"stale-nonce=0" (en /etc/turnserver.conf)
...he añadido este parámetro en los tutoriales:

Instalacion certificados SSL y Coturn para OpenMeetings 5.0.0-M4 en
CentOS 7-8.pdf
...y
Instalacion certificados SSL y Coturn para OpenMeetings 5.0.0-M4 en
Ubuntu 18.04.pdf

...y los he vuelto a subir a:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=278373
03
...ahí se encuentran a vuestra disposición.
Gracias a Maxim por haberlo comentado.
Saludos
Alvaro

...
El jue, 23-04-2020 a las 18:19 +0200, Alvaro escribió:
> Hola,
> Se encuentra a vuestra disposición dos nuevos tutoriales llamados:
> 
> Instalacion certificados SSL y Coturn para OpenMeetings 5.0.0-M4 en
> CentOS 7-8.pdf
> ...y
> Instalacion certificados SSL y Coturn para OpenMeetings 5.0.0-M4 en
> Ubuntu 18.04.pdf
> 
> Están testeados con un servidor OpenMeetings 5.0.0-M4 instalado en un
> pcen casa, tras NAT router, y cada uno en sala veía y oia a las
> demáscámaras y la suya propia correctamente.Así mismo en las pruebas
> hechas, hemos subido archivos, grabado videoy compartido escritorio
> sin error alguno.
> Pueden encontrarlos en: https://cwiki.apache.org/confluence/pages/vie
> wpage.action?pageId=27837303
> Saludos
> Alvaro
> 
> .
> 
> 
>

Re: Новые учебники Установка SSL сертификаты и Coturn для OpenMeetings 5.0.0-M4

.. в российском списке рассылки Константин дает представление опомочь
решить проблему повторного подключения на сервере Turn:
"stale-nonce=0" (/etc/turnserver.conf)
'добавил этот параметр в учебники:

Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
CentOS 7-8.pdf
...И
Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
Ubuntu 18.04.pdf

... и перезагружены на:

https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+
installing+OpenMeetings+and+Tools

Там он в вашем распоряжении.
Спасибо Максиму, чтобы прокомментировать это.
Отношении
Альваро

--

El jue, 23-04-2020 a las 18:19 +0200, Alvaro escribió:
> 
> Привет
> В вашем распоряжении новые учебники под названием:
> 
> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
> CentOS 7-8.pdf
> ...и
> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
> Ubuntu 18.04.pdf
> 
> Он тестируется с сервером OpenMeetings 5.0.0-M4, установленным на
> пкдома, после маршрутизатора NAT; и каждый в комнате увидел и услышал
> другиекамеры и ваши собственные правильно.Кроме того, в тестах
> сделано, мы загрузили файлы, записанное видеои общий рабочий стол без
> каких-либо ошибок.
> Вы можете скачать учебник прямо здесь:
> 
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+fo
> r+installing+OpenMeetings+and+Tools
> 
> Всего хорошего
> Альваро
> 
> 
> ...

About invitation

Is it okay to send an invitation to this mailing list so that multiple 
users can make use of that invitation to attend the room?


Greetings.

Re: [DISCUSSION] next release