Fix "Either -e peer_address or -y must be specified" in TURN allocation test

Another real failure from a live run: turnutils_uclient refuses to run at
all without either -e <peer> or -y — a bare auth-only invocation isn't
enough for it to actually attempt anything. Add -e 127.0.0.1 to both
tools/pstn-test-check.sh's and tools/coturn-test-check.sh's invocations;
loopback is always reachable since the test already runs via `docker exec`
inside the coturn container itself, and it lets the test actually prove
data relays through the allocation, not just that auth succeeded.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H4k6J1qXXyYxhGEgnJaMvn

tools/coturn-test-check.sh

@@ -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

@@ -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