Re: Premium templates and themes

[Peter Dähn]

Hi,

general here: https://openmeetings.apache.org/themes-and-branding.html

special here: 
https://cwiki.apache.org/confluence/display/OPENMEETINGS/Custom+Themes


custom Theme by now for OM4 and om5 before bootstrap (should be M3)

Greetings Peter

Am 30.03.20 um 13:37 schrieb Hassan Ayoub:

Hello,
1- Is there a place I can find premium themes and templates for openmeetings?
2- For editing the template structure and theme, is jquery, css, html is 
enoufgh or it should be done on the java level and rebuilding the code?
Thanks in advanced

Re: Можно ли вам задать вопрос по openmeetings ?

[Maxim Solodovnik]

Доброй ночи

нужно послать письмо с любым заголовком на
user-russian-subscr...@openmeetings.apache.org
дождаться письма от робота
сделать что говорит

потом можно писать :)

On Wed, 1 Apr 2020 at 22:32, oleg ivanov  wrote:

> Добрый день !
> Можно ли вам задать вопрос по openmeetings по почте?
> Пробывал через user-russian@openmeetings.apache.org
>  но
> что то не получается или я не умею пользоваться.
>
>
>


-- 
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

should be fixed

On Wed, 1 Apr 2020 at 21:58, Maxim Solodovnik  wrote:

