[OpenSIPS-Users] Two OpenSIPS proxies issue

[Ali Pey]

Does this mean that you found the problem?

Basically you need to follow the Ack's request URI and Route headers to see
why it's being routed the way it is and then you'd know how to fix it.

This is a good example similar to your scenario that you can use as a
reference: http://www.tech-invite.com/Ti-sip-dialog.html

Regards,
Ali Pey


On Thu, Jul 5, 2012 at 10:18 PM, <duane.larson at gmail.com> wrote:

> I see that the third 200 OK is edited by my OpenSIPS/Proxy server but that
> is because in the location table in the "received" field I stored the
> received Public IP address so that the replies are sent to the Public IP
> address of the device instead of the private IP that was in the original
> contact header.
>
>
>
> On , Ali Pey <alipey at gmail.com> wrote:
> > Examine the Contact header of the 200 OK. That's where this usually gets
> messed up.
> >
> > Regards,
> > Ali Pey
> >
> > On Wed, Jul 4, 2012 at 3:49 PM, Duane Larson duane.larson at gmail.com>
> wrote:
> >
> >
> > I have the following scenario
> >
> >
> > LAN OpenSIPS/SBC INTERNET OpenSIPS/Proxy
> >
> >
> >
> >
> > I have the OpenSIPS/SBC device because the firewall that is protecting
> the LAN doesn't play well with SIP.  It has the following IPs (LAN =
> 192.168.88.1), WAN (99.xx.xx.161).
> >
> >
> >
> > The OpenSIPS/Proxy device sits on the internet and has the following IP
> 50.xx.xx.156.
> >
> > All of the devices on the LAN point to the OpenSIPS/SBC as their proxy
> and then the OpenSIPS/SBC relays all requests to the OpenSIPS/Proxy.
> >
> >
> >
> >
> >
> > The issue I am seeing is that when a call is set up after the Callee
> sends the 200 OK the Caller sends the ACK but the ACK is never getting to
> the Callee.  So the Callee keeps sending 200 OKs and eventually when
> someone hangs up the other person doesn't know.
> >
> >
> >
> >
> >
> > I see that when the Caller sends the ACK it is sent to the OpenSIPS/SBC
> LAN address, then the OpenSIPS/SBC sends the ACK to the OpenSIPS/Proxy,
> then the OpenSIPS/Proxy sends it back to the OpenSIPS/SBC WAN address.  All
> of that is good but the next thing that happens is that the OpenSIPS/SBC
> sends the ACK not to the Callee but to its WAN interface.  I know this has
> something to do with my VIA headers but I am not sure how my config is
> messed up.
> >
> >
> >
> >
> >
> >
> > Here is the siptrace of the call
> >
> > http://pastebin.com/wpbut5Nb
> >
> > Here is the current config on the OpenSIPS/SBC box
> >
> >
> >
> >
> >
> > http://pastebin.com/PsahZEX3
> >
> >
> > Any ideas where I've messed up?
> >
> >
> >
> > _______________________________________________
> >
> >
> > Users mailing list
> >
> >
> > Users at lists.opensips.org
> >
> >
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120706/9022ae38/attachment.htm>