Hi Vince,

Check how long your pcap is. If you want it to be long then have a 2 to 3 min 
pcap and accordingly change the pause time in your scenario

If you want to limit your calls then use this call rate options

See below:

*** Call rate options:

   -r               : Set the call rate (in calls per seconds).  This value can 
bechanged during
                      test by pressing '+','_','*' or '/'. Default is 10.
                      pressing '+' key to increase call rate by 1 * rate_scale,
                      pressing '-' key to decrease call rate by 1 * rate_scale,
                      pressing '*' key to increase call rate by 10 * rate_scale,
                      pressing '/' key to decrease call rate by 10 * rate_scale.

   -rp              : Specify the rate period for the call rate.  Default is 1 
second and default
                      unit is milliseconds.  This allows you to have n calls 
every m milliseconds
                      (by using -r n -rp m).
                      Example: -r 7 -rp 2000 ==> 7 calls every 2 seconds.
                               -r 10 -rp 5s => 10 calls every 5 seconds.
   -rate_scale      : Control the units for the '+', '-', '*', and '/' keys.
   -rate_increase   : Specify the rate increase every -fd units (default is 
seconds).  This allows
                      you to increase the load for each independent logging 
period.
                      Example: -rate_increase 10 -fd 10s
                        ==> increase calls by 10 every 10 seconds.
   -rate_max        : If -rate_increase is set, then quit after the rate 
reaches this value.
                      Example: -rate_increase 10 -rate_max 100
                        ==> increase calls by 10 until 100 cps is hit.
   -no_rate_quit    : If -rate_increase is set, do not quit after the rate 
reaches -rate_max.
   -l               : Set the maximum number of simultaneous calls. Once this 
limit is reached,
                      traffic is decreased until the number of open calls goes 
down. Default:
                        (3 * call_duration (s) * rate).
   -m               : Stop the test and exit when 'calls' calls are processed
   -users           : Instead of starting calls at a fixed rate, begin 'users' 
calls at startup,
                      and keep the number of calls constant.


Hope it Helps.


Sushma

From: Linux Vince <lin...@gmail.com<mailto:lin...@gmail.com>>
Date: Thursday, November 6, 2014 at 10:43 AM
To: sipp-users 
<sipp-users@lists.sourceforge.net<mailto:sipp-users@lists.sourceforge.net>>
Subject: [Sipp-users] SIPP UAC With Media

I am able to send media both ways i.e. using UAC and UAS both.

However call disconnects exactly after 21 seconds.

I am testing it as below

SIPP UAC -----> SBC Kamailio with rtpproxy ------> SIPP UAS

Also i specified only one call length in UAC i.e. "-l 1" but it still generates 
more than one concurrent calls.

Here is my UAC command

sipp -sf uac_pcap.xml -d 100000 -s 01191989898 10.0.0.15 -l 1 -mp 5606 -i 
10.0.0.18

I am using default XML provided here - 
http://sipp.sourceforge.net/doc3.3/uac_pcap.xml

Here is my UAS command

sipp -sf uas.xml -p 5060 -i 10.0.0.19 -mi 10.0.0.19 -skip_rlimit

XML i created using

sipp -sd uas > uas.xml

and added below lines

<recv request="ACK"
        rtd="true"
        crlf="true">
  </recv>

  <nop>
    <action>
      <exec play_pcap_audio="g711a.pcap"/>
    </action>
  </nop>

  <pause milliseconds="8000"/>

  <recv request="BYE">
  </recv>

Please help.
------------------------------------------------------------------------------
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to