For the last two days, I've been struggling with getting a scenario working
where I have SIPp (running 3.3) acting as a UAC, waiting for INVITE/UPDATE
refreshes from the UAS.  Regardless of what I've tried (see below) it
appears that SIPp will exit after 2 minutes (no errors being reported and
no SIP messages being received to close the session). I've enabled
-trace_err however it is completely empty.  My main question is SIPp hard
coded to exit after 2 minutes of not receiving a request, regardless of
pause/timeout being set to greater than 2 minutes (i.e pause
milliseconds="840000" or timeout="840000") ?

Essentially, I'm waiting for the session to be refreshed by the UAS at the
15 minute mark (half of session-expires: 1800);  call setup is successfully
however when SIPp reaches the following element), SIPp will exit after 2
minutes:

<recv request="INVITE|UPDATE" timeout="840000" regexp_match="true">

I've made several attempts to get this to work by:
1) Timing out the receive request after 1 minute and returning to the label
right before it

<label id="2" />
<recv request="INVITE|UPDATE" timeout="60000" ontimeout="2"
regexp_match="true">

2) Pausing right before the element for 14 minutes
<pause milliseconds="840000" />
<recv request="INVITE|UPDATE" timeout="60000" ontimeout="2"
regexp_match="true">

3) Timing out the request every minute and looping back to the label before
the request
<label id="2" />
<recv request="INVITE|UPDATE" timeout="60000" ontimeout="3"
regexp_match="true">
<label id="3" />
<pause milliseconds="60000" next="2" />

4) Setting global timeouts (although this should only affect elements that
are devoid of "timeout" attribute) to different values

Despite all these attempts, the call will end after 2 minutes.  Therefore,
before posting XML and log files (trace_err is empty), I was wondering if
this was a global value embedded in the code that will cause SIPp to exit
after 2 minutes. I've searched through the archive however I was unable to
find any scenarios that exhibited the same behavior. I appreciate any
feedback. Thank you




------------------------------ Scenario Screen -------- [1-9]: Change
Screen --
  Timestamp: Fri Mar 22 16:18:26 2013

  Call-rate(length)   Port   Total-time  Total-calls  Remote-host
  10.0(0 ms)/1.000s   5060     125.39 s            1  10.88.87.216:5060(TCP)

  Call limit reached (-m 1), 0.000 s period  0 ms scheduler resolution
  0 calls (limit 25200)                  Peak was 1 calls, after 0 s
  0 Running, 3 Paused, 0 Woken up
  0 dead call msg (discarded)            0 out-of-call msg (discarded)
  1 open sockets

                                 Messages  Retrans   Timeout
Unexpected-Msg
      INVITE ---------->         1         0         0
         100 <----------         1         0         0         0
         180 <----------         1         0         0         0
         200 <----------  E-RTD1 1         0         0         0

         ACK ---------->         1         0
  INVITE|UPDATE <----------         1         0         0         0
         200 ---------->         1         0
       Pause [    14:00]         1                             0
  INVITE|UPDATE <----------         0         0         0         0
         200 ---------->         0         0
         BYE ---------->         0         0
------- Waiting for active calls to end. Press [q] again to force exit.
-------

----------------------------- Statistics Screen ------- [1-9]: Change
Screen --
  Start Time             | 2013-03-22   16:16:21:048    1363986981.048493
  Last Reset Time        | 2013-03-22   16:18:26:443    1363987106.443695
  Current Time           | 2013-03-22   16:18:26:443    1363987106.443828
-------------------------+---------------------------+--------------------------
  Counter Name           | Periodic value            | Cumulative value
-------------------------+---------------------------+--------------------------
  Elapsed Time           | 00:00:00:000              | 00:02:05:395
  Call Rate              |    0.000 cps              |    0.008 cps
-------------------------+---------------------------+--------------------------
  Incoming call created  |        0                  |        0
  OutGoing call created  |        0                  |        1
  Total Call created     |                           |        1
  Current Call           |        0                  |
-------------------------+---------------------------+--------------------------
  Successful call        |        0                  |        0
  Failed call            |        0                  |        1
-------------------------+---------------------------+--------------------------
  Response Time 1        | 00:00:00:000              | 00:00:01:336
  Call Length            | 00:00:00:000              | 00:02:05:288
------- Waiting for active calls to end. Press [q] again to force exit.
-------

---------------------------- Repartition Screen ------- [1-9]: Change
Screen --
  Average Response Time Repartition 1
    <No repartion defined>
  Average Call Length Repartition
    <No repartion defined>
------- Waiting for active calls to end. Press [q] again to force exit.
-------



-- 
-Matt Chung
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to