Nextcloud/aio-talk and turn > how is the information flow?

ℹ️ Support 💬 Talk (spreed)
, ,
1

I am trying to understand which ports have to be fwded with aio-talk and why.

My setup
Nextcloud, mysql, redis running as docker behind a reverse proxy.
My Turn server
Tried Coturn and eturnal as docker. Both work okay.
Till this point, I was forwarding Ports 49152 - 49407 (UDP) and 3478 (UDP/TCP) to the turn server. Everything fine.

Now I installed nextcloud/aio-talk high performance backend (HPB) also via docker. I am a bit lost what to do with my existing turn server.
I have now the ports 49152 - 49407 (UDP) and 3478 (UDP/TCP) to my nextcloud/aio-talk and apparently since everything still seems to work I do not need the turn server any more

But the documentation explicitly talks about HPB and turn server - both - are needed. So if I were to still keep using my existing (and working) coturn servers which ports do I use / forward? Since 3478 is already “blocked” by HPB…

On the other hand, the setup I have without separate turn server works fine, but I don’t understand why / how. Does the nextcloud/aio-talk have it’s own inbuilt turn server?

Thanks for your inputs.

2

to answer my own question partly -
eturnal is integrated in aio-talk

so it would mean, all ports that I forwarded to my “older” eturnal instance (stand alone) can / should now be forwarded to aio-talk?

3

any opinions here? Specifically, do I need to forward udp 49152-65535 explicitly to this container (running behind NAT)? I have otherwise deactivated upnp if it is relevant…