I am having an issue with 1.5.4 where force_send_socket() isn't behaving as I would expect. <br><br>I have an LCR scenario where depending on which gateway I am sending to, I send from a different socket. <br><br>It appears that calling force_send_socket from failure_route has no affect on the routing. In my initial route block I call force_send_socket(X.X.X.180:5060). In my failure_route I am calling force_send_socket(X.X.X.179:5060), yet after calling the subsequent time, my sip trace and tcpdump are clearly showing kamailio is still sending from X.X.X.180:5060.<br>
<br>I have added a lot of debug lines, so I am 100% sure the second call to force_send_socket is happening.<br><br>Am I misusing this module in some way?<br>