overlay: nats-server.conf, janus, coturn, nats-server/turnserver binaries; f7hpb.sh install overlay and coturn permissions

INSTALL.md

@@ -34,7 +34,7 @@ sudo ./install.sh
 - ✅ Устанавливает бинарники в `/usr/bin` и `/usr/sbin`
 - ✅ Копирует конфиги с подстановкой секретов
 - ✅ Настраивает systemd unit файлы
-- ✅ Сохраняет секреты в `/etc/f7cloud-spreed-signaling/.secrets.txt`
+- ✅ Сохраняет секреты в `/etc/f7cloud-talk-signaling/.secrets.txt`
 
 #### Вариант 2: Использование переменных окружения
 
@@ -82,9 +82,9 @@ sudo ./install.sh
 
 **ВАЖНО: Обязательно отредактируйте конфиги перед запуском!**
 
-1. **Signaling server** (`/etc/f7cloud-spreed-signaling/server.conf`):
+1. **Signaling server** (`/etc/f7cloud-talk-signaling/server.conf`):
    ```bash
-   nano /etc/f7cloud-spreed-signaling/server.conf
+   nano /etc/f7cloud-talk-signaling/server.conf
    ```
    - Укажите реальные URL бэкендов Nextcloud в секции `[nextcloud-backend-0]`
    - Проверьте секреты (они уже сгенерированы)
@@ -149,7 +149,7 @@ sudo journalctl -u coturn -f
 ├── events/            # Janus event handlers
 └── loggers/           # Janus loggers
 
-/etc/f7cloud-spreed-signaling/
+/etc/f7cloud-talk-signaling/
 ├── server.conf         # Конфиг signaling (с секретами!)
 └── .secrets.txt       # Сохраненные секреты
 
@@ -170,7 +170,7 @@ sudo journalctl -u coturn -f
 
 Все секреты автоматически генерируются при установке и сохраняются в:
 ```
-/etc/f7cloud-spreed-signaling/.secrets.txt
+/etc/f7cloud-talk-signaling/.secrets.txt
 ```
 
 **ВАЖНО:** Сохраните этот файл в безопасном месте! Он понадобится для:
@@ -182,7 +182,7 @@ sudo journalctl -u coturn -f
 
 Если автоматический скрипт не подходит, можно установить вручную:
 
