It may be worthwhile speaking with the devs for sipp to see if they can make an adjustment to the default scenarios to account for this. It's a real pain. I seem to remember running into this alot. I usually mock up my own scenario with the RURIs changed..<div>
<br><div><br></div><div>-Brett</div><div><br></div><div><br><div class="gmail_quote">On Thu, Jul 16, 2009 at 11:29 PM, David <span dir="ltr"><<a href="mailto:dave.nwk@gmail.com">dave.nwk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Wed, Jul 15, 2009 at 4:09 PM, Iņaki Baz Castillo<<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>> wrote:<br>
><br>
> The ACK for a 200 is an *in-dialog* request so it must be setnt to the proxy<br>
> (since it did loose-routing by adding Record-Route header) and the RURI must<br>
> be the final destination.<br>
><br>
> SIPp doesn't handle corretly this case, I already tested it time ago. You must<br>
> to improve your SIPp scenario and set in the ACK RURI the Contact received in<br>
> the 200. That's all.<br>
<br>
</div>Ah.. darn sipp! I'll see if I can fix.<br>
I was able to make successful calls with another client, fortunately.<br>
<br>
Cheers<br>
<div><div></div><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></div>