Daniel-Constantin Mierla writes:
Probably the code that needs to be changed is in the core, where the message is built (msg_translator.c). rr module adds second conditional lump for record route, but at that stage is not aware what is going to be the final target address.
OK.
One more workaround would be using separate sockets, one tls and one websocket, I ended up doing so because the latest versions of web browsers do not allow traffic to standard sip ports anyhow because of the the slipstream attack.
The problem with using 443 port is that then it is not possible to run web server on the same host unless it is configured to proxy websocket traffic to sip proxy. But proxying causes its own issues due to which I would prefer direct access from browser to sip proxy.
I will try to look over the code soon, if nothing happens in 1-2 days, you can open an issue not to be forgotten.
OK, thanks,
-- Juha