Tlloancy Turn Relay Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
WebRTC in the browser needs ICE servers. STUN discovers a public address. TURN relays the media when a direct path is impossible. coturn does that work. This plugin does not.
tlloancy Turn Relay signs a username and a password that coturn accepts for a limited time (use-auth-secret). The shared secret stays on the server. Callers receive iceServers for RTCPeerConnection and leave iceTransportPolicy at all.
Other plugins, including a video plugin, call tlloancy_turn_relay_get_ice_servers() when a call starts. They do not collect a TURN host of their own.
Publication is off until you turn it on. A published card is JSON. It never contains the shared secret.
- STUN only — the card lists a
stun:URL. - Shared — the card also lists the credential endpoint. Another site must present an invitation token.
- Private — the card contains the class and nothing else.
You can paste another site’s card URL. Private and loopback addresses are refused. The admin drawing measures latency in your browser with RTCPeerConnection. A figure advertised by the remote card is ignored.
Step-by-step guides: docs/USER-GUIDE.md (English) and docs/MODE-DEMPLOI.md (French).
External services
Nothing is contacted when you only issue credentials for your own coturn host.
If an administrator pastes a card URL, the server fetches that HTTPS URL once. The request sends no secret and no visitor data. The response is limited to 8 KB and redirects are not followed.
If an administrator then enables “During a call” on a shared node and stores that node’s invitation token, a call requests credentials from that node’s endpoint. The request sends the invitation token. It does not send your shared secret or the contents of the call. At most two nodes are asked.
The diagnostics buttons resolve your own TURN host and open a TCP connection to its TLS port. They run only when an administrator clicks them.
Screenshots
No screenshots provided
