I am deploying the chatmail stack on a server located behind a NAT (without a public IP directly assigned to the network interface). While the necessary UDP ports (3478 and the 49152–65535 range) are forwarded correctly on the router, chatmail-turn fails to function properly.
I tested version 0.4 . In ICE candidates I see only the internal address, the external address is not used.
Does chatmail-turn currently support CLI arguments or environment variables to manually specify the listening and external (public) IP addresses?
I am deploying the chatmail stack on a server located behind a NAT (without a public IP directly assigned to the network interface). While the necessary UDP ports (3478 and the 49152–65535 range) are forwarded correctly on the router, chatmail-turn fails to function properly.
I tested version 0.4 . In ICE candidates I see only the internal address, the external address is not used.
Does chatmail-turn currently support CLI arguments or environment variables to manually specify the listening and external (public) IP addresses?