ACQS not saving uniqueID

[linjo]

hello, I am currently exploring using ACQS stand alone with Asterisk 1.4 ( Ubuntu Hardy ) .
I have down loaded and installed astguiclient_2.0.4 .
I am able to place call data into the Asterisk DB and and have ACQS successfully originate the call and mark the entry as dead.
However on closer inspection I notice that AST_manager_listen.pl uses uniqueid to select records for update, but this field has not been filled in by AST_send_action_child.pl and has been set up as a DOUBLE in the DB ( whilst it is actually an alpha numeric). The upshot is that instead of just marking my call as DEAD it marks all calls on that channel as DEAD.

I seem to have some incompatible code is there an updated/ patched version I should be using ?

Any help would be appreciated.

[mflorell]

Which Asterisk version are you using?

what are the keepalives in your astguiclient.conf set to?

[linjo]

Hi , thanks for replying.
I'm using Asterisk 1.4.17 and have 1,2 and 6 keepalives set in astguiclient.conf

i think I've solved the initial problem I changed the uniqueID field in the asterisk DB to a varchar and made sure that I entered the same caller id in the callerid and the cmd_line_f columns. AST_manager_listen.pl then seems to use the caller id to find the uniqueID and write that back to the DB.

However now I'm getting some results they don't seem to be very complete, I get a DEAD result whether the call was made and was successfully or if it failed ( due to invalid number or no resource available etc) . Is this functionality some where else in astguiclient or have I not set up ACQS correctly?

Thanks for your help

[mflorell]

DEAD means the call was hung up in the system.

Have you set the servers table entry for asterisk_version to your proper Asterisk version?

Also, I would strongly suggest that you upgrade to at least 1.4.18, because 1.4.17 has many serious bugs that affect system stability and performance.

[linjo]

Is there no way of telling which calls where successful and which failed (ie they where never made in the first place)?

yes, I have got 1.4.17 as the asterisk_version in the servers table.

I'm using 1.4.17 because that is the package that came with ubuntu hardy and I assumed that they would provide a stable version ! I guess I will have to try and install from source.

[mflorell]

Unfortunately we stopped thinking of ACQS running independantly a long time ago. In VICIDIAL we have the vicidial_auto_calls table that keeps track of whether the call was made successfully or not, along with the call_log and vicidial_log tables that tell you the length of the calls.