You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Arndt, Wolfgang <ar...@lernenfoerdern.de> on 2020/04/01 01:19:12 UTC

AW: Openmeetings Docker Image / Kurento / Turn / NAT

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

Posted by Maxim Solodovnik <so...@gmail.com>.
should be fixed

On Wed, 1 Apr 2020 at 21:58, Maxim Solodovnik <so...@gmail.com> 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.finnendahl@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|<policy
>> domain="coder" rights="none" pattern="PS" />|<!--policy domain="coder"
>> rights="none" pattern="PS" />|g; s|<policy domain="coder" rights="none"
>> pattern="XPS" />|<policy domain="coder" rights="none" pattern="XPS" /-->|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|<policy
>> domain="coder" rights="none" pattern="PS" />|<!--policy domain="coder"
>> rights="none" pattern="PS" />|g; s|<policy domain="coder" rights="none"
>> pattern="XPS" />|<policy domain="coder" rights="none" pattern="XPS" /-->|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

Posted by Maxim Solodovnik <so...@gmail.com>.
My bad
Doesn't test it (github issue already reported)
Will take a look


On Wed, Apr 1, 2020, 21:56 Orm Finnendahl <
orm.finnendahl@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|<policy
> domain="coder" rights="none" pattern="PS" />|<!--policy domain="coder"
> rights="none" pattern="PS" />|g; s|<policy domain="coder" rights="none"
> pattern="XPS" />|<policy domain="coder" rights="none" pattern="XPS" /-->|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|<policy
> domain="coder" rights="none" pattern="PS" />|<!--policy domain="coder"
> rights="none" pattern="PS" />|g; s|<policy domain="coder" rights="none"
> pattern="XPS" />|<policy domain="coder" rights="none" pattern="XPS" /-->|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

Posted by Orm Finnendahl <or...@selma.hfmdk-frankfurt.de>.
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|<policy domain="coder" rights="none" pattern="PS" />|<!--policy domain="coder" rights="none" pattern="PS" />|g; s|<policy domain="coder" rights="none" pattern="XPS" />|<policy domain="coder" rights="none" pattern="XPS" /-->|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|<policy domain="coder" rights="none" pattern="PS" />|<!--policy domain="coder" rights="none" pattern="PS" />|g; s|<policy domain="coder" rights="none" pattern="XPS" />|<policy domain="coder" rights="none" pattern="XPS" /-->|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

Posted by Maxim Solodovnik <so...@gmail.com>.
should be done :)

On Wed, 1 Apr 2020 at 16:18, Daniel Baker <in...@collisiondetection.biz>
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 <in...@collisiondetection.biz>
> 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 <in...@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=8888 -p 5443:5443 -p 8888:8888
>>> -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=8888 -p 5443:5443 -p 8888:8888
>>> -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 <so...@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 <ar...@lernenfoerdern.de>
>>>> wrote:
>>>>
>>>>> 😊
>>>>> Can you tell me how to build this commit locally?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *Von:* Maxim Solodovnik <so...@gmail.com>
>>>>> *Gesendet:* Mittwoch, 1. April 2020 09:12
>>>>> *An:* Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>
>>>>> *Gesendet:* Mittwoch, 1. April 2020 05:34
>>>>> *An:* Openmeetings user-list <us...@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 <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
>>
>>
>
> --
> WBR
> Maxim aka solomax
>
>

-- 
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

Posted by Daniel Baker <in...@collisiondetection.biz>.
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 <info@collisiondetection.biz 
> <ma...@collisiondetection.biz>> 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
>>     <info@collisiondetection.biz
>>     <ma...@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=8888 -p 5443:5443
>>>         -p 8888:8888 -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=8888 -p 5443:5443
>>>         -p 8888:8888 -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
>>>         <solomax666@gmail.com <ma...@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
>>>             <arndt@lernenfoerdern.de
>>>             <ma...@lernenfoerdern.de>> wrote:
>>>
>>>                 😊
>>>                 Can you tell me how to build this commit locally?
>>>
>>>                 *Von:* Maxim Solodovnik <solomax666@gmail.com
>>>                 <ma...@gmail.com>>
>>>                 *Gesendet:* Mittwoch, 1. April 2020 09:12
>>>                 *An:* Openmeetings user-list
>>>                 <user@openmeetings.apache.org
>>>                 <ma...@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
>>>                 <arndt@lernenfoerdern.de
>>>                 <ma...@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=8888 -p
>>>                     5443:5443 -p 8888:8888 -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 <solomax666@gmail.com
>>>                     <ma...@gmail.com>>
>>>                     *Gesendet:* Mittwoch, 1. April 2020 05:34
>>>                     *An:* Openmeetings user-list
>>>                     <user@openmeetings.apache.org
>>>                     <ma...@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
>>>                     <arndt@lernenfoerdern.de
>>>                     <ma...@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
>
>
>
> -- 
> WBR
> Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

Posted by Maxim Solodovnik <so...@gmail.com>.
Yes sure :)
Will do it with low priority :)

