Thanks. With some tweaking, this approach worked.
Ron
________________________________
From: mayamatakeshi [mailto:mayamatake...@gmail.com]
Sent: Thursday, February 24, 2011 11:15 AM
To: SHACHAM, RON (RON)
Cc: sipp-users@lists.sourceforge.net
Subject: Re: [Sipp-users] Receiving messages in two different acceptable
orderings
On Fri, Feb 25, 2011 at 12:21 AM, SHACHAM, RON (RON)
<rshac...@research.att.com<mailto:rshac...@research.att.com>> wrote:
Hi.
Is there some way to script a scenario to allow for multiple correct
orderings of messages?
Here is a simple example: when a SUBSCRIBE is sent, the sender
should be ready to receive either the 200 OK or the NOTIFY first, as
per RFC 3265.
If I just write the scenario with <recv> of the response first, it will not
know what to do if the NOTIFY sometimes comes first, and will mark it
as an unexpected message.
Any help would be really appreciated.
I think you can use recv with tags "optional" and "next" like this (I wrote
from memory, please check syntax):
<recv request="NOTIFY" optional="true" next="handle_overlapping_notify"/>
<recv response="200" /> # for SUBSCRIBE
<recv request="NOTIFY"/>
<send>
200 OK for NOTIFY here.
</send>
<nop next="all_done"/>
<label id="handle_overlapping_notify"/>
<send">
200 OK for NOTIFY here.
</send>
<recv response="200" /> # for SUBSCRIBE
<label id="all_done"/>
Maybe there is a simpler and cleaner way, but this i what I would start with.
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
