Project

General

Profile

AMD not working

Added by Moose man about 2 months ago

So i've got 2 installs - 1 live (on a bare bones dell server) and 1 test install on a VM i just setup today to test an issue with AMD.

What seems to be happening is if i enable AMD no calls get through at all, they all just get hungup on as soon as the call is answered.

The test machine is bog standard out of the box, no letsencrypt ssl, nothing, just straight up on a LAN installed from the latest ISO and updated via github to the latest version.

Without AMD enabled on the campaign the calls work without issue, every call is connected to the agent but as soon as you enable AMD calls just never get to the agents.

For my test machine i've got a campaign set to ratio dial with 1 agent and the ratio set to 1.

Here is what the asterisk CLI shows when the call is made

-- Called 96Number_Removed@default
-- Executing [96Number_Removed@default:1] AGI("Local/96Number_Removed@default-0000000e;2", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script Executing Application: (EXEC) Options: (Set(_CAMPCUST=24538026))
-- <Local/96Number_Removed@default-0000000e;2>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing [96Number_Removed@default:2] Dial("Local/96Number_Removed@default-0000000e;2", "SIP/Number_Removed@CC,,tTo") in new stack
Using SIP RTP CoS mark 5
-- Called SIP/Number_Removed@CC
> 0x29abcf0 -- Strict RTP learning after remote address set to: provider-gateway:31554
-- SIP/CC-0000000c is making progress passing it to Local/96Number_Removed@default-0000000e;2
-- Local/96Number_Removed@default-0000000e;1 is making progress
-- SIP/CC-0000000c answered Local/96Number_Removed@default-0000000e;2
-- Local/96Number_Removed@default-0000000e;1 answered
-- Executing [138369@default:1] AGI("Local/96Number_Removed@default-0000000e;1", "agi-VDAD_local_optimize.agi,V8111625080000000010") in new stack
-- Launched AGI Script /usr/share/asterisk/agi-bin/agi-VDAD_local_optimize.agi
Manager 'sendcron' logged off from 127.0.0.1
-- Channel SIP/CC-0000000c joined 'simple_bridge' basic-bridge <9af2bd42-4bc2-49b0-a7d3-3a4ea43a739c>
-- Channel Local/96Number_Removed@default-0000000e;2 joined 'simple_bridge' basic-bridge <9af2bd42-4bc2-49b0-a7d3-3a4ea43a739c>
Manager 'sendcron' logged on from 127.0.0.1
-- Channel SIP/CC-0000000c left 'simple_bridge' basic-bridge <9af2bd42-4bc2-49b0-a7d3-3a4ea43a739c>
-- Executing [8369@default:1] AGI("SIP/CC-0000000c", "agi://127.0.0.1:4577/call_log") in new stack
-- Channel Local/96Number_Removed@default-0000000e;2 left 'simple_bridge' basic-bridge <9af2bd42-4bc2-49b0-a7d3-3a4ea43a739c>
Spawn extension (default, 96Number_Removed, 2) exited non-zero on 'Local/96Number_Removed@default-0000000e;2'
-- Executing [h@default:1] AGI("Local/96Number_Removed@default-0000000e;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----5-----0-----SIP 200 OK)") in new stack
-- AGI Script Executing Application: (EXEC) Options: (Set(_CAMPCUST=24538026))
-- <SIP/CC-0000000c>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing [8369@default:2] AMD("SIP/CC-0000000c", "2000,2000,1000,5000,120,50,4,256") in new stack
-- AMD: SIP/CC-0000000c (N/A) (N/A) (Fmt: slin)
-- AMD: initialSilence [2000] greeting [2000] afterGreetingSilence [1000] totalAnalysisTime [5000] minimumWordLength [120] betweenWordsSilence [50] maximumNumberOfWords [4] silenceThreshold [256] maximumWordLength [5000]
-- AMD: Channel [SIP/CC-0000000c]. Changed state to STATE_IN_SILENCE
-- AMD: Channel [SIP/CC-0000000c]. ANSWERING MACHINE: silenceDuration:2000 initialSilence:2000
-- Executing [8369@default:3] AGI("SIP/CC-0000000c", "VD_amd.agi,8369") in new stack
-- Launched AGI Script /usr/share/asterisk/agi-bin/VD_amd.agi
-- <SIP/CC-0000000c> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
-- <SIP/CC-0000000c> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
-- <SIP/CC-0000000c>AGI Script VD_amd.agi completed, returning 4
Spawn extension (default, 8369, 3) exited non-zero on 'SIP/CC-0000000c'
-- Executing [h@default:1] AGI("SIP/CC-0000000c", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------SIP 200 OK)") in new stack
-- <SIP/CC-0000000c>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------SIP 200 OK) completed, returning 0
Manager 'sendcron' logged off from 127.0.0.1
-- <Local/96Number_Removed@default-0000000e;1>AGI Script agi-VDAD_local_optimize.agi completed, returning 0
-- Executing [138369@default:2] Wait("Local/96Number_Removed@default-0000000e;1", "2") in new stack
-- <Local/96Number_Removed@default-0000000e;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----5-----0-----SIP 200 OK) completed, returning 0 == Spawn extension (default, 138369, 2) exited non-zero on 'Local/96Number_Removed@default-0000000e;1'
[Aug 11 16:25:14] WARNING[5580][C-0000001b]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
-- Executing [h@default:1] AGI("Local/96Number_Removed@default-0000000e;1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------)") in new stack
-- <Local/96Number_Removed@default-0000000e;1>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------) completed, returning 0

