astGUIclient-VICIDIAL handles volumes like that over a few manager connections. We have done that for 3 years across multiple versions of Asterisk and it is very stable.
The way we designed it, we have a listening daemon, a sending daemon and a status daemon. The sending script spawns children that run new actions and then die off. The listen script has an open manager connection but only listens for events and updates database from those events. The status update script keeps tabs on the status of channels in the system through it's "command" manager connection so it only receives responses to it's own commands, not all output. The manager is much more stable than it was 3 years ago, although it does still have it's rare bugs it works very well. MATT--- On 8/4/06, Manrique Feoli <[EMAIL PROTECTED]> wrote:
Hi, I've read all over that the manager conection (via sockets) isn't good for high traffic applications with multiple manager connections at the same time with one asterisk, the connection hangs and many other problems. having said that, my question is: Has anyone worked on a fairly high traffic environment BUT with ONLY ONE connection to administer asterisk via the manager, that is to do Login/Logout call generation, etc?? that is sending commands and receiving many events per minute or even per second. I'm talking about 60 lines / 2 E1 with working full at some peak times, with 30 agents on SIP. is it stable enough? what other way should I go if not. I appreaciate any point of view, or past experiences.... anything thanx _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
