agi-VDAD_ALL_inbound.agi using wrong callerid

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

agi-VDAD_ALL_inbound.agi using wrong callerid

Postby Acidshock » Wed Jul 25, 2018 4:41 pm

Ok trying to figure out how to get around this problem. For some reason agi-VDAD_ALL_inbound is setting the callerID number to the generated number used for tracking.

How the call flow works on this:

CustomerCalls->InboundGroup--(NoAnswer/Drop)-->CallMenu--(Presses 1 for different department, plus set to CIDLOOKUPRC) -->DifferentInboundGroup

Call is answered but then the agent only sees Y72513023000818665 as their phone number and no lead information.

AGI Log:

2018-07-25 12:46:19|12:46:21|agi-VDAD_ALL_inbound.agi|NNNNN No available balance agent found
2018-07-25 12:46:19|12:46:21|agi-VDAD_ALL_inbound.agi|ring_no_answer_agents reset
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi|Perl Environment Dump:
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi|0|CIDLOOKUPRC-----LB-----PlatILTCM-----TestTTS--------------------100025-----1-----PLAT------------------------------
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- accountcode =
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- arg_1 = CIDLOOKUPRC-----LB-----PlatILTCM-----TestTTS--------------------100025-----1-----PLAT------------------------------
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- callerid = 5551239876
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- calleridname = Y7251245450081866591
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- callingani2 = 62
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- callingpres = 0
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- callingtns = 0
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- callington = 0
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- channel = SIP/fr-00000517
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- context = TestTTS
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- dnid = 15625551234
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- enhanced = 0.0
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- extension = 1
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- language = en
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- priority = 1
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- rdnis = unknown
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- request = agi-VDAD_ALL_inbound.agi
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- threadid = 140151960815360
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- type = SIP
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- uniqueid = 1532547945.2781
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi| -- version = 11.25.1-vici
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi|AGI Variables: |1532547945.2781|SIP/fr-00000517|1|SIP|Y7251245450081866591|
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi|+++++ INBOUND CALL VDCL STARTED : |PlatILTCM|Y7251245450081866591-TestTTS|2018-07-25 12:46:24
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi|Holiday check: |0|SELECT count(*) from vicidial_call_time_holidays where holiday_date='2018-07-25' and holiday_status='ACTIVE';||Xmas|NewYears|July4th||
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi|VDAD vicidial_list search |Y7251245450081866591|SELECT lead_id,called_count from vicidial_list where phone_number='Y7251245450081866591' and list_id IN('100025','100026') order by last_local_call_time desc limit 1;|
2018-07-25 12:46:24|12:46:24|agi-VDAD_ALL_inbound.agi|VDAD vicidial_list insert |82260081|SELECT LAST_INSERT_ID() LIMIT 1;|
2018-07-25 12:46:24|12:46:27|agi-VDAD_ALL_inbound.agi||SELECT campaign_id FROM vicidial_campaigns where active='Y' and campaign_allow_inbound='Y';|82260081|
2018-07-25 12:46:24|12:46:27|agi-VDAD_ALL_inbound.agi|callerID changed: "Y7251246240082260081 <Y7251245450081866591>"
2018-07-25 12:46:24|12:46:27|agi-VDAD_ALL_inbound.agi|0|SELECT auto_call_id from vicidial_auto_calls where uniqueid='1532547945.2781' and server_ip='192.168.0.33';|
2018-07-25 12:46:24|12:46:27|agi-VDAD_ALL_inbound.agi||INSERT INTO vicidial_auto_calls SET server_ip='192.168.0.33', campaign_id='PlatILTCM', status='LIVE', lead_id='82260081', uniqueid='1532547945.2781', callerid='Y7251246240082260081', channel='SIP/fr-00000517', phone_code='1', phone_number='Y7251245450081866591', call_time='2018-07-25 12:46:24', call_type='IN', stage='LIVE-0', queue_priority='0' ;|
2018-07-25 12:46:24|12:46:27|agi-VDAD_ALL_inbound.agi|1|SELECT count(*) from vicidial_auto_calls where status = 'LIVE' and campaign_id='PlatILTCM';|
2018-07-25 12:46:24|12:46:27|agi-VDAD_ALL_inbound.agi|1|UPDATE vicidial_auto_calls SET queue_position='1' WHERE auto_call_id='2612516';|


VERSION: 2.14-645a
BUILD: 171214-2045
VERSION: 2.14-698a | BUILD: 190207-2301 | Asterisk:13.24.1-vici | Vicibox 8.1.2
Acidshock
 
Posts: 428
Joined: Wed Mar 03, 2010 3:19 pm

Re: agi-VDAD_ALL_inbound.agi using wrong callerid

Postby mflorell » Wed Jul 25, 2018 5:24 pm

Look for the In-Group "Action Transfer CID" setting, and set it to "CUSTOMERCLOSER".

Also, for the Call Menu, you need to use the "CLOSER" Search Method.
mflorell
Site Admin
 
Posts: 18338
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: agi-VDAD_ALL_inbound.agi using wrong callerid

Postby Acidshock » Wed Jul 25, 2018 5:49 pm

Awesome, learned something new! I am testing it now. However can you explain to me what is going on behind the scenes on CUSTOMER vs CUSTOMERCLOSER as the action? How does the CLOSER search method work? Feel free to get technical I have a decent understanding but I would like to further my knowledge.

Thanks in advance. Love you guys!
VERSION: 2.14-698a | BUILD: 190207-2301 | Asterisk:13.24.1-vici | Vicibox 8.1.2
Acidshock
 
Posts: 428
Joined: Wed Mar 03, 2010 3:19 pm

Re: agi-VDAD_ALL_inbound.agi using wrong callerid

Postby mflorell » Wed Jul 25, 2018 6:11 pm

The CLOSER method allows it to look at the lead_id that is embedded at the end of that 20-character CallerIDname string to identify the lead that is tied to that call.

The use of CUSTOMERCLOSER on the Action Transfer CID will set the customer's phone number as the CallerIDname and the 20-character string as the CallerIDname so wherever the call goes from there it can use those two pieces of information to identify the call.
mflorell
Site Admin
 
Posts: 18338
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida


Return to Support

Who is online

Users browsing this forum: No registered users and 93 guests