AMD Send to Action not working

[DarthGamer]

Hi,

Yesterday we turned on our Sangoma NetAnalyzer as a paraxip proxy. According to the logs, it's working ok.

Code: Select all

1401367615-375326-994027220-43891,2014-05-29,,,831633******,Answering-Machine,08:46:55.419,08:47:00.828,08:47:03.338,,08:47:03.368,Answering Machine
1401367994-891291-1926835179-44276,2014-05-29,,,8447506******,Answering-Machine,08:53:14.945,08:53:18.014,08:53:20.974,,08:53:21.004,Answering Machine


The problem we are facing now is that the "AMD Send to Action" doesn't seem to work. "AMD send to Action" is setup to yes, and the "CPD AMD Action" is setup to MESSAGE.

However, when I check the history for the phones above, it doesn't seem to be playing the message:


831633****** Was marked as AA (from what I understand, should have been AL or AM ?)

Code: Select all

#   DATE/TIME   LENGTH    STATUS    TSR    CAMPAIGN    LIST    LEAD    HANGUP REASON   
1   2014-05-29 15:47:03    0    AA    VDAD    IRETAIN    1001    14391925    CALLER    



8447506******

Code: Select all


#   DATE/TIME   LENGTH    STATUS    TSR    CAMPAIGN    LIST    LEAD    HANGUP REASON
1   2014-05-29 15:53:12    0    AA    VDAD    IRETAIN    1001    14387761    CALLER    


Anyone have any idea how to make this to work properly?


Vicidial Version:

VERSION: 2.7-401a
BUILD: 130508-2256
© 2013 ViciDial Group

Aterisk version: 1.8.23.0

Paraxip Config:

Code: Select all


[paraxip]
disallow=all
allow=ulaw
type=friend
username=paraxip
fromuser=paraxip
secret=test
fromdomain=192.168.1.118
host=192.168.1.118
insecure=port,invite
outboundproxy=192.168.1.206:5062,force
context=vicidial-auto-external
enable-netborder-cpd=true
qualify=1000


TESTSIPTRUNKP = SIP/paraxip

exten => _7X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _7X.,2,Dial(${TESTSIPTRUNKP}/8${EXTEN:1},,To)
exten => _7X.,3,Hangup


[DarthGamer]

For what is worth, I see the proxy sends back the proper result to the asterisk server:

Code: Select all

X-Netborder-Detailed-CPD-Result-v2-0: Answering Machine
X-Netborder-Detailed-CPD-Result-v2-0: Answering Machine
X-Netborder-Detailed-CPD-Result-v2-0: Answering Machine
X-Netborder-Detailed-CPD-Result-v2-0: Answering Machine
X-Netborder-Detailed-CPD-Result-v2-0: Answering Machine
X-Netborder-Detailed-CPD-Result-v2-0: Answering Machine
X-Netborder-Detailed-CPD-Result-v2-0: Answering Machine
X-Netborder-Detailed-CPD-Result-v2-0: Answering Machine
X-Netborder-Detailed-CPD-Result-v2-0: Answering Machine


It seems it's a bug on the vicidial?

[mflorell]

What does the vicidial_cpd_log show for those calls?

Did you patch asterisk with the cpd patch before installing it?

[DarthGamer]

vicidial_cpd_log shows
+--------+----------------------+-----------------+----------------------+---------------+----------+---------------------+-------------------+-----------+-------------+
| cpd_id | channel | uniqueid | callerid | server_ip | lead_id | event_date | result | status | cpd_seconds |
+--------+----------------------+-----------------+----------------------+---------------+----------+---------------------+-------------------+-----------+-------------+
| 19076 | SIP/paraxip-0000069e | 1401367967.3030 | V5291552460014387761 | 192.168.1.118 | 14387761 | 2014-05-29 15:53:12 | Answering-Machine | PROCESSED | 0.00 |
| 19038 | SIP/paraxip-0000059d | 1401367615.2567 | V5291546550014391925 | 192.168.1.118 | 14391925 | 2014-05-29 15:47:03 | Answering-Machine | PROCESSED | 0.00 |
+--------+----------------------+-----------------+----------------------+---------------+----------+---------------------+-------------------+-----------+-------------+

The call remains with status AA, instead of AM or AL.

We are using GoAutoDial CE 3.0, so I didn't patch anything before installing. What should I look for to see if the patch is applied or not? I know that if I put the "enable-netborder-cpd=true" line on the paraxip config, asterisk appends the ";cpd=on;" to the call.

[DarthGamer]

I noticed something.

My routing extension for the campaigns was 8368.

Changed it to 8369, since help says:

Code: Select all

- 8368 - DEFAULT - Will send the call to the next available agent no matter what server they are on
- 8369 - Used for Answering Machine Detection after that, same behavior as 8368


Still calls remains as AA. The AMD send to action still doesn't seem to work.

[mflorell]

You could try upgrading, the version of Vicidial you are using is over a year old.

[DarthGamer]

For closure. Dropped the goautodial server and moved to vicibox.

The AMD send to action works perfectly.

[mflorell]

Thanks for the update, that is a common solution to a whole host of problems

[Iz3k34l]

are you able to say what the analyzer costs?