<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 11 Nov 2021, at 07:22, Olle E. Johansson <<a href="mailto:oej@edvina.net" class="">oej@edvina.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class="Apple-interchange-newline"><br class=""><blockquote type="cite" class=""><div class="">10 nov. 2021 kl. 18:21 skrev Ross McKillop <<a href="mailto:ross@rsmck.co.uk" class="">ross@rsmck.co.uk</a>>:</div><br class="Apple-interchange-newline"><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi,<div class=""><br class=""></div><div class="">Thanks, I was almost certain that is set but it seems it may not be so will double check that, thank you :) </div><div class=""><br class=""></div><div class="">Now to solve the other issue…. </div></div></div></blockquote>Just a nit-picking note: All these are non-standard fixes. The standard based way is to use the outbound module, it’s the way to allow the sip server to use an inbound TCP connection for outbound requests. This applies to client2server connections.</div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class=""></div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">For server2server connections there is a requirement of mutual TLS auth in order to be able to reuse the connection in both directions</div></div></blockquote><br class=""></div><div>I thought this would be possible with TCP too.</div><div><br class=""></div><div>I looked at the outbound module but this is a 'drop in' replacement for something that already exists, so I'm trying to avoid rewriting headers as would be required for flow IDs etc, however it's a definite preferred method for improvement.</div><div><br class=""></div><div>As an aside, and it may be the same issue in <a href="https://www.mail-archive.com/sr-users@lists.kamailio.org/msg15589.html" class="">https://www.mail-archive.com/sr-users@lists.kamailio.org/msg15589.html</a>, when you force an outbound socket on a specific port and a reply is received on that port, both $Rp and $Rut show the port on the first listen directive, not the port it was actually received on, which makes it a bit harder to do what I was trying to as well :/</div><div><br class=""></div><div>Ross</div><div><br class=""></div></body></html>