Hi,
I have noticed that SIPP client call-rate is somehow influenced by the server.
So if the response from server does not match the scenario or the response is
delayed SIPP client vers 3.1 does not reach the target call.
Has someone encountered this problem?
Best regards,
Dan
From: Dan Flucus [mailto:dan.flu...@iquestint.com]
Sent: Thursday, July 08, 2010 10:58 AM
To: sipp-users@lists.sourceforge.net
Subject: [ Non iQuest : could be Junk ] [Sipp-users] Smaller call-rate than
expected
Hello,
I want to execute some performance tests using SIPP v3.1 on a Red Hat4 machine
and I have a problem with the call-rate.
The call of sipp:
"sipp -nd -trace_err -trace_stat -nr -i IP_HOST -p PORT_HOST -m 1000 -inf
dlg_sub.csv -sf dlg_sub.xml -t un -r 1 -rate_increase 1 -rate_max 15 -fd 10
-no_rate_quit -recv_timeout 10000 IP_SERVER:PORT_SERVER"
My problem is that after 7-8 call/seconds the actual call-rate is a lot smaller
than the expected call-rate, so when the target call-rate is above 10 I see
that SIPP sends 4 to 6 call/seconds.
I tried to increase the number of sockets "-max_socket 65535" but still no luck.
Any suggestions?
Best regards!
Dan
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