> My bad
> Doesn't test it (github issue already reported)
> Will take a look
>
>
> On Wed, Apr 1, 2020, 21:56 Orm Finnendahl <
> orm.finnend...@selma.hfmdk-frankfurt.de> wrote:
>
>> Hi,
>>
>>  latest commit (M4) doesn't build on our machine.
>>
>> Building stops here:
>>
>> Step 33/38 : RUN cat /etc/issue && echo "OM server of type ${OM_TYPE}
>> will be built" && apt-get update && apt-get install -y
>> --no-install-recommends apt-utils   && apt-get install -y
>> --no-install-recommends software-properties-common gnupg2
>>  dirmngr unzip wget ghostscript libgs-dev imagemagick
>>sox sudo libreoffice openjdk-11-jre ffmpeg   && apt-get
>> clean   && rm -rf /var/lib/apt/lists/* && && wget
>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/lastSuccessfulBuild/artifact/openmeetings-server/target/apache-openmeetings-${OM_VERSION}-SNAPSHOT.tar.gz
>> -O ${work}/om.tar.gz   && tar -xzf ${work}/om.tar.gz --strip-components=1
>> -C ${OM_HOME}/   && rm -rf ${work}/om.tar.gz   && wget
>> https://repo1.maven.org/maven2/mysql/mysql-connector-java/${MYSQL_J_VER}/mysql-connector-java-${MYSQL_J_VER}.jar
>> -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && wget
>> https://repo1.maven.org/maven2/com/ibm/db2/jcc/${DB2_J_VER}/jcc-${DB2_J_VER}.jar
>> -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && sed -i 's|> domain="coder" rights="none" pattern="PS" />||g'
>> /etc/ImageMagick-6/policy.xml
>>  ---> Running in 6017fe8f01b5
>> /bin/sh: 1: Syntax error: "&&" unexpected
>> The command '/bin/sh -c cat /etc/issue && echo "OM server of type
>> ${OM_TYPE} will be built" && apt-get update && apt-get install -y
>> --no-install-recommends apt-utils   && apt-get install -y
>> --no-install-recommends software-properties-common gnupg2
>>  dirmngr unzip wget ghostscript libgs-dev imagemagick
>>sox sudo libreoffice openjdk-11-jre ffmpeg   && apt-get
>> clean   && rm -rf /var/lib/apt/lists/* && && wget
>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/lastSuccessfulBuild/artifact/openmeetings-server/target/apache-openmeetings-${OM_VERSION}-SNAPSHOT.tar.gz
>> -O ${work}/om.tar.gz   && tar -xzf ${work}/om.tar.gz --strip-components=1
>> -C ${OM_HOME}/   && rm -rf ${work}/om.tar.gz   && wget
>> https://repo1.maven.org/maven2/mysql/mysql-connector-java/${MYSQL_J_VER}/mysql-connector-java-${MYSQL_J_VER}.jar
>> -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && wget
>> https://repo1.maven.org/maven2/com/ibm/db2/jcc/${DB2_J_VER}/jcc-${DB2_J_VER}.jar
>> -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && sed -i 's|> domain="coder" rights="none" pattern="PS" />||g'
>> /etc/ImageMagick-6/policy.xml' returned a non-zero code: 2
>>
>> openmeetings-docker#
>>
>> Looks like a typo. The prevous git commit (M3.1) built without
>> problems.
>>
>> --
>> Orm
>>
>>

-- 
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

My bad
Doesn't test it (github issue already reported)
Will take a look


On Wed, Apr 1, 2020, 21:56 Orm Finnendahl <
orm.finnend...@selma.hfmdk-frankfurt.de> wrote:

> Hi,
>
>  latest commit (M4) doesn't build on our machine.
>
> Building stops here:
>
> Step 33/38 : RUN cat /etc/issue && echo "OM server of type ${OM_TYPE}
> will be built" && apt-get update && apt-get install -y
> --no-install-recommends apt-utils   && apt-get install -y
> --no-install-recommends software-properties-common gnupg2
>  dirmngr unzip wget ghostscript libgs-dev imagemagick
>sox sudo libreoffice openjdk-11-jre ffmpeg   && apt-get
> clean   && rm -rf /var/lib/apt/lists/* && && wget
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/lastSuccessfulBuild/artifact/openmeetings-server/target/apache-openmeetings-${OM_VERSION}-SNAPSHOT.tar.gz
> -O ${work}/om.tar.gz   && tar -xzf ${work}/om.tar.gz --strip-components=1
> -C ${OM_HOME}/   && rm -rf ${work}/om.tar.gz   && wget
> https://repo1.maven.org/maven2/mysql/mysql-connector-java/${MYSQL_J_VER}/mysql-connector-java-${MYSQL_J_VER}.jar
> -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && wget
> https://repo1.maven.org/maven2/com/ibm/db2/jcc/${DB2_J_VER}/jcc-${DB2_J_VER}.jar
> -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && sed -i 's| domain="coder" rights="none" pattern="PS" />||g'
> /etc/ImageMagick-6/policy.xml
>  ---> Running in 6017fe8f01b5
> /bin/sh: 1: Syntax error: "&&" unexpected
> The command '/bin/sh -c cat /etc/issue && echo "OM server of type
> ${OM_TYPE} will be built" && apt-get update && apt-get install -y
> --no-install-recommends apt-utils   && apt-get install -y
> --no-install-recommends software-properties-common gnupg2
>  dirmngr unzip wget ghostscript libgs-dev imagemagick
>sox sudo libreoffice openjdk-11-jre ffmpeg   && apt-get
> clean   && rm -rf /var/lib/apt/lists/* && && wget
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/lastSuccessfulBuild/artifact/openmeetings-server/target/apache-openmeetings-${OM_VERSION}-SNAPSHOT.tar.gz
> -O ${work}/om.tar.gz   && tar -xzf ${work}/om.tar.gz --strip-components=1
> -C ${OM_HOME}/   && rm -rf ${work}/om.tar.gz   && wget
> https://repo1.maven.org/maven2/mysql/mysql-connector-java/${MYSQL_J_VER}/mysql-connector-java-${MYSQL_J_VER}.jar
> -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && wget
> https://repo1.maven.org/maven2/com/ibm/db2/jcc/${DB2_J_VER}/jcc-${DB2_J_VER}.jar
> -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && sed -i 's| domain="coder" rights="none" pattern="PS" />||g'
> /etc/ImageMagick-6/policy.xml' returned a non-zero code: 2
>
> openmeetings-docker#
>
> Looks like a typo. The prevous git commit (M3.1) built without
> problems.
>
> --
> Orm
>
>

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Orm Finnendahl]

Hi,

 latest commit (M4) doesn't build on our machine.

Building stops here:

Step 33/38 : RUN cat /etc/issue && echo "OM server of type ${OM_TYPE} will 
be built" && apt-get update && apt-get install -y --no-install-recommends   
  apt-utils   && apt-get install -y --no-install-recommends 
software-properties-common gnupg2 dirmngr unzip wget 
ghostscript libgs-dev imagemagick sox sudo libreoffice 
openjdk-11-jre ffmpeg   && apt-get clean   && rm -rf /var/lib/apt/lists/*   
  && && wget 
https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/lastSuccessfulBuild/artifact/openmeetings-server/target/apache-openmeetings-${OM_VERSION}-SNAPSHOT.tar.gz
 -O ${work}/om.tar.gz   && tar -xzf ${work}/om.tar.gz --strip-components=1 -C 
${OM_HOME}/   && rm -rf ${work}/om.tar.gz   && wget 
https://repo1.maven.org/maven2/mysql/mysql-connector-java/${MYSQL_J_VER}/mysql-connector-java-${MYSQL_J_VER}.jar
 -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && wget 
https://repo1.maven.org/maven2/com/ibm/db2/jcc/${DB2_J_VER}/jcc-${DB2_J_VER}.jar
 -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && sed -i 's|||g' 
/etc/ImageMagick-6/policy.xml
 ---> Running in 6017fe8f01b5
/bin/sh: 1: Syntax error: "&&" unexpected
The command '/bin/sh -c cat /etc/issue && echo "OM server of type 
${OM_TYPE} will be built" && apt-get update && apt-get install -y 
--no-install-recommends apt-utils   && apt-get install -y 
--no-install-recommends software-properties-common gnupg2 dirmngr   
  unzip wget ghostscript libgs-dev imagemagick sox sudo 
libreoffice openjdk-11-jre ffmpeg   && apt-get clean   && rm -rf 
/var/lib/apt/lists/* && && wget 
https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/lastSuccessfulBuild/artifact/openmeetings-server/target/apache-openmeetings-${OM_VERSION}-SNAPSHOT.tar.gz
 -O ${work}/om.tar.gz   && tar -xzf ${work}/om.tar.gz --strip-components=1 -C 
${OM_HOME}/   && rm -rf ${work}/om.tar.gz   && wget 
https://repo1.maven.org/maven2/mysql/mysql-connector-java/${MYSQL_J_VER}/mysql-connector-java-${MYSQL_J_VER}.jar
 -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && wget 
https://repo1.maven.org/maven2/com/ibm/db2/jcc/${DB2_J_VER}/jcc-${DB2_J_VER}.jar
 -P ${OM_HOME}/webapps/openmeetings/WEB-INF/lib   && sed -i 's|||g' 
/etc/ImageMagick-6/policy.xml' returned a non-zero code: 2

openmeetings-docker#

Looks like a typo. The prevous git commit (M3.1) built without
problems.

--
Orm

Re: M4 release date? low-latency kernel?

[Maxim Solodovnik]

Well I can check the params if you send me the command :)

This server was rented years ago @Hetzner (sponsored by my employer)
And still cost something about 50euro per month :)

On Wed, 1 Apr 2020 at 18:57,  wrote:

> Hello,
>
> You must have NVMe disks on your demo next server - it is so fast. :)
>
> We'll then I'll test the latest build of M4 ona low-latency kernel.
>
> Ubuntu makes a few low-latency kernels for audio and video recording (for
> example Ubuntu Studio) - because they have very low latency - like 1-2 ms -
> so I'll test that too on M4, adn I'll let the group know if there is a
> noticable improvement in response time.
>
> I'm going to have to use either the M3 or latest M4 in production starting
> on Monday!
>
> Best,
>
> ed
>
> Quoting Maxim Solodovnik :
>
> Hello Ed,
>
> On Wed, 1 Apr 2020 at 16:33,  wrote:
>
>>   Hello Maxime,
>>
>> Do you have a date planned for the M4 release?
>>
>
> In case all blockers will be resolved
> And there will be none of new blockers
> I hope to perform M4 release in couple of weeks
>
>
>>
>> Do you have a tentative date for the 5.0.0 stable release?
>>
>
> This actually depends on critical issues reported
> I was hoping M2 will be the last one 
> we will see :))
>
>
>>
>> Is M4 actually a release candidate ? the last one?
>>
>
> please see above
>
>
>>
>> Lastly, I notice that your test server (demo-next) is very fast and
>> very responsive. Are you using a low-latency kernel there? If not, has
>> anyne tested ubuntu low-latency kernel with OpenMeetings 5.0.0 M3 or M4?
>>
>
> Well,
> It is dedicated server with 24G RAM and 8cores CPU
> I'm not sure what low-lanency kernel is :(
>
>
>
>>
>> Thank you,
>>
>>   Ed
>>
>> Quoting Daniel Baker :
>>
>> >
>> >
>> >   I installed it  with a new mysql database   (no backup and import
>> > ) and  get this :
>> >
>> >   I have not set  up letencrypt yet so the cameras won't turn on
>> > which might explain bottom right error.
>> >
>> >
>> >
>> >   I am aiming to test the new   Moodle  Plugin
>> >  Name OpenMeetings
>> >
>> >  Version 5.0.0-M4-SNAPSHOT
>> >
>> >  Revision fd1ca91
>> >
>> >  Build date 2020-03-31T08:53:30Z
>> >
>> >
>> >
>> >
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>

-- 
WBR
Maxim aka solomax

Re: M4 release date? low-latency kernel?

[info]

 Hello,

You must have NVMe disks on your demo next server - it is so fast. :)

 We'll then I'll test the latest build of M4 ona low-latency kernel.  

Ubuntu makes a few low-latency kernels for audio and video recording  
(for example Ubuntu Studio) - because they have very low latency -  
like 1-2 ms - so I'll test that too on M4, adn I'll let the group know  
if there is a noticable improvement in response time.


I'm going to have to use either the M3 or latest M4 in production  
starting on Monday!


Best,

 ed

Quoting Maxim Solodovnik :


Hello Ed,

   On Wed, 1 Apr 2020 at 16:33,  wrote:


  Hello Maxime,

Do you have a date planned for the M4 release?


 
In case all blockers will be resolved
And there will be none of new blockers
I hope to perform M4 release in couple of weeks
 


Do you have a tentative date for the 5.0.0 stable release?  


 
This actually depends on critical issues reported
I was hoping M2 will be the last one 
we will see :))
 


Is M4 actually a release candidate ? the last one?


 
please see above
 


Lastly, I notice that your test server (demo-next) is very fast and 
very responsive. Are you using a low-latency kernel there? If not, has 
anyne tested ubuntu low-latency kernel with OpenMeetings 5.0.0 M3 or M4?


 
Well,
It is dedicated server with 24G RAM and 8cores CPU
I'm not sure what low-lanency kernel is :(
 
 


Thank you,

  Ed

Quoting Daniel Baker :


 

   I installed it  with a new mysql database   (no backup and import 
) and  get this :

   I have not set  up letencrypt yet so the cameras won't turn on 
which might explain bottom right error.

    

   I am aiming to test the new   Moodle  Plugin
      Name OpenMeetings

      Version 5.0.0-M4-SNAPSHOT

      Revision fd1ca91

      Build date 2020-03-31T08:53:30Z

    

    


    
--
   WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

should be done :)

On Wed, 1 Apr 2020 at 16:18, Daniel Baker 
wrote:

> Thank you !
> On 01/04/2020 10:16, Maxim Solodovnik wrote:
>
> Yes sure :)
> Will do it with low priority :)
>
> On Wed, 1 Apr 2020 at 16:14, Daniel Baker 
> wrote:
>
>> I think  you have  build  instructions  on the github page so I can  use
>> those ?
>> On 01/04/2020 10:12, Maxim Solodovnik wrote:
>>
>> Sure,
>> I can switch master to use M4-SNAPSHOT
>> But you have to build it on your machine before use ...
>>
>> Is it OK?
>>
>> On Wed, 1 Apr 2020 at 16:09, Daniel Baker 
>> wrote:
>>
>>> Could  I  use  the  alpha/ next  / M4  version?
>>>
>>> apache/openmeetings:5.0.0-M3
>>>
>>>
>>> Thanks,
>>>
>>>
>>> Dan
>>>
>>>
>>>
>>> On 01/04/2020 09:56, Maxim Solodovnik wrote:
>>>
>>> I mean run
>>> ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p :
>>> -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
>>> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3.1
>>> instead of
>>> ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p :
>>> -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
>>> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>>>
>>> :))
>>>
>>> On Wed, 1 Apr 2020 at 15:40, Maxim Solodovnik 
>>> wrote:
>>>
 Well it would be too expensive
 Thanks :)))
 Hopefully I can visit Europe when the corona pandemic will be over :))

 Please try 5.0.0-M3.1
 Hopefully will work :)

 On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang 
 wrote:

> 
> Can you tell me how to build this commit locally?
>
>
>
>
>
>
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Mittwoch, 1. April 2020 09:12
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> I'm stupid russian monkey :(((
>
>
>
> full dockerized M3 has bug :(((
>
> It was fixed by this
> https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
>  commit
>
> This is why TURN_URL is NOT working :(((
>
>
>
> Not sure if I can drop current M3 image, will try to
>
> As a workaround - you can rebuild locally ...
>
>
>
> On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang 
> wrote:
>
> First of all: Thx to you for helping me. I am up now again and give it
> the next try
>
>
>
> Here is my non dockerized coturn config
>
>
>
> root@docker-ibb-01:/var/log# cat /etc/turnserver.conf
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> lt-cred-mech
>
> use-auth-secret
>
> static-auth-secret=somegibberishtext
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
>
>
> I started the OM Conatiner with
>
>
>
> root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm
> --expose=5443 --expose= -p 5443:5443 -p : -e
> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>
>
>
> xxx.xxx.xxx.xxx is my external ip
>
>
>
>
>
> No audio, video
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Mittwoch, 1. April 2020 05:34
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> Well
>
> Usually it all ends up on second or third email 
>
> Maybe you can try with non-dockerized-turnserver ?
>
>
>
> On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang 
> wrote:
>
> I give up for now. This is annoying.
>
> Why things must be so complicated :-(
>
>
>
> I tested for open ports. I openend all outgoing ports for the host
> where coturn and the Docker OM Container is.
>
>
>
> Is there a step by step way to test?
>
>
>
> It is such an unormal setup?
>
>
>
>
>
> Wolfgang
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>


 --
 WBR
 Maxim aka solomax

>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>
> --
> WBR
> Maxim aka solomax
>
>

-- 
WBR
Maxim aka solomax

Re: M4 release date? low-latency kernel?

[Maxim Solodovnik]

Hello Ed,

On Wed, 1 Apr 2020 at 16:33,  wrote:

>   Hello Maxime,
>
> Do you have a date planned for the M4 release?
>

In case all blockers will be resolved
And there will be none of new blockers
I hope to perform M4 release in couple of weeks


>
> Do you have a tentative date for the 5.0.0 stable release?
>

This actually depends on critical issues reported
I was hoping M2 will be the last one 
we will see :))


>
> Is M4 actually a release candidate ? the last one?
>

please see above


>
> Lastly, I notice that your test server (demo-next) is very fast and
> very responsive. Are you using a low-latency kernel there? If not, has
> anyne tested ubuntu low-latency kernel with OpenMeetings 5.0.0 M3 or M4?
>

Well,
It is dedicated server with 24G RAM and 8cores CPU
I'm not sure what low-lanency kernel is :(



>
> Thank you,
>
>   Ed
>
> Quoting Daniel Baker :
>
> >
> >
> >   I installed it  with a new mysql database   (no backup and import
> > ) and  get this :
> >
> >   I have not set  up letencrypt yet so the cameras won't turn on
> > which might explain bottom right error.
> >
> >
> >
> >   I am aiming to test the new   Moodle  Plugin
> >  Name OpenMeetings
> >
> >  Version 5.0.0-M4-SNAPSHOT
> >
> >  Revision fd1ca91
> >
> >  Build date 2020-03-31T08:53:30Z
> >
> >
> >
> >
>


-- 
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

Great news :))
Can you also check if coturn-docker also works?

On Wed, 1 Apr 2020 at 16:34, Arndt, Wolfgang 
wrote:

> Heureka!
>
> It is working now, i have audio and video.
>
>
>
> Big thank you!
>
>
>
> Now can i test it!
>
>
>
>
>
>
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Mittwoch, 1. April 2020 10:57
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> I mean run
>
> ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p : -e
> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3.1
>
> instead of
>
> ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p : -e
> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>
>
>
> :))
>
>
>
> On Wed, 1 Apr 2020 at 15:40, Maxim Solodovnik 
> wrote:
>
> Well it would be too expensive
>
> Thanks :)))
>
> Hopefully I can visit Europe when the corona pandemic will be over :))
>
>
>
> Please try 5.0.0-M3.1
>
> Hopefully will work :)
>
>
>
> On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang 
> wrote:
>
> 
> Can you tell me how to build this commit locally?
>
>
>
>
>
>
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Mittwoch, 1. April 2020 09:12
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> I'm stupid russian monkey :(((
>
>
>
> full dockerized M3 has bug :(((
>
> It was fixed by this
> https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
>  commit
>
> This is why TURN_URL is NOT working :(((
>
>
>
> Not sure if I can drop current M3 image, will try to
>
> As a workaround - you can rebuild locally ...
>
>
>
> On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang 
> wrote:
>
> First of all: Thx to you for helping me. I am up now again and give it the
> next try
>
>
>
> Here is my non dockerized coturn config
>
>
>
> root@docker-ibb-01:/var/log# cat /etc/turnserver.conf
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> lt-cred-mech
>
> use-auth-secret
>
> static-auth-secret=somegibberishtext
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
>
>
> I started the OM Conatiner with
>
>
>
> root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm
> --expose=5443 --expose= -p 5443:5443 -p : -e
> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>
>
>
> xxx.xxx.xxx.xxx is my external ip
>
>
>
>
>
> No audio, video
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Mittwoch, 1. April 2020 05:34
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> Well
>
> Usually it all ends up on second or third email 
>
> Maybe you can try with non-dockerized-turnserver ?
>
>
>
> On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang 
> wrote:
>
> I give up for now. This is annoying.
>
> Why things must be so complicated :-(
>
>
>
> I tested for open ports. I openend all outgoing ports for the host where
> coturn and the Docker OM Container is.
>
>
>
> Is there a step by step way to test?
>
>
>
> It is such an unormal setup?
>
>
>
>
>
> Wolfgang
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

Re: Suggested AWS EC2 setup - OM 5.0.0 M3 / Ubuntu 18.04

[Maxim Solodovnik]

This "the user’s cam and audio dropped (it could be after 3, 5 8, 15 mins…
no pattern)" observation is super useful!
Thanks for that
There are lots of complains regarding such drops
Will ask users to report their browsers :)

On Wed, 1 Apr 2020 at 16:32, Daniel Baker 
wrote:

> Wow  thanks.  will give  this  a  try.
>
> Did you consider making a AWS CloudFormation
>   template ?
>
>
> Thanks,
>
>
> Dan
> On 01/04/2020 10:20, Denis Noctor wrote:
>
> Hi there everyone,
>
> I thought this email might be of some interest to those setting up OM on
> an AWS EC2 instance using Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-1063-aws
> x86_64). There are lots of tutorials online regarding how to setup an AWS
> EC2 instance, so there is no need for me to talk about that. I am assuming
> you have this up and running.
>
> However there are lots of *free* AMIs (Amazon Machine Images) in AWS that
> can be automatically installed which will install a LAMP image (Linux,
> Apache, MySQL, and PHP setup) and the one I used was:
> “ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20190212.1
> (ami-0a313d6098716f372)”
>
>  I will have to update my PHP version at some stage though.
>
> My AWS Setup is as follows:
> Instance type: t3a.large (8 gigs Ram , 2 vCPUS), I was previously using a
> t3a.medium (4 gigs Ram , 2 vCPUS)… which seemed to run okay… but needed to
> elimate any doubts I had by cranking up the RAM. Some of you may decide to
> go for lower or higher instances depending on your budget and desired
> performance levels etc.
>
> It is also important to note that I am using an Elastic IP address, which
> basically means the IP address of my domain will never change and as a
> result my registered domain name, for example “ABC.COM” will be directed
> to this IP address…. Even if I “stop” my server to save money.
>
> I am also using a “AWS load balancer” which also entitles me to a free
> certificate which automatically renews every 12 months when set up (again
> lots of info on the internet about this)  - which is an IMPORTANT POINT as
> I am not using LetsEncrypt… AND AS A RESULT DEVIATE FROM ALVARO’S WONDERFUL
> INSTRUCTIONS.
>
> Let’s begin…
>
> If you are setting up a clean install… simply follow Alvaro’s instructions
> via this link:
>
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools?preview=/27838216/140774282/Installation%20OpenMeetings%205.0.0-M3%20on%20Ubuntu%2018.04%20LTS.pdf
>
> Again, this is for OM 5.0.0-M3. If you wish to update to further snapshots
> please refer to the official website, forums and links.
>
> Please note the current version of Alvaro’s PDF… at the time of writing it
> was v6.
>
> (Assuming you have already got an AWS certificate:  you can setup your
> domain as https… redirecting all http to https…. I recommend you do this
> before).
>
> NEXT STAGE – SETTING UP THE TURN SERVER.
>
> I had originally used a free TURN server service… using
> https://numb.viagenie.ca/  whereby you can setup an account… and had
> tested it… and it seemed to be okay…. But I don’t like to be dependent on a
> 3rd party… especially when it comes to testing… I decided to set up my
> own… on the same AWS EC2 instance.
>
> Please refer to Alvaro’s additional setup regarding “Installation SSL
> certificates and Coturn for OpenMeetings 5.0.0-M3”… via the following link
> --- BUT PLEASE NOTE WE ARE NOT GOING TO FOLLOW ALL THE INSTRUCTIONS TO THE
> LETTER:
>
>
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools?preview=/27838216/148644256/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
>
> As I am using an AWS certificate, I am going to bypass / ignore all
> references to “letsencrypt”… and here is the why… with AWS certificates you
> have no control over them… you cannot download the certificate and store it
> on your server… you cannot download files, like in “letsencrypt” in
> Alvaro’s example … you have no access to “fullchain.pem”, “privkey.pem”.
> These files are stored elsewhere in AWS... but are automatically detected
> and enforced by AWS… (you could use Letsencrypt as an alternative
> certificate source but this is not what this email is all about… and I
> haven’t had the need to test it.)
>
> SKIP PARTS 1,2,3 AND 4 of Alvaro’s tutorial in “Installation SSL
> certificates and Coturn for OpenMeetings 5.0.0-M3”… and go straight to part
> (5)… do as instructed.
>
> In part (6) of the tutorial I decided not to change the user name in the
> following as I had already set up the user name in the original OM 5.0.0 M3
> instructions (“nobody”):
> so instead of making the change:
> *user=kurento:a_new_password*
>
> I changed it to user=nobody:a_new_password
>
> making all the other changes in part (6) as stated.
>
> I *DID NOT *implement changes in part (7)  regarding
>  DAEMON_USER="kurento"… I left it as "nobody"
>
>
>
> However, I 

AW: Openmeetings Docker Image / Kurento / Turn / NAT

[Arndt , Wolfgang]

Heureka!

It is working now, i have audio and video.

 
Big thank you!

 
Now can i test it!

 
 
 
 
 
Von: Maxim Solodovnik 
Gesendet: Mittwoch, 1. April 2020 10:57
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
I mean run

ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p : -e 
TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e 
TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3.1

instead of

ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p : -e 
TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e 
TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3

 
:))

 
On Wed, 1 Apr 2020 at 15:40, Maxim Solodovnik  wrote:

Well it would be too expensive

Thanks :)))

Hopefully I can visit Europe when the corona pandemic will be over :))

 
Please try 5.0.0-M3.1

Hopefully will work :) 

 
On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang mailto:ar...@lernenfoerdern.de> > wrote:


Can you tell me how to build this commit locally?

 
 
 
 
 
Von: Maxim Solodovnik mailto:solomax...@gmail.com> >
Gesendet: Mittwoch, 1. April 2020 09:12
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
I'm stupid russian monkey :(((

 
full dockerized M3 has bug :(((

It was fixed by this 
https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
 commit

This is why TURN_URL is NOT working :(((

 
Not sure if I can drop current M3 image, will try to

As a workaround - you can rebuild locally ...

 
On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang  wrote:

First of all: Thx to you for helping me. I am up now again and give it the next 
try

 
Here is my non dockerized coturn config

 
root@docker-ibb-01:/var/log# cat /etc/turnserver.conf

listening-port=3478

verbose

fingerprint

lt-cred-mech

use-auth-secret

static-auth-secret=somegibberishtext

simple-log

log-file=/var/log/turn.log

min-port=49152

max-port=55000

 
 
I started the OM Conatiner with

 
root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm --expose=5443 
--expose= -p 5443:5443 -p : -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e 
TURN_USER="kurento" -e TURN_PASS="somegibberishtext" 
apache/openmeetings:5.0.0-M3

 
xxx.xxx.xxx.xxx is my external ip

 
 
No audio, video

 
 
Von: Maxim Solodovnik mailto:solomax...@gmail.com> >
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
Well

Usually it all ends up on second or third email 

Maybe you can try with non-dockerized-turnserver ?

 
On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang  wrote:

I give up for now. This is annoying.

Why things must be so complicated :-(

 
I tested for open ports. I openend all outgoing ports for the host where coturn 
and the Docker OM Container is.

 
Is there a step by step way to test?

 
It is such an unormal setup?

 
 
Wolfgang

 
 
 
 
 
 
 
 


 
--

WBR
Maxim aka solomax



 
--

WBR
Maxim aka solomax



 
--

WBR
Maxim aka solomax



 
--

WBR
Maxim aka solomax

M4 release date? low-latency kernel?

[info]

 Hello Maxime,

Do you have a date planned for the M4 release?

Do you have a tentative date for the 5.0.0 stable release?  

Is M4 actually a release candidate ? the last one?

Lastly, I notice that your test server (demo-next) is very fast and  
very responsive. Are you using a low-latency kernel there? If not, has  
anyne tested ubuntu low-latency kernel with OpenMeetings 5.0.0 M3 or M4?


Thank you,

 Ed

Quoting Daniel Baker :


 

  I installed it  with a new mysql database   (no backup and import  
) and  get this :


  I have not set  up letencrypt yet so the cameras won't turn on  
which might explain bottom right error.


   

  I am aiming to test the new   Moodle  Plugin
 Name OpenMeetings

 Version 5.0.0-M4-SNAPSHOT

 Revision fd1ca91

 Build date 2020-03-31T08:53:30Z

   

   

Re: Suggested AWS EC2 setup - OM 5.0.0 M3 / Ubuntu 18.04

[Daniel Baker]

Wow  thanks.  will give  this  a  try.

Did you consider making a AWS CloudFormation 
  template ?



Thanks,


Dan

On 01/04/2020 10:20, Denis Noctor wrote:


Hi there everyone,

I thought this email might be of some interest to those setting up OM 
on an AWS EC2 instance using Ubuntu 18.04.4 LTS (GNU/Linux 
4.15.0-1063-aws x86_64). There are lots of tutorials online regarding 
how to setup an AWS EC2 instance, so there is no need for me to talk 
about that. I am assuming you have this up and running.


However there are lots of _free_ AMIs (Amazon Machine Images) in AWS 
that can be automatically installed which will install a LAMP image 
(Linux, Apache, MySQL, and PHP setup) and the one I used was:
“ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20190212.1 
(ami-0a313d6098716f372)”


 I will have to update my PHP version at some stage though.

My AWS Setup is as follows:
Instance type: t3a.large (8 gigs Ram , 2 vCPUS), I was previously 
using a t3a.medium (4 gigs Ram , 2 vCPUS)… which seemed to run okay… 
but needed to elimate any doubts I had by cranking up the RAM. Some of 
you may decide to go for lower or higher instances depending on your 
budget and desired performance levels etc.


It is also important to note that I am using an Elastic IP address, 
which basically means the IP address of my domain will never change 
and as a result my registered domain name, for example “ABC.COM 
” will be directed to this IP address…. Even if I 
“stop” my server to save money.


I am also using a “AWS load balancer” which also entitles me to a free 
certificate which automatically renews every 12 months when set up 
(again lots of info on the internet about this)  - which is an 
IMPORTANT POINT as I am not using LetsEncrypt… AND AS A RESULT DEVIATE 
FROM ALVARO’S WONDERFUL INSTRUCTIONS.


Let’s begin…

If you are setting up a clean install… simply follow Alvaro’s 
instructions via this link:

https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools?preview=/27838216/140774282/Installation%20OpenMeetings%205.0.0-M3%20on%20Ubuntu%2018.04%20LTS.pdf

Again, this is for OM 5.0.0-M3. If you wish to update to further 
snapshots please refer to the official website, forums and links.


Please note the current version of Alvaro’s PDF… at the time of 
writing it was v6.


(Assuming you have already got an AWS certificate:  you can setup your 
domain as https… redirecting all http to https…. I recommend you do 
this before).


NEXT STAGE – SETTING UP THE TURN SERVER.

I had originally used a free TURN server service… using 
https://numb.viagenie.ca/ whereby you can setup an account… and had 
tested it… and it seemed to be okay…. But I don’t like to be dependent 
on a 3^rd party… especially when it comes to testing… I decided to set 
up my own… on the same AWS EC2 instance.


Please refer to Alvaro’s additional setup regarding “Installation SSL 
certificates and Coturn for OpenMeetings 5.0.0-M3”… via the following 
link --- BUT PLEASE NOTE WE ARE NOT GOING TO FOLLOW ALL THE 
INSTRUCTIONS TO THE LETTER:


https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools?preview=/27838216/148644256/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf

As I am using an AWS certificate, I am going to bypass / ignore all 
references to “letsencrypt”… and here is the why… with AWS 
certificates you have no control over them… you cannot download the 
certificate and store it on your server… you cannot download files, 
like in “letsencrypt” in Alvaro’s example … you have no access to 
“fullchain.pem”, “privkey.pem”. These files are stored elsewhere in 
AWS... but are automatically detected and enforced by AWS… (you could 
use Letsencrypt as an alternative certificate source but this is not 
what this email is all about… and I haven’t had the need to test it.)


SKIP PARTS 1,2,3 AND 4 of Alvaro’s tutorial in “Installation SSL 
certificates and Coturn for OpenMeetings 5.0.0-M3”… and go straight to 
part (5)… do as instructed.


In part (6) of the tutorial I decided not to change the user name in 
the following as I had already set up the user name in the original OM 
5.0.0 M3 instructions (“nobody”):

so instead of making the change:
*user=kurento:a_new_password*

I changed it to user=nobody:a_new_password

making all the other changes in part (6) as stated.

I *_DID NOT _*implement changes in part (7) regarding 
 DAEMON_USER="kurento"… I left it as "nobody"


However, I did make changes to the 
/opt/open503/webapps/openmeetings/WEB-INF/classes/applicationContext.xml 
as follows:



class="org.apache.openmeetings.core.remote.KurentoHandler" 
init-method="init" destroy-method="destroy"


p:kurentoWsUrl="ws://127.0.0.1:/kurento 
"


p:checkTimeout="1"

p:watchThreadCount="10"

p:turnUrl="*PUBLIC IP 

Suggested AWS EC2 setup - OM 5.0.0 M3 / Ubuntu 18.04

[Denis Noctor]

Hi there everyone,

I thought this email might be of some interest to those setting up OM on an
AWS EC2 instance using Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-1063-aws
x86_64). There are lots of tutorials online regarding how to setup an AWS
EC2 instance, so there is no need for me to talk about that. I am assuming
you have this up and running.

However there are lots of *free* AMIs (Amazon Machine Images) in AWS that
can be automatically installed which will install a LAMP image (Linux,
Apache, MySQL, and PHP setup) and the one I used was:
“ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20190212.1
(ami-0a313d6098716f372)”

 I will have to update my PHP version at some stage though.

My AWS Setup is as follows:
Instance type: t3a.large (8 gigs Ram , 2 vCPUS), I was previously using a
t3a.medium (4 gigs Ram , 2 vCPUS)… which seemed to run okay… but needed to
elimate any doubts I had by cranking up the RAM. Some of you may decide to
go for lower or higher instances depending on your budget and desired
performance levels etc.

It is also important to note that I am using an Elastic IP address, which
basically means the IP address of my domain will never change and as a
result my registered domain name, for example “ABC.COM” will be directed to
this IP address…. Even if I “stop” my server to save money.

I am also using a “AWS load balancer” which also entitles me to a free
certificate which automatically renews every 12 months when set up (again
lots of info on the internet about this)  - which is an IMPORTANT POINT as
I am not using LetsEncrypt… AND AS A RESULT DEVIATE FROM ALVARO’S WONDERFUL
INSTRUCTIONS.

Let’s begin…

If you are setting up a clean install… simply follow Alvaro’s instructions
via this link:
https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools?preview=/27838216/140774282/Installation%20OpenMeetings%205.0.0-M3%20on%20Ubuntu%2018.04%20LTS.pdf

Again, this is for OM 5.0.0-M3. If you wish to update to further snapshots
please refer to the official website, forums and links.

Please note the current version of Alvaro’s PDF… at the time of writing it
was v6.

(Assuming you have already got an AWS certificate:  you can setup your
domain as https… redirecting all http to https…. I recommend you do this
before).

NEXT STAGE – SETTING UP THE TURN SERVER.

I had originally used a free TURN server service… using
https://numb.viagenie.ca/  whereby you can setup an account… and had tested
it… and it seemed to be okay…. But I don’t like to be dependent on a 3rd
party… especially when it comes to testing… I decided to set up my own… on
the same AWS EC2 instance.

Please refer to Alvaro’s additional setup regarding “Installation SSL
certificates and Coturn for OpenMeetings 5.0.0-M3”… via the following link
--- BUT PLEASE NOTE WE ARE NOT GOING TO FOLLOW ALL THE INSTRUCTIONS TO THE
LETTER:

https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools?preview=/27838216/148644256/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf

As I am using an AWS certificate, I am going to bypass / ignore all
references to “letsencrypt”… and here is the why… with AWS certificates you
have no control over them… you cannot download the certificate and store it
on your server… you cannot download files, like in “letsencrypt” in
Alvaro’s example … you have no access to “fullchain.pem”, “privkey.pem”.
These files are stored elsewhere in AWS... but are automatically detected
and enforced by AWS… (you could use Letsencrypt as an alternative
certificate source but this is not what this email is all about… and I
haven’t had the need to test it.)

SKIP PARTS 1,2,3 AND 4 of Alvaro’s tutorial in “Installation SSL
certificates and Coturn for OpenMeetings 5.0.0-M3”… and go straight to part
(5)… do as instructed.

In part (6) of the tutorial I decided not to change the user name in the
following as I had already set up the user name in the original OM 5.0.0 M3
instructions (“nobody”):
so instead of making the change:
*user=kurento:a_new_password*

I changed it to user=nobody:a_new_password

making all the other changes in part (6) as stated.

I *DID NOT *implement changes in part (7)  regarding
 DAEMON_USER="kurento"… I left it as "nobody"



However, I did make changes to the
/opt/open503/webapps/openmeetings/WEB-INF/classes/applicationContext.xml as
follows:




 Remember we are still in part (7)… after saving the changes to the above
(applicationContext.xml), I *DID NOT* make changes to

sudo chown -R kurento /opt/open503

I decided to keep it the same as per the original 5.0.0 M3 setup… (keeping
it as “nobody”)

I *DID NOT* modify:

sudo nano /etc/init.d/tomcat3

(i.e. changing “nobody” to “kurento”)

*AND FINALLY I MADE THE FOLLOWING CHANGE* – NOT IN THE STEPS:
/etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini

turnURL=* nobody*:*PASSWORD* @* PUBLIC IP ADDRESS OF AWS SERVER*:3478

Reboot 

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Daniel Baker]

Thank you !

On 01/04/2020 10:16, Maxim Solodovnik wrote:

Yes sure :)
Will do it with low priority :)

On Wed, 1 Apr 2020 at 16:14, Daniel Baker > wrote:


I think  you have  build  instructions  on the github page so I
can  use  those ?

On 01/04/2020 10:12, Maxim Solodovnik wrote:

Sure,
I can switch master to use M4-SNAPSHOT
But you have to build it on your machine before use ...

Is it OK?

On Wed, 1 Apr 2020 at 16:09, Daniel Baker
mailto:i...@collisiondetection.biz>> wrote:

Could  I  use  the  alpha/ next  / M4  version?

apache/openmeetings:5.0.0-M3


Thanks,


Dan



On 01/04/2020 09:56, Maxim Solodovnik wrote:

I mean run
ocker run -i --rm --expose=5443 --expose= -p 5443:5443
-p : -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e
TURN_USER="kurento" -e TURN_PASS="somegibberishtext"
apache/openmeetings:5.0.0-M3.1
instead of
ocker run -i --rm --expose=5443 --expose= -p 5443:5443
-p : -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e
TURN_USER="kurento" -e TURN_PASS="somegibberishtext"
apache/openmeetings:5.0.0-M3

:))

On Wed, 1 Apr 2020 at 15:40, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

Well it would be too expensive
Thanks :)))
Hopefully I can visit Europe when the corona pandemic
will be over :))

Please try 5.0.0-M3.1
Hopefully will work :)

On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang
mailto:ar...@lernenfoerdern.de>> wrote:


Can you tell me how to build this commit locally?

*Von:* Maxim Solodovnik mailto:solomax...@gmail.com>>
*Gesendet:* Mittwoch, 1. April 2020 09:12
*An:* Openmeetings user-list
mailto:user@openmeetings.apache.org>>
*Betreff:* Re: Openmeetings Docker Image / Kurento /
Turn / NAT

I'm stupid russian monkey :(((

full dockerized M3 has bug :(((

It was fixed by this

https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
 commit

This is why TURN_URL is NOT working :(((

Not sure if I can drop current M3 image, will try to

As a workaround - you can rebuild locally ...

On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang
mailto:ar...@lernenfoerdern.de>> wrote:

First of all: Thx to you for helping me. I am up
now again and give it the next try

Here is my non dockerized coturn config

root@docker-ibb-01:/var/log# cat
/etc/turnserver.conf

listening-port=3478

verbose

fingerprint

lt-cred-mech

use-auth-secret

static-auth-secret=somegibberishtext

simple-log

log-file=/var/log/turn.log

min-port=49152

max-port=55000

I started the OM Conatiner with

root@docker-ibb-01:/home/wolfgang/coturn# docker
run -i --rm --expose=5443 --expose= -p
5443:5443 -p : -e
TURN_URL="xxx.xxx.xxx.xxx:3478" -e
TURN_USER="kurento" -e
TURN_PASS="somegibberishtext"
apache/openmeetings:5.0.0-M3

xxx.xxx.xxx.xxx is my external ip

No audio, video

*Von:* Maxim Solodovnik mailto:solomax...@gmail.com>>
*Gesendet:* Mittwoch, 1. April 2020 05:34
*An:* Openmeetings user-list
mailto:user@openmeetings.apache.org>>
*Betreff:* Re: Openmeetings Docker Image /
Kurento / Turn / NAT

Well

Usually it all ends up on second or third email 

Maybe you can try with non-dockerized-turnserver ?

On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang
mailto:ar...@lernenfoerdern.de>> wrote:

I give up for now. This is annoying.

Why things must be so complicated :-(

I tested for open ports. I openend all
outgoing ports for the host where coturn and
the Docker OM Container is.

Is there a step by step way to test?

It is such an unormal setup?

Wolfgang


-- 


   

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

Yes sure :)
Will do it with low priority :)

On Wed, 1 Apr 2020 at 16:14, Daniel Baker 
wrote:

> I think  you have  build  instructions  on the github page so I can  use
> those ?
> On 01/04/2020 10:12, Maxim Solodovnik wrote:
>
> Sure,
> I can switch master to use M4-SNAPSHOT
> But you have to build it on your machine before use ...
>
> Is it OK?
>
> On Wed, 1 Apr 2020 at 16:09, Daniel Baker 
> wrote:
>
>> Could  I  use  the  alpha/ next  / M4  version?
>>
>> apache/openmeetings:5.0.0-M3
>>
>>
>> Thanks,
>>
>>
>> Dan
>>
>>
>>
>> On 01/04/2020 09:56, Maxim Solodovnik wrote:
>>
>> I mean run
>> ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p :
>> -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
>> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3.1
>> instead of
>> ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p :
>> -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
>> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>>
>> :))
>>
>> On Wed, 1 Apr 2020 at 15:40, Maxim Solodovnik 
>> wrote:
>>
>>> Well it would be too expensive
>>> Thanks :)))
>>> Hopefully I can visit Europe when the corona pandemic will be over :))
>>>
>>> Please try 5.0.0-M3.1
>>> Hopefully will work :)
>>>
>>> On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang 
>>> wrote:
>>>
 
 Can you tell me how to build this commit locally?











 *Von:* Maxim Solodovnik 
 *Gesendet:* Mittwoch, 1. April 2020 09:12
 *An:* Openmeetings user-list 
 *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT



 I'm stupid russian monkey :(((



 full dockerized M3 has bug :(((

 It was fixed by this
 https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
  commit

 This is why TURN_URL is NOT working :(((



 Not sure if I can drop current M3 image, will try to

 As a workaround - you can rebuild locally ...



 On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang 
 wrote:

 First of all: Thx to you for helping me. I am up now again and give it
 the next try



 Here is my non dockerized coturn config



 root@docker-ibb-01:/var/log# cat /etc/turnserver.conf

 listening-port=3478

 verbose

 fingerprint

 lt-cred-mech

 use-auth-secret

 static-auth-secret=somegibberishtext

 simple-log

 log-file=/var/log/turn.log

 min-port=49152

 max-port=55000





 I started the OM Conatiner with



 root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm
 --expose=5443 --expose= -p 5443:5443 -p : -e
 TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
 TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3



 xxx.xxx.xxx.xxx is my external ip





 No audio, video





 *Von:* Maxim Solodovnik 
 *Gesendet:* Mittwoch, 1. April 2020 05:34
 *An:* Openmeetings user-list 
 *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT



 Well

 Usually it all ends up on second or third email 

 Maybe you can try with non-dockerized-turnserver ?



 On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang 
 wrote:

 I give up for now. This is annoying.

 Why things must be so complicated :-(



 I tested for open ports. I openend all outgoing ports for the host
 where coturn and the Docker OM Container is.



 Is there a step by step way to test?



 It is such an unormal setup?





 Wolfgang




















 --

 WBR
 Maxim aka solomax




 --

 WBR
 Maxim aka solomax

>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>
> --
> WBR
> Maxim aka solomax
>
>

-- 
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Daniel Baker]

I think  you have  build  instructions  on the github page so I can  
use  those ?


On 01/04/2020 10:12, Maxim Solodovnik wrote:

Sure,
I can switch master to use M4-SNAPSHOT
But you have to build it on your machine before use ...

Is it OK?

On Wed, 1 Apr 2020 at 16:09, Daniel Baker > wrote:


Could  I  use  the  alpha/ next  / M4  version?

apache/openmeetings:5.0.0-M3


Thanks,


Dan



On 01/04/2020 09:56, Maxim Solodovnik wrote:

I mean run
ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p
: -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e
TURN_USER="kurento" -e TURN_PASS="somegibberishtext"
apache/openmeetings:5.0.0-M3.1
instead of
ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p
: -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e
TURN_USER="kurento" -e TURN_PASS="somegibberishtext"
apache/openmeetings:5.0.0-M3

:))

On Wed, 1 Apr 2020 at 15:40, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

Well it would be too expensive
Thanks :)))
Hopefully I can visit Europe when the corona pandemic will be
over :))

Please try 5.0.0-M3.1
Hopefully will work :)

On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang
mailto:ar...@lernenfoerdern.de>> wrote:


Can you tell me how to build this commit locally?

*Von:* Maxim Solodovnik mailto:solomax...@gmail.com>>
*Gesendet:* Mittwoch, 1. April 2020 09:12
*An:* Openmeetings user-list
mailto:user@openmeetings.apache.org>>
*Betreff:* Re: Openmeetings Docker Image / Kurento / Turn
/ NAT

I'm stupid russian monkey :(((

full dockerized M3 has bug :(((

It was fixed by this

https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
 commit

This is why TURN_URL is NOT working :(((

Not sure if I can drop current M3 image, will try to

As a workaround - you can rebuild locally ...

On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang
mailto:ar...@lernenfoerdern.de>> wrote:

First of all: Thx to you for helping me. I am up now
again and give it the next try

Here is my non dockerized coturn config

root@docker-ibb-01:/var/log# cat /etc/turnserver.conf

listening-port=3478

verbose

fingerprint

lt-cred-mech

use-auth-secret

static-auth-secret=somegibberishtext

simple-log

log-file=/var/log/turn.log

min-port=49152

max-port=55000

I started the OM Conatiner with

root@docker-ibb-01:/home/wolfgang/coturn# docker run
-i --rm --expose=5443 --expose= -p 5443:5443 -p
: -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e
TURN_USER="kurento" -e TURN_PASS="somegibberishtext"
apache/openmeetings:5.0.0-M3

xxx.xxx.xxx.xxx is my external ip

No audio, video

*Von:* Maxim Solodovnik mailto:solomax...@gmail.com>>
*Gesendet:* Mittwoch, 1. April 2020 05:34
*An:* Openmeetings user-list
mailto:user@openmeetings.apache.org>>
*Betreff:* Re: Openmeetings Docker Image / Kurento /
Turn / NAT

Well

Usually it all ends up on second or third email 

Maybe you can try with non-dockerized-turnserver ?

On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang
mailto:ar...@lernenfoerdern.de>> wrote:

I give up for now. This is annoying.

Why things must be so complicated :-(

I tested for open ports. I openend all outgoing
ports for the host where coturn and the Docker OM
Container is.

Is there a step by step way to test?

It is such an unormal setup?

Wolfgang


-- 


WBR
Maxim aka solomax


-- 


WBR
Maxim aka solomax



-- 
WBR

Maxim aka solomax



-- 
WBR

Maxim aka solomax




--
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

Sure,
I can switch master to use M4-SNAPSHOT
But you have to build it on your machine before use ...

Is it OK?

On Wed, 1 Apr 2020 at 16:09, Daniel Baker 
wrote:

> Could  I  use  the  alpha/ next  / M4  version?
>
> apache/openmeetings:5.0.0-M3
>
>
> Thanks,
>
>
> Dan
>
>
>
> On 01/04/2020 09:56, Maxim Solodovnik wrote:
>
> I mean run
> ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p : -e
> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3.1
> instead of
> ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p : -e
> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>
> :))
>
> On Wed, 1 Apr 2020 at 15:40, Maxim Solodovnik 
> wrote:
>
>> Well it would be too expensive
>> Thanks :)))
>> Hopefully I can visit Europe when the corona pandemic will be over :))
>>
>> Please try 5.0.0-M3.1
>> Hopefully will work :)
>>
>> On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang 
>> wrote:
>>
>>> 
>>> Can you tell me how to build this commit locally?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Von:* Maxim Solodovnik 
>>> *Gesendet:* Mittwoch, 1. April 2020 09:12
>>> *An:* Openmeetings user-list 
>>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>>
>>>
>>>
>>> I'm stupid russian monkey :(((
>>>
>>>
>>>
>>> full dockerized M3 has bug :(((
>>>
>>> It was fixed by this
>>> https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
>>>  commit
>>>
>>> This is why TURN_URL is NOT working :(((
>>>
>>>
>>>
>>> Not sure if I can drop current M3 image, will try to
>>>
>>> As a workaround - you can rebuild locally ...
>>>
>>>
>>>
>>> On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang 
>>> wrote:
>>>
>>> First of all: Thx to you for helping me. I am up now again and give it
>>> the next try
>>>
>>>
>>>
>>> Here is my non dockerized coturn config
>>>
>>>
>>>
>>> root@docker-ibb-01:/var/log# cat /etc/turnserver.conf
>>>
>>> listening-port=3478
>>>
>>> verbose
>>>
>>> fingerprint
>>>
>>> lt-cred-mech
>>>
>>> use-auth-secret
>>>
>>> static-auth-secret=somegibberishtext
>>>
>>> simple-log
>>>
>>> log-file=/var/log/turn.log
>>>
>>> min-port=49152
>>>
>>> max-port=55000
>>>
>>>
>>>
>>>
>>>
>>> I started the OM Conatiner with
>>>
>>>
>>>
>>> root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm
>>> --expose=5443 --expose= -p 5443:5443 -p : -e
>>> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
>>> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>>>
>>>
>>>
>>> xxx.xxx.xxx.xxx is my external ip
>>>
>>>
>>>
>>>
>>>
>>> No audio, video
>>>
>>>
>>>
>>>
>>>
>>> *Von:* Maxim Solodovnik 
>>> *Gesendet:* Mittwoch, 1. April 2020 05:34
>>> *An:* Openmeetings user-list 
>>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>>
>>>
>>>
>>> Well
>>>
>>> Usually it all ends up on second or third email 
>>>
>>> Maybe you can try with non-dockerized-turnserver ?
>>>
>>>
>>>
>>> On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang 
>>> wrote:
>>>
>>> I give up for now. This is annoying.
>>>
>>> Why things must be so complicated :-(
>>>
>>>
>>>
>>> I tested for open ports. I openend all outgoing ports for the host where
>>> coturn and the Docker OM Container is.
>>>
>>>
>>>
>>> Is there a step by step way to test?
>>>
>>>
>>>
>>> It is such an unormal setup?
>>>
>>>
>>>
>>>
>>>
>>> Wolfgang
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> WBR
>>> Maxim aka solomax
>>>
>>>
>>>
>>>
>>> --
>>>
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>

-- 
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Daniel Baker]

Could  I  use  the  alpha/ next  / M4  version?

apache/openmeetings:5.0.0-M3


Thanks,


Dan



On 01/04/2020 09:56, Maxim Solodovnik wrote:

I mean run
ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p 
: -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e 
TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3.1

instead of
ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p 
: -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e 
TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3


:))

On Wed, 1 Apr 2020 at 15:40, Maxim Solodovnik > wrote:


Well it would be too expensive
Thanks :)))
Hopefully I can visit Europe when the corona pandemic will be over :))

Please try 5.0.0-M3.1
Hopefully will work :)

On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang
mailto:ar...@lernenfoerdern.de>> wrote:


Can you tell me how to build this commit locally?

*Von:* Maxim Solodovnik mailto:solomax...@gmail.com>>
*Gesendet:* Mittwoch, 1. April 2020 09:12
*An:* Openmeetings user-list mailto:user@openmeetings.apache.org>>
*Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT

I'm stupid russian monkey :(((

full dockerized M3 has bug :(((

It was fixed by this

https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
 commit

This is why TURN_URL is NOT working :(((

Not sure if I can drop current M3 image, will try to

As a workaround - you can rebuild locally ...

On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang
mailto:ar...@lernenfoerdern.de>> wrote:

First of all: Thx to you for helping me. I am up now again
and give it the next try

Here is my non dockerized coturn config

root@docker-ibb-01:/var/log# cat /etc/turnserver.conf

listening-port=3478

verbose

fingerprint

lt-cred-mech

use-auth-secret

static-auth-secret=somegibberishtext

simple-log

log-file=/var/log/turn.log

min-port=49152

max-port=55000

I started the OM Conatiner with

root@docker-ibb-01:/home/wolfgang/coturn# docker run -i
--rm --expose=5443 --expose= -p 5443:5443 -p :
-e TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento"
-e TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3

xxx.xxx.xxx.xxx is my external ip

No audio, video

*Von:* Maxim Solodovnik mailto:solomax...@gmail.com>>
*Gesendet:* Mittwoch, 1. April 2020 05:34
*An:* Openmeetings user-list mailto:user@openmeetings.apache.org>>
*Betreff:* Re: Openmeetings Docker Image / Kurento / Turn
/ NAT

Well

Usually it all ends up on second or third email 

Maybe you can try with non-dockerized-turnserver ?

On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang
mailto:ar...@lernenfoerdern.de>>
wrote:

I give up for now. This is annoying.

Why things must be so complicated :-(

I tested for open ports. I openend all outgoing ports
for the host where coturn and the Docker OM Container is.

Is there a step by step way to test?

It is such an unormal setup?

Wolfgang


-- 


WBR
Maxim aka solomax


-- 


WBR
Maxim aka solomax



-- 
WBR

Maxim aka solomax



--
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

I mean run
ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p : -e
TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3.1
instead of
ocker run -i --rm --expose=5443 --expose= -p 5443:5443 -p : -e
TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3

:))

On Wed, 1 Apr 2020 at 15:40, Maxim Solodovnik  wrote:

> Well it would be too expensive
> Thanks :)))
> Hopefully I can visit Europe when the corona pandemic will be over :))
>
> Please try 5.0.0-M3.1
> Hopefully will work :)
>
> On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang 
> wrote:
>
>> 
>> Can you tell me how to build this commit locally?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Von:* Maxim Solodovnik 
>> *Gesendet:* Mittwoch, 1. April 2020 09:12
>> *An:* Openmeetings user-list 
>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>
>>
>>
>> I'm stupid russian monkey :(((
>>
>>
>>
>> full dockerized M3 has bug :(((
>>
>> It was fixed by this
>> https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
>>  commit
>>
>> This is why TURN_URL is NOT working :(((
>>
>>
>>
>> Not sure if I can drop current M3 image, will try to
>>
>> As a workaround - you can rebuild locally ...
>>
>>
>>
>> On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang 
>> wrote:
>>
>> First of all: Thx to you for helping me. I am up now again and give it
>> the next try
>>
>>
>>
>> Here is my non dockerized coturn config
>>
>>
>>
>> root@docker-ibb-01:/var/log# cat /etc/turnserver.conf
>>
>> listening-port=3478
>>
>> verbose
>>
>> fingerprint
>>
>> lt-cred-mech
>>
>> use-auth-secret
>>
>> static-auth-secret=somegibberishtext
>>
>> simple-log
>>
>> log-file=/var/log/turn.log
>>
>> min-port=49152
>>
>> max-port=55000
>>
>>
>>
>>
>>
>> I started the OM Conatiner with
>>
>>
>>
>> root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm
>> --expose=5443 --expose= -p 5443:5443 -p : -e
>> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
>> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>>
>>
>>
>> xxx.xxx.xxx.xxx is my external ip
>>
>>
>>
>>
>>
>> No audio, video
>>
>>
>>
>>
>>
>> *Von:* Maxim Solodovnik 
>> *Gesendet:* Mittwoch, 1. April 2020 05:34
>> *An:* Openmeetings user-list 
>> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>>
>>
>>
>> Well
>>
>> Usually it all ends up on second or third email 
>>
>> Maybe you can try with non-dockerized-turnserver ?
>>
>>
>>
>> On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang 
>> wrote:
>>
>> I give up for now. This is annoying.
>>
>> Why things must be so complicated :-(
>>
>>
>>
>> I tested for open ports. I openend all outgoing ports for the host where
>> coturn and the Docker OM Container is.
>>
>>
>>
>> Is there a step by step way to test?
>>
>>
>>
>> It is such an unormal setup?
>>
>>
>>
>>
>>
>> Wolfgang
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> WBR
>> Maxim aka solomax
>>
>>
>>
>>
>> --
>>
>> WBR
>> Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

Well it would be too expensive
Thanks :)))
Hopefully I can visit Europe when the corona pandemic will be over :))

Please try 5.0.0-M3.1
Hopefully will work :)

On Wed, 1 Apr 2020 at 15:20, Arndt, Wolfgang 
wrote:

> 
> Can you tell me how to build this commit locally?
>
>
>
>
>
>
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Mittwoch, 1. April 2020 09:12
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> I'm stupid russian monkey :(((
>
>
>
> full dockerized M3 has bug :(((
>
> It was fixed by this
> https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
>  commit
>
> This is why TURN_URL is NOT working :(((
>
>
>
> Not sure if I can drop current M3 image, will try to
>
> As a workaround - you can rebuild locally ...
>
>
>
> On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang 
> wrote:
>
> First of all: Thx to you for helping me. I am up now again and give it the
> next try
>
>
>
> Here is my non dockerized coturn config
>
>
>
> root@docker-ibb-01:/var/log# cat /etc/turnserver.conf
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> lt-cred-mech
>
> use-auth-secret
>
> static-auth-secret=somegibberishtext
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
>
>
> I started the OM Conatiner with
>
>
>
> root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm
> --expose=5443 --expose= -p 5443:5443 -p : -e
> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>
>
>
> xxx.xxx.xxx.xxx is my external ip
>
>
>
>
>
> No audio, video
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Mittwoch, 1. April 2020 05:34
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> Well
>
> Usually it all ends up on second or third email 
>
> Maybe you can try with non-dockerized-turnserver ?
>
>
>
> On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang 
> wrote:
>
> I give up for now. This is annoying.
>
> Why things must be so complicated :-(
>
>
>
> I tested for open ports. I openend all outgoing ports for the host where
> coturn and the Docker OM Container is.
>
>
>
> Is there a step by step way to test?
>
>
>
> It is such an unormal setup?
>
>
>
>
>
> Wolfgang
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

AW: Openmeetings Docker Image / Kurento / Turn / NAT

[Arndt , Wolfgang]


Can you tell me how to build this commit locally?

 
 
 
 
 
Von: Maxim Solodovnik 
Gesendet: Mittwoch, 1. April 2020 09:12
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
I'm stupid russian monkey :(((

 
full dockerized M3 has bug :(((

It was fixed by this 
https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
 commit

This is why TURN_URL is NOT working :(((

 
Not sure if I can drop current M3 image, will try to

As a workaround - you can rebuild locally ...

 
On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang  wrote:

First of all: Thx to you for helping me. I am up now again and give it the next 
try

 
Here is my non dockerized coturn config

 
root@docker-ibb-01:/var/log# cat /etc/turnserver.conf

listening-port=3478

verbose

fingerprint

lt-cred-mech

use-auth-secret

static-auth-secret=somegibberishtext

simple-log

log-file=/var/log/turn.log

min-port=49152

max-port=55000

 
 
I started the OM Conatiner with

 
root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm --expose=5443 
--expose= -p 5443:5443 -p : -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e 
TURN_USER="kurento" -e TURN_PASS="somegibberishtext" 
apache/openmeetings:5.0.0-M3

 
xxx.xxx.xxx.xxx is my external ip

 
 
No audio, video

 
 
Von: Maxim Solodovnik mailto:solomax...@gmail.com> >
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
Well

Usually it all ends up on second or third email 

Maybe you can try with non-dockerized-turnserver ?

 
On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang  wrote:

I give up for now. This is annoying.

Why things must be so complicated :-(

 
I tested for open ports. I openend all outgoing ports for the host where coturn 
and the Docker OM Container is.

 
Is there a step by step way to test?

 
It is such an unormal setup?

 
 
Wolfgang

 
 
 
 
 
 
 
 


 
--

WBR
Maxim aka solomax



 
--

WBR
Maxim aka solomax

AW: Openmeetings Docker Image / Kurento / Turn / NAT

[Arndt , Wolfgang]

I’am waiting for the things to come 


Where can i send chocolate or beer ?

 
 
 
Von: Maxim Solodovnik 
Gesendet: Mittwoch, 1. April 2020 09:44
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
Thanks :)

 
It seems to be possible to drop existing tags from git and docker

But maybe I'll better create 5.0.0-M3.1

Stay tuned :)

 
On Wed, 1 Apr 2020 at 14:40, Rohrbach, Gerald  wrote:

Maxim,

 
well with your perfect support during this time you can get more beer that you 
can ever drink..

In every country in the world!

 
Gerald

 
Von: Maxim Solodovnik [mailto:solomax...@gmail.com 
 ]
Gesendet: Mittwoch, 1. April 2020 09:12
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
I'm stupid russian monkey :(((

 
full dockerized M3 has bug :(((

It was fixed by this 
https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
 commit

This is why TURN_URL is NOT working :(((

 
Not sure if I can drop current M3 image, will try to

As a workaround - you can rebuild locally ...

 
On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang mailto:ar...@lernenfoerdern.de> > wrote:

First of all: Thx to you for helping me. I am up now again and give it the next 
try

 
Here is my non dockerized coturn config

 
root@docker-ibb-01:/var/log# cat /etc/turnserver.conf

listening-port=3478

verbose

fingerprint

lt-cred-mech

use-auth-secret

static-auth-secret=somegibberishtext

simple-log

log-file=/var/log/turn.log

min-port=49152

max-port=55000

 
 
I started the OM Conatiner with

 
root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm --expose=5443 
--expose= -p 5443:5443 -p : -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e 
TURN_USER="kurento" -e TURN_PASS="somegibberishtext" 
apache/openmeetings:5.0.0-M3

 
xxx.xxx.xxx.xxx is my external ip

 
 
No audio, video

 
 
Von: Maxim Solodovnik mailto:solomax...@gmail.com> >
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
Well

Usually it all ends up on second or third email 

Maybe you can try with non-dockerized-turnserver ?

 
On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang mailto:ar...@lernenfoerdern.de> > wrote:

I give up for now. This is annoying.

Why things must be so complicated :-(

 
I tested for open ports. I openend all outgoing ports for the host where coturn 
and the Docker OM Container is.

 
Is there a step by step way to test?

 
It is such an unormal setup?

 
 
Wolfgang

 
 
 
 
 
 
 
 


 
--

WBR
Maxim aka solomax



 
--

WBR
Maxim aka solomax



 
--

WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

Thanks :)

It seems to be possible to drop existing tags from git and docker
But maybe I'll better create 5.0.0-M3.1
Stay tuned :)

On Wed, 1 Apr 2020 at 14:40, Rohrbach, Gerald 
wrote:

> Maxim,
>
>
>
> well with your perfect support during this time you can get more beer that
> you can ever drink..
>
> In every country in the world!
>
>
>
> Gerald
>
>
>
> *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com]
> *Gesendet:* Mittwoch, 1. April 2020 09:12
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> I'm stupid russian monkey :(((
>
>
>
> full dockerized M3 has bug :(((
>
> It was fixed by this
> https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
>  commit
>
> This is why TURN_URL is NOT working :(((
>
>
>
> Not sure if I can drop current M3 image, will try to
>
> As a workaround - you can rebuild locally ...
>
>
>
> On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang 
> wrote:
>
> First of all: Thx to you for helping me. I am up now again and give it the
> next try
>
>
>
> Here is my non dockerized coturn config
>
>
>
> root@docker-ibb-01:/var/log# cat /etc/turnserver.conf
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> lt-cred-mech
>
> use-auth-secret
>
> static-auth-secret=somegibberishtext
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
>
>
> I started the OM Conatiner with
>
>
>
> root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm
> --expose=5443 --expose= -p 5443:5443 -p : -e
> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>
>
>
> xxx.xxx.xxx.xxx is my external ip
>
>
>
>
>
> No audio, video
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Mittwoch, 1. April 2020 05:34
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> Well
>
> Usually it all ends up on second or third email 
>
> Maybe you can try with non-dockerized-turnserver ?
>
>
>
> On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang 
> wrote:
>
> I give up for now. This is annoying.
>
> Why things must be so complicated :-(
>
>
>
> I tested for open ports. I openend all outgoing ports for the host where
> coturn and the Docker OM Container is.
>
>
>
> Is there a step by step way to test?
>
>
>
> It is such an unormal setup?
>
>
>
>
>
> Wolfgang
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

AW: Openmeetings Docker Image / Kurento / Turn / NAT

[Rohrbach, Gerald]

Maxim,

well with your perfect support during this time you can get more beer that you 
can ever drink..
In every country in the world!

Gerald

Von: Maxim Solodovnik [mailto:solomax...@gmail.com]
Gesendet: Mittwoch, 1. April 2020 09:12
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

I'm stupid russian monkey :(((

full dockerized M3 has bug :(((
It was fixed by this 
https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
 commit
This is why TURN_URL is NOT working :(((

Not sure if I can drop current M3 image, will try to
As a workaround - you can rebuild locally ...

On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang 
mailto:ar...@lernenfoerdern.de>> wrote:
First of all: Thx to you for helping me. I am up now again and give it the next 
try

Here is my non dockerized coturn config

root@docker-ibb-01:/var/log# cat /etc/turnserver.conf
listening-port=3478
verbose
fingerprint
lt-cred-mech
use-auth-secret
static-auth-secret=somegibberishtext
simple-log
log-file=/var/log/turn.log
min-port=49152
max-port=55000


I started the OM Conatiner with

root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm --expose=5443 
--expose= -p 5443:5443 -p : -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e 
TURN_USER="kurento" -e TURN_PASS="somegibberishtext" 
apache/openmeetings:5.0.0-M3

xxx.xxx.xxx.xxx is my external ip


No audio, video


Von: Maxim Solodovnik mailto:solomax...@gmail.com>>
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list 
mailto:user@openmeetings.apache.org>>
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

Well
Usually it all ends up on second or third email 
Maybe you can try with non-dockerized-turnserver ?

On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang 
mailto:ar...@lernenfoerdern.de>> wrote:
I give up for now. This is annoying.
Why things must be so complicated :-(

I tested for open ports. I openend all outgoing ports for the host where coturn 
and the Docker OM Container is.

Is there a step by step way to test?

It is such an unormal setup?


Wolfgang










--
WBR
Maxim aka solomax


--
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

[Maxim Solodovnik]

I'm stupid russian monkey :(((

full dockerized M3 has bug :(((
It was fixed by this
https://github.com/openmeetings/openmeetings-docker/commit/7f08a946aa0b22a0101520a406159ca832fbcbdb
 commit
This is why TURN_URL is NOT working :(((

Not sure if I can drop current M3 image, will try to
As a workaround - you can rebuild locally ...

On Wed, 1 Apr 2020 at 14:06, Arndt, Wolfgang 
wrote:

> First of all: Thx to you for helping me. I am up now again and give it the
> next try
>
>
>
> Here is my non dockerized coturn config
>
>
>
> root@docker-ibb-01:/var/log# cat /etc/turnserver.conf
>
> listening-port=3478
>
> verbose
>
> fingerprint
>
> lt-cred-mech
>
> use-auth-secret
>
> static-auth-secret=somegibberishtext
>
> simple-log
>
> log-file=/var/log/turn.log
>
> min-port=49152
>
> max-port=55000
>
>
>
>
>
> I started the OM Conatiner with
>
>
>
> root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm
> --expose=5443 --expose= -p 5443:5443 -p : -e
> TURN_URL="xxx.xxx.xxx.xxx:3478" -e TURN_USER="kurento" -e
> TURN_PASS="somegibberishtext" apache/openmeetings:5.0.0-M3
>
>
>
> xxx.xxx.xxx.xxx is my external ip
>
>
>
>
>
> No audio, video
>
>
>
>
>
> *Von:* Maxim Solodovnik 
> *Gesendet:* Mittwoch, 1. April 2020 05:34
> *An:* Openmeetings user-list 
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> Well
>
> Usually it all ends up on second or third email 
>
> Maybe you can try with non-dockerized-turnserver ?
>
>
>
> On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang 
> wrote:
>
> I give up for now. This is annoying.
>
> Why things must be so complicated :-(
>
>
>
> I tested for open ports. I openend all outgoing ports for the host where
> coturn and the Docker OM Container is.
>
>
>
> Is there a step by step way to test?
>
>
>
> It is such an unormal setup?
>
>
>
>
>
> Wolfgang
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

AW: Openmeetings Docker Image / Kurento / Turn / NAT

[Arndt , Wolfgang]

First of all: Thx to you for helping me. I am up now again and give it the next 
try

 
Here is my non dockerized coturn config

 
root@docker-ibb-01:/var/log# cat /etc/turnserver.conf

listening-port=3478

verbose

fingerprint

lt-cred-mech

use-auth-secret

static-auth-secret=somegibberishtext

simple-log

log-file=/var/log/turn.log

min-port=49152

max-port=55000

 
 
I started the OM Conatiner with

 
root@docker-ibb-01:/home/wolfgang/coturn# docker run -i --rm --expose=5443 
--expose= -p 5443:5443 -p : -e TURN_URL="xxx.xxx.xxx.xxx:3478" -e 
TURN_USER="kurento" -e TURN_PASS="somegibberishtext" 
apache/openmeetings:5.0.0-M3

 
xxx.xxx.xxx.xxx is my external ip

 
 
No audio, video

 
 
Von: Maxim Solodovnik 
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list 
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
Well

Usually it all ends up on second or third email 

Maybe you can try with non-dockerized-turnserver ?

 
On Wed, 1 Apr 2020 at 08:19, Arndt, Wolfgang  wrote:

I give up for now. This is annoying.

Why things must be so complicated :-(

 
I tested for open ports. I openend all outgoing ports for the host where coturn 
and the Docker OM Container is.

 
Is there a step by step way to test?

 
It is such an unormal setup?

 
 
Wolfgang

 
 
 
 
 
 
 
 


 
--

WBR
Maxim aka solomax

Re: invitation-email: reply to

[Maxim Solodovnik]

https://openmeetings.apache.org/GeneralConfiguration.html

inviter.email.as.replyto

On Wed, 1 Apr 2020 at 13:34, R. Scholz 
wrote:

> Hello,
>
> where I can find the configuration for the "reply to". I only find the
> email for "mail.smtp.system.email" but when I send a invitation
> there is my other address in "reply to".
>
> Best regards,
>
> René
>
>

-- 
WBR
Maxim aka solomax

Re: OpenMeetings

[Maxim Solodovnik]

Please do not send personal emails
Write to the list (in CC)

On Wed, 1 Apr 2020 at 13:19, Encho Bratovanov  wrote:

>
>
> Thanks for the quick answer.
> I can't shure who E-mail is work and for this reason i send to all
> available. For further I will use only  one e-mail ?!?
> I will test you advise.
> Can I use you E-mail for further queshens?!?
> Thanks again :)
>
> > Оригинално писмо 
> >От: Maxim Solodovnik solomax...@gmail.com
> >Относно: Re: OpenMeetings
> >До: Openmeetings user-list 
> >Изпратено на: 31.03.2020 19:27
>
> Hello,
>
> please do not use multiple mailing lists :)
>
> to set up init.d script to autostart I would use
> sudo update-rc.d tomcat3 defaults
>
> According to KMS
> please check /etc/defaults/kurento-media-server
>
> On Tue, 31 Mar 2020 at 23:24, Encho Bratovanov < ebratova...@abv.bg>
> wrote:
>
>  Hello,  First I can ask you, how to configurate Tomcat3 start
> automatically after Linux reboot.  And second, in beginning
> kurento-media-server was start automatically after Linux restart, but now
> the media server is not start automatically.  Every time when Linux reboot
> / update and etc./
>  I must type :  sudo /etc/init.d/kurento-media-server start  sudo
> /etc/init.d/tomcat3 start  How it’s can do automatically  Thanks in advance
>
>
>
> --
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

invitation-email: reply to

[R. Scholz]

Hello,

where I can find the configuration for the "reply to". I only find the 
email for "mail.smtp.system.email" but when I send a invitation

there is my other address in "reply to".

Best regards,

René