Allow configuring STUN/TURN port

Question

Allow configuring STUN/TURN port

mwild1 opened this issue 2 years ago · 5 comments

mwild1 commented 2 years ago

This can be useful to run multiple instances, avoid discovery and to bypass ISP blocks on the standard port.

See also #143

Answer 1 · 2023-01-18T17:57:52.000Z

I observe that mod_turn_external doesn't support multiple services, mod_external_services would be needed

Answer 2 · 2023-01-18T18:40:42.000Z

We don't need multiple services, do we? Just the custom port? (which is supported)

Answer 3 · 2023-01-18T19:08:35.000Z

I may be misunderstanding what "multiple instances" refers to then, thinking multiple TURN services.

Answer 4 · 2023-01-19T10:48:41.000Z

Ah, sorry, I see I said that. I meant that if you have another TURN service on the same machine being used for something else (and not using REST auth or whatever), it's a way to have Snikket's own TURN service not conflict with it (by changing the port). Snikket will only be using one service.

Answer 5 · 2023-07-13T19:53:31.000Z

Seems that this might be possible now?
https://github.com/snikket-im/snikket-server/blob/master/docs/advanced/firewall.md

But I would be looking to disable the TURN server and instead set a custom one, as we already have a TURN server that can be used by multiple services.

Edit: Seems it is possible, will try this approach → #100