Seeking Guidance: How to ensure encryption on STUN Servers?

[Vinayak Bhat]

Hello Community,

I'm encountering an interesting situation regarding the encryption of STUN packets, and I'm seeking guidance on how to ensure encryption on STUN servers.

Here's the scenario:

When hitting the ICE TURN server at turns:kms.relsocial.net:5500?transport=tcp, I've observed that the STUN packets are TLS encrypted.

However, when hitting the ICE STUN server directly at stun:kms.relsocial.net:5500, the STUN packets are not TLS encrypted.

It's worth noting that port 5500 is configured as the tls-listening-port.

Could someone provide insights into why this discrepancy might occur? Additionally, I'm seeking advice on how to ensure that STUN packets are encrypted when accessing the STUN server directly.

Your expertise and suggestions would be highly appreciated.

Thank you!