On 23 March 2013 04:21, Matt Chung <itsmemattch...@gmail.com> wrote: > 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:
This surprises me, and doesn't match what I've seen in my use of SIPp. I certainly don't think there should be a hard-coded limit of 2 minutes. I'd like to see, if possible, the command line you're using to start SIPp, the XML file, and the version of SIPp (i.e. the first line of `sipp -v`). That should let me try and reproduce it. -- Robert K. Day robert....@merton.oxon.org ------------------------------------------------------------------------------ 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
