Hello all, I just started using sipp and have run into a problem with a simple deREGISTER scenario, I send a deREGISTER and then expect to receive a 200, when the 200 comes in I get
2008-02-20 16:53:49:066 1203548029.066692: Aborting call on unexpected message for Call-Id '[EMAIL PROTECTED]': while expecting '200' (index 1), received 'SIP/2.0 200 OK Via: SIP/2.0/UDP 10.89.47.201:5080;branch=z9hG4bK-25704-1-0;received=10.89.47.201 From: <sip:[EMAIL PROTECTED]>;tag=1 To: <sip:[EMAIL PROTECTED]>;tag=1_1146_t63_2801 Call-ID: [EMAIL PROTECTED] CSeq: 1 REGISTER Date: Wed, 20 Feb 2008 21:50:30 GMT Content-Length: 0 '. I am wondering if the received= parameter in the Via is causing the response to not be matched correctly. Does anyone know the transaction matching algorithm in sipp well enough to know if that could be causing issues? I can throw the same message at a different UAS and the test completes successfully, and the only real difference I see in that 200 OK and the one that is causing problems is the received parameter. Thanks, Chris ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
