As subject says: Here my observations so far:
a) In a two-party connection both parties have this
iceServerConfig (w.r.t. the server):
There is no
relay candidate in the list, however, those are not required so far.
b) The turnserver is started,
/etc/turnserver.conf is as it has been generated at installation time
ubuntu@jitsi-meet:~$ ps aux | grep turnserver turnser+ 4832 0.1 0.2 633208 9604 ? Ssl 13:32 0:00 /usr/bin/turnserver --daemon -c /etc/turnserver.conf --pidfile /run/turnserver/turnserver.pid ubuntu@jitsi-meet:~$ cat /run/turnserver/turnserver.pid 4832
c) The turnserver.conf has
no-tcp specified, what means IMHO, that no TCP listener is started (??)(commenting that doesn’t help either)
d) I can’t see a listener on this port (
sudo netstat -tupan) - ok, that can be an NGINX trick
e) The firewall is open and the port forwarding works. I can capture packets on the jitsi box
e) Once I run the trickle ice test against this URL the TCP connection or jitsi-meet I only see “TCP RESTARTS” on every incoming “SYNC” request…
f) The UDP TURN instance at 3479 works, although it delivers internal addresses as TURN adresses (but this might be the way you are using TURN):
Can somebody explain to me, why the TURNS instance is not working?