Yes for question #1. For #2, you should be able to do it with a regular expression on the Retry-After header and a test attribute on a subsequent <nop> (you have to do it on an element after the 503, otherwise it won't work).
Charles Michael Hirschbichler <[EMAIL PROTECTED]> wrote on 10/25/2007 09:33:12 AM: > Hmm, OK, thanks > > the "variable" tag is new, isn't it? > > two more questions > * is it possible to loop?, like > <label 1> > <send register> > <recv 200 next 2> > <recv 503 and grep to "2"> > <multiply assign_to="2" value="1000" /> > <pause variable="2"> > <next 1> > <label 2> > > * 2nd question: > I get on some calls "503 Server too busy" (containing a > "Retry-After"-value) and sometimes "503 Service Unavailable" (no > "Retry-After"). Is it possible to differ between these two Responses? > A <recv response="503"> would catch both of the messages ... > > thanks! > BR > Michael > > Charles P Wright wrote: > > Michael, > > > > I have never done it, but you do require a few modifications. For the > > pause: > > <pause variable="2" /> > > You also probably need to multiply $2 by 1000 to convert from seconds to > > milliseconds. In your original action add: > > <multiply assign_to="2" value="1000" /> <!-- $2 *= 1000 --> > > One very minor thing is that you'll need another <recv response="200" /> > > after your send. > > > > Charles > > > > [EMAIL PROTECTED] wrote on 10/25/2007 09:12:07 AM: > > > >> Hi listmembers! > >> > >> I am working on a load-test for a registrar, but after a very high load, > > > >> I get a "503 Server too busy" with a "Retry After: 10"-Header. > >> Does anyone in this list ever reused this header by grepping the numeric > > > >> part out, and using it with a "next"-field and a Pause-command - is it > >> possible to reuse the value of a variable in the pause-command? > >> > >> Something like this: > >> > >> ------------------------------------------------------------------------ > >> .... > >> > >> <send> > >> ... REGISTER ... > >> </send> > >> > >> <recv response="200" optional="true" next="2" /> > >> > >> <recv response="503"> > >> <action> > >> <!-- Search for retry-time --> > >> <ereg regexp="***" search_in="hdr" header="Retry After:" > >> check_it="true" assign_to="2" /> > >> </action> > >> </recv> > >> > >> <pause milliseconds="$2"/> > >> > >> <send> > >> ... REGISTER ... > >> </send> > >> > >> <label id="2"/> > >> > >> .... > >> > >> ------------------------------------------------------------------------ > >> > >> Thanks in advance > >> Michael > >> > >> PS: also thanks to the users, who posted their SIPp-cps - high-scores! I > > > >> think, Charles Wright made the race with 10.000 calls per second. > >> > >> > >> -- > >> Michael Hirschbichler, Dipl.-Ing. > >> Institut fuer Breitbandkommunikation > >> Technische Universitaet Wien > >> A-1040 Wien, Favoritenstr. 9-11/388 > >> Tel: +43 1 58801 38846 > >> > >> > > ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Splunk Inc. > >> Still grepping through log files to find problems? Stop. > >> Now Search log events and configuration files using AJAX and a browser. > >> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >> _______________________________________________ > >> Sipp-users mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/sipp-users > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