-1. Скопируйте бинарники из `signaling-server/` в соответствующие директории
+1. Скопируйте бинарники из `overlay/usr/bin/` и `overlay/usr/sbin/` в `/usr/bin/` и `/usr/sbin/`
 2. Скопируйте конфиги из `config/` и `systemd/`
 3. Сгенерируйте секреты вручную:
    ```bash
@@ -206,7 +206,8 @@ sudo systemctl stop signaling janus nats-server coturn
 
 # Обновите бинарники из репозитория
 git pull
-sudo cp signaling-server/* /usr/bin/  # или соответствующие пути
+sudo cp overlay/usr/bin/signaling overlay/usr/bin/turnserver /usr/bin/
+sudo cp overlay/usr/sbin/nats-server /usr/sbin/
 
 # Перезапустите сервисы
 sudo systemctl start signaling janus nats-server coturn

f7hpb.sh

@@ -22,6 +22,16 @@ get_var() {
         printf -v "$name" '%s' "$val"
     fi
 }
+# Опциональная переменная: запрос с возможностью оставить пустым
+get_var_optional() {
+    local name="$1"
+    local prompt="$2"
+    local val="${!name}"
+    if [ -z "$val" ]; then
+        read -rp "$prompt: " val
+        printf -v "$name" '%s' "$val"
+    fi
+}
 
 # Путь к env-файлу: аргумент скрипта или запрос
 ENV_FILE="${1:-}"
@@ -41,6 +51,9 @@ get_var HPB_INTERNAL_SECRET "HPB internal_secret"
 get_var HPB_BACKEND_SECRET  "HPB backend secret"
 get_var F7CLOUD_URL "URL F7 Cloud (например https://cloud.example.com)"
 HPB_DOMAIN="${F7CLOUD_URL}"
+get_var STATIC_AUTH_SECRET "TURN static-auth-secret (источник уточняется)"
+# TURN REST API key для Janus (пока не задан, позже — из конфига coturn)
+get_var_optional TURN_REST_API_KEY "TURN REST API key для Janus (Enter — пропустить)"
 
 > "$ERROR_LOG"
 echo "=== Лог установки F7_HPB ===" >> "$ERROR_LOG"
@@ -74,37 +87,82 @@ mkdir -p /etc/f7cloud-spreed-signaling
 
 if [ -f "$R/server.conf.example" ]; then
     cp "$R/server.conf.example" /etc/f7cloud-spreed-signaling/server.conf
-    sed -i "s|hashkey.*=.*|hashkey = \"${HPB_HASHKEY}\"|i" /etc/f7cloud-spreed-signaling/server.conf
+    sed -i "s|hashkey = .*|hashkey = \"${HPB_HASHKEY}\"|i" /etc/f7cloud-spreed-signaling/server.conf
-    sed -i "s|blockkey.*=.*|blockkey = \"${HPB_BLOCKKEY}\"|i" /etc/f7cloud-spreed-signaling/server.conf
+    sed -i "s|blockkey = .*|blockkey = \"${HPB_BLOCKKEY}\"|i" /etc/f7cloud-spreed-signaling/server.conf
-    sed -i "s|internal.*secret.*=.*|internal_secret = \"${HPB_INTERNAL_SECRET}\"|i" /etc/f7cloud-spreed-signaling/server.conf
+    sed -i "s|internalsecret = .*|internalsecret = \"${HPB_INTERNAL_SECRET}\"|i" /etc/f7cloud-spreed-signaling/server.conf
-    sed -i "s|backend.*secret.*=.*|secret = \"${HPB_BACKEND_SECRET}\"|i" /etc/f7cloud-spreed-signaling/server.conf
+    sed -i "s|secret = YOUR_NEXTCLOUD_BACKEND_SECRET|secret = \"${HPB_BACKEND_SECRET}\"|g" /etc/f7cloud-spreed-signaling/server.conf
-    sed -i "s|https://.*nextcloud|${F7CLOUD_URL}|i" /etc/f7cloud-spreed-signaling/server.conf
+    sed -i "s|url = https://[^ ]*|url = ${F7CLOUD_URL}|" /etc/f7cloud-spreed-signaling/server.conf
-    sed -i "s|https://.*hpb|https://${HPB_DOMAIN}|i" /etc/f7cloud-spreed-signaling/server.conf
+    # [turn]: apikey, secret, servers — из переменных, ключи не теряются
+    REALM="${F7CLOUD_URL#*://}"; REALM="${REALM%%/*}"; REALM="${REALM%%:*}"
+    [ -n "$TURN_REST_API_KEY" ]     && sed -i "s|apikey = YOUR_TURN_API_KEY|apikey = ${TURN_REST_API_KEY}|" /etc/f7cloud-spreed-signaling/server.conf
+    [ -n "$STATIC_AUTH_SECRET" ]    && sed -i "s|secret = YOUR_TURN_SHARED_SECRET|secret = ${STATIC_AUTH_SECRET}|" /etc/f7cloud-spreed-signaling/server.conf
+    [ -n "$REALM" ]                 && sed -i "s|servers = turn:.*|servers = turn:${REALM}:9991?transport=udp,turn:${REALM}:9991?transport=tcp|" /etc/f7cloud-spreed-signaling/server.conf
 fi
 
-for bin in "$R/signaling-server" "$R/build/signaling-server" "$R/signaling-server-server"; do
+# Бинарник signaling только из overlay (signaling-server убран как дубликат)
-    [ -f "$bin" ] && cp "$bin" /usr/bin/ 2>/dev/null && chmod +x "/usr/bin/$(basename "$bin")" && break
+if [ -f "$R/overlay/usr/bin/signaling" ]; then
-done
+    cp "$R/overlay/usr/bin/signaling" /usr/bin/ && chmod +x /usr/bin/signaling
-find "$R" -maxdepth 2 -name "*.service" -exec cp {} /etc/systemd/system/ \;
+else
+    log_error "Бинарник signaling не найден: $R/overlay/usr/bin/signaling"
+    exit 1
+fi
+
+# Юниты: coturn, nats-server, janus, signaling
+find "$R" -name "*.service" -exec cp {} /etc/systemd/system/ \;
 
 # Overlay: файлы и каталоги из репозитория на те же пути в системе
 if [ -d "$R/overlay" ]; then
     echo "Установка overlay (nats, janus, coturn, бинарники)..."
+    REALM="${F7CLOUD_URL#*://}"; REALM="${REALM%%/*}"; REALM="${REALM%%:*}"
     [ -f "$R/overlay/etc/nats-server.conf" ] && cp "$R/overlay/etc/nats-server.conf" /etc/
     [ -d "$R/overlay/etc/janus" ]          && cp -a "$R/overlay/etc/janus" /etc/
+    # janus.jcfg: stun_server = домен, turn_rest_api_key = переменная (пока пусто)
+    if [ -f /etc/janus/janus.jcfg ] && [ -n "$REALM" ]; then
+        sed -i "s|stun_server = \".*\"|stun_server = \"$REALM\"|" /etc/janus/janus.jcfg
+    fi
+    [ -n "$TURN_REST_API_KEY" ] && [ -f /etc/janus/janus.jcfg ] && sed -i "s|turn_rest_api_key = \".*\"|turn_rest_api_key = \"$TURN_REST_API_KEY\"|" /etc/janus/janus.jcfg
     [ -d "$R/overlay/etc/coturn" ]         && cp -a "$R/overlay/etc/coturn" /etc/
+    [ -f "$R/overlay/etc/turnserver.conf" ] && cp "$R/overlay/etc/turnserver.conf" /etc/
+    # Библиотеки и плагины Janus
+    if [ -d "$R/overlay/usr/lib/x86_64-linux-gnu/janus" ]; then
+        mkdir -p /usr/lib/x86_64-linux-gnu
+        cp -a "$R/overlay/usr/lib/x86_64-linux-gnu/janus" /usr/lib/x86_64-linux-gnu/
+    fi
+    # Подстановка в turnserver.conf: реальный IP, realm (домен), static-auth-secret
+    if [ -f /etc/turnserver.conf ]; then
+        REAL_IP=$(hostname -I 2>/dev/null | awk '{print $1}')
+        [ -z "$REAL_IP" ] && REAL_IP=$(ip -4 route get 8.8.8.8 2>/dev/null | grep -oP 'src \K[^ ]+' || true)
+        [ -n "$REAL_IP" ] && sed -i "s|listening-ip=192.168.70.81|listening-ip=$REAL_IP|g" /etc/turnserver.conf && sed -i "s|relay-ip=192.168.70.81|relay-ip=$REAL_IP|g" /etc/turnserver.conf
+        [ -n "$REALM" ] && sed -i "s|^realm=.*|realm=$REALM|" /etc/turnserver.conf
+        [ -n "$STATIC_AUTH_SECRET" ] && sed -i "s|^static-auth-secret=.*|static-auth-secret=$STATIC_AUTH_SECRET|" /etc/turnserver.conf
+    fi
     [ -f "$R/overlay/usr/sbin/nats-server" ] && cp "$R/overlay/usr/sbin/nats-server" /usr/sbin/ && chmod +x /usr/sbin/nats-server
+    [ -f "$R/overlay/usr/bin/janus" ]        && cp "$R/overlay/usr/bin/janus" /usr/bin/       && chmod +x /usr/bin/janus
     [ -f "$R/overlay/usr/bin/turnserver" ]   && cp "$R/overlay/usr/bin/turnserver" /usr/bin/   && chmod +x /usr/bin/turnserver
+    [ -f "$R/overlay/usr/bin/signaling" ]    && cp "$R/overlay/usr/bin/signaling" /usr/bin/    && chmod +x /usr/bin/signaling
     # Права для coturn: пользователь turnserver, каталоги 750
-    if [ -d /etc/coturn ]; then
+    if [ -d /etc/coturn ] || [ -f /etc/turnserver.conf ]; then
         getent passwd turnserver >/dev/null 2>&1 || (useradd -r -s /usr/sbin/nologin turnserver 2>/dev/null || true)
+        [ -f /etc/turnserver.conf ] && chown turnserver:turnserver /etc/turnserver.conf && chmod 640 /etc/turnserver.conf
+        if [ -d /etc/coturn ]; then
             chown -R turnserver:turnserver /etc/coturn
             find /etc/coturn -type d -exec chmod 750 {} \;
             find /etc/coturn -type f -exec chmod 640 {} \;
         fi
     fi
+fi
+
+# Пользователи для служб (если ещё не созданы)
+getent passwd nats >/dev/null 2>&1       || (useradd -r -s /usr/sbin/nologin nats 2>/dev/null || true)
+getent passwd _signaling >/dev/null 2>&1 || (useradd -r -s /usr/sbin/nologin _signaling 2>/dev/null || true)
 
 systemctl daemon-reload 2>/dev/null || true
+# Включить и запустить службы
+for svc in coturn nats-server janus signaling; do
+    systemctl enable "$svc" 2>/dev/null || true
+    systemctl start "$svc" 2>/dev/null || true
+done
+# Совместимость со старыми именами
 systemctl enable f7cloud-spreed-signaling 2>/dev/null || systemctl enable signaling 2>/dev/null || true
 systemctl start f7cloud-spreed-signaling 2>/dev/null || systemctl start signaling 2>/dev/null || true
 

install.sh

@@ -1,318 +0,0 @@
-#!/bin/bash
-# Скрипт установки HPB - Nextcloud Spreed Signaling Stack
-# Автоматически генерирует секреты и настраивает все сервисы
-
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-INSTALL_DIR="/etc/f7cloud-spreed-signaling"
-BIN_DIR="/usr/bin"
-SBIN_DIR="/usr/sbin"
-LIB_DIR="/usr/lib/x86_64-linux-gnu/janus"
-CONFIG_DIR="/etc/janus"
-SYSTEMD_DIR="/etc/systemd/system"
-
-# Цвета для вывода
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-NC='\033[0m' # No Color
-
-log_info() {
-    echo -e "${GREEN}[INFO]${NC} $1"
-}
-
-log_warn() {
-    echo -e "${YELLOW}[WARN]${NC} $1"
-}
-
-log_error() {
-    echo -e "${RED}[ERROR]${NC} $1"
-}
-
-# Проверка прав root
-check_root() {
-    if [[ $EUID -ne 0 ]]; then
-        log_error "Этот скрипт должен запускаться от root"
-        exit 1
-    fi
-}
-
-# Генерация случайных hex строк
-generate_hex() {
-    local length=$1
-    openssl rand -hex "$length" | tr -d '\n'
-}
-
-# Генерация base64 строки
-generate_base64() {
-    local length=$1
-    openssl rand -base64 "$length" | tr -d '\n' | tr -d '=' | head -c "$length"
-}
-
-# Генерация всех секретов
-generate_secrets() {
-    log_info "Проверка секретов..."
-    
-    # Проверяем переменные окружения или файл с секретами
-    if [ -f "/tmp/hpb-secrets.env" ]; then
-        log_info "Загрузка секретов из /tmp/hpb-secrets.env..."
-        source /tmp/hpb-secrets.env
-        
-        # Используем секреты из файла, если они заданы
-        SIGNALING_HASHKEY=${HPB_HASHKEY:-${SIGNALING_HASHKEY:-$(generate_hex 32)}}
-        SIGNALING_BLOCKKEY=${HPB_BLOCKKEY:-${SIGNALING_BLOCKKEY:-$(generate_hex 16)}}
-        SIGNALING_INTERNAL_SECRET=${HPB_INTERNAL_SECRET:-${SIGNALING_INTERNAL_SECRET:-$(generate_hex 32)}}
-        SIGNALING_BACKEND_SECRET=${HPB_BACKEND_SECRET:-${SIGNALING_BACKEND_SECRET:-$(generate_hex 32)}}
-        TURN_SECRET=${TURN_SECRET:-$(generate_hex 32)}
-        TURN_API_KEY=${TURN_API_KEY:-$(generate_base64 16)}
-        JANUS_ADMIN_SECRET=${JANUS_ADMIN_SECRET:-$(generate_base64 16)}
-        
-        log_info "Секреты загружены из файла"
-    else
-        # Проверяем переменные окружения
-        SIGNALING_HASHKEY=${HPB_HASHKEY:-$(generate_hex 32)}
-        SIGNALING_BLOCKKEY=${HPB_BLOCKKEY:-$(generate_hex 16)}
-        SIGNALING_INTERNAL_SECRET=${HPB_INTERNAL_SECRET:-$(generate_hex 32)}
-        SIGNALING_BACKEND_SECRET=${HPB_BACKEND_SECRET:-$(generate_hex 32)}
-        TURN_SECRET=${TURN_SECRET:-$(generate_hex 32)}
-        TURN_API_KEY=${TURN_API_KEY:-$(generate_base64 16)}
-        JANUS_ADMIN_SECRET=${JANUS_ADMIN_SECRET:-$(generate_base64 16)}
-        
-        if [ -n "${HPB_HASHKEY:-}" ] || [ -n "${HPB_BLOCKKEY:-}" ] || [ -n "${HPB_INTERNAL_SECRET:-}" ]; then
-            log_info "Секреты загружены из переменных окружения"
-        else
-            log_info "Секреты сгенерированы автоматически"
-        fi
-    fi
-}
-
-# Создание пользователей системы
-create_users() {
-    log_info "Создание системных пользователей..."
-    
-    # Пользователь для signaling
-    if ! id "_signaling" &>/dev/null; then
-        useradd --system --no-create-home --shell /usr/sbin/nologin \
-            --comment "Nextcloud Talk signaling server" _signaling || true
-        log_info "Пользователь _signaling создан"
-    else
-        log_warn "Пользователь _signaling уже существует"
-    fi
-    
-    # Пользователь для NATS (обычно уже есть)
-    if ! id "nats" &>/dev/null; then
-        useradd --system --no-create-home --shell /usr/sbin/nologin \
-            --comment "NATS Server" nats || true
-        log_info "Пользователь nats создан"
-    else
-        log_warn "Пользователь nats уже существует"
-    fi
-    
-    # Пользователь для coturn (обычно уже есть)
-    if ! id "turnserver" &>/dev/null; then
-        useradd --system --no-create-home --shell /usr/sbin/nologin \
-            --comment "coTURN STUN/TURN Server" turnserver || true
-        log_info "Пользователь turnserver создан"
-    else
-        log_warn "Пользователь turnserver уже существует"
-    fi
-}
-
-# Копирование бинарников
-install_binaries() {
-    log_info "Установка бинарников..."
-    
-    # Signaling
-    if [[ -f "$SCRIPT_DIR/signaling-server/signaling" ]]; then
-        cp "$SCRIPT_DIR/signaling-server/signaling" "$BIN_DIR/signaling"
-        chmod 755 "$BIN_DIR/signaling"
-        log_info "signaling установлен в $BIN_DIR/signaling"
-    else
-        log_error "Бинарник signaling не найден!"
-        exit 1
-    fi
-    
-    # Janus
-    if [[ -f "$SCRIPT_DIR/signaling-server/janus/bin/janus" ]]; then
-        cp "$SCRIPT_DIR/signaling-server/janus/bin/janus" "$BIN_DIR/janus"
-        chmod 755 "$BIN_DIR/janus"
-        log_info "janus установлен в $BIN_DIR/janus"
-        
-        # Janus библиотеки
-        mkdir -p "$LIB_DIR"
-        cp -r "$SCRIPT_DIR/signaling-server/janus/lib/"* "$LIB_DIR/"
-        log_info "Janus библиотеки установлены в $LIB_DIR"
-    else
-        log_error "Бинарник janus не найден!"
-        exit 1
-    fi
-    
-    # NATS Server
-    if [[ -f "$SCRIPT_DIR/signaling-server/nats-server" ]]; then
-        cp "$SCRIPT_DIR/signaling-server/nats-server" "$SBIN_DIR/nats-server"
-        chmod 755 "$SBIN_DIR/nats-server"
-        log_info "nats-server установлен в $SBIN_DIR/nats-server"
-    else
-        log_error "Бинарник nats-server не найден!"
-        exit 1
-    fi
-    
-    # coTURN
-    if [[ -f "$SCRIPT_DIR/signaling-server/turnserver" ]]; then
-        cp "$SCRIPT_DIR/signaling-server/turnserver" "$BIN_DIR/turnserver"
-        chmod 755 "$BIN_DIR/turnserver"
-        # Создаем симлинк coturn -> turnserver
-        ln -sf turnserver "$BIN_DIR/coturn"
-        log_info "turnserver установлен в $BIN_DIR/turnserver"
-    else
-        log_error "Бинарник turnserver не найден!"
-        exit 1
-    fi
-}
-
-# Установка конфигов с подстановкой секретов
-install_configs() {
-    log_info "Установка конфигурационных файлов..."
-    
-    # Создаем директории
-    mkdir -p "$INSTALL_DIR"
-    mkdir -p "$CONFIG_DIR"
-    
-    # Signaling server.conf
-    if [[ -f "$SCRIPT_DIR/server.conf.example" ]]; then
-        # Определяем URL Nextcloud из переменной окружения или используем плейсхолдер
-        NEXTCLOUD_URL=${F7CLOUD_URL:-${NEXTCLOUD_URL:-"https://your-nextcloud.example"}}
-        
-        sed -e "s|YOUR_32_OR_64_BYTE_HEX_HASHKEY|$SIGNALING_HASHKEY|g" \
-            -e "s|YOUR_16_24_OR_32_BYTE_HEX_BLOCKKEY|$SIGNALING_BLOCKKEY|g" \
-            -e "s|YOUR_INTERNAL_CLIENT_SECRET|$SIGNALING_INTERNAL_SECRET|g" \
-            -e "s|YOUR_NEXTCLOUD_BACKEND_SECRET|$SIGNALING_BACKEND_SECRET|g" \
-            -e "s|YOUR_TURN_API_KEY|$TURN_API_KEY|g" \
-            -e "s|YOUR_TURN_SHARED_SECRET|$TURN_SECRET|g" \
-            -e "s|https://your-nextcloud.example|$NEXTCLOUD_URL|g" \
-            "$SCRIPT_DIR/server.conf.example" > "$INSTALL_DIR/server.conf"
-        chmod 600 "$INSTALL_DIR/server.conf"
-        chown _signaling:_signaling "$INSTALL_DIR/server.conf"
-        log_info "server.conf создан в $INSTALL_DIR/server.conf"
-        log_warn "ВАЖНО: Отредактируйте $INSTALL_DIR/server.conf - укажите реальные URL бэкендов Nextcloud!"
-    else
-        log_error "server.conf.example не найден!"
-        exit 1
-    fi
-    
-    # Janus конфиги
-    if [[ -d "$SCRIPT_DIR/config/janus" ]]; then
-        cp -r "$SCRIPT_DIR/config/janus/"* "$CONFIG_DIR/"
-        # Подставляем admin_secret в janus.jcfg
-        sed -i "s|admin_secret = \"CHANGE_ME\"|admin_secret = \"$JANUS_ADMIN_SECRET\"|g" \
-            "$CONFIG_DIR/janus.jcfg"
-        chown -R root:root "$CONFIG_DIR"
-        log_info "Janus конфиги установлены в $CONFIG_DIR"
-    else
-        log_error "Janus конфиги не найдены!"
-        exit 1
-    fi
-    
-    # coTURN turnserver.conf
-    if [[ -f "$SCRIPT_DIR/config/coturn/turnserver.conf.example" ]]; then
-        # Получаем публичный IP (если доступен) или оставляем плейсхолдер
-        PUBLIC_IP=$(curl -s --max-time 2 https://api.ipify.org 2>/dev/null || echo "YOUR_PUBLIC_IP")
-        DOMAIN=$(hostname -f 2>/dev/null || echo "YOUR_DOMAIN")
-        
-        sed -e "s|YOUR_TURN_STATIC_AUTH_SECRET|$TURN_SECRET|g" \
-            -e "s|YOUR_PUBLIC_IP|$PUBLIC_IP|g" \
-            -e "s|YOUR_DOMAIN|$DOMAIN|g" \
-            "$SCRIPT_DIR/config/coturn/turnserver.conf.example" > "/etc/turnserver.conf"
-        chmod 640 "/etc/turnserver.conf"
-        chown turnserver:turnserver "/etc/turnserver.conf"
-        log_info "turnserver.conf создан в /etc/turnserver.conf"
-        log_warn "ВАЖНО: Отредактируйте /etc/turnserver.conf - укажите реальные IP адреса и пути к сертификатам!"
-    else
-        log_error "turnserver.conf.example не найден!"
-        exit 1
-    fi
-    
-    # NATS конфиг
-    if [[ -f "$SCRIPT_DIR/config/nats/nats-server.conf" ]]; then
-        cp "$SCRIPT_DIR/config/nats/nats-server.conf" "/etc/nats-server.conf"
-        chmod 644 "/etc/nats-server.conf"
-        chown nats:nats "/etc/nats-server.conf"
-        log_info "nats-server.conf установлен в /etc/nats-server.conf"
-    else
-        log_error "nats-server.conf не найден!"
-        exit 1
-    fi
-}
-
-# Установка systemd unit файлов
-install_systemd() {
-    log_info "Установка systemd unit файлов..."
-    
-    if [[ -d "$SCRIPT_DIR/systemd" ]]; then
-        cp "$SCRIPT_DIR/systemd/"*.service "$SYSTEMD_DIR/"
-        systemctl daemon-reload
-        log_info "Systemd unit файлы установлены"
-    else
-        log_error "Systemd unit файлы не найдены!"
-        exit 1
-    fi
-}
-
-# Сохранение секретов в файл (для справки)
-save_secrets() {
-    SECRETS_FILE="$INSTALL_DIR/.secrets.txt"
-    cat > "$SECRETS_FILE" <<EOF
-# Сгенерированные секреты при установке $(date)
-# ВАЖНО: Сохраните этот файл в безопасном месте!
-
-# Signaling Server
-hashkey = $SIGNALING_HASHKEY
-blockkey = $SIGNALING_BLOCKKEY
-internalsecret = $SIGNALING_INTERNAL_SECRET
-backend_secret = $SIGNALING_BACKEND_SECRET
-
-# TURN Server (используется в signaling и turnserver)
-turn_secret = $TURN_SECRET
-turn_apikey = $TURN_API_KEY
-
-# Janus
-admin_secret = $JANUS_ADMIN_SECRET
-
-EOF
-    chmod 600 "$SECRETS_FILE"
-    log_warn "Секреты сохранены в $SECRETS_FILE"
-    log_warn "ВАЖНО: Сохраните этот файл в безопасном месте!"
-}
-
-# Основная функция установки
-main() {
-    log_info "Начало установки HPB - Nextcloud Spreed Signaling Stack"
-    
-    check_root
-    generate_secrets
-    create_users
-    install_binaries
-    install_configs
-    install_systemd
-    save_secrets
-    
-    log_info ""
-    log_info "=========================================="
-    log_info "Установка завершена успешно!"
-    log_info "=========================================="
-    log_info ""
-    log_warn "СЛЕДУЮЩИЕ ШАГИ:"
-    log_warn "1. Отредактируйте $INSTALL_DIR/server.conf - укажите URL бэкендов Nextcloud"
-    log_warn "2. Отредактируйте /etc/turnserver.conf - укажите реальные IP и пути к сертификатам"
-    log_warn "3. Проверьте конфиги в $CONFIG_DIR/janus/"
-    log_warn "4. Секреты сохранены в $INSTALL_DIR/.secrets.txt"
-    log_info ""
-    log_info "Для запуска сервисов выполните:"
-    log_info "  systemctl enable signaling janus nats-server coturn"
-    log_info "  systemctl start signaling janus nats-server coturn"
-    log_info ""
-}
-
-# Запуск
-main "$@"

overlay/etc/janus/janus.jcfg

@@ -268,7 +268,7 @@ media: {
 # be used for gathering candidates, and enable or disable the
 # internal libnice debugging, if needed.
 nat: {
-	stun_server = "global-hpb.f7cloud.ru" # HAND-EDIT
+	stun_server = ""
 	stun_port = 5349 # HAND-EDIT PORT-EDIT (443)
 	nice_debug = false
 	full_trickle = true # HAND-EDIT
@@ -330,7 +330,7 @@ nat: {
 	# by default; if that one is missing, the 'session_id' will be used as the
 	# username instead.
 	#turn_rest_api = "http://yourbackend.com/path/to/api"
-	turn_rest_api_key = "wU6fR0Eb0J4Aky5NuNeo3w==" # HAND-EDIT
+	turn_rest_api_key = ""
 	#turn_rest_api_method = "GET"
 	#turn_rest_api_timeout = 10
 

overlay/etc/turnserver.conf

@@ -0,0 +1,774 @@
+# Coturn TURN SERVER configuration file
+#
+# Boolean values note: where a boolean value is supposed to be used,
+# you can use '0', 'off', 'no', 'false', or 'f' as 'false,
+# and you can use '1', 'on', 'yes', 'true', or 't' as 'true'
+# If the value is missing, then it means 'true' by default.
+#
+
+# Listener interface device (optional, Linux only).
+# NOT RECOMMENDED.
+#
+#listening-device=eth0
+
+# TURN listener port for UDP and TCP (Default: 3478).
+# Note: actually, TLS & DTLS sessions can connect to the
+# "plain" TCP & UDP port(s), too - if allowed by configuration.
+#
+#listening-port=3478
+
+# TURN listener port for TLS (Default: 5349).
+# Note: actually, "plain" TCP & UDP sessions can connect to the TLS & DTLS
+# port(s), too - if allowed by configuration. The TURN server
+# "automatically" recognizes the type of traffic. Actually, two listening
+# endpoints (the "plain" one and the "tls" one) are equivalent in terms of
+# functionality; but Coturn keeps both endpoints to satisfy the RFC 5766 specs.
+# For secure TCP connections, Coturn currently supports
+# TLS version 1.0, 1.1 and 1.2.
+# For secure UDP connections, Coturn supports DTLS version 1.
+#
+tls-listening-port=5349
+# PORT-EDIT (5349)
+
+# Alternative listening port for UDP and TCP listeners;
+# default (or zero) value means "listening port plus one".
+# This is needed for RFC 5780 support
+# (STUN extension specs, NAT behavior discovery). The TURN Server
+# supports RFC 5780 only if it is started with more than one
+# listening IP address of the same family (IPv4 or IPv6).
+# RFC 5780 is supported only by UDP protocol, other protocols
+# are listening to that endpoint only for "symmetry".
+#
+#alt-listening-port=0
+
+# Alternative listening port for TLS and DTLS protocols.
+# Default (or zero) value means "TLS listening port plus one".
+#
+#alt-tls-listening-port=0
+
+# Some network setups will require using a TCP reverse proxy in front
+# of the STUN server. If the proxy port option is set a single listener
+# is started on the given port that accepts connections using the
+# haproxy proxy protocol v2.
+# (https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt)
+#
+#tcp-proxy-port=5555
+
+# Listener IP address of relay server. Multiple listeners can be specified.
+# If no IP(s) specified in the config file or in the command line options,
+# then all IPv4 and IPv6 system IPs will be used for listening.
+#
+#listening-ip=172.17.19.101
+#listening-ip=10.207.21.238
+#listening-ip=2607:f0d0:1002:51::4
+listening-ip=127.0.0.1
+listening-ip=127.0.1.1
+listening-ip=::1
+listening-ip=192.168.70.81
+listening-ip=
+
+# Auxiliary STUN/TURN server listening endpoint.
+# Aux servers have almost full TURN and STUN functionality.
+# The (minor) limitations are:
+#
+# 1) Auxiliary servers do not have alternative ports and
+# they do not support STUN RFC 5780 functionality (CHANGE REQUEST).
+#
+# 2) Auxiliary servers also are never returning ALTERNATIVE-SERVER reply.
+#
+# Valid formats are 1.2.3.4:5555 for IPv4 and [1:2::3:4]:5555 for IPv6.
+#
+# There may be multiple aux-server options, each will be used for listening
+# to client requests.
+#
+#aux-server=172.17.19.110:33478
+#aux-server=[2607:f0d0:1002:51::4]:33478
+
+# (recommended for older Linuxes only)
+# Automatically balance UDP traffic over auxiliary servers (if configured).
+# The load balancing is using the ALTERNATE-SERVER mechanism.
+# The TURN client must support 300 ALTERNATE-SERVER response for this
+# functionality.
+#
+#udp-self-balance
+
+# Relay interface device for relay sockets (optional, Linux only).
+# NOT RECOMMENDED.
+#
+#relay-device=eth1
+
+# Relay address (the local IP address that will be used to relay the
+# packets to the peer).
+# Multiple relay addresses may be used.
+# The same IP(s) can be used as both listening IP(s) and relay IP(s).
+#
+# If no relay IP(s) specified, then the turnserver will apply the default
+# policy: it will decide itself which relay addresses to be used, and it
+# will always be using the client socket IP address as the relay IP address
+# of the TURN session (if the requested relay address family is the same
+# as the family of the client socket).
+#
+#relay-ip=172.17.19.105
+#relay-ip=2607:f0d0:1002:51::5
+relay-ip=192.168.70.81
+relay-ip=
+
+# For Amazon EC2 users:
+#
+# TURN Server public/private address mapping, if the server is behind NAT.
+# In that situation, if a -X is used in form "-X <ip>" then that ip will be reported
+# as relay IP address of all allocations. This scenario works only in a simple case
+# when one single relay address is be used, and no RFC5780 functionality is required.
+# That single relay address must be mapped by NAT to the 'external' IP.
+# The "external-ip" value, if not empty, is returned in XOR-RELAYED-ADDRESS field.
+# For that 'external' IP, NAT must forward ports directly (relayed port 12345
+# must be always mapped to the same 'external' port 12345).
+#
+# In more complex case when more than one IP address is involved,
+# that option must be used several times, each entry must
+# have form "-X <public-ip/private-ip>", to map all involved addresses.
+# RFC5780 NAT discovery STUN functionality will work correctly,
+# if the addresses are mapped properly, even when the TURN server itself
+# is behind A NAT.
+#
+# By default, this value is empty, and no address mapping is used.
+#
+#external-ip=60.70.80.91
+#
+#OR:
+#
+#external-ip=60.70.80.91/172.17.19.101
+#external-ip=60.70.80.92/172.17.19.102
+
+# Number of the relay threads to handle the established connections
+# (in addition to authentication thread and the listener thread).
+# If explicitly set to 0 then application runs relay process in a
+# single thread, in the same thread with the listener process
+# (the authentication thread will still be a separate thread).
+#
+# If this parameter is not set, then the default OS-dependent
+# thread pattern algorithm will be employed. Usually the default
+# algorithm is optimal, so you have to change this option
+# if you want to make some fine tweaks.
+#
+# In the older systems (Linux kernel before 3.9),
+# the number of UDP threads is always one thread per network listening
+# endpoint - including the auxiliary endpoints - unless 0 (zero) or
+# 1 (one) value is set.
+#
+#relay-threads=0
+
+# Lower and upper bounds of the UDP relay endpoints:
+# (default values are 49152 and 65535)
+#
+min-port=49152
+max-port=65535
+
+# Uncomment to run TURN server in 'normal' 'moderate' verbose mode.
+# By default the verbose mode is off.
+verbose
+
+# Uncomment to run TURN server in 'extra' verbose mode.
+# This mode is very annoying and produces lots of output.
+# Not recommended under normal circumstances.
+#
+#Verbose
+
+# Uncomment to use fingerprints in the TURN messages.
+# By default the fingerprints are off.
+#
+fingerprint
+
+# Uncomment to use long-term credential mechanism.
+# By default no credentials mechanism is used (any user allowed).
+#
+#lt-cred-mech
+
+# This option is the opposite of lt-cred-mech.
+# (TURN Server with no-auth option allows anonymous access).
+# If neither option is defined, and no users are defined,
+# then no-auth is default. If at least one user is defined,
+# in this file, in command line or in usersdb file, then
+# lt-cred-mech is default.
+#
+#no-auth
+
+# Enable prometheus exporter
+# If enabled the turnserver will expose an endpoint with stats on a prometheus format
+# this endpoint is listening on a different port to not conflict with other configurations.
+#
+# You can simply run the turnserver and access the port 9641 and path /metrics
+#
+# For mor info on the prometheus exporter and metrics
+# https://prometheus.io/docs/introduction/overview/
+# https://prometheus.io/docs/concepts/data_model/
+#
+#prometheus
+
+# TURN REST API flag.
+# (Time Limited Long Term Credential)
+# Flag that sets a special authorization option that is based upon authentication secret.
+#
+# This feature's purpose is to support "TURN Server REST API", see
+# "TURN REST API" link in the project's page
+# https://github.com/coturn/coturn/
+#
+# This option is used with timestamp:
+#
+# usercombo -> "timestamp:userid"
+# turn user -> usercombo
+# turn password -> base64(hmac(secret key, usercombo))
+#
+# This allows TURN credentials to be accounted for a specific user id.
+# If you don't have a suitable id, then the timestamp alone can be used.
+# This option is enabled by turning on secret-based authentication.
+# The actual value of the secret is defined either by the option static-auth-secret,
+# or can be found in the turn_secret table in the database (see below).
+#
+# Read more about it:
+#  - https://tools.ietf.org/html/draft-uberti-behave-turn-rest-00
+#  - https://www.ietf.org/proceedings/87/slides/slides-87-behave-10.pdf
+#
+# Be aware that use-auth-secret overrides some parts of lt-cred-mech.
+# The use-auth-secret feature depends internally on lt-cred-mech, so if you set
+# this option then it automatically enables lt-cred-mech internally
+# as if you had enabled both.
+#
+# Note that you can use only one auth mechanism at the same time! This is because,
+# both mechanisms conduct username and password validation in different ways.
+#
+# Use either lt-cred-mech or use-auth-secret in the conf
+# to avoid any confusion.
+#
+use-auth-secret
+
+# 'Static' authentication secret value (a string) for TURN REST API only.
+# If not set, then the turn server
+# will try to use the 'dynamic' value in the turn_secret table
+# in the user database (if present). The database-stored  value can be changed on-the-fly
+# by a separate program, so this is why that mode is considered 'dynamic'.
+#
+static-auth-secret=
+
+# Server name used for
+# the oAuth authentication purposes.
+# The default value is the realm name.
+#
+#server-name=blackdow.carleon.gov
+
+# Flag that allows oAuth authentication.
+#
+#oauth
+
+# 'Static' user accounts for the long term credentials mechanism, only.
+# This option cannot be used with TURN REST API.
+# 'Static' user accounts are NOT dynamically checked by the turnserver process,
+# so they can NOT be changed while the turnserver is running.
+#
+#user=username1:key1
+#user=username2:key2
+# OR:
+#user=username1:password1
+#user=username2:password2
+#
+# Keys must be generated by turnadmin utility. The key value depends
+# on user name, realm, and password:
+#
+# Example:
+# $ turnadmin -k -u ninefingers -r north.gov -p youhavetoberealistic
+# Output: 0xbc807ee29df3c9ffa736523fb2c4e8ee
+# ('0x' in the beginning of the key is what differentiates the key from
+# password. If it has 0x then it is a key, otherwise it is a password).
+#
+# The corresponding user account entry in the config file will be:
+#
+#user=ninefingers:0xbc807ee29df3c9ffa736523fb2c4e8ee
+# Or, equivalently, with open clear password (less secure):
+#user=ninefingers:youhavetoberealistic
+#
+
+# SQLite database file name.
+#
+# The default file name is /var/db/turndb or /usr/local/var/db/turndb or
+# /var/lib/turn/turndb.
+#
+#userdb=/var/db/turndb
+
+# PostgreSQL database connection string in the case that you are using PostgreSQL
+# as the user database.
+# This database can be used for the long-term credential mechanism
+# and it can store the secret value for secret-based timed authentication in TURN REST API.
+# See http://www.postgresql.org/docs/8.4/static/libpq-connect.html for 8.x PostgreSQL
+# versions connection string format, see
+# http://www.postgresql.org/docs/9.2/static/libpq-connect.html#LIBPQ-CONNSTRING
+# for 9.x and newer connection string formats.
+#
+#psql-userdb="host=<host> dbname=<database-name> user=<database-user> password=<database-user-password> connect_timeout=30"
+
+# MySQL database connection string in the case that you are using MySQL
+# as the user database.
+# This database can be used for the long-term credential mechanism
+# and it can store the secret value for secret-based timed authentication in TURN REST API.
+#
+# Optional connection string parameters for the secure communications (SSL):
+# ca, capath, cert, key, cipher
+# (see http://dev.mysql.com/doc/refman/5.1/en/ssl-options.html for the
+# command options description).
+#
+# Use the string format below (space separated parameters, all optional):
+#
+#mysql-userdb="host=<host> dbname=<database-name> user=<database-user> password=<database-user-password> port=<port> connect_timeout=<seconds> read_timeout=<seconds>"
+
+# If you want to use an encrypted password in the MySQL connection string,
+# then set the MySQL password encryption secret key file with this option.
+#
+# Warning: If this option is set, then the mysql password must be set in "mysql-userdb" in an encrypted format!
+# If you want to use a cleartext password then do not set this option!
+#
+# This is the file path for the aes encrypted secret key used for password encryption.
+#
+#secret-key-file=/path/
+
+# MongoDB database connection string in the case that you are using MongoDB
+# as the user database.
+# This database can be used for long-term credential mechanism
+# and it can store the secret value for secret-based timed authentication in TURN REST API.
+# Use the string format described at http://hergert.me/docs/mongo-c-driver/mongoc_uri.html
+#
+#mongo-userdb="mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]"
+
+# Redis database connection string in the case that you are using Redis
+# as the user database.
+# This database can be used for long-term credential mechanism
+# and it can store the secret value for secret-based timed authentication in TURN REST API.
+# Use the string format below (space separated parameters, all optional):
+#
+#redis-userdb="ip=<ip-address> dbname=<database-number> password=<database-user-password> port=<port> connect_timeout=<seconds>"
+
+# Redis status and statistics database connection string, if used (default - empty, no Redis stats DB used).
+# This database keeps allocations status information, and it can be also used for publishing
+# and delivering traffic and allocation event notifications.
+# The connection string has the same parameters as redis-userdb connection string.
+# Use the string format below (space separated parameters, all optional):
+#
+#redis-statsdb="ip=<ip-address> dbname=<database-number> password=<database-user-password> port=<port> connect_timeout=<seconds>"
+
+# The default realm to be used for the users when no explicit
+# origin/realm relationship is found in the database, or if the TURN
+# server is not using any database (just the commands-line settings
+# and the userdb file). Must be used with long-term credentials
+# mechanism or with TURN REST API.
+#
+# Note: If the default realm is not specified, then realm falls back to the host domain name.
+#       If the domain name string is empty, or set to '(None)', then it is initialized as an empty string.
+#
+realm=
+
+# This flag sets the origin consistency
+# check. Across the session, all requests must have the same
+# main ORIGIN attribute value (if the ORIGIN was
+# initially used by the session).
+#
+#check-origin-consistency
+
+# Per-user allocation quota.
+# default value is 0 (no quota, unlimited number of sessions per user).
+# This option can also be set through the database, for a particular realm.
+#
+#user-quota=0
+
+# Total allocation quota.
+# default value is 0 (no quota).
+# This option can also be set through the database, for a particular realm.
+#
+#total-quota=0
+
+# Max bytes-per-second bandwidth a TURN session is allowed to handle
+# (input and output network streams are treated separately). Anything above
+# that limit will be dropped or temporarily suppressed (within
+# the available buffer limits).
+# This option can also be set through the database, for a particular realm.
+#
+#max-bps=0
+
+#
+# Maximum server capacity.
+# Total bytes-per-second bandwidth the TURN server is allowed to allocate
+# for the sessions, combined (input and output network streams are treated separately).
+#
+# bps-capacity=0
+
+# Uncomment if no UDP client listener is desired.
+# By default UDP client listener is always started.
+#
+#no-udp
+
+# Uncomment if no TCP client listener is desired.
+# By default TCP client listener is always started.
+#
+#no-tcp
+
+# Uncomment if no TLS client listener is desired.
+# By default TLS client listener is always started.
+#
+#no-tls
+
+# Uncomment if no DTLS client listener is desired.
+# By default DTLS client listener is always started.
+#
+#no-dtls
+
+# Uncomment if no UDP relay endpoints are allowed.
+# By default UDP relay endpoints are enabled (like in RFC 5766).
+#
+#no-udp-relay
+
+# Uncomment if no TCP relay endpoints are allowed.
+# By default TCP relay endpoints are enabled (like in RFC 6062).
+#
+#no-tcp-relay
+
+# Uncomment if extra security is desired,
+# with nonce value having a limited lifetime.
+# The nonce value is unique for a session.
+# Set this option to limit the nonce lifetime.
+# Set it to 0 for unlimited lifetime.
+# It defaults to 600 secs (10 min) if no value is provided. After that delay,
+# the client will get 438 error and will have to re-authenticate itself.
+#
+#stale-nonce=600
+
+# Uncomment if you want to set the maximum allocation
+# time before it has to be refreshed.
+# Default is 3600s.
+#
+#max-allocate-lifetime=3600
+
+# Uncomment to set the lifetime for the channel.
+# Default value is 600 secs (10 minutes).
+# This value MUST not be changed for production purposes.
+#
+#channel-lifetime=600
+
+# Uncomment to set the permission lifetime.
+# Default to 300 secs (5 minutes).
+# In production this value MUST not be changed,
+# however it can be useful for test purposes.
+#
+#permission-lifetime=300
+
+# Certificate file.
+# Use an absolute path or path relative to the
+# configuration file.
+# Use PEM file format.
+#
+cert=/etc/letsencrypt/live/hpb-prod.f7cloud.ru-rsa/fullchain.pem
+
+# Private key file.
+# Use an absolute path or path relative to the
+# configuration file.
+# Use PEM file format.
+#
+pkey=/etc/letsencrypt/live/hpb-prod.f7cloud.ru-rsa/privkey.pem
+
+# Private key file password, if it is in encoded format.
+# This option has no default value.
+#
+#pkey-pwd=...
+
+# Allowed OpenSSL cipher list for TLS/DTLS connections.
+# Default value is "DEFAULT".
+#
+#cipher-list="DEFAULT"
+
+# CA file in OpenSSL format.
+# Forces TURN server to verify the client SSL certificates.
+# By default this is not set: there is no default value and the client
+# certificate is not checked.
+#
+# Example:
+#CA-file=/etc/ssh/id_rsa.cert
+
+# Curve name for EC ciphers, if supported by OpenSSL
+# library (TLS and DTLS). The default value is prime256v1,
+# if pre-OpenSSL 1.0.2 is used. With OpenSSL 1.0.2+,
+# an optimal curve will be automatically calculated, if not defined
+# by this option.
+#
+#ec-curve-name=prime256v1
+
+# Use 566 bits predefined DH TLS key. Default size of the key is 2066.
+#
+#dh566
+
+# Use 1066 bits predefined DH TLS key. Default size of the key is 2066.
+#
+#dh1066
+
+# Use custom DH TLS key, stored in PEM format in the file.
+# Flags --dh566 and --dh2066 are ignored when the DH key is taken from a file.
+#
+dh-file=/etc/certs/dhp/dhp.pem
+
+# Flag to prevent stdout log messages.
+# By default, all log messages go to both stdout and to
+# the configured log file. With this option everything will
+# go to the configured log only (unless the log file itself is stdout).
+#
+#no-stdout-log
+
+# Option to set the log file name.
+# By default, the turnserver tries to open a log file in
+# /var/log, /var/tmp, /tmp and the current directory
+# (Whichever file open operation succeeds first will be used).
+# With this option you can set the definite log file name.
+# The special names are "stdout" and "-" - they will force everything
+# to the stdout. Also, the "syslog" name will force everything to
+# the system log (syslog).
+# In the runtime, the logfile can be reset with the SIGHUP signal
+# to the turnserver process.
+#
+log-file=/var/tmp/turnserver.log
+
+# Option to redirect all log output into system log (syslog).
+#
+#syslog
+
+# This flag means that no log file rollover will be used, and the log file
+# name will be constructed as-is, without PID and date appendage.
+# This option can be used, for example, together with the logrotate tool.
+#
+#simple-log
+
+# Enable full ISO-8601 timestamp in all logs.
+#new-log-timestamp
+
+# Set timestamp format (in strftime(1) format)
+#new-log-timestamp-format "%FT%T%z"
+
+# Disabled by default binding logging in verbose log mode to avoid DoS attacks.
+# Enable binding logging and UDP endpoint logs in verbose log mode.
+#log-binding
+
+# Option to set the "redirection" mode. The value of this option
+# will be the address of the alternate server for UDP & TCP service in the form of
+# <ip>[:<port>]. The server will send this value in the attribute
+# ALTERNATE-SERVER, with error 300, on ALLOCATE request, to the client.
+# Client will receive only values with the same address family
+# as the client network endpoint address family.
+# See RFC 5389 and RFC 5766 for the description of ALTERNATE-SERVER functionality.
+# The client must use the obtained value for subsequent TURN communications.
+# If more than one --alternate-server option is provided, then the functionality
+# can be more accurately described as "load-balancing" than a mere "redirection".
+# If the port number is omitted, then the default port
+# number 3478 for the UDP/TCP protocols will be used.
+# Colon (:) characters in IPv6 addresses may conflict with the syntax of
+# the option. To alleviate this conflict, literal IPv6 addresses are enclosed
+# in square brackets in such resource identifiers, for example:
+# [2001:db8:85a3:8d3:1319:8a2e:370:7348]:3478 .
+# Multiple alternate servers can be set. They will be used in the
+# round-robin manner. All servers in the pool are considered of equal weight and
+# the load will be distributed equally. For example, if you have 4 alternate servers,
+# then each server will receive 25% of ALLOCATE requests. A alternate TURN server
+# address can be used more than one time with the alternate-server option, so this
+# can emulate "weighting" of the servers.
+#
+# Examples:
+#alternate-server=1.2.3.4:5678
+#alternate-server=11.22.33.44:56789
+#alternate-server=5.6.7.8
+#alternate-server=[2001:db8:85a3:8d3:1319:8a2e:370:7348]:3478
+
+# Option to set alternative server for TLS & DTLS services in form of
+# <ip>:<port>. If the port number is omitted, then the default port
+# number 5349 for the TLS/DTLS protocols will be used. See the previous
+# option for the functionality description.
+#
+# Examples:
+#tls-alternate-server=1.2.3.4:5678
+#tls-alternate-server=11.22.33.44:56789
+#tls-alternate-server=[2001:db8:85a3:8d3:1319:8a2e:370:7348]:3478
+
+# Option to suppress TURN functionality, only STUN requests will be processed.
+# Run as STUN server only, all TURN requests will be ignored.
+# By default, this option is NOT set.
+#
+#stun-only
+
+# Option to hide software version. Enhance security when used in production.
+# Revealing the specific software version of the agent through the
+# SOFTWARE attribute might allow them to become more vulnerable to
+# attacks against software that is known to contain security holes.
+# Implementers SHOULD make usage of the SOFTWARE attribute a
+# configurable option (https://tools.ietf.org/html/rfc5389#section-16.1.2)
+#
+#no-software-attribute
+
+# Option to suppress STUN functionality, only TURN requests will be processed.
+# Run as TURN server only, all STUN requests will be ignored.
+# By default, this option is NOT set.
+#
+#no-stun
+
+# This is the timestamp/username separator symbol (character) in TURN REST API.
+# The default value is ':'.
+# rest-api-separator=:
+
+# Flag that can be used to allow peers on the loopback addresses (127.x.x.x and ::1).
+# This is an extra security measure.
+#
+# (To avoid any security issue that allowing loopback access may raise,
+# the no-loopback-peers option is replaced by allow-loopback-peers.)
+#
+# Allow it only for testing in a development environment!
+# In production it adds a possible security vulnerability, so for security reasons
+# it is not allowed using it together with empty cli-password.
+#
+#allow-loopback-peers
+
+# Flag that can be used to disallow peers on well-known broadcast addresses (224.0.0.0 and above, and FFXX:*).
+# This is an extra security measure.
+#
+no-multicast-peers
+
+# Option to set the max time, in seconds, allowed for full allocation establishment.
+# Default is 60 seconds.
+#
+#max-allocate-timeout=60
+
+# Option to allow or ban specific ip addresses or ranges of ip addresses.
+# If an ip address is specified as both allowed and denied, then the ip address is
+# considered to be allowed. This is useful when you wish to ban a range of ip
+# addresses, except for a few specific ips within that range.
+#
+# This can be used when you do not want users of the turn server to be able to access
+# machines reachable by the turn server, but would otherwise be unreachable from the
+# internet (e.g. when the turn server is sitting behind a NAT)
+#
+# Examples:
+# denied-peer-ip=83.166.64.0-83.166.95.255
+# allowed-peer-ip=83.166.68.45
+denied-peer-ip=10.0.0.0-10.255.255.255
+denied-peer-ip=172.16.0.0-172.31.255.255
+denied-peer-ip=192.168.0.0-192.168.255.255
+denied-peer-ip=100.64.0.0-100.127.255.255
+denied-peer-ip=169.254.0.0-169.254.255.255
+denied-peer-ip=192.0.0.0-192.0.0.255
+denied-peer-ip=192.0.2.0-192.0.2.255
+denied-peer-ip=198.18.0.0-198.19.255.255
+denied-peer-ip=198.51.100.0-198.51.100.255
+denied-peer-ip=203.0.113.0-203.0.113.255
+denied-peer-ip=fc00::-fdff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
+denied-peer-ip=fe80::-febf:ffff:ffff:ffff:ffff:ffff:ffff:ffff
+denied-peer-ip=::ffff:0:0-::ffff:ffff:ffff
+denied-peer-ip=64:ff9b::-64:ff9b::ffff:ffff
+denied-peer-ip=64:ff9b:1::-64:ff9b:1:ffff:ffff:ffff:ffff:ffff
+denied-peer-ip=2001::-2001:1ff:ffff:ffff:ffff:ffff:ffff:ffff
+denied-peer-ip=2001:db8::-2001:db8:ffff:ffff:ffff:ffff:ffff:ffff
+denied-peer-ip=2002::-2002:ffff:ffff:ffff:ffff:ffff:ffff:ffff
+
+# File name to store the pid of the process.
+# Default is /var/run/turnserver.pid (if superuser account is used) or
+# /var/tmp/turnserver.pid .
+#
+#pidfile="/var/run/turnserver.pid"
+
+# Require authentication of the STUN Binding request.
+# By default, the clients are allowed anonymous access to the STUN Binding functionality.
+#
+#secure-stun
+
+# Mobility with ICE (MICE) specs support.
+#
+#mobility
+
+# Allocate Address Family according
+# If enabled then TURN server allocates address family according  the TURN
+# Client <=> Server communication address family.
+# (By default Coturn works according RFC 6156.)
+# !!Warning: Enabling this option breaks RFC6156 section-4.2 (violates use default IPv4)!!
+#
+keep-address-family
+
+# User name to run the process. After the initialization, the turnserver process
+# will attempt to change the current user ID to that user.
+#
+#proc-user=<user-name>
+
+# Group name to run the process. After the initialization, the turnserver process
+# will attempt to change the current group ID to that group.
+#
+#proc-group=<group-name>
+
+# Turn OFF the CLI support.
+# By default it is always ON.
+# See also options cli-ip and cli-port.
+#
+no-cli
+
+#Local system IP address to be used for CLI server endpoint. Default value
+# is 127.0.0.1.
+#
+#cli-ip=127.0.0.1
+
+# CLI server port. Default is 5766.
+#
+#cli-port=5766
+
+# CLI access password. Default is empty (no password).
+# For the security reasons, it is recommended that you use the encrypted
+# form of the password (see the -P command in the turnadmin utility).
+#
+# Secure form for password 'qwerty':
+#
+#cli-password=$5$79a316b350311570$81df9cfb9af7f5e5a76eada31e7097b663a0670f99a3c07ded3f1c8e59c5658a
+#
+# Or unsecure form for the same password:
+#
+#cli-password=qwerty
+
+# Enable Web-admin support on https. By default it is Disabled.
+# If it is enabled it also enables a http a simple static banner page
+# with a small reminder that the admin page is available only on https.
+#
+#web-admin
+
+# Local system IP address to be used for Web-admin server endpoint. Default value is 127.0.0.1.
+#
+#web-admin-ip=127.0.0.1
+
+# Web-admin server port. Default is 8080.
+#
+#web-admin-port=8080
+
+# Web-admin server listen on STUN/TURN worker threads
+# By default it is disabled for security resons! (Not recommended in any production environment!)
+#
+#web-admin-listen-on-workers
+
+#acme-redirect=http://redirectserver/.well-known/acme-challenge/
+# Redirect ACME, i.e. HTTP GET requests matching '^/.well-known/acme-challenge/(.*)' to '<URL>$1'.
+# Default is '', i.e. no special handling for such requests.
+
+# Server relay. NON-STANDARD AND DANGEROUS OPTION.
+# Only for those applications when you want to run
+# server applications on the relay endpoints.
+# This option eliminates the IP permissions check on
+# the packets incoming to the relay endpoints.
+#
+#server-relay
+
+# Maximum number of output sessions in ps CLI command.
+# This value can be changed on-the-fly in CLI. The default value is 256.
+#
+#cli-max-output-sessions
+
+# Set network engine type for the process (for internal purposes).
+#
+#ne=[1|2|3]
+
+# Do not allow an TLS/DTLS version of protocol
+#
+no-tlsv1
+no-tlsv1_1
+#no-tlsv1_2

systemd/signaling.service

@@ -1,5 +1,5 @@
 [Unit]
-Description=Nextcloud Talk signaling server
+Description=F7 Talk signaling server
 
 [Service]
 ExecStart=/usr/bin/signaling --config /etc/f7cloud-spreed-signaling/server.conf