I’m attempting to implement a full ICE connection using a TURN server, however I’m seeing that only ICE lite is supported? is this true? is there really no method to fully implement an ICE connection with a TURN server using mediasoup?
As documented mediasoup is a ICE Lite server and that has absolutely zero relationship with the fact that there is a TURN server or not, which is something completely unrelated and orthogonal.
ok but regarding ice lite vs ice full, why is mediasoup restricting users to ice lite? what are the advantages besides the server load being reduced? don’t the disadvantages of using ice lite compared to full ice outweigh the reduced server load?
mediasoup is supposed to run in a server with reachable public IP (or port forwarding or whatever). Given that assumption, being ICE Lite is enough since the only scenario in which Full ICE is required is when both endpoints are behind NAT without a publicly reachable IP. And it happens that implementing a ICE Lite stack is way easier than implementing a Full ICE stack so there is no relevant reason to implement the latter in mediasoup.
The point here is: why do you think that mediasoup should implement Full ICE? Just because browsers or libwebrtc do it is not a valid answer.
Sorry for the late reply, you have shed light which explains my confusion, thanks.