On Wed, 1 Apr 2020 at 16:14, Daniel Baker <in...@collisiondetection.biz>
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 <in...@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=8888 -p 5443:5443 -p 8888:8888
>> -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=8888 -p 5443:5443 -p 8888:8888
>> -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 <so...@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 <ar...@lernenfoerdern.de>
>>> wrote:
>>>
>>>> 😊
>>>> Can you tell me how to build this commit locally?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *Von:* Maxim Solodovnik <so...@gmail.com>
>>>> *Gesendet:* Mittwoch, 1. April 2020 09:12
>>>> *An:* Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>
>>>> *Gesendet:* Mittwoch, 1. April 2020 05:34
>>>> *An:* Openmeetings user-list <us...@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 <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
>
>

-- 
WBR
Maxim aka solomax

Re: Openmeetings Docker Image / Kurento / Turn / NAT

Posted by Daniel Baker <in...@collisiondetection.biz>.
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 <info@collisiondetection.biz 
> <ma...@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=8888 -p 5443:5443 -p
>>     8888:8888 -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=8888 -p 5443:5443 -p
>>     8888:8888 -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
>>     <solomax666@gmail.com <ma...@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
>>         <arndt@lernenfoerdern.de <ma...@lernenfoerdern.de>> wrote:
>>
>>             😊
>>             Can you tell me how to build this commit locally?
>>
>>             *Von:* Maxim Solodovnik <solomax666@gmail.com
>>             <ma...@gmail.com>>
>>             *Gesendet:* Mittwoch, 1. April 2020 09:12
>>             *An:* Openmeetings user-list
>>             <user@openmeetings.apache.org
>>             <ma...@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
>>             <arndt@lernenfoerdern.de
>>             <ma...@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=8888 -p 5443:5443 -p
>>                 8888:8888 -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 <solomax666@gmail.com
>>                 <ma...@gmail.com>>
>>                 *Gesendet:* Mittwoch, 1. April 2020 05:34
>>                 *An:* Openmeetings user-list
>>                 <user@openmeetings.apache.org
>>                 <ma...@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
>>                 <arndt@lernenfoerdern.de
>>                 <ma...@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

Posted by Maxim Solodovnik <so...@gmail.com>.
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 <in...@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=8888 -p 5443:5443 -p 8888:8888 -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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@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 <ar...@lernenfoerdern.de>
>> wrote:
>>
>>> 😊
>>> Can you tell me how to build this commit locally?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Von:* Maxim Solodovnik <so...@gmail.com>
>>> *Gesendet:* Mittwoch, 1. April 2020 09:12
>>> *An:* Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>
>>> *Gesendet:* Mittwoch, 1. April 2020 05:34
>>> *An:* Openmeetings user-list <us...@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 <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

Posted by Daniel Baker <in...@collisiondetection.biz>.
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=8888 -p 5443:5443 -p 
> 8888:8888 -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=8888 -p 5443:5443 -p 
> 8888:8888 -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 <solomax666@gmail.com 
> <ma...@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
>     <arndt@lernenfoerdern.de <ma...@lernenfoerdern.de>> wrote:
>
>         😊
>         Can you tell me how to build this commit locally?
>
>         *Von:* Maxim Solodovnik <solomax666@gmail.com
>         <ma...@gmail.com>>
>         *Gesendet:* Mittwoch, 1. April 2020 09:12
>         *An:* Openmeetings user-list <user@openmeetings.apache.org
>         <ma...@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
>         <arndt@lernenfoerdern.de <ma...@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=8888 -p 5443:5443 -p 8888:8888
>             -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 <solomax666@gmail.com
>             <ma...@gmail.com>>
>             *Gesendet:* Mittwoch, 1. April 2020 05:34
>             *An:* Openmeetings user-list <user@openmeetings.apache.org
>             <ma...@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
>             <arndt@lernenfoerdern.de <ma...@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

Posted by Maxim Solodovnik <so...@gmail.com>.
Great news :))
Can you also check if coturn-docker also works?

On Wed, 1 Apr 2020 at 16:34, Arndt, Wolfgang <ar...@lernenfoerdern.de>
wrote:

> Heureka!
>
> It is working now, i have audio and video.
>
>
>
> Big thank you!
>
>
>
> Now can i test it!
>
>
>
>
>
>
>
>
>
>
>
> *Von:* Maxim Solodovnik <so...@gmail.com>
> *Gesendet:* Mittwoch, 1. April 2020 10:57
> *An:* Openmeetings user-list <us...@openmeetings.apache.org>
> *Betreff:* Re: Openmeetings Docker Image / Kurento / Turn / NAT
>
>
>
> I mean run
>
> ocker run -i --rm --expose=5443 --expose=8888 -p 5443:5443 -p 8888:8888 -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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@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 <ar...@lernenfoerdern.de>
> wrote:
>
> 😊
> Can you tell me how to build this commit locally?
>
>
>
>
>
>
>
>
>
>
>
> *Von:* Maxim Solodovnik <so...@gmail.com>
> *Gesendet:* Mittwoch, 1. April 2020 09:12
> *An:* Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>
> *Gesendet:* Mittwoch, 1. April 2020 05:34
> *An:* Openmeetings user-list <us...@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 <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

