On 9/21/05, Matt Florell <[EMAIL PROTECTED]> wrote:
> We have sevaral call centers as well, and we just restrict a single server
> to 50 recordings at once and then we would pass the next recording as an
> IAX2 channel to another recording server. It's a scalable system for us that
> is relatively cheap and works well since we can mix and gsm-encode the audio
> on these multiple servers at night when not in production leaving the NSF
> server just for storage and not audio processing.
Interesting approach,
How do you deal with queue management ?
Do you have central server that manages all queues ?
How many phone calls u have at same time ? Inbound or outbound ?
Could you share a little bit more on the architecture of your system ?
regards
m
We wrote VICIDIAL(part of the GPL astGUIclient suite http://astguiclient.sf.net) for our call center operations. Yes it does use a central queue and does not use Asterisk queues or agents. The system is based on a MySQL database and meetme rooms for the agents that use a web-client app for lead information and call control.
We mostly do outbound and the volume is split across several servers, and for inbound we do have forwarding to other servers if the defined capacity is exceeded a certain point.
As for our distributed recording approach, it's easy with meetme rooms to record a call on one server from another server, you just drop a call into the meetme room that is a monitor exten on another server over IAX2, TDMoE or a crossover Zap T1 connection.
As for phone calls at one time: for inbound we almost never exceed 50 agents on a single server with no more than 72 incoming lines live at once. Our average is actually much less than that. For outbound we usually have about 15-40 agents per server with upto 96 lines dialing out concurrently. At our main office location we've had over 100 agents on at one time across 6 Asterisk servers handling over 350 calls at once with a total of more than 550 live channels on our Asterisk servers(includes recording, client and trunk channels).
We mostly use cheaper single CPU systems instead of more expensive multi-CPU systems which is more cost effective in a larger setup and allows for greater flexibility, redundancy and scalability.
I'll also be presenting a case-study on our whole setup at Astricon next month. The presentation file will be available on the astGUIclient project website after I present it for those who are interested.
MATT---
_______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com --
Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
