My solution to this is:
Use a field in the .csv file to identify the 1st call (in my case with the word
'register' for the first line, and <blank> for all others)
At the start of your calling script check for this [field] from the csv file to
see if it is 'register' and jump to a registration section of the script if it
matches. Proceed with the call section of the script if not - i.e. for all
subsequent calls
At the end of the registration section include something like:
<pause milliseconds="90000" next ="1">
To pause 90 seconds and then return to a <label id="1"/> the start of the
registration script.
The downside to this is because the registration script never exits, you will
have to end the scenario with ctrl+c once all your calls have finished
You could probably get around this with some global variable the other calls
use to indicate that they're all finished and cause the registration 'call' to
exit, but I've never bothered.
Remember your "m" and "l" will now have to be set to no of calls+1 as the
registration will consume 1 call.
If you have to handle 'OPTIONS' pings then these will probably come in with the
same call ID as registration (they do with Broadsoft at least) so instead of a
pause you can include a recv of the OPTIONS with a timeout of 90 seconds to
handle these.
As to your second issue, You imply that you're getting SIPp to respond to
registrations automatically. How? I just use a looping branch of the script
running as my first 'call' to handle incoming registrations much as described
above - and this would not have any timing issues.
Matt
________________________________
From: Knight Hwang [mailto:183405...@qq.com]
Sent: Wednesday, 19 June 2013 8:18 p.m.
To: sipp-users
Subject: [Sipp-users] long time calling and register expires issue
hi sipp users
i have two problems about sipp's register mechansim.
the first one is about the long time calling test and the sip extensions'
re-register. we want to use sipp to test our ippbx's performance for calling
many days, and our ippbx require the sip users to register every 1800 seconds,
here is the problem, how the sipp can register every 1800 seconds during the
calling scenario test?
the second is about the re-register time. our ippbx will re-register at the
half of the expires time, but the sipp ignores the re-register request. For
example, the register time set in the ippbx is 1800 seconds, after registered
900 seconds, the ippbx will send register request to the sipp, but the sipp
will ignore the request till the register expired. i noticed that the
re-register's call-id is the same with the previous register msg. Is there a
way to solve this problem?
Any help is greatly appreciated,
Thanks and Regards,
long
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
