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 <solomax...@gmail.com> > *Gesendet:* Mittwoch, 1. April 2020 05:34 > *An:* Openmeetings user-list <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 <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
