When running SIPp as a client, we can provide the server endpoint. When using the TLS transport and a hostname server endpoint, the
application already resolve the ip of the host. However, there are no SNI added in the ClientHello during the TLS handshake.

This is something supported by OpenSSL than can be programmatically injected into the ssl context. I guess that WolfSSL supports it as well, but have not checked.

Do you see this as a good addition to the application ?
It could be either compilation flags (like Kamailio) or execution options.

Relevant links :

• https://www.cloudflare.com/learning/ssl/what-is-sni/
• https://datatracker.ietf.org/doc/html/rfc6066#section-3
• https://manpages.debian.org/experimental/libssl-doc/SSL_set_tlsext_host_name.3ssl.en.html
• Some known opensource server also support it : https://github.com/search?q=repo%3Akamailio%2Fkamailio%20tlsext&type=code