Andreas,
The pseudo code looks correct to me. The chance should send the 500 1%
of the time, and after sending the 200, you should exit. The only
suggestion I can make it to add some action elements with logging to try
to debug your scenario.
Charles
Andreas Byström <[EMAIL PROTECTED]> wrote on 06/08/2007 10:54:58
AM:
> Hi Charles
>
> you are correct, there is a label at the end to jump to in case of a
> "200 OK scenario"
> This is how it looks like today (pseudo code):
>
> <recv request="INVITE" crlf="true" next="1" chance="0.01">
> <!-- Send 100 Trying -->
> <pause distribution="uniform" min="600" max="900" />
> <!-- Send 183 Ringing -->
> <pause distribution="uniform" min="200" max="400" />
> <!-- Send 200 OK (Answer call) -->
> <recv request="ACK" optional="true" crlf="true">
> <recv request="BYE">
> <!-- Send 200 OK -->
> <pause milliseconds="4000" next="2"/>
>
> <label id="1"/>
>
> <!-- Send 100 Trying -->
> <!-- Send 500 error -->
>
> <label id="2"/>
>
>
> Should it be enough to set chance="0.01" in the beginning?
>
> Regards,
> // Andreas
>
> -----Original Message-----
> From: Charles P Wright [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 08, 2007 1:30 PM
> To: Andreas Byström
> Cc: [email protected];
[EMAIL PROTECTED]
> Subject: Re: [Sipp-users] Question on random branching
>
> Andreas,
>
> Do you have a label at the end of your scenario that you jump to
> after your standard call setup? Something like:
>
> <recv request="INVITE" crlf="true" next="1" chance="0.01">
> </recv>
> <send 100 />
> <send 180 />
> <send 200 next="2" />
> <label id="1" />
> <send 500 />
> <label id="2" />
>
> Assuming this isn't it if you post your full scenario, then you
> should be able to get better answers.
>
> Charles
>
> [EMAIL PROTECTED] wrote on 06/08/2007 04:47:32
AM:
>
> > Hi all,
> >
> > I have been browsing through the mail archive but cant find any
> > answer to the problem I have. I hope that someone can help me
> >
> > I'm writing a AUS scenario and it starts with receiving an Invite.
> > Then I want that in 99% of the cases the call should be setup with
> > 180, 200 and so on. However, for 1% of the calls I want to send 500
> > Server Error instead (to simulate a specific case). When reading the
> > manual I found the "chance" command and tried to using that. This is
> > how my script starts:
> > <recv request="INVITE" crlf="true" next="1" chance="0.01">
> > </recv>
> > Now label=1 is jumping to a place where I send 500, and if I dont
> > jump the script continues with setting up a simple call.
> >
> > The problem is when I run this scenario Iget the 500 in all cases,
> > not only in 1% of the cases. Looking again in the documentaiton I
> > can only find examples where test and chance is used togheter. But
> > it also says that "test and chance can be combined, i.e to have..."
> > so I guess I should be able to use chance alone? If this is not
> > possible, can I add a test that is always true?
> >
> > Thanks in advance!
> > // Andreas
> >
-------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Sipp-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/sipp-users
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
