The issue has more to do with the sheer amount of data passed to the client from within the Asterisk application when you have 50-100+ clients connected to the AMI on full output mode. Running a system with FreePBX/Trixbox especially generates vast amounts of output that has to be generated on every AMI connection for every client. This is not trivial and can result in lockups very easily, although this has gotten much better since the early 1.0 versions.
The new Asterisk Manager web API in 1.4 is a good step where sending of Actions does not require an actual Telnet conneciton to the AMI, but I think to be able to handle larger numbers of concurrent connections that a separate send-only and a separate receive-only type of interface be built where Asterisk would just output all AMI data to a single server-like application that would then broadcast it to all connected clients. This would remove the burden of so many connections going directly into Asterisk and would allow for much larger scaling of AMI-type applications that require real-time output of AMI events. As for how to go about doing this, I can't help you there. I did build a very specialized version of something like this 4 years ago for the astGUIclient project called the Asterisk Central Queue System(ACQS) It is based on 1.0 Asterisk but it still works with 1.2 and 1.4. It is limited in what it does, but it does scale much better than using direct AMI connections. http://astguiclient.sourceforge.net/acqs.html MATT--- On 5/16/07, Dean Collins <[EMAIL PROTECTED]> wrote:
If it's not stable what needs to be done to improve this? What are the issues? What are the alternatives (eg is Adhearsion an alternative here) I am about to start looking into a project that requires every user to have AMI access so looking to fund development in this space. Regards, Dean Collins Cognation Pty Ltd [EMAIL PROTECTED] +1-212-203-4357 Ph [image: Call Button]<http://click.mexuar.com/webuser/click/7/userurl/Cognation> ------------------------------ *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Damon Estep *Sent:* Wednesday, 16 May 2007 7:32 AM *To:* Asterisk Users Mailing List - Non-Commercial Discussion *Subject:* [asterisk-users] asterisk manager interface stability There are many past posts stating that AMI is not stable when multiple client computers are allowed to connect, particularly when connections are dropped. Has much progress been made on this? Is it more stable now than in the past? As of what versions were these issues improved? Is it feasible to connect a large number of windows computers directly to AMI for the purpose of initiating calls from software? _______________________________________________ --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
