Page 1 of 1

retain uniqueid in closer_log when dropping to/from ingroups

PostPosted: Thu Aug 24, 2017 8:34 pm
by retloc
Vicibox 7.03
VERSION: 2.14-585a
BUILD: 170114-1356
Asterisk 1.8.23.0

So per this previous support conversation...
viewtopic.php?f=4&t=37537


The most reliable solution was routing the call to one in-group for 2 seconds and dropping to a backup in-group. My problem now is retaining the uniqueid in the vicidial_closer_log between the two calls for reports.

I updated the ingroups Action Transfer CID to CUSTOMERCLOSER ( also tried just CLOSER ) with no success. Any suggestions?

Re: retain uniqueid in closer_log when dropping to/from ingr

PostPosted: Fri Aug 25, 2017 9:06 am
by mflorell
The "uniqueid" should not be changing on inbound calls going from one in-group to another. Could you please explain in more detail how you are doing this?

Re: retain uniqueid in closer_log when dropping to/from ingr

PostPosted: Fri Aug 25, 2017 1:10 pm
by retloc
I have 2 Ingroups assosiated to a DID. I also have two campaigns

users in campaign 100 select INGROUP-A
users in campaign 200 select INGROUP-A and INGROUP-B

CIDLOOKUP in DID settings
CUSTOMERCLOSER for action xfer ID in both ingroups

Route method to INGROUP-A
INGROUP A has Drop action set to 2 seconds and sends the call to INGROUP-B
Call is answered in INGROUP B

in vicidial_closer_log the specific calls uniqueid is different between the INGROUP_A and INGROUP-B records

Re: retain uniqueid in closer_log when dropping to/from ingr

PostPosted: Fri Aug 25, 2017 4:46 pm
by mflorell
Sorry, this was caused by a change in Asterisk, so there's not much we can do to prevent it since VICIdial collects the uniqueid of the call directly from Asterisk.

When we have needed to link these two kinds of records together in the past, we have used the vicidial_xfer_log table with the lead_id and the call_date to match up multi-leg in-group logs in the vicidial_closer_log table.

I will see if there might be a better way to do this though.

Re: retain uniqueid in closer_log when dropping to/from ingr

PostPosted: Fri Aug 25, 2017 5:24 pm
by retloc
If I drop the call to an extension and send the call back up using CLOSER I am able to retain the uniqueID. However, I have a lot of ingroups and I would prefer not having to take the call "out" of vicidial.

exten => 5554,1,Answer
exten => 5554,2,Set(CALLERID(number)=${CDR(src)})
exten => 5554,3,AGI(agi-VDAD_ALL_inbound.agi,CLOSER-----LB-----INGROUP2-----8005551234-----Closer-----park----------999-----1)

Re: retain uniqueid in closer_log when dropping to/from ingr

PostPosted: Sat Aug 26, 2017 12:01 am
by mflorell
When VICIdial first did in-group transfers, it did them a similar way with direct dialplan transfers. I looked up when this changed, and it was way back in 2008(svn revision 959).

This change to using an IAX loop to pass in-group transfers through was actually done to prevent issues on higher-load systems where sometimes in-group transferred calls would error and hangup during the redirect. This problem was eliminated with the use of the IAX loop. The byproduct of this was the loss of the same uniqueid.

To undo that change, you can actually just make a change in a single line of the extensions.conf file as well, but you need to understand that this change can result in calls being lost.


change this line:

exten => _90009.,2,Dial(${TRUNKloop}/9${EXTEN},,to)

to this:

exten => _90009.,2,AGI(agi-VDAD_ALL_inbound.agi,CLOSER-----LB-----CL_TESTCAMP-----7275551212-----Closer-----park----------999-----1)


I am actually working on more thorough logging within the vicidial_xfer_log table to store both the original uniqueid and the current uniqueid, which should help make tracing multi-transferred calls easier.