From miconda@gmail.com Tue Sep 20 10:16:20 2011 From: Daniel-Constantin Mierla To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] wt_timer, delayed replies and sendto error Date: Tue, 20 Sep 2011 10:16:12 +0200 Message-ID: <4E784BCC.5030600@gmail.com> In-Reply-To: <4E734CF7.4060809@sipwise.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1165313185==" --===============1165313185== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, On 9/16/11 3:19 PM, Andreas Granig wrote: > 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=3D1, 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=3D0, but still call > force_send_socket(192.168.51.205:5060), I get the same error, like this: > > INFO: