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: [email protected] [mailto:[email protected]] 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.
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
_______________________________________________ -- 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