AW: Openmeetings Docker Image / Kurento / Turn / NAT

Posted by Arndt, Wolfgang <ar...@lernenfoerdern.de>.
Heureka!

It is working now, i have audio and video.

 
Big thank you!

 
Now can i test it!

 
 
 
 
 
Von: Maxim Solodovnik <so...@gmail.com>
Gesendet: Mittwoch, 1. April 2020 10:57
An: Openmeetings user-list <us...@openmeetings.apache.org>
Betreff: Re: Openmeetings Docker Image / Kurento / Turn / NAT

 
I mean run

ocker run -i --rm --expose=5443 --expose=8888 -p 5443:5443 -p 8888:8888 -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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@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 <arndt@lernenfoerdern.de <ma...@lernenfoerdern.de> > wrote:

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

 
 
 
 
 
Von: Maxim Solodovnik <solomax666@gmail.com <ma...@gmail.com> >
Gesendet: Mittwoch, 1. April 2020 09:12
An: Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <solomax666@gmail.com <ma...@gmail.com> >
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list <us...@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 <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

Posted by Maxim Solodovnik <so...@gmail.com>.
I mean run
ocker run -i --rm --expose=5443 --expose=8888 -p 5443:5443 -p 8888:8888 -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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@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 <ar...@lernenfoerdern.de>
> wrote:
>
>> 😊
>> Can you tell me how to build this commit locally?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Von:* Maxim Solodovnik <so...@gmail.com>
>> *Gesendet:* Mittwoch, 1. April 2020 09:12
>> *An:* Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>
>> *Gesendet:* Mittwoch, 1. April 2020 05:34
>> *An:* Openmeetings user-list <us...@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 <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

Posted by Maxim Solodovnik <so...@gmail.com>.
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 <ar...@lernenfoerdern.de>
wrote:

> 😊
> Can you tell me how to build this commit locally?
>
>
>
>
>
>
>
>
>
>
>
> *Von:* Maxim Solodovnik <so...@gmail.com>
> *Gesendet:* Mittwoch, 1. April 2020 09:12
> *An:* Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>
> *Gesendet:* Mittwoch, 1. April 2020 05:34
> *An:* Openmeetings user-list <us...@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 <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

AW: Openmeetings Docker Image / Kurento / Turn / NAT

Posted by Arndt, Wolfgang <ar...@lernenfoerdern.de>.
😊
Can you tell me how to build this commit locally?

 
 
 
 
 
Von: Maxim Solodovnik <so...@gmail.com>
Gesendet: Mittwoch, 1. April 2020 09:12
An: Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <solomax666@gmail.com <ma...@gmail.com> >
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list <us...@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 <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

AW: Openmeetings Docker Image / Kurento / Turn / NAT

Posted by Arndt, Wolfgang <ar...@lernenfoerdern.de>.
I’am waiting for the things to come 😉


Where can i send chocolate or beer ?

 
 
 
Von: Maxim Solodovnik <so...@gmail.com>
Gesendet: Mittwoch, 1. April 2020 09:44
An: Openmeetings user-list <us...@openmeetings.apache.org>
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 <G....@funkegruppe.de> 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:solomax666@gmail.com <ma...@gmail.com> ]
Gesendet: Mittwoch, 1. April 2020 09:12
An: Openmeetings user-list <us...@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 <arndt@lernenfoerdern.de <ma...@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=8888 -p 5443:5443 -p 8888:8888 -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 <solomax666@gmail.com <ma...@gmail.com> >
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list <us...@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 <arndt@lernenfoerdern.de <ma...@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

Posted by Maxim Solodovnik <so...@gmail.com>.
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 <G....@funkegruppe.de>
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:solomax666@gmail.com]
> *Gesendet:* Mittwoch, 1. April 2020 09:12
> *An:* Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>
> *Gesendet:* Mittwoch, 1. April 2020 05:34
> *An:* Openmeetings user-list <us...@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 <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

AW: Openmeetings Docker Image / Kurento / Turn / NAT

Posted by "Rohrbach, Gerald" <G....@funkegruppe.de>.
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:solomax666@gmail.com]
Gesendet: Mittwoch, 1. April 2020 09:12
An: Openmeetings user-list <us...@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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>>
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list <us...@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 <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

Posted by Maxim Solodovnik <so...@gmail.com>.
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 <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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>
> *Gesendet:* Mittwoch, 1. April 2020 05:34
> *An:* Openmeetings user-list <us...@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 <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

AW: Openmeetings Docker Image / Kurento / Turn / NAT

Posted by Arndt, Wolfgang <ar...@lernenfoerdern.de>.
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=8888 -p 5443:5443 -p 8888:8888 -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 <so...@gmail.com>
Gesendet: Mittwoch, 1. April 2020 05:34
An: Openmeetings user-list <us...@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 <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

Re: Openmeetings Docker Image / Kurento / Turn / NAT

Posted by Maxim Solodovnik <so...@gmail.com>.
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 <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