The XML file is in attachment. However, please note that the script works just fine at lower rates. The problem happens when the value in the -r option is greater than the value in the -rp option.
Also if I start the script with the value in -r smaller than the value in -rp and then I manually increase the rate using the + or * keys, I can increase the rate above the 1000 threshold and everything keeps working fine. The problem is only with the startup of the script and only with that particular option values combination.

Thanks for your time,

Carlo Carrano


mahendra kedia wrote:
Can you please share the sipp xml file, which will help to understand the issue....


On Mon, Feb 17, 2014 at 7:38 AM, Carlo Carrano <[email protected]> wrote:
Hello,
I'm running sipp v3.4.0-RTPSTREAM.
I found that I am not able to start a registration script when the
registration rate is greater than 1000 reg/sec. I'm using options -r
1047 -rp 1000.
If the registration rate is less than or equal 1000, the script works
fine. Otherwise, it starts but does not generate any load.

Here is a screenshot for a working case:

------------------------------ Scenario Screen -------- [1-9]: Change
Screen --
   Call-rate(length)   Port   Total-time  Total-calls Remote-host
1000.0(0 ms)/1.000s   5500       6.00 s         5982 135.1.216.65:5060(UDP)

   998 new calls during 1.001 s period    0 ms scheduler resolution
   0 calls (limit 3000)                   Peak was 5 calls, after 0 s
   0 Running, 5983 Paused, 473 Woken up
   0 dead call msg (discarded)            0 out-of-call msg (discarded)
   3 open sockets

                                  Messages  Retrans Timeout   Unexpected-Msg
     REGISTER ---------->         5982      0         0
          200 <----------  E-RTD1 5982      0 0         0
------ [+|-|*|/]: Adjust rate ---- [q]: Soft exit ---- [p]: Pause
traffic -----


And here is a screenshot for a non-working case:

------------------------------ Scenario Screen -------- [1-9]: Change
Screen --
   Call-rate(length)   Port   Total-time  Total-calls Remote-host
1047.0(0 ms)/1.000s   5500       2.00 s            0 135.1.216.65:5060(UDP)

   0 new calls during 1.002 s period      1 ms scheduler resolution
   0 calls (limit 3141)                   Peak was 0 calls, after 0 s
   0 Running, 2 Paused, 3 Woken up
   0 dead call msg (discarded)            0 out-of-call msg (discarded)
   3 open sockets

                                  Messages  Retrans Timeout   Unexpected-Msg
     REGISTER ---------->         0         0         0
          200 <----------  E-RTD1 0         0 0         0
------ [+|-|*|/]: Adjust rate ---- [q]: Soft exit ---- [p]: Pause
traffic -----


Note that if I start the script with less than 1000 reg/sec and then I
increase them manually, everything works just fine.
Here is a screen shot showing that:

------------------------------ Scenario Screen -------- [1-9]: Change
Screen --
   Call-rate(length)   Port   Total-time  Total-calls Remote-host
1030.0(0 ms)/1.000s   5500      10.01 s        10208 135.1.216.65:5060(UDP)

   1033 new calls during 1.002 s period   0 ms scheduler resolution
   0 calls (limit 3090)                   Peak was 5 calls, after 2 s
   0 Running, 10209 Paused, 481 Woken up
   0 dead call msg (discarded)            0 out-of-call msg (discarded)
   3 open sockets

                                  Messages  Retrans Timeout   Unexpected-Msg
     REGISTER ---------->         10208     0         0
          200 <----------  E-RTD1 10208     0 0         0
------ [+|-|*|/]: Adjust rate ---- [q]: Soft exit ---- [p]: Pause
traffic -----


So, it seems that sipp is capable of handling a rate greater than 1000,
but not if starting the script with that value.

I need to start several scripts like this from a shell script, for lab
automation registration and call load testing. Is there a way to
overcome this limitation?

Thanks in advance for any help you can give,

Carlo

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users


<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE scenario SYSTEM "sipp.dtd">

<!-- Test Scenario Name: register                                       -->
<!-- Description: This uac xml scenario can be used to register         -->
<!--              subscribers.                                          -->
<!-- Test Version: 1.0 (works with sipp V3.0 and forward)               -->
<!-- Test xml file: register.xml                                        -->
<!-- Test csv file: register.csv                                        -->
<!--                                                                    -->
<!--                                                                    -->

<scenario name="3rd Party Registration Scenario">
  <!-- Send the initial Registration request                              -->
  <send retrans="2000">
    <![CDATA[

    REGISTER sip:nscg-stdn.[field1]:5060 SIP/2.0
    Via: SIP/2.0/[transport] [local_ip]:[local_port]
    From: <sip:scsf-stdn.[field1]:5060>;tag=[call_number]
    To: <sip:+1[field0]@[field1]>
    Contact: <sip:scsf-stdn.[field1]:5060>
    Call-ID: [call_id]
    CSeq: 1 REGISTER
    Expires: 600000
    Max-Forwards: 70
    P-Associated-URI: <sip:+1[field0]@[field1]>
    P-Associated-URI: <tel:+1[field0]>
    Timestamp: 10
    Content-Length: 0

    ]]>
  </send>

  <!-- Wait for 200 O.k.                                                  -->
  <recv response="200" rtd="true" rrs="true">
  </recv>

  <!-- definition of the response time repartition table (unit is ms)   -->
  <ResponseTimeRepartition value="5, 10, 15, 20, 25, 30, 35, 40"/>

  <!-- definition of the call length repartition table (unit is ms)     -->
  <CallLengthRepartition value="10, 20, 30, 40, 50, 60, 70"/>

</scenario>

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to