asterisk users - Mar 2010 - AMD reporting NOTSURE most of the time

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 suspicion that the problem may be due to the timing source on
virtual server when its under load delivering lots of asterisk calls, since
the AMDSTATUS always reports things such as:-

AMDSTATUS:NOTSURE-AMDCAUSE:TOOLONG-5500

My AMD.conf settings are all set to default:-

[general]
initial_silence = 2500          ; Maximum silence duration before the
greeting.
                                ; If exceeded then MACHINE.
greeting = 1500                 ; Maximum length of a greeting. If exceeded
then MACHINE.
after_greeting_silence = 800    ; Silence after detecting a greeting.
                                ; If exceeded then HUMAN
total_analysis_time = 5000      ; Maximum time allowed for the algorithm to
decide
                                ; on a HUMAN or MACHINE
min_word_length = 100           ; Minimum duration of Voice to considered as
a word
between_words_silence = 50      ; Minimum duration of silence after a word
to consider
                                ; the audio what follows as a new word
maximum_number_of_words = 5     ; Maximum number of words in the greeting.
                                ; If exceeded then MACHINE
silence_threshold = 256


Just wondering if any of you AMD users have any ideas as to what I should
check. When I view this on the console I see that it jumps to too long
almost immediately:-

AMD: initialSilence [2500] greeting [1500] afterGreetingSilence [800]
totalAnalysisTime [5000] minimumWordLength [100] betweenWordsSilence [50]
maximumNumberOfWords [5] silenceThreshold [256] maximumWordLength [5000]

    -- AMD: Channel [SIP/faktortel-00001385]. Changed state to
STATE_IN_SILENCE

    -- AMD: Channel [SIP/faktortel-00001385]. Too long...

    -- AMD: Channel [SIP/faktortel-00001385]. Too long...


Thanks


Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100324/32371230/attachment.htm

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 last week, and 70% said NOTSURE).
>
> I have a suspicion that the problem may be due to the timing source on
> virtual server when its under load delivering lots of asterisk calls,
> since the AMDSTATUS always reports things such as:-
>
> AMDSTATUS:NOTSURE-AMDCAUSE:TOOLONG-5500
Looks like it's missing the first word - some VoIP providers take a 
while to pass audio - might be that there is a delay in your dialplan or 
that the first words of audio are simply not transmitted.

-- 
Cheers,

Matt Riddell
Managing Director
_______________________________________________

http://www.venturevoip.com/news.php (Daily Asterisk News)
http://www.venturevoip.com/exchange.php (Full ITSP Solution)
http://www.venturevoip.com/st.php (SmoothTorque Predictive Dialer)

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 last week, and 70% said NOTSURE).
>
> I have a suspicion that the problem may be due to the timing source on
> virtual server when its under load delivering lots of asterisk calls,
> since the AMDSTATUS always reports things such as:-
>
> AMDSTATUS:NOTSURE-AMDCAUSE:TOOLONG-5500
Alternatively your threshold might be too high - do a few tests to your 
own phone and make sure it recognizes the individual words.

-- 
Cheers,

Matt Riddell
Managing Director
_______________________________________________

http://www.venturevoip.com/news.php (Daily Asterisk News)
http://www.venturevoip.com/exchange.php (Full ITSP Solution)
http://www.venturevoip.com/st.php (SmoothTorque Predictive Dialer)

On Tue, Mar 23, 2010 at 9:06 PM, Steve Moran <sam at matara.net> 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 last week, and 70% said NOTSURE).
>
Hi.  Did you ever resolve this?  I am having the same problem as you when I
use AMD with outgoing calls through my Vitelity line.  Sending the calls out
PSTN seems to work as normal.  I tried tweaking the threshold setting as
someone else pointed out but it didn't make any difference.

-- 
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100410/2fc1028e/attachment.htm