Can you try the latest master (or the last commit backported to your local branch)? Maybe I nailed down with one more condition in the core.
Cheers, Daniel On 19.08.21 18:08, Juha Heinanen wrote: > 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 -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
