Hi Guys, Thanks for your feedback, so no one is using sipxecs for this amount of calls per day ?
My call center are running 24/24 7/7 so when I see that I need to restart services for small changes on sipxecs I can't imagine rollout that in production yet (I'm running stable version), for example if I go to dialplan and apply a change on a rule it's require to restart SIP registrar and SIP Proxy on all servers, a reload will be preferable. I'll try the nightly build to see the improvements. Best Regards. Cyril 2011/8/3 Michael Picher <[email protected]> > I agree with Josh... might be something you want to start testing with the > 4.5.2 dev versions. I wouldn't expect you'd want to run in production until > 4.8 ish... > > That being said, it will be a very robust solution with agents and queues > being able to span multiple servers and being able to add servers to > increase capacity at will... > > Mike > > > On Wed, Aug 3, 2011 at 12:24 PM, Josh Patten <[email protected]> wrote: > >> It should be noted that OpenACD is far from ready in sipXecs 4.4. The >> integration will be much tighter in 4.6, though I'm not sure if there will >> be much in the way of reporting and supervisor capabilities. Perhaps one of >> the devs could chime in? >> >> >> >> On Wed, Aug 3, 2011 at 11:16 AM, Tony Graziano < >> [email protected]> wrote: >> >>> you really should read the wiki on the newer openacd package being >>> integrated into sipx now for that kind of call volume. >>> On Aug 3, 2011 12:13 PM, <[email protected]> wrote: >>> > Hi Guys, >>> > >>> > I just want to know if one of you have experience with sipxecs on call >>> center environment, for handling in my case 200 000 calls per day and 350 >>> agents connected simultaneously during peak hours? >>> > >>> > I'm really interested by replacing my Avaya per sipxecs regarding what >>> I have observed on sipxecs capacity. >>> > >>> > So let me know about you experiences. >>> > >>> > Best Regards. >>> > >>> > Cyril >>> > >>> > >>> > >>> > _______________________________________________ >>> > sipx-users mailing list >>> > [email protected] >>> > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> >> -- >> Josh Patten >> eZuce >> Solutions Architect >> O.978-296-1005 X2050 >> M.979-574-5699 >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > Michael Picher > eZuce > Director of Technical Services > O.978-296-1005 X2015 > M.207-956-0262 > @mpicher <http://twitter.com/mpicher> > www.ezuce.com > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
