From agranig@sipwise.com Fri Sep 16 15:19:56 2011 From: Andreas Granig To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] wt_timer, delayed replies and sendto error Date: Fri, 16 Sep 2011 15:19:51 +0200 Message-ID: <4E734CF7.4060809@sipwise.com> In-Reply-To: <4E73450F.5040303@sipwise.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0632516687==" --===============0632516687== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Me again, On 09/16/2011 02:46 PM, Andreas Granig wrote: > And this is what I'd need to add if I got you right: > > # the default reply route used when transaction is already gone > onreply_route > { > if(reply from inside) > force_send_socket(localhost); > else > force_send_socket(public interface); > } I've tried to implement and test this, but there's one issue with it. If I have mhomed=1, then my injected (out of any transaction) reply hits this default route and is sent to the next hop (in my case 192.168.51.1:5060) according to the 2nd via header, so this is fine. However if I set mhomed=0, but still call force_send_socket(192.168.51.205:5060), I get the same error, like this: INFO: