[OpenSIPS-Users] Broken Loose Routing?

Brett Nemeroff brett at nemeroff.com
Thu Oct 30 14:53:23 CET 2008

On Thu, Oct 30, 2008 at 8:44 AM, Iñaki Baz Castillo <ibc at aliax.net> wrote:

> 2008/10/30 Brett Nemeroff <brett at nemeroff.com>:
> > Hey All,I'm having a problem with a multi-homed proxy. It operates on two
> > IPs, one is an internal address and the other is an external public IP.
> >
> > The call I'm having trouble with goes like this:
> >
> > Call from PSTN->SIP gateway on internal network TO OpenSIPs
> >
> > OpenSIPs uses LCR + RTProxy and sends call to Provider
> >
> > Call is established just fine.
> >
> > Hangup on Provider side. Provider sends OpenSIPs BYE
> >
> > OpenSIPs sends BYE to INTERNAL IP (why?)
> If the BYE from providers arrives correctly to OpenSIPS it means that
> loose routing is working correctly.
> When OpenSIPS receives that in-dialog request (BYE) it must route it
> to the address indicated in RURI. What is that RURI?
> Note also that the RURI in the BYE is the URI in the Contact of the
> INVITE, and if there NAT issues the proxy must change
> (fix_natted_contact) that Contact and replace the private IP:port with
> the received IP:port.
> So, show a capture to find the problem.

Yes, the BYE arrives just fine.. it's that it isn't relaying it with loose
routing right. OpenSIPs is sending it's own internal address instead of
sending it to the other party.. The 200 OK and ACKs all work just fine..
just the BYE is broken.

I tried to post the full trace, but it was too long (41K with a limit of
40K) So I stuck it in a pastebin: http://www.pastebin.ca/1240174
The R-URI in the BYE from the provider looks good.. But it comes with route
headers that show both addresses from the double RR. Which I thought was
right. I was under the assumption that the loose routing should inspect the
route header and skip routes that are itself?

Please note, the provider isn't sending the BYE to the internal address. The
provider sends it to OpenSIPs Public address. Which is correct.. but then
OpenSIPs kills the dialog and relays the BYE to it's OWN internal address.
Which of course, there is no longer a dialog since it was killed and it
replies "404 Not here".

Any ideas?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20081030/8fb5c7e9/attachment.htm 

More information about the Users mailing list