Hi David,<br><br>What have you used on FS for call center, mod_fifo?<br><br>Can you describe your experience with that, I'm currently interested in call center + FS scenario.<br><br>Diego<br><br><div class="gmail_quote">
On Fri, Aug 28, 2009 at 9:01 PM, David Knell <span dir="ltr"><<a href="mailto:dave@3c.co.uk">dave@3c.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Raimund,<br>
<br>
One FreeSWITCH box will be quite enough to handle the call volumes that<br>
you're talking about, and it ought to be much more stable than the<br>
Asterisk solution which you've outlined below.<br>
<br>
It's probably best to forget about live failover without calls dropping<br>
- this isn't something that's supported, and there'd be a lot of work to<br>
do to develop code to keep two boxed in sync. Once you get used to a<br>
stable solution - i.e. something which doesn't crash - then live<br>
failover, HA, etc., will seem somewhat irrelevant.<br>
<br>
I recently did some work on an FS-based call center solution - drop me a<br>
note if I could be of any help with yours.<br>
<br>
Cheers --<br>
<br>
Dave<br>
<div><div></div><div class="h5"><br>
> Hello List,<br>
><br>
> I have read the current thread about scalability and I would need some<br>
> advice about a callcenter setup:<br>
><br>
> First where I come from:<br>
> I have lot's of problems with an asterisk solution. I have regular<br>
> crash's and lock-ups, with downgrading and other stuff i got it<br>
> somewhat stable, but have nevertheless regular hickups. I am desperate<br>
> and want to get rid of asterisk and I hope that freeSwitch will<br>
> provide me with a more stable solution.<br>
><br>
><br>
> Our Setup (really nothing special):<br>
> * 1 Asterisk box, New IBM Hardware (3 month old), 2 HE rack server, 3<br>
> GIG of RAM, Xircom analog switch connected to mobile stations for 4<br>
> different providers, Digium 4port cards TP400<something><br>
> * 8 queues<br>
> * ~60 agents (which logon, logoff, pause, unpause), not more than 40<br>
> concurrently online<br>
> * ~ 7K - 9K calls (well, CDR entries) a day (not that much for a bpx)<br>
> * Music on Hold in the call-queues<br>
> * No special announcement<br>
> * Transfers between calls in queues and different agents as well as<br>
> non agents (i mention this because we have transfer related chrashes<br>
> in asterisk)<br>
><br>
> The current Problems:<br>
> * Lockups with different causes (ranging from calls not terminated to<br>
> heavy thread locking through the AMI interface)<br>
> * Crashes and library aborts (pthread, libc, crashes related to music<br>
> on hold, app_queue, transfers)<br>
><br>
> We used Asterisk: 1.4.23, 1.4.24, 1.4.26rc3, 1.4.26rc5, 1.4.26 and are<br>
> now back to 1.4.21.2 (stock debian) as anything beyond that is for<br>
> whatever reason highly unstable for our szenario. Maybe we should have<br>
> been segmenting the box into one asterisk dedicted to talking to the<br>
> hardware, one especial for queue/sip handling, i do not know. (all<br>
> issues are well documented in <a href="http://issues.asterisk.org" target="_blank">issues.asterisk.org</a>, but it seems to be<br>
> very, very difficult to get to the bottom of them as they exist since<br>
> 1.4.23 as it seems and are open until know and not fixable since month.)<br>
><br>
><br>
> Now, I really would appreciate some success-stories on how you guys<br>
> managed to get a stable pbx system with freeSWITCH in regard of HA and<br>
> scalability:<br>
><br>
> * How to segment freeSWITCH? Or is it stable enough to handle all in<br>
> one for such a szenario as outlined above?<br>
> * What would be the best strategie for High Availability / Failover?<br>
> -> I read in the WIKI (featurelist) that Livemigration of calls from<br>
> one box to another should be possible?<br>
> -> I was thinking about using memcached for storing all state<br>
> information so another freeswitch box can takeover calls from the<br>
> first box if it dies, is this possible? If so, how?<br>
> -> Is there anotherway to somehow configure freeSWITCH that in the<br>
> event of a crash i do not loose the current established calls?<br>
><br>
> Basically I just want a stable PBX where I do not have to fear every<br>
> day it will core-dump or abort or Lock up. Is freeSWITCH mature enough<br>
> so i can sleep at night for at least 3 month without a crash?<br>
><br>
><br>
><br>
> Thank you for your Time and help in advance, and I am more than<br>
> willing to take all the information gathered here and create a wiki<br>
> page to help other people with the same questions/problems.<br>
><br>
> best<br>
> Ray<br>
><br>
><br>
--<br>
</div></div><font color="#888888">David Knell, Director, 3C Limited<br>
T: +44 20 3298 2000<br>
E: <a href="mailto:dave@3c.co.uk">dave@3c.co.uk</a><br>
W: <a href="http://www.3c.co.uk" target="_blank">http://www.3c.co.uk</a><br>
</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br>