I am connecting to Jitsi from WebRTC (libjingle). I give libjingle external STUN servers, which resolve fine. Jitsi is set up on my internal network and there are no firewalls.
When making a connection, I see this in the Android log:
08-01 19:08:27.139 21040-19824/live.attach.testcontainer I/libjingle: (port.cc:1364): Jingle:Conn[0x9f43e700:audio:LMZfC6xe:1:0:local:udp:192.168.0.x:34213->p3FkE96H:1:2113932031:local:udp:192.168.0.x:10000|C-WI|9079268943356378622|9]: Timing-out STUN ping 36593947324641745570584b after 5001 ms
08-01 19:08:27.165 21040-19824/live.attach.testcontainer I/libjingle: (port.cc:1148): Jingle:Conn[0x9f43e700:audio:LMZfC6xe:1:0:local:udp:192.168.0.x:34213->p3FkE96H:1:2113932031:local:udp:192.168.0.x:10000|C-WI|9079268943356378622|9]: Unwritable after 5 ping failures and 5027 ms without a response, ms since last received ping=116225800 ms since last received data=116225800 rtt=100
Apparently, libjingle tries to contact the Jitsi machine with STUN calls.
I saw there is a jitsi repo with a separate TURN/STUN server. Will I need to set this up on the machine for Jitsi to work, or should it work without? Due to my understanding, there is no need for STUN when using an MCU, and Jitsi should itself try to tunnel a client-side NAT, if that is necessary. Is my understanding correct?