xmastree

All right, good to know. I have set up a port forwarding for the port specified in the template. Why I changed the port? → Good question, for a better conscience I usually change the default port.... No idea if this is so useful. By the way, in the meantime I grabbed two cell phones (cellular) and made a call (video and audio) and sent some messages. Works. I also tried the whole thing with the default port (port forwarding, calls, messages). Same behavior. I'm still surprised that turns does not work for me.... Nevertheless, many thanks to you, @ich777.

I have adjusted the Docker according to your suggestion. The port then also jumps to 5349, but the talk settings show the same behavior. Turns does not work unfortunately. probably not i have already tried Nextcloud messaging and calling over the mobile network... that works. At least with a device that is located within the network.

Hello all, hello ich777, I have recently started to deal with Nextcloud-Talk, so now I may also deal with Stun/Turn. I pulled the docker from ich777 for this and filled out the template accordingly. Since my Nextcloud instance runs in a costom-network, I chose the same network in the Stun-Turn server. If I now enter my dyndns domain in the Nextcloud Talk settings, the green tick also appears. But only if I choose "turn: only" or "turn: and turns:". With "only turns:" a red exclamation mark appears. Have I perhaps done something wrong here? In addition, in the context of stun/turn, I kept reading about "denied ip addresses" when the server has access to the local network. How is that handled in this Docker? Attached are some screenshots of my configuration. I would be very happy if one of you experts could enlighten me a bit.