TURN configured but no TURN candidate gathered

Description

The peer connection has at least one TURN server in its ICE server configuration, but no relay candidate was gathered during ICE gathering.

If the connection was already established over a direct or STUN path before TURN allocation completed, the browser may not need to use TURN, so no TURN candidate may be returned to the application side. This is expected. Otherwise, it could be a connectivity issue.

What do we do here?

We check that the configuration includes a TURN server. We then check whether any TURN candidate was gathered. If TURN is configured but no TURN candidate appears, we mark it as an observation.

Notes

• If you expected TURN to be used (e.g. in a restrictive network), check for ICE candidate errors (e.g. icecandidateerror / onicecandidateerror events) in the Logs tab and any TURN-related observations (timeouts, authentication, server errors) to diagnose connectivity or configuration issues