Hi listers, We want to implement one call center with asterisk. The idea is it should be scalable, with openser as an dispatcher and bunch of asterisk servers to do ACD, Queues, Agents things... Easy to say :(
Look closely to the current asterisk, we do see some problem: - SIP registrations was stored in astdb. - And queue members also was stored in astdb. - ... asterisk was built as standalone PBX, so it's understandable. Is it time to replace astdb with something like MySQL, so all asterisk boxes in cluster can have identical access to all the informations, devstates, etc...? Our first thought is replacing the astdb implementation, currently with DB1, with MySQL. app_dbodbc is a hint, but there are still many things to consider: concurrency access from many box to same row, performance issues, ... We need your pointers here. Where are the caveats? Is it the correct way to start add clustering capabilities to asterisk? Your replies are much appreciated, -- With best regards, Nguyen
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
