in the institution I work for we have deployed Mozilla Hubs on an Amazon virtual machine. In order to better control our user experience we wanted to host an own STUN and TURN servers and use those instead of what I understand is the default for a Hubs installation, namely:
STUN -> from Google
TURN -> hosted on the Hubs machine itself
By exploring the machine we found a file that appears to be relevant in the following path:
I am not sure whether this path is the same on every installation or only on ours, however, we have tried to change the values for the STUN server and introduce those for the TURN server something like this:
Dear all,
in the institution I work for we have deployed Mozilla Hubs on an Amazon virtual machine. In order to better control our user experience we wanted to host an own STUN and TURN servers and use those instead of what I understand is the default for a Hubs installation, namely:
By exploring the machine we found a file that appears to be relevant in the following path:
/hab/pkgs/mozillareality/ita/0.0.1/20211117212826/schemas/janus-gateway.toml
I am not sure whether this path is the same on every installation or only on ours, however, we have tried to change the values for the STUN server and introduce those for the TURN server something like this:
... nat.stun_server = { "type" = "string", "default" = "turn.myinstitution.com" } nat.stun_port = { "type" = "number", "default" = 5349} nat.turn_server = { "type" = "string", "default" = "turn.myinstitution.com" } nat.turn_port = { "type" = "number", "default" = 5349} nat.turn_user = { "type" = "string", "default" = "myadmin" } nat.turn_pwd = { "type" = "string", "default" = "mypassword" } ...
We have restarted the machine, but upon accessing Hubs again, inspecting the WebRTC connections would still report the old values.
Is there any pointer you can give us on how to properly set a custom STUN and TURN server for Hubs?
Thanks in advance and my best regards
Antonio