root/ubuntu-post-install
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #314 from outis1one/claude/ionos-script-integration-x32ofw

Browse Source 
Fix "Either -e peer_address or -y must be specified" in TURN allocati…
This commit is contained in:
Outis
2026-08-11 22:18:48 -04:00
committed by GitHub
parent 5fff3f7c48 9f4f779220
commit c12d0d6cb1
2 changed files with 16 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/coturn-test-check.sh
+6 -1
View File
@@ -166,7 +166,12 @@ else
# server that never offered one. See tools/pstn-test-check.sh's
# matching comment — confirmed live this was the actual cause of a
# "Cannot complete Allocation" failure, not a real coturn problem.
OUT="$(docker exec coturn timeout 10 turnutils_uclient -u "$_u" -w "$_p" "$TEST_HOST" -p "$COTURN_PORT" 2>&1)"
#
# -e <peer> is also required — turnutils_uclient refuses to run at
# all without either -e or -y ("Either -e peer_address or -y must
# be specified", confirmed live). Loopback is fine since this runs
# via `docker exec` inside the coturn container itself.
OUT="$(docker exec coturn timeout 10 turnutils_uclient -u "$_u" -w "$_p" -e 127.0.0.1 "$TEST_HOST" -p "$COTURN_PORT" 2>&1)"
RC=$?
if [ "$RC" -eq 0 ]; then
ok "$c: TURN allocation succeeded (credentials + relay range + reachability all confirmed working)"
tools/pstn-test-check.sh
+10 -1
View File
@@ -216,7 +216,16 @@ else
# problem that doesn't exist. Confirmed live: this was the actual
# cause of a "Cannot complete Allocation" failure against an
# otherwise fully working coturn instance.
OUT="$(docker exec "$COTURN_CONTAINER" timeout 10 turnutils_uclient -u "$TURN_USERNAME" -w "$TURN_PASSWORD" 127.0.0.1 -p "${TURN_PORT:-3478}" 2>&1)"
#
# -e <peer> is required too — turnutils_uclient refuses to run at
# all without either -e or -y ("Either -e peer_address or -y must
# be specified", confirmed live), since without a peer address it
# has nothing to relay data to/from and there'd be no way to prove
# the allocation actually works end to end, not just that auth
# succeeded. Loopback is fine here — the test runs via `docker exec`
# inside the coturn container itself, so 127.0.0.1 is always
# reachable regardless of what's actually listening there.
OUT="$(docker exec "$COTURN_CONTAINER" timeout 10 turnutils_uclient -u "$TURN_USERNAME" -w "$TURN_PASSWORD" -e 127.0.0.1 127.0.0.1 -p "${TURN_PORT:-3478}" 2>&1)"
if [ $? -eq 0 ]; then
ok "Live TURN allocation succeeded with Asterisk's own configured credentials (user '$TURN_USERNAME')"
else