Maybe we’re halfway there but an help is needed.
OS: Ubuntu 18.04
Jitsi-meet: last revision (Quick-Installation)
Behind NAT … without the need of any “Advanced Configuration” [great value-added from last revision !!]
ISSUE: at the beginning everything works like a charm.
Then, partecipants on LAN can see & hear each other … but audio & video are not available with people from WAN (using both Smartphone and Pc/Mac)
Partial Origin: Public-IP has changed for some reasons.
Are you using a DynDNS service?
It’s not enough having DDNS up to date.
I’ve recently found that my jitsi server (coturn) wasn’t able to work properly until the update of the external-IP recorded during the installation in /etc/turnserver.conf. That’s static .
Now, making use of a DDNS client such ad ddClient or inadyn can solve both issues.
Once configured, they update the DDNS with the new IP so that jitsi server is still reachable.
And if you assign them a script, you are able to get up to date also the above mentioned external-ip, re-enabling coturn to do its job.
For our purpose I’ve modified a script suggested elsewhere in the forum from xentity :
#!/bin/bash DNSNAME=“mydomain.tld" # get the actual IP from the Internet IPint=$(host -tA $DNSNAME 188.8.131.52 | grep address | cut -d " " -f4 ) # get the configured IP of Jitsi IPjitsi=$(grep 'external-ip' /etc/turnserver.conf | grep -oE "[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+") #remove echo after debug if [ "$IPjitsi" == "$IPint" ] then echo "IP has not been changed!" exit 0 else echo "... actual IP: $IPjitsi" echo "... NEW IP: $IPint" fi #clear config sed -i '/external-ip/d' /etc/turnserver.conf #get IP and renew line echo external-ip =$IPint >> /etc/turnserver.conf sudo service jicofo restart sudo service jitsi-videobridge2 restart
MANUALLY executing the script … the “Voice & Video” problem (with partecipants from the WAN) is solved (for me), but I’m stopped here for some of my mistakes.
I’m in trouble with ddClient ver. (3.8.3-1.1ubuntu1) [ universe]:
'cause I’m not able to have it executing any script.
And I’m in trouble with inadyn (ver. 1.99.4-1build1) too.
This one is able to execute a script esplicitally assigned … but I’m not able to correctly customize the –system parameter for having it working with my DDNS provider.
Hope somebody could help us on the "last step” …
a) having the script working w/ ddClient, or
b) having inadyn customized to work for “generc” DDNS providers.