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..
-Brett On Thu, Jul 16, 2009 at 11:29 PM, David <[email protected]> wrote: > On Wed, Jul 15, 2009 at 4:09 PM, Iñaki Baz Castillo<[email protected]> wrote: > > > > The ACK for a 200 is an *in-dialog* request so it must be setnt to the > proxy > > (since it did loose-routing by adding Record-Route header) and the RURI > must > > be the final destination. > > > > SIPp doesn't handle corretly this case, I already tested it time ago. You > must > > to improve your SIPp scenario and set in the ACK RURI the Contact > received in > > the 200. That's all. > > Ah.. darn sipp! I'll see if I can fix. > I was able to make successful calls with another client, fortunately. > > Cheers > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
