Dolby.io Director ICE / TURN / DTLS Diagnostics

PHP-proxied Director calls, TURN transport filtering, ICE candidate gathering, and optional browser-to-browser loopback media tests for DTLS, RTP, VPN, UDP blackhole, and possible DPI symptoms.

Stream Name

Publishing Token

ICE Transport Policy

Stream Account ID optional

TURN transport filters

TURN UDP 3478

TURN TCP 3478

TURNS TLS 443

Other TURN / TURNS

Relay classification uses candidate.url. The relay candidate port itself is usually an allocated ephemeral port, not 3478 or 443. Use All candidates to match the original page and show host/srflx candidates; Relay only intentionally suppresses host/srflx.

Additional diagnostics

Run DTLS/RTP loopback media test

Force relay for loopback

Verbose getStats logging

Show subscribe preview iframe

The loopback test creates two RTCPeerConnections in this browser, exchanges an offer/answer, sends generated video/audio, and checks if ICE, DTLS, and RTP counters actually move through the selected TURN path.

Ready.

Diagnostic Log

0 entries

Live Summary

Awaiting test

DPI / VPN Suspicion Score

0 / 10

No evidence yet.

Director Result

Mode

Publish

Director endpoint

https://director.millicast.com/api/director/publish

Resolved account

—

Resolved stream

—

Candidate result

—

Observed Relay Paths

Relay UDP 3478

—

Relay TCP 3478

—

Relay TLS 443

—

Host candidates

—

Server reflexive

—

Loopback DTLS / RTP Flow

ICE

—

DTLS

—

RTP Flow

—

Selected pair

—

Bytes sent

—

Bytes received

—

Packets received

—

RTT

—

ICE Servers Returned By Director

No response yet.

Subscribe Preview Viewer

Open Viewer

Iframe is a visual reference only; browser security prevents reading its internal WebRTC stats.

Interpretation

ICE-only success does not prove media will work. The strongest browser-side evidence of filtering is: relay selected, ICE connected, but DTLS fails or RTP counters stay at zero. That points to UDP blackhole, VPN filtering, DPI appliance behavior, or TURN/SRTP path filtering.