TCP ICE candidate (Direct TCP) for WebRTC has been added

[getroot]

WebRTC sessions can now connect over TCP without going through a TURN relay. This is implemented as Direct TCP ICE (RFC 6544), so the player talks to OvenMediaEngine directly over TCP when UDP is blocked. Compared to the previous TURN-based TCP path, there is one fewer hop and no relay overhead, which lowers latency and saves resources.

You can test it on the latest master branch.

What you need to configure

<IceCandidates>
    <IceCandidate>${PublicIP}:10000/udp</IceCandidate>
    <IceCandidate>${PublicIP}:10000/tcp</IceCandidate>   <!-- new -->
    <TcpRelay>${PublicIP}:3478</TcpRelay>                <!-- optional, for clients without RFC 6544 -->
    <DefaultTransport>udptcp</DefaultTransport>          <!-- new, default: udptcp -->
    <TcpRelayForce>false</TcpRelayForce>                 <!-- replaces the old TcpForce -->
</IceCandidates>

Direct TCP ICE and TURN relay can be used together. If you only need direct TCP, you can drop <TcpRelay>.

Transport policy (?transport)

Value	What is sent
(none)	follows <DefaultTransport> (default: udptcp)
udp	UDP direct only
tcp	Direct TCP ICE only
relay	TURN relay only
udptcp	UDP direct + TCP direct
all	UDP + TCP + TURN relay (full fallback)

Behavior change

?transport=tcp used to mean "go through the TURN relay over TCP". It now means Direct TCP ICE. To keep the previous behavior, use ?transport=relay.

<TcpForce> is renamed to <TcpRelayForce>. The old name is still accepted for backward compatibility.

Backward compatibility

Existing OvenPlayer setups continue to work without changes. Direct TCP ICE is added on top of the existing UDP and TURN relay paths, and the default policy keeps the previous behavior unless you opt into the new modes.

Manual

https://docs.ovenmediaengine.com/dev/live-source/webrtc#bind
https://docs.ovenmediaengine.com/dev/streaming/webrtc-publishing#configuration