The [cseq] keyword might work for you (if you use it in all of your messages). Alternatively, you can introduce an integer variable and increment it yourself for the CSeq.
Charles "Fabio Margarido" <[EMAIL PROTECTED]> wrote on 02/26/2008 11:40:51 AM: > On Tue, Feb 26, 2008 at 12:14 PM, Charles P Wright <[EMAIL PROTECTED] > com> wrote: > > The last_cseq_number is taken from your last response not the messages in > > the scenario. > > That explains it then... My scenario is as follows: > > INVITE (CSeq 1) ---------------> > 183 (CSeq 1) <--------------- > PRACK (CSeq 2) ---------------> > 200 (CSeq 2) <--------------- > UPDATE (CSeq 3) ---------------> > 200 (CSeq 3) <--------------- > 200 (CSeq 1) <--------------- > ACK (CSeq 1) ---------------> > pause > BYE (CSeq 4) ---------------> > 200 (CSeq 4) <--------------- > > If I interrupt the call during the conversation pause, the BYE SIPp > sends, which should have CSeq 4, goes out with CSeq 2 and is rejected > by my application. Is there a way to work around this without having > to specify the CSeq number in the DefaultMessage as you suggested? > Thanks ------------------------------------------------------------------------- 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
