Calls Do Not Connect about eturnal HOT 2 CLOSED

Not entirely sure what the root cause was, but this issue has been solved (at least for now).

Not sure if it did anything, but I removed the relay_min_port and relay_max_port settings from eturnal.yml, and moved them into my docker-compose file (the port range did not change). A quick docker compose down && docker compose up -d --remove-orphans and I suddenly had no issues.

Unfortunately do not have the log files, but if/when the issue pops up again, I will make sure to turn on log_level=debug and capture the eturnal logs.

Thanks for your help @weiss

from eturnal.

The first thing I'd double-check is whether the relay port range (all UDP ports between relay_min_port and relay_max_port) are accessible for clients. The Trickle ICE thing doesn't check this part of the setup. The Matrix VoIP tester claims to do that, but that's not trivial to do (which is why Trickle ICE and others don't), so I'm not entirely conviced they perform this check correctly (I'd be interested in the Relayed […] log line eturnal logs for the VoIP tester to verify this part).

I can see in my firewall logs that it is trying to make a direct connection (from peer2 to peer), and not using the relay server (public server IP), which I believe should not be the case?

Clients always try peer2peer before falling back to TURN relaying, so that's probably fine.

from eturnal.