What are the general and reasonable call rates or call volumes companies
and organizations test against for PBX products, commercial and open
source.
Like how many calls in a day or how many calls per second, calls per
hour, etc.. In a way, 1 call/sec or 3600 calls/hr seems extreme but on
another end maybe not, and some test tools like SIPp default at 1
call/sec.
And how would you set up the test config in relation between call volume
and call rate? For example, you could set a call rate of 1 call/sec but
involve 10, 20, or 100 callers in the test. What would be reasonable and
extreme for such test profiles or configs? 1 call/sec with 1000 users
too extreme? Or with 100 users too extreme?
Are there some industry references for how one should set up these call
volume / call rate tests? I assume its easier to find load test info
about web services / web performance testing regarding # requests or
hits per hour, etc. than it is it for telecom load testing.
More elaboration on the topic of what I'm asking about:
Well, just like with industry benchmarking of computer hardware, and
sometimes software, like some PC/software reviews test against CPU
performance, memory, # of cycles of processing graphics, etc. and all
that stuff...
I was looking for something similar for PBX benchmarking, like a typical
good PBX should be able to handle x calls/sec or x calls/hr, and/or call
volume of x calls/day.
And whether the PBX call load tests done at PBX development companies or
benchmarking companies were smart tests that also tested PBX features
like call transfers, conferencing, audio/DTMF voice path verification,
etc. or whether they were dumbed down tests like calling party makes
call to called party, called party answers, wait some time, hangup,
repeat test.
Reason I was asking is SIPp defaults at 1 call/sec call rate and with
exception to dumbed down tests, that call rate is rather extreme
sometimes, like when we involve GUI interfaces that monitor the state of
phones involved in a load test with that kind of call rate.
I was just wondering, how companies like Cisco, Avaya, Nortel, etc. or
open source communities like Asterisk run PBX load tests and tell their
customers or management that we've run so many calls or calls/hr and PBX
is holding up well (and whether that included running nice add on
applications like a GUI phone interface software to monitor/control
phones during a load test, or just simple dumb load tests).
Maybe this information is confidential but it sure would be nice to
share with the rest of the telecom industry.
Any help appreciated.
Regards,
David
QA Engineer - new to load testing in the telecom industry
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
