Page 1 of 1

70 Seats inbound/outbound Server/Hardware Requirements

PostPosted: Sat Aug 27, 2011 4:57 pm
by Taeseer
Hi Everyone There,

I am a new guy in the field of Asterisk Server configruation and administration.
My agenda of post is given below:

1. Number of Agents 70 to 90
2. Campaigns Inbound/outbound both
3. Call Recordings
4. Real Time Monitoring
5. Number of calls or call load on server for inbound around 3000 calls

Please help me for Hardware selection. What type of hardware requirements for the Server I have to keep in my mind? according to my requirement.

Thanks
Taeseer.

PostPosted: Sat Aug 27, 2011 6:34 pm
by williamconley
Cool but you need to try again on numbers 1 & 5.

70 to 90 agents ... how many at one time for outbound (inbound is not worth discussing unless you have a large group of agents reserved for inbound ... as opposed to just getting return calls).

Also, we need to know the number of lines per agent you'll be dialing. If you don't know, we can't guess. For instance: Press 1 campaigns can reach 100 lines per agent, whereas Business to Business campaigns with a lot of inbound calls can be 1:1 dialing or less.

You also did not mention a time period for those 3000 calls in number 5. Remember that this is not a "service" you are getting a quote for, this is hardware that must handle the calls. The reason I mention this distinction is that the "aggregate total" is something a service company will ask so they can "bill you" for it. But this is a piece of hardware, and it only cares how many of those calls are live RIGHT NOW. So: How many simultaneous calls do you expect? If you have a mix of inbound and outbound this can be hard to calculate, but we gotta start somewhere.

All that being said: Normally 75 agents is a three dialer system ... but you have "to 90" and you are recording calls.

So you will likely need 4 dialers plus a database server and a web server (plus an archive server for safety). All at least Core2Quad (make the db server an 8 core system with 15k SAS drives) and you should be good.

Will this be an all-at-once jump off the cliff launch, or can you bring this system up a piece at a time?

70 Seats inbound/outbound Server/Hardware Requirements

PostPosted: Sat Aug 27, 2011 7:44 pm
by Taeseer
Thank you for reply,

1stly, number of agents may increase up to 100, dial in 24hours rotating shifts. servers will remain engaged and loaded with calls.

2ndly, 30000 calls in 24 hours means 100 concurrent calls at a time. Calls will be inbound.

What you should you propose hardware requirements for my needs?
And also please let me know One SQL DB Server will handle 30000 calls in 24/7?

And Please also do let me know Goautodial will be the best solution for dialer or we should have to purchase paid dialing system?

Regards,
Taeseer.

PostPosted: Sat Aug 27, 2011 8:23 pm
by williamconley
you must stop with the aggregate numbers. in 24/7? unless you want those calls to last for 24 hours that is not relevant. remember that these calls could be from 2 seconds to 2 hours each. the "capacity" is measured ONLY in "simultaneous" calls. the system does not measure the calls it has made today and "crash" because it was "too many for the day". i have had a single server (not a cluster, just one server) handle 30000 calls in one day without a problem.

30000 calls in one day does not "mean" 100 calls at a time. you may "assume" that 30000 calls in one day would likely result in 100 at one time ... But: Depending on the length and cadence of the calls and the overlap resulting from those values, it could be anywhere from 10 to 1000 calls at a time during any moment of the day (if you are processing calling card calls to relatives who talk for hours vs press 1 calls that mostly last for less than 5 seconds, and if your calls are not "spread out" but bunched up ... there's a huge range of possibilities).

based on the variables involved, my previous post is still as close as i can get.

and to directly answer your 2nd question, will one sql DB handle 30000 calls in one day? certainly. i have rooms that handle 30000 calls during the first couple hours of their day. 30000 inbound or outbound in a day is not a problem. but ... how many at one time are 22000 in One Hour and the rest "Spread out"? how many starting Per Second? those numbers are worth looking at.