I've got another server running vicidial and this is the different i can see in the CLI when running calls with AMD on

-- Executing [8369@default:2] AMD("SIP/CC-0000000c", "2000,2000,1000,5000,120,50,4,256") in new stack
-- AMD: SIP/CC-0000000c (N/A) (N/A) (Fmt: slin)

specifically the (N/A) (N/A) and the SIP/CC vs the working vicidial with the Local/connected leads number

On a working vicidial system it shows as

-- Executing [8369@default:3] AMD("Local/69number-removed@default-ae95,1", "2000|2000|1000|5000|120|50|4|256") in new stack
-- AMD: Local/69number-removed@default-39ca,1 0410372042 (null) (Fmt: 64)

Can anyone point me in the right direction here to get AMD to work with goautodial 4?


Replies (5)

RE: AMD not working - Added by Moose man about 1 month ago

So reading this

http://vicidial.org/docs/ASTERISK_13.txt

It implies that Asterisk 13.17.x doesn't have a functioning AMD version.

"NOTE: Asterisk 13.20 and higher has a functioning version of the AMD app, unlike earlier Asterisk 13 versions"

So basically the goautodial 4 iso leaves us on 13.17.2 which means no AMD if i'm understanding this correctly.

What are the chances of me totally breaking goautodial 4 by updated asterisk to 13.20.x?

RE: AMD not working - Added by Moose man about 1 month ago

Ok so i've sorted this out for anyone else reading this down the track (kinda feel like i'm yelling in the void here but i'm sure this will help someone at some point).

I took and old post from a year ago from Wittie and implemented his dialplan edits in extensions.conf. See post here: https://goautodial.org/boards/3/topics/18960

This still didnt work right away but stay with me.

Looking at the 8369 AMD dial plan entries that get auto populated this is slightly different. I've left Wittie's dialplan entires there and left the auto populated ones commented out.

Then looking at the console the AMD seems to be triggering based on detecting too much silence at the beginning of the call, the AMD seems to think the silence went for longer than 2 seconds. It doesn't but it seems to think it does so it hangups on the call (see below).

-- AMD: initialSilence [2000] greeting [2000] afterGreetingSilence [1000] totalAnalysisTime [5000] minimumWordLength [120] betweenWordsSilence [50] maximumNumberOfWords [4] silenceThreshold [256] maximumWordLength [5000]
-- AMD: Channel [SIP/CC2-00000001]. Changed state to STATE_IN_SILENCE
-- AMD: Channel [SIP/CC2-00000001]. ANSWERING MACHINE: silenceDuration:2000 initialSilence:2000

To solve that i just adjusted the initialSilence to a longer time frame and bam, good to go.

RE: AMD not working - Added by Moose man about 1 month ago

So further testing shows while changing the initial silence value to 5 stops all calls being hungup immediately the AMD is still just broken in asterisk 13.17.2.

The vicidial link i posted above is correct, AMD is just fundamentally broken in that version of asterisk. 13.20.x apparently works but not 13.17.2 which is what goautodial 4 is on.

RE: AMD not working - Added by Wittie Manansala 22 days ago

Try to update it to Asterisk 13.21.0

RE: AMD not working - Added by Moose man 11 days ago

I gave that a crack on VM, i setup the ISO and did all the updates then recompiled asterisk and it pretty much just broke everything.

It was probably my lack of understanding on how to update/recompile.

At the end of the day i had a working version of asterisk but lots of stuff was broken due to miss configured paths and a bunch of other stuff.

    (1-5/5)
    Go to top