Re: [SR-Users] multihomed Kamailio and enable_double_rr

2013-08-21 Thread Steve Davies
Hi, On 20 August 2013 23:37, Daniel-Constantin Mierla wrote: > I would use also the tags - something like: > - save for invite: > $sht(x=>$ci::$ft) = $sel(contact.uri); > - save for 200ok of invite > $sht(x=>$ci::$tt) = $sel(contact.uri); > > For bye, if uri==myself, then if $sht(x=>$ci::$tt)!=

Re: [SR-Users] multihomed Kamailio and enable_double_rr

2013-08-21 Thread Daniel-Constantin Mierla
Hello, On 8/21/13 10:36 AM, Steve Davies wrote: On 20 August 2013 18:49, Daniel-Constantin Mierla > wrote: I wanted to add such logic in default config for kamailio as well (not mangle contact if not first proxy), but forgot about it, I'll do it soon. T

Re: [SR-Users] multihomed Kamailio and enable_double_rr

2013-08-21 Thread Steve Davies
On 20 August 2013 18:49, Daniel-Constantin Mierla wrote: > I wanted to add such logic in default config for kamailio as well (not > mangle contact if not first proxy), but forgot about it, I'll do it soon. > There is a new function is_first_hop() in devel version, for older version > the solution

Re: [SR-Users] multihomed Kamailio and enable_double_rr

2013-08-20 Thread Daniel-Constantin Mierla
On 8/20/13 9:08 PM, Steve Davies wrote: On 20 August 2013 18:49, Daniel-Constantin Mierla > wrote: If you cannot control 41.221.230.60 or ask for a change there, the solution is to use htable in your config to store the contact uri from invite and repl

Re: [SR-Users] multihomed Kamailio and enable_double_rr

2013-08-20 Thread Steve Davies
On 20 August 2013 18:49, Daniel-Constantin Mierla wrote: > If you cannot control 41.221.230.60 or ask for a change there, the > solution is to use htable in your config to store the contact uri from > invite and replace it in bye before loose_route(). > Let me have a go at doing it this way. F

Re: [SR-Users] multihomed Kamailio and enable_double_rr

2013-08-20 Thread Daniel-Constantin Mierla
Hello, the problem with the BYE is that the R-URI is the ip address of kamailio, resulting in match for strict routing rather than loose routing (both cases are handled by loose_route() function). My guess of what happens is that 41.221.230.60 detects the invite as coming from behind nat and

[SR-Users] multihomed Kamailio and enable_double_rr

2013-08-20 Thread Steve Davies
Hi, I'm having a problem with routing of BYEs in my multi homed Kamailio. My setup is a phone on 172.16.230.1, talking to Kamailio on 172.16.230.128. On the "outside" Kamailio uses 10.64.5.16 and its talking to 41.221.230.60 I'm using the stock Kamailio 4.0.3 kamailio.cfg, with: WITH_NAT defin