Hi , I have done some tests in the environment below. PC1: sipp PC2: openser+mediaproxy (NAT) script: nat-mediaproxy.5.0.cfg from configs.GettingStarted.tar.gz
Below is the testing parameter shown in sipp 3 calls / second concurrent call: 30 Over 30 concurrent calls, message 481 begins to happen. The CPU usage of PC2 is almost 90% and then PC2 will hang.
As I expect openser should handle over thousand of calls but there is a different between my testing. What I miss to configure for getting more concurrent call?
On 5/26/06, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
On 05/26/06 04:33, unplug wrote:
Hi, How about using openser to handle over several hundred calls per second?
Very important is your configuration script. If you run openser just as a simple proxy, then it can go up to thousands of call setups per second. The performances increase if you use it in stateless mode - suitable for load balancing/dispatching.
The only way to measure the real capacity of your platform is to set it up in a lab and then perform some tests using tools like sipp.
Daniel
If not possbile, what is the limitation of openser to handle call?
On 5/26/06, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello,
On 05/25/06 07:26, Script Head wrote:
Hello,
I am deploying OpenSER to distribute calls for a number of Asterisk boxes. I believe there are some people on this list to have a similar setup. I'd like to know what kind of hardware do you guys run OpenSER on and how many calls per second can you set up with your specs. I am looking to set up about 30-40 calls per second so I was wondering what kind of hardware I'd need.
a usual pc nowadays should do it without any problems. The amount of registered users influence the memory usage, the 30-40 call setups per second has no big impact in the system.
Cheers, Daniel
ScriptHead
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users