Unusual AMD activity

[xCape]

Specs:

I have a clustered MySQL 5.0 database with 2 nodes and one Management server.
Another server running Apache 2.2.8
The first dialer is running the latest cvs trunk of vicidial with asterisk 1.2.19

AMD is working when it goes to an answering machine but does not work when a human answers the phone. I noticed there is a new feature in the Campaign screen called 'Drop call seconds' I'm not sure if this is the problem. Anyway here is the output from the CLI:

-- Zap/1-1 answered Local/3135551212@default-1e80,2
> Channel Local/3135551212@default-1e80,1 was answered.
-- Executing AGI("Local/3135551212@default-1e80,1", "agi://127.0.0.1:4577/call_log") in new stack
== Manager 'sendcron' logged off from 127.0.0.1
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing AMD("Local/3135551212@default-1e80,1", "2000|2000|1000|5000|120|50|4|256") in new stack
-- AMD: Local/3135551212@default-1e80,1 2482836062 (null) (Fmt: 64)
-- AMD: initialSilence [2000] greeting [2000] afterGreetingSilence [1000] totalAnalysisTime [5000] minimumWordLength [120] betweenWordsSilence [50] maximumNumberOfWords [4] silenceThreshold [256]
== Spawn extension (default, 3135551212, 2) exited non-zero on 'Local/3135551212@default-1e80,2'
-- Executing DeadAGI("Local/3135551212@default-1e80,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----7-----0") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---7-----0 completed, returning 0
-- AMD: Word detected. iWordsCount:1
-- AMD: Changed state to STATE_IN_SILENCE
-- AMD: Word detected. iWordsCount:2
-- AMD: Changed state to STATE_IN_SILENCE
-- AMD: HUMAN: silenceDuration:1000 afterGreetingSilence:1000
-- Executing AGI("Zap/1-1", "VD_amd.agi|8369") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/VD_amd.agi
-- AGI Script VD_amd.agi completed, returning 0
-- Executing AGI("Zap/1-1", "agi-VDAD_LB_transfer.agi|8369") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_LB_transfer.agi
-- AGI Script agi-VDAD_LB_transfer.agi completed, returning 0
-- Executing AGI("Zap/1-1", "agi-VDAD_LB_transfer.agi|8369") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_LB_transfer.agi
-- AGI Script agi-VDAD_LB_transfer.agi completed, returning 0
-- Executing AGI("Zap/1-1", "agi-VDAD_LB_transfer.agi|8369") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_LB_transfer.agi
-- AGI Script agi-VDAD_LB_transfer.agi completed, returning 0
-- Executing Hangup("Zap/1-1", "") in new stack
== Spawn extension (default, 8369, 7) exited non-zero on 'Zap/1-1'
-- Executing DeadAGI("Zap/1-1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
-- Hungup 'Zap/1-1'


It goes directly to Hangup when it detects a human. Any help would be appreciated.

Thank you.

[mflorell]

What kind of trunks are you using?

Have you tried changing the AMD settings?

[xCape]

I just noticed that the extensions.conf in the new scratch install is different from what i've been using. "The 8369 area"

Once I edited my existing extensions.conf it gave me my human message.

Thanks for your fast reply.

[mel0683]

hi,

that's what i need, AMD only in full answering machine, should be hung up on live person answered. right now its also sending in live person too..please help..thanks

here my 8369 extensions:
; VICIDIAL_auto_dialer transfer script AMD with Load Balanced:
exten => 8369,1,AGI(agi://127.0.0.1:4577/call_log)
;exten => 8369,1,AGI(call_log.agi,${EXTEN})
exten => 8369,2,AMD(3500|1500|300|5000|120|50|5|256)
exten => 8369,3,AGI(VD_amd.agi,${EXTEN})
exten => 8369,4,AGI(agi-VDAD_LB_transfer.agi,${EXTEN})
exten => 8369,5,AGI(agi-VDAD_LB_transfer.agi,${EXTEN})
exten => 8369,6,AGI(agi-VDAD_LB_transfer.agi,${EXTEN})
exten => 8369,7,Hangup

and my 8320 extensions:
; this is used for playing a message to an answering machine forwarded from AMD in VICIDIAL
; replace conf with the message file you want to leave
exten => 8320,1,WaitForSilence(2000,2)
exten => 8320,2,Playback(85100008)
exten => 8320,3,AGI(VD_amd_post.agi,${EXTEN})
exten => 8320,5,Hangup

[xCape]

This is outlined in the Administrators Manual.

[mel0683]

yes i have admin manual, and i did instruction below

Full Answering Machine Detection -
Use the easy-prompt process to record your new prompt.(Follow the same procedure as the
above step for this only you don't need to delay the beginning by 2-3 seconds) Take your prompt
number and put it into the "Playback" line as shown in the dialplan(extensions.conf) entries below:
exten => 8369,1,AGI(call_log.agi,${EXTEN})
exten => 8369,2,AMD(3500|1500|300|5000|120|50|5|256)
exten => 8369,3,AGI(VD_amd.agi,${EXTEN})
exten => 8369,4,AGI(agi-VDAD_LB_transfer.agi,${EXTEN})
exten => 8369,5,AGI(agi-VDAD_LB_transfer.agi,${EXTEN})
exten => 8369,6,AGI(agi-VDAD_LB_transfer.agi,${EXTEN})
exten => 8369,7,Hangup
exten => 8320,1,WaitForSilence(2000,2)
exten => 8320,2,Playback(85100001)
exten => 8320,3,AGI(VD_amd_post.agi,${EXTEN})
exten => 8320,4,Playback(85100001)
exten => 8320,5,Hangup
exten => 8321,1,Playback(85100001)
exten => 8321,2,AGI(VD_amd_post.agi,${EXTEN})
exten => 8321,3,Playback(85100001)
exten => 8321,4,Hangup
Then set the "Campaign VDAD exten" in the Campaign Detail screen to 8369(or whatever
extension you defined for those lines), set the "Answering Machine Message" field to 8320 and set the
"AMD Send to VM exten" field is set to "Y". Now after the recording is played the first time, the status
of the lead will be changed to "AL" and the recording will be played again just to ensure the customer
has heard it.
3. To set the Remote Agent up and start dialing first go to the Remote Agent Modification screen. If
you are using Full Answering Machine Detection you will need to set the "External Extension" field to
8321, for the play-message-immediately method this field can be populated with anything and for the
other two methods this field should be populated with 8320(or whatever extension you used for
Playback).
4. To start dialing you need to change the status to ACTIVE and click submit.
5. When you are finished dialing you need to change the status to INACTIVE. This may take a minute
to stop dialing.