The last_cseq_number is taken from your last response not the messages in the scenario.
Charles "Fabio Margarido" <[EMAIL PROTECTED]> wrote on 02/26/2008 09:42:07 AM: > On Fri, Feb 22, 2008 at 3:41 PM, Charles P Wright <[EMAIL PROTECTED]> wrote: > > In the trunk revision you can change the built-in messages with the > > DefaultMessage element: > > Nice. I'll try to figure out a way to change it and see what happens... > But from my understanding, the current version should also work. Like > you said, the default message is currently: > > > /* bye */ > > "BYE [last_Request_URI] SIP/2.0\n" > > "Via: SIP/2.0/[transport] > > [local_ip]:[local_port];branch=[branch]\n" > > "[last_From]\n" > > "[last_To]\n" > > "Call-ID: [call_id]\n" > > "CSeq: [last_cseq_number+1] BYE\n" > > "Max-Forwards: 70\n" > > "Contact: > > <sip:[EMAIL PROTECTED]:[local_port];transport=[transport]>\n" > > "Content-Length: 0\n\n", > > > > If the CSeq value used is last+1, it shouldn't always go out as 2, as > it does in my scenario (seeing that I have other methods, PRACK, > UPDATE in between INVITE and BYE), should it? Maybe the > 'last_cseq_number' variable is not being updated correctly. My script > is using fixed numbers for all of the CSeqs, could this be the cause? > 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
