Duane,<div><br></div><div>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.</div><div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>Regards,</div><div>Ali Pey<br><br><div class="gmail_quote">On Sat, Jul 7, 2012 at 3:35 PM, osiris123d <span dir="ltr"><<a href="mailto:duane.larson@gmail.com" target="_blank">duane.larson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is driving me crazy. I was right the first time when I said that one of<br>
the ACKs was not showing up as a loose route. It is the third ACK that is<br>
coming from the OpenSIPS/Proxy. When it reaches the OpenSIPS/SBC device the<br>
ACK fails as a loose route.<br>
<br>
It would make sense that this would not be a loose route because there are<br>
no Route headers so the loose_route() function would return FALSE.<br>
<br>
The issue still remains that when the ACK reaches the OpenSIPS/SBC it still<br>
isn't routed to the Callee, instead it is looped and routed to the same<br>
interface it came from because that is whats in the RURI.<br>
<br>
--<br>
View this message in context: <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Two-OpenSIPS-proxies-issue-tp7580685p7580743.html" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/Two-OpenSIPS-proxies-issue-tp7580685p7580743.html</a><br>
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>