[bug]: SNI isn't being set on websocket client connections
gtjoseph opened this issue · comments
Severity
Minor
Versions
all
Components/Modules
tcptls.c,iostream.c
Operating Environment
all
Frequency of Occurrence
Constant
Issue Description
When creating secure websocket client connections (wss), the destination hostname isn't being set in the TLS SNI extension. This causes TLS negotiation failures when the remote server hosts multiple virtual servers and needs SNI to distinguish between them.
Relevant log output
No response
Asterisk Issue Guidelines
- Yes, I have read the Asterisk Issue Guidelines