INBOUND CALLBACK QUEUE CALL ANSWERED EVENT ISSUE

[areon]

Hello,

We use INBOUND CALLBACK QUEUE functionality in our project for inbound calls.

We have two questions^
1. How to differentiate callback call from the usual inbound call when Start call URL or Script used?
All parameters are identical, CallerID looks like Y7011632440001506519 (like inbound call)
2. How to understand for callback call on API level when remote side answered the call?
The agent becomes in "incall' status immediately after start callback call,
-
Thank you.

VERSION: 2.14-687a
BUILD: 180908-1618

[williamconley]

Some of these URL fields allow putting NO parameters in and will then fill ALL of them in by default. Not sure if these are them or not, but one way or another your best bet with something like this is to run two test calls, one of each flavor, and run a diff on the resulting strings. Also note that there is a URL log for this which captures a decent amount of info to help out.

Failing that of course, remember that if the URL is pointed to a php file that has access to MySQL, you could just check the live calls table for this record and find out what its status is and/or go straight to the lead record or even check for a callback record.

"How to understand for callback call on API level" ... are you asking if there is an agent api method to find out what kind of call this is? If so, the options for YOUR installation of Vicidial's API are in the trunk/docs folder for both the agent api and the non-agent API. And if that doesn't provide a happy response, there's still the "hit the DB directly" method to build your own solution.

Run some tests. Check a lead record and the callback table and see what's there at each stage of a sample call such as you describe. Then it'll be easier to build a web page that can detect that difference (or at least one of them, there may be several).

[areon]

williamconley wrote : you could just check the live calls table for this record and find out what its status is and/or go straight to the lead record or even check for a callback record.

Code: Select all

select * from asterisk.vicidial_auto_calls;
Inbound queue callback call  looks like
1267784   10.10.64.82   inVR   CLOSER   1535687   1562231078.123100   Y7041204390001535687   IAX2/ASTloop-5126      0632871026   2019-07-04 12:04:39   IN   CLOSER-0   2019-07-04 12:04:39   NONE   99   168   168   13      8600053.


Small difference: agent_only and agent_grab both are defined.

We can also check vicidial_inbound_callback_queue table for inbound queue call back, like this

Code: Select all

select * from asterisk.vicidial_inbound_callback_queue where icbq_status in ('SENDING', 'LIVE') and lead_id = 1535687

But it is not so good idea do this for each inbound call.

Thanks.

[williamconley]

But it is not so good idea do this for each inbound call.

This is what mysql is for, and why this information is stored in mysql.

Why would you think it's not a good idea to get this information? If you think this is going to overload your server, you should look at how many queries a vicidial server processes every second already. Adding one more per call will have virtually no notable impact.