Hi, We currently fire multiple HTTP requests (via multi-curl) to the AJAM interface in order to place calls. We are finding Asterisk has it's limits however, and I've found astmanproxy recommended for helping maintain the connections. This would prove particularly useful with multiple servers of course. However, in testing astmanproxy crashes with buffer overflows. This leads to the inevitable question: Is astmanproxy still recommended for use or are we missing some knowledge here? Platform is 64 bit Intel, Ubuntu 9.04, Asterisk 1.6 with latest trunk of astmanproxy from github. Thanks, James -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090721/18d559c8/attachment.htm -------------- next part -------------- No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.21/2252 - Release Date: 07/21/09 05:58:00
2009/7/21 James Green <james.green at mjog.com>> Hi, > > We currently fire multiple HTTP requests (via multi-curl) to the AJAM > interface in order to place calls. We are finding Asterisk has it's limits > however, and I've found astmanproxy recommended for helping maintain the > connections. This would prove particularly useful with multiple servers of > course. > > However, in testing astmanproxy crashes with buffer overflows. > > This leads to the inevitable question: Is astmanproxy still recommended for > use or are we missing some knowledge here? > > Platform is 64 bit Intel, Ubuntu 9.04, Asterisk 1.6 with latest trunk of > astmanproxy from github. >We successfully used astmanproxy here with 1.6.1.1 (intel 32 bits ).> > Thanks, > > James > > > > No virus found in this outgoing message. > Checked by AVG - www.avg.com > Version: 8.5.392 / Virus Database: 270.13.21/2252 - Release Date: 07/21/09 > 05:58:00 > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090722/ab6854f0/attachment.htm
On Tue, Jul 21, 2009 at 10:15 AM, James Green <james.green at mjog.com> wrote:> Hi, > > We currently fire multiple HTTP requests (via multi-curl) to the AJAM > interface in order to place calls. We are finding Asterisk has it's limits > however, and I've found astmanproxy recommended for helping maintain the > connections. This would prove particularly useful with multiple servers of > course. > > However, in testing astmanproxy crashes with buffer overflows. > > This leads to the inevitable question: Is astmanproxy still recommended for > use or are we missing some knowledge here? > > Platform is 64 bit Intel, Ubuntu 9.04, Asterisk 1.6 with latest trunk of > astmanproxy from github. > > Thanks, > > James > >When faced with this same problem, creating and FTPing .call files to the outgoing spool directory freed up the AMI for other functions. Plain, simple, and "Just Worked" I looked at, but never tried AstManProxy because I prefer to eliminate levels of complexity and points of failure rather than add, whenever possible. Not saying that this is your best solution, just what I found to be much more reliable than pounding the AMI. -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell) +12024369784 (Skype) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090722/1a7ee2d2/attachment.htm
Hmm I was given the impression that the .call files were risky due to locking issues... Is this no longer the case perhaps? I also require knowledge of whether the originate was successful or otherwise, with BUSY vs CONGESTION, etc. ________________________________ From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Steve Totaro Sent: 22 July 2009 17:56 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] astmanproxy? When faced with this same problem, creating and FTPing .call files to the outgoing spool directory freed up the AMI for other functions. Plain, simple, and "Just Worked" I looked at, but never tried AstManProxy because I prefer to eliminate levels of complexity and points of failure rather than add, whenever possible. Not saying that this is your best solution, just what I found to be much more reliable than pounding the AMI. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090723/dc5b5575/attachment.htm -------------- next part -------------- No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.24/2255 - Release Date: 07/22/09 18:00:00