[RESOLVED] Problem to manage AMD call detected

General and Support topics relating to ViciDialNow and GoAutoDial ISO installers

Moderators: enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, s0lid

[RESOLVED] Problem to manage AMD call detected

Postby brando16 » Mon Oct 31, 2016 4:12 am

Hi all,

I noticed when the call recognized MACHINE the call come in to queue with agent, instead of hungup the call.
I modified the 8369 match pattern in the dialplan (extensions.conf) after the row "exten => 8369,n,AGI(VD_amd.agi,${EXTEN})" in my file row=524, i inserted this gotoif for redirect the call are recognized MACHINE into hangup:

exten => 8369,n,GotoIf($["${AMDSTATUS}"="MACHINE"]?8369,[label for hungup last line of this match pattern])


I hope this helpful someone have same problems with AMD detection. I ask the developer if this modification are possibile to inserted in next release, because at today doesn't work full AMD detection the call enter anyway to an agent.

Version of goautodial CE 3.3

i hope clear which modification i do.

for more info reply to this topic

best regards
Vicibox VERSION: 2.14-580a | BUILD: 161029-2304 | OpenSuSE v.42.1 64-bit | Kernel v.4.1.13 | Asterisk v.11.25.1-vici | DAHDI v.2.10.2 | LibPRI v.1.4.14 | Amfletec VoiceSync v.1.3.8 | ViciDial SVN Trunk v.2.12-533a build 161205-1650 revision 2461
brando16
 
Posts: 88
Joined: Tue Jul 30, 2013 11:00 am

Re: [RESOLVED] Problem to manage AMD call detected

Postby williamconley » Sat Jan 14, 2017 9:30 pm

This works as designed in all versions of Vicidial (lots of clients have tested it). What were your AMD settings in the campaign?
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20018
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)


Return to ViciDialNow - GoAutoDial

Who is online

Users browsing this forum: No registered users and 22 guests