<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16850" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=400230208-23072009>Hmm I was given the impression that the .call files
were risky due to locking issues... Is this no longer the case
perhaps?</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=400230208-23072009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=400230208-23072009>I also require knowledge of whether the originate was
successful or otherwise, with BUSY vs CONGESTION, etc.</SPAN></FONT></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] <B>On Behalf Of </B>Steve
Totaro<BR><B>Sent:</B> 22 July 2009 17:56<BR><B>To:</B> Asterisk Users Mailing
List - Non-Commercial Discussion<BR><B>Subject:</B> Re: [asterisk-users]
astmanproxy?<BR></FONT></DIV>When faced with this same problem, creating and
FTPing .call files to the outgoing spool directory freed up the AMI for other
functions.<BR><BR>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.<BR><BR>Not saying that this is
your best solution, just what I found to be much more reliable than pounding the
AMI.
<P><FONT face=Arial size=2></FONT></P></BODY></HTML>