On Thu, Apr 15, 2010 at 4:06 PM, Baji Panchumarti <
baji.panchuma...@gmail.com> wrote:
> Steve, Chris :
>
> I too had this problem and the solution was not tweaking
> the AMD parameters, but playing a short audio file (even
> a really really short one) before executing the AMD function.
>
> T
Steve, Chris :
I too had this problem and the solution was not tweaking
the AMD parameters, but playing a short audio file (even
a really really short one) before executing the AMD function.
The key is executing the "Background" step before AMD()
Please see sample dialplan below :
ext
On Tue, Mar 23, 2010 at 9:06 PM, Steve Moran wrote:
> I am running Asterisk and using Answer machine detection with call files on
> a virtual Vcloud server running Centos 5.3 and LAMP. I am finding that AMD
> is only detecting HUMAN or MACHINE for about 30% of the calls (I sent over
> 50,000 outb
On 24/03/10 3:06 PM, Steve Moran wrote:
> I am running Asterisk and using Answer machine detection with call files
> on a virtual Vcloud server running Centos 5.3 and LAMP. I am finding
> that AMD is only detecting HUMAN or MACHINE for about 30% of the calls
> (I sent over 50,000 outbound calls las
On 24/03/10 3:06 PM, Steve Moran wrote:
> I am running Asterisk and using Answer machine detection with call files
> on a virtual Vcloud server running Centos 5.3 and LAMP. I am finding
> that AMD is only detecting HUMAN or MACHINE for about 30% of the calls
> (I sent over 50,000 outbound calls las
I am running Asterisk and using Answer machine detection with call files on
a virtual Vcloud server running Centos 5.3 and LAMP. I am finding that AMD
is only detecting HUMAN or MACHINE for about 30% of the calls (I sent over
50,000 outbound calls last week, and 70% said NOTSURE).
I have a suspici
