I somewhat miraculously figured this out…
After almost giving up, I decided to look at the script provided in github:
#!/bin/bash
# T&M Hansson IT AB © - 2024, https://www.hanssonit.se/
true
SCRIPT_NAME="Nextcloud Talk"
SCRIPT_EXPLAINER="This script installs Nextcloud Talk which is a replacement for Teams/Skype and similar.
You will also be offered the possibility to install the so-called High-Performance-Backend, which makes it possible to host more video calls than it would be with the standard Talk app.
It's called 'Talk Signaling' and you will be offered to install it as part two of this script.
And last but not least, Talk Recording is also offered to be installed. It enables recording of sessions in Talk and it's part three of this script."
# shellcheck source=lib.sh
source /var/scripts/fetch_lib.sh
# Get all needed variables from the library
nc_update
turn_install
# Check for errors + debug code and abort if something isn't right
This file has been truncated. show original
This config provided by the script contained one line different than any recommendations I’ve seen on this forum:
lt-cred-mech
This guide specifically mentions it can’t be enabled when use-auth-secret is also enabled, but in my case, it only works with both config options set.
Background
The configuration of Nextcloud Talk mainly depends on your desired usage:
As long as it shall be used only within one local network, nothing should be needed at all. Just verify that all browsers support the underlying WebRTC protocol (all famous ones do on current versions) and you should be good to go.
Talk tries to establish a direct peer-to-peer (P2P) connection, thus on connections throughout the local network (behind a NAT /router), clients do not only need to know each others …
Cheers!