provided by Star2Billing S.L.

When I try limit the number of calls, I definitely get console messages...

[Apr 13 05:29:00] NOTICE[11031]: pbx.c:3495 increase_call_count: Maximum call limit of 50 calls exceeded by 'SIP/sipp-18cda5b0'!
[Apr 13 05:29:00] WARNING[11031]: chan_sip.c:16571 handle_request_invite: Failed to start PBX (call limit reached)

When I set the limit to 150, I'm still not getting more than 99-100.

I'm convinced it's in AGI or A2B.

I think I found sth in the manpage of mysql!

You ROCK! That did it!

I got 200 calls @ 7cps!!!!

Cpu0 : 34.4%us, 33.4%sy, 0.0%ni, 26.1%id, 0.3%wa, 0.3%hi, 5.4%si, 0.0%st
Cpu1 : 46.0%us, 34.3%sy, 0.0%ni, 11.7%id, 4.0%wa, 1.0%hi, 3.0%si, 0.0%st
Mem: 4043488k total, 3310516k used, 732972k free, 183576k buffers
Swap: 2031608k total, 0k used, 2031608k free, 917636k cached


Thanks!

Before you go into production with that figure in your head you should consider some far more important questions.
How many file-descriptors are available to Asterisk? What was the maximum PDD? What was your load average in relation to the number of CPU cores after sustaining this for 5 minutes? Were any RTP packets arriving with a jitter of >50ms? How many rates were in the rate cards in total, how many call plans did they span, and how many call plans were exercised by the testing? Was each call to a different destination number?
I notice your total RAM usage is very close to 3GB, which is the maximum addressable by a 32-bit app. Are you sure you're running a 64-bit build of Asterisk so it can use >3GB RAM? On a related note, I notice the kernel is holding nearly 1GB of disk cache; perhaps you might consider allocating more RAM to the SQL server tuple cache.

Bear in mind that 7cps is an appreciable amount of traffic; given an ACD of 3 minutes this equates to 42 E1s (1,260 concurrent channels). You've already established that (given your current configuration) Asterisk is limiting to you 200 concurrent calls, so it's unlikely you'll have to deal with much more than 1cps on each machine.

Hi If you still haveing the problem, I can help you may be.. Wht we have is end to end testing that we send u specifed number of call with specified number concurrent calls to any server and in turn u route it back to us. so we can put yr server in question in between to see if it holds more than 100 calls.. this is our Inhouse test bed that we use to chk traffice and routing .. and codec Issues is any
AM

you might need to uncomment or change some parameters in the safe_asterisk script to handle more than 200 calls!

look at this part :



Regards,
/Areski

Hello amirza,

If you don't mind, I would be interested in learning more about your end to end testing infrastructure. I would like to replicate it and do some testing of our own servers capacity.

Thank you