STUN Server Returns LAN IP about nextcloud-spreed-signaling HOT 2 CLOSED

It appears that the WAN IPv4 address must be passed to Janus as well as Coturn.

For Janus:
command: ["janus", "--full-trickle", "--nat-1-1=8.7.6.5"] into the appropriate section in docker-compose.yml

For Coturn:
external-ip=8.7.6.5/10.0.0.11 into /etc/coturn/turnserver.conf inside the running Docker container.

I'll keep testing this setup, though it seems to be working as expected.

I'm wondering if it might make sense to map turnserver.conf into the Docker container (similar to nats or spreed), so users can more easily configure external-ip.

from nextcloud-spreed-signaling.

If Janus is not running directly in the internet, it needs access to a STUN server to get its external IP or it must be configured through the nat 1-1 setting manually.

There is documentation at the Nextcloud Talk docs on how to setup coturn: https://nextcloud-talk.readthedocs.io/en/latest/TURN/

from nextcloud-spreed-signaling.