[OpenSIPS-Users] Two OpenSIPS proxies issue

[Ali Pey]

Duane,

The Ack should not have any request-route headers. Only Route headers. If
you see request-route headers, then you need to find how they got there and
fix that first.

I believe it is ok if the Ack doesn't go through loose route, in that case
it should be sent to the request-uri destination ip and that IP should be
your client IP.

Let me know if this help. If not, can you attach here a wireshark trace and
I will go through your signalling for you. Going thought a text trace can
be quit time consuming. In wireshark it's a lot easier to jump from a
message to another through the call flow. You can use tcpdump to capture to
.cap file for wireshark.

Regards,
Ali Pey

On Sat, Jul 7, 2012 at 3:35 PM, osiris123d <duane.larson at gmail.com> wrote:

> This is driving me crazy.  I was right the first time when I said that one
> of
> the ACKs was not showing up as a loose route.  It is the third ACK that is
> coming from the OpenSIPS/Proxy.  When it reaches the OpenSIPS/SBC device
> the
> ACK fails as a loose route.
>
> It would make sense that this would not be a loose route because there are
> no Route headers so the loose_route() function would return FALSE.
>
> The issue still remains that when the ACK reaches the OpenSIPS/SBC it still
> isn't routed to the Callee, instead it is looped and routed to the same
> interface it came from because that is whats in the RURI.
>
> --
> View this message in context:
> http://opensips-open-sip-server.1449251.n2.nabble.com/Two-OpenSIPS-proxies-issue-tp7580685p7580743.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> 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/20120708/bbb8b22b/attachment.htm>