vicidial.org

by **lmoreira** » Fri Mar 16, 2018 8:11 am

Hi guys,

This system setup:
ViciBox 8.0.1 VERSION: 2.14-664a | BUILD: 180310-2321 | Asterisk 11.25.3-vici | Cluster 6 Servers | No Digium/Sangoma Hardware | About 100 Agents
04 Dialers (Intel(R) Xeon(R) 8xCPU X5560 @ 2.80GHz, RAM 8GB, HD 500GB SAS 15k)
01 WebServers (Intel(R) Xeon(R) 8xCPU X5560 @ 2.80GHz, RAM 8GB, HD 500GB SAS 15k)
01 DB (Intel(R) Xeon(R) 24xCPU X5660 @ 2.80GHz, RAM 24GB, HD 500GB SAS 15k)

Problem: Only first extended alt number is been Dialed.
Campaigns with Auto Alt-Number Dialing: ALL + ADDRESS + EXTENDED

Lead 19841056 example with 5 extended alt numbers, but only 1st was dailed:

Code: Select all: Lead information: CARLOS XXXXXX XXXXXX65372 - XXXXXX2899 Lead ID: 19841056 List ID: 9999 GMT offset: -3.00 CSLR: Y3 Fronter: VDAD Called Count: 12 Last Local Call: 2018-03-16 09:22:19 Tel1 : XXXXXX2899 Tel2 : XXXXXX6740 Tel3 : XXXXXX8525 EXTENDED ALTERNATE PHONE NUMBERS FOR THIS LEAD: # ALT PHONE ALT NOTE ALT COUNT ACTIVE 1 55 XXXXXX2899 1 Y 2 55 XXXXXX2413 2 Y 3 55 XXXXXX1049 3 Y 4 55 XXXXXX6045 4 Y 5 55 XXXXXX0501 5 Y CALLS TO THIS LEAD: # DATE/TIME LENGTH STATUS TSR CAMPAIGN LIST LEAD HANGUP REASON PHONE 1 2018-03-16 09:23:05 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX2899 <= Extended 2 2018-03-16 09:22:17 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX8525 3 2018-03-16 09:21:30 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX6740 4 2018-03-16 09:20:44 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX2899 <= Extended 5 2018-03-16 09:05:10 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX2899 6 2018-03-16 09:04:20 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX8525 7 2018-03-16 09:03:34 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX6740 8 2018-03-16 09:02:48 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX2899 9 2018-03-16 08:47:06 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX2899 10 2018-03-16 08:46:19 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX8525 11 2018-03-16 08:45:35 0 NA VDAD BANHONDA 9999 19841056 NONE XXXXXX6740 12 2018-03-16 08:44:32 0 AB VDAD BANHONDA 9999 19841056 NONE XXXXXX2899 From logs: action_process.2018-03-16:2018-03-16 8:44:50|2018-03-16 8:44:50|2018-03-16 08:44:50|114425642|||Originate|V3160844500019841056| action_process.2018-03-16:CallerID: V3160844500019841056 action_process.2018-03-16:Callerid: V3160844500019841056 action_process.2018-03-16:VDACnote: BANHONDA|19841056|55|8530216740|OUT|ALT|0 action_process.2018-03-16:2018-03-16 9:22:19|2018-03-16 9:22:19|2018-03-16 09:22:19|114435549|||Originate|V3160922190019841056| action_process.2018-03-16:CallerID: V3160922190019841056 action_process.2018-03-16:Callerid: V3160922190019841056 action_process.2018-03-16:VDACnote: BANHONDA|19841056|55|85987642899|OUT|X1|0

Any help appreciated!

by **blackbird2306** » Fri Mar 16, 2018 11:19 am

I see duplicate numbers for this lead, which is known to make problems. Tel1 xx2899 and Extended1 xx2899 seem to be equal? Are you using lead recycling anyway?

by **williamconley** » Fri Mar 16, 2018 11:34 am

Is "AB" in the AUTO ALT NUMBER DIALING FOR THIS CAMPAIGN?

by **blackbird2306** » Fri Mar 16, 2018 11:54 am

"AB" status is the first call not the last one

by **williamconley** » Fri Mar 16, 2018 12:06 pm

blackbird2306 wrote:"AB" status is the first call not the last one

It's all I had, man. lol

UNLESS ... the other numbers are in the DNC.

by **lmoreira** » Fri Mar 16, 2018 1:14 pm

blackbird2306 wrote:I see duplicate numbers for this lead, which is known to make problems. Tel1 xx2899 and Extended1 xx2899 seem to be equal? Are you using lead recycling anyway?

Nope. Tel1 is 84XXXXX2899 Extended1 is 85XXXXX2899. My first suspect was dupe numbers on main numbers and extended. There was a lot of dupes on leads. So I clean up all dupe numbers on same leads (vicidial_list and vicidial_list_alt_phones with same lead). Same behavior. Only first one extended is called.

Yes, leads recycling is activated. They reset list often.

williamconley wrote:Is "AB" in the AUTO ALT NUMBER DIALING FOR THIS CAMPAIGN?

UNLESS ... the other numbers are in the DNC.

Yes, It's there. Also NA, B, N, etc... It suppose to dial ALT NUMBERS on almost all status. NA is 70% of dial results.

No, DNC is disable on Campaign.

On astguiclient there is no X2, X3, etc... dial status. I see many X1, XLAST, ALT, ADDR3, NONE.

So, Doing reset on list make it return to tel1>tel2>tel3>ext1>ext2??

by **williamconley** » Fri Mar 16, 2018 1:18 pm

Check your astguiclient logs (turn them on in system settings if they are off) and find where the flow stops for the call. If "shooting from the hip of what may be wrong" fails, it's time to trace and actually troubleshoot the problem. 8-)

by **lmoreira** » Sat Mar 17, 2018 7:47 am

This issue has started couple weeks ago, I'm not sure when it first occurred. We do ViciDial upgrade not too often, but It's running latest since this issue showed up.

I'm looking at logs, but so far, no luck! I've got extreme case from yesterday, with full logs activated.

First, I stopped list reset until no lead pop up on hopper. Then I got the most dialed lead on the list. It's lead_id 19890126

This lead was called 51 times, and just 1st extended alt number was called 12 times, but none from 2, 3, and 4th.

Code: Select all: Lead information: ALAN XXXX XXXX - XXXXXX Lead ID: 19890126 List ID: 2001 GMT offset: -3.00 CSLR: N Fronter: VDAD Called Count: 51 Last Local Call: 2018-03-16 16:36:53 Tel1: 69XXXXX1888 tel2: 69XXXXX4951 Tel3: 69XXXXX4951 EXTENDED ALTERNATE PHONE NUMBERS FOR THIS LEAD: # ALT PHONE ALT NOTE ALT COUNT ACTIVE 1 55 69XXXXX7700 1 Y 2 55 69XXXXX2445 2 Y 3 55 69XXXXX6752 3 Y 4 55 91XXXXX7700 4 Y CALLS TO THIS LEAD: # DATE/TIME LENGTH STATUS TSR CAMPAIGN LIST LEAD HANGUP REASON PHONE CALLER ID 1 2018-03-16 16:37:42 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 2 2018-03-16 16:36:49 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 3 2018-03-16 16:36:05 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 4 2018-03-16 16:35:20 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 5 2018-03-16 16:09:02 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 6 2018-03-16 16:08:13 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 7 2018-03-16 16:07:28 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 8 2018-03-16 16:06:39 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 9 2018-03-16 15:44:22 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 10 2018-03-16 15:43:10 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 11 2018-03-16 15:41:49 0 AB VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 12 2018-03-16 15:41:45 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 13 2018-03-16 15:35:53 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 14 2018-03-16 15:34:45 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 15 2018-03-16 15:33:47 0 AB VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 16 2018-03-16 15:33:46 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 17 2018-03-16 15:24:23 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 18 2018-03-16 15:23:36 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 19 2018-03-16 15:22:15 0 AB VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 20 2018-03-16 15:22:12 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 21 2018-03-16 15:16:24 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 22 2018-03-16 15:15:21 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 23 2018-03-16 15:14:34 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 24 2018-03-16 15:13:45 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 25 2018-03-16 14:57:35 0 AB VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 26 2018-03-16 14:57:16 0 AB VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 27 2018-03-16 14:56:44 0 AB VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 28 2018-03-16 14:56:42 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 29 2018-03-16 14:40:17 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 30 2018-03-16 14:38:55 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 31 2018-03-16 14:38:04 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 32 2018-03-16 14:36:46 0 AB VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 33 2018-03-16 14:08:40 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 34 2018-03-16 14:07:52 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 35 2018-03-16 14:06:46 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 36 2018-03-16 14:05:54 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 37 2018-03-16 13:51:49 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 38 2018-03-16 13:50:54 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 39 2018-03-16 13:49:46 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 40 2018-03-16 13:48:57 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 41 2018-03-16 13:17:22 6 N claudemir BANHONDA 2001 19890126 AGENT 69XXXXX1888 42 2018-03-16 13:16:56 5 N claudemir BANHONDA 2001 19890126 AGENT 69XXXXX1888 43 2018-03-16 13:15:14 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 44 2018-03-16 13:14:25 71 N claudemir BANHONDA 2001 19890126 AGENT 69XXXXX1888 45 2018-03-16 13:13:13 4 FALHA claudemir BANHONDA 2001 19890126 CALLER 6XXXXX4951 46 2018-03-16 13:12:49 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX4951 47 2018-03-16 13:12:00 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888 48 2018-03-16 12:53:07 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX7700 49 2018-03-16 12:52:09 0 NA VDAD BANHONDA 2001 19890126 NONE 6XXXXX4951 50 2018-03-16 12:51:15 N dulcielledemorais BANHONDA 2001 19890126 NONE 69XXXXX4951 51 2018-03-16 12:50:57 0 NA VDAD BANHONDA 2001 19890126 NONE 69XXXXX1888

I turned on logs on 16:00, and I got this from this lead:

Code: Select all: # grep 19890126 vdautodial.2018-03-16 2018-03-16 16:06:40|| number call dialed|BANHONDA|V3161606400019890126|INSERT INTO vicidial_manager values('','','2018-03-16 16:06:40','NEW','N','191.1.1.81','','Originate','V3161606400019890126','Exten: 8368','Context: default','Channel: Local/9969XXXXX4951@default','Priority: 1','Callerid: V3161606400019890126','Timeout: 30000','','','','VDACnote: BANHONDA|19890126|55|69XXXXX4951 |OUT|ALT|0')|-3.00|ALT|| 2018-03-16 16:07:28|| dead call vac deleted|1453232|SENT|19890126|V3161606400019890126|1521227233|1||OUT|30|5|35|30|38|0E0|| 2018-03-16 16:07:28||SELECT result FROM vicidial_cpd_log where callerid='V3161606400019890126' order by cpd_id desc limit 1;|| 2018-03-16 16:07:28||SELECT list_id,called_count from vicidial_list where lead_id='19890126' limit 1;|| 2018-03-16 16:07:28|| dead NA call added to log 1521227203.11406987|19890126|69XXXXX4951|SENT|NA|1|1|0| 2018-03-16 16:07:28|| dead call vac lead marked NA|19890126|69XXXXX4951|SENT|| 2018-03-16 16:07:28||SELECT auto_alt_dial,auto_alt_dial_statuses,use_internal_dnc,use_campaign_dnc,use_other_campaign_dnc FROM vicidial_campaigns where campaign_id='BANHONDA';|ALT_AND_ADDR3_AND_EXTENDED| CPFNOE NI DEC NA B NEW NANQUE XDROP FALHA PM PDROP LRERR ERI AM ADC A ADCT AL NENCON DROP AFAX AB AA N DC -|NA|19890126|ALT| 2018-03-16 16:07:28||SELECT address3,gmt_offset_now,state,list_id FROM vicidial_list where lead_id='19890126';|69XXXXX4951|| 2018-03-16 16:07:28||SELECT address3,gmt_offset_now,state,list_id FROM vicidial_list where lead_id='19890126';|0|| 2018-03-16 16:07:28|-- VDH record inserted: |1| |INSERT INTO vicidial_hopper SET lead_id='19890126',campaign_id='BANHONDA',status='READY',list_id='2001',gmt_offset_now='-3.00',state='RO',alt_dial='ADDR3',user='',priority='20',source='A';|| 2018-03-16 16:07:28| VNA match, log processed: V3161606400019890126|1|1| 2018-03-16 16:36:06|| number call dialed|BANHONDA|V3161636060019890126|INSERT INTO vicidial_manager values('','','2018-03-16 16:36:06','NEW','N','191.1.1.81','','Originate','V3161636060019890126','Exten: 8368','Context: default','Channel: Local/9969XXXXX4951@default','Priority: 1','Callerid: V3161636060019890126','Timeout: 30000','','','','VDACnote: BANHONDA|19890126|55|69XXXXX4951|OUT|ADDR3|0')|-3.00|ADDR3|| 2018-03-16 16:36:49|| dead call vac deleted|1461083|SENT|19890126|V3161636060019890126|1521228974|1||OUT|30|5|35|7|35|0E0|| 2018-03-16 16:36:49||SELECT result FROM vicidial_cpd_log where callerid='V3161636060019890126' order by cpd_id desc limit 1;|| 2018-03-16 16:36:49||SELECT list_id,called_count from vicidial_list where lead_id='19890126' limit 1;|| 2018-03-16 16:36:49|| dead NA call added to log 1521228967.11413016|19890126|69XXXXX4951|SENT|NA|1|1|0| 2018-03-16 16:36:49|| dead call vac lead marked NA|19890126|69XXXXX4951|SENT|| 2018-03-16 16:36:49||SELECT auto_alt_dial,auto_alt_dial_statuses,use_internal_dnc,use_campaign_dnc,use_other_campaign_dnc FROM vicidial_campaigns where campaign_id='BANHONDA';|ALT_AND_ADDR3_AND_EXTENDED| CPFNOE NI DEC NA B NEW NANQUE XDROP FALHA PM PDROP LRERR ERI AM ADC A ADCT AL NENCON DROP AFAX AB AA N DC -|NA|19890126|ADDR3| 2018-03-16 16:36:49||SELECT count(*) FROM vicidial_list_alt_phones where lead_id='19890126';|4| 2018-03-16 16:36:49||SELECT alt_phone_id,phone_number,active FROM vicidial_list_alt_phones where lead_id='19890126' and alt_phone_count='1';|69992417700|1|| 2018-03-16 16:36:49|-- VDH record inserted: |1| |INSERT INTO vicidial_hopper SET lead_id='19890126',campaign_id='BANHONDA',status='READY',list_id='2001',gmt_offset_now='-3.00',state='RO',alt_dial='X1',user='',priority='15',source='A';|X1|15280749|| 2018-03-16 16:36:49| VNA match, log processed: V3161636060019890126|1|1|

So, I removed NA status (70%+) from lead recycling. Let's check If It's makes extended alt be dialed today. Just a long shot...

If you see some on the logs that I missed, please, let me know. I'll keep tracking this issue until be sure if It's now my bad.

by **blackbird2306** » Sat Mar 17, 2018 8:51 am

The thing is lead recycling and resetting the list will start all from beginning phone number 1 without notice of alternate number dialing. But it is conspicuous that after dialing extended 1 number there is always a break about 15-20 minutes. As you mentioned before try this for testing:

1. turn off lead recycling completly for all statuses
2. don't reset the list or only when there are no dialable leads anymore

After testing with above steps try next to call with campaign setting "Auto Alt-Number Dialing" --> "Extended Only"

by **williamconley** » Sat Mar 17, 2018 10:48 am

Before you try anything else, turn off lead recycling.

by **blackbird2306** » Sat Mar 17, 2018 11:03 am

As I have mentioned above turn off lead recycling completely and don't reset the list. After testing and when it's not working, then try it with auto alt-number dialing extended only!

by **lmoreira** » Tue Mar 20, 2018 12:37 pm

blackbird2306 wrote:As I have mentioned above turn off lead recycling completely and don't reset the list. After testing and when it's not working, then try it with auto alt-number dialing extended only!

williamconley wrote:Before you try anything else, turn off lead recycling.

Hi guys,

Thanks for suggestions. Lead recycling was turned off, still not dialing all Extended Alt. Few cases,ext #2 or #3 was dialed, but It's not consistent for all leads.

See his example: 7 calls for this lead.
Sequence: tel1 >> tel2 >> tel3 >> ext1 (11:25) >> then 13:50 list reset >> tel1 (13:59) >> tel2 >> tel3

I'm looking on logs, but really I don't know what could be suspicious or not.

Code: Select all: Lead ID: 19887686 List ID: 2001 GMT offset: -3.00 CSLR: Y2 Fronter: VDAD Called Count: 7 Last Local Call: 2018-03-20 13:59:50 tel1 = 85XXXXX6672 <= dialed 2x tel2 = 88XXXXX0923 <= dialed 2x tel3 = 85XXXXX1058 <= dialed 2x EXTENDED ALTERNATE PHONE NUMBERS FOR THIS LEAD: 1 55 88XXXXX1141 <= dialed 1x 2 55 85XXXXX8779 3 55 88XXXXX0143 4 55 85XXXXX4770 5 55 85XXXXX9000 6 55 85XXXXX1141 CALLS TO THIS LEAD: 1 2018-03-20 14:00:36 0 NA VDAD 2001 19887686 NONE 85XXXXX1058 <= tel3 2 2018-03-20 13:59:48 0 NA VDAD 2001 19887686 NONE 88XXXXX0923 <= tel2 3 2018-03-20 13:59:03 0 NA VDAD 2001 19887686 NONE 85XXXXX6672 <= tel1 4 2018-03-20 11:25:43 0 NA VDAD 2001 19887686 NONE 88XXXXX1141 <= Ext1 5 2018-03-20 11:24:45 0 ADCT VDAD 2001 19887686 NONE 85XXXXX1058 <= tel3 6 2018-03-20 11:24:42 0 NA VDAD 2001 19887686 NONE 88XXXXX0923 <= tel2 7 2018-03-20 11:23:56 0 NA VDAD 2001 19887686 NONE 85XXXXX6672 <= tel1

by **williamconley** » Tue Mar 20, 2018 12:46 pm

williamconley wrote:Check your astguiclient logs (turn them on in system settings if they are off) and find where the flow stops for the call. If "shooting from the hip of what may be wrong" fails, it's time to trace and actually troubleshoot the problem.

by **lmoreira** » Wed Mar 21, 2018 9:48 am

I diged into the logs a lot. Then I compared leads whict was dialed to ext1 only, and ext1+ext2 only, and ext1+ext2+ext3 only and stopped calling.

All of them, stopped calling after no-agent status (VDAD). After that, next extended alt number wont be dialed at all. Once list is reset, it starts over from tel1>tel2>tel3 then, on ext1 if no-agent status (VDAD) come up, none of extended alternatives number is dial.

Certainty It's bug.

by **blackbird2306** » Thu Mar 22, 2018 8:01 am

Please make some tests with auto alt-number dialing setting "Extended Only" so we can pinpoint the error. Inform us about the results.

by **mflorell** » Thu Mar 22, 2018 10:38 am

I have tested this and cannot replicate your issue.

Link to the ticket you opened with my feedback:
http://www.vicidial.org/VICIDIALmantis/view.php?id=1085

by **lmoreira** » Thu Mar 22, 2018 1:01 pm

@mflorell

I dont have MAIN, or X1, X2... on alt_dial, as you show:

Code: Select all: +---------------------+--------------+----------+--------+--------------+-------------------+----------+ | call_date | phone_number | lead_id | status | called_count | user | alt_dial | +---------------------+--------------+----------+--------+--------------+-------------------+----------+ | 2018-03-22 13:55:48 | 69XXXX3893 | 19893782 | NA | 4 | VDAD | | | 2018-03-22 13:54:39 | 63XXXX3893 | 19893782 | NA | 3 | VDAD | ADDR3 | | 2018-03-22 13:53:31 | 63XXXX3893 | 19893782 | NA | 2 | VDAD | ALT | | 2018-03-22 13:51:51 | 98XXXX3893 | 19893782 | AB | 1 | VDAD | NONE | | 2018-03-22 10:32:28 | 69XXXX3893 | 19893782 | NA | 4 | VDAD | | | 2018-03-22 10:31:33 | 63XXXX3893 | 19893782 | NA | 3 | VDAD | ADDR3 | | 2018-03-22 10:30:36 | 98XXXX3893 | 19893782 | NA | 2 | VDAD | ALT | | 2018-03-22 10:29:37 | 69XXXX3893 | 19893782 | NA | 1 | VDAD | NONE | | 2018-03-22 09:11:44 | 69XXXX3893 | 19893782 | NA | 4 | VDAD | | | 2018-03-22 09:10:43 | 63XXXX3893 | 19893782 | NA | 3 | VDAD | ADDR3 | | 2018-03-22 09:09:46 | 98XXXX3893 | 19893782 | NA | 2 | VDAD | ALT | | 2018-03-22 09:08:52 | 69XXXX3893 | 19893782 | NA | 1 | VDAD | NONE | | 2018-03-21 15:12:15 | 69XXXX3893 | 19893782 | NA | 4 | VDAD | | | 2018-03-21 15:11:10 | 63XXXX3893 | 19893782 | NA | 3 | VDAD | ADDR3 | | 2018-03-21 15:10:06 | 98XXXX3893 | 19893782 | NA | 2 | VDAD | ALT | | 2018-03-21 15:09:09 | 69XXXX3893 | 19893782 | NA | 1 | VDAD | NONE | | 2018-03-21 13:49:30 | 69XXXX3893 | 19893782 | NA | 4 | VDAD | | +---------------------+--------------+----------+--------+--------------+-------------------+----------+

by **mflorell** » Thu Mar 22, 2018 2:30 pm

Maybe that's your issue, although I don't know how to replicate that issue since I don't have that problem on my system.

by **lmoreira** » Tue Mar 27, 2018 4:28 pm

mflorell wrote:Maybe that's your issue, although I don't know how to replicate that issue since I don't have that problem on my system.

Maybe... But there is no customization on this system.

Logs still strange. If you could guide me where I need to look at...

@mflorell, Could you check this logs and say If am I wrong?

Code: Select all: ==> MAIN PHONE NUMBER DIALED 2018-03-27 17:50:06|| number call dialed|BANHONDA|V3271750060019890844|INSERT INTO vicidial_manager values('','','2018-03-27 17:50:06','NEW','N','191.1.1.81','','Originate','V3271750060019890844','Exten: 8368','Context: default','Channel: Local/9983XXXXX0495@default','Priority: 1','Callerid: V3271750060019890844','Timeout: 40000','','','','VDACnote: BANHONDA|19890844|55|83XXXXX0495|OUT|NONE|0')|-3.00|NONE|| 2018-03-27 17:50:41|| dead call vac deleted|923482|DISCONNECT|19890844|V3271750060019890844|1522183828|1||OUT|40|5|45|6|12|0E0|| 2018-03-27 17:50:41||SELECT result FROM vicidial_cpd_log where callerid='V3271750060019890844' order by cpd_id desc limit 1;|| 2018-03-27 17:50:41||SELECT list_id,called_count from vicidial_list where lead_id='19890844' limit 1;|| 2018-03-27 17:50:41|| dead NA call added to log 1522183822.1168780|19890844|83XXXXX0495|DISCONNECT|ADC|||0| 2018-03-27 17:50:41|| dead call vac lead marked ADC|19890844|83XXXXX0495|DISCONNECT|| ==> ALT DIAL is set to EXTENDED_ONLY 2018-03-27 17:50:41||SELECT auto_alt_dial,auto_alt_dial_statuses,use_internal_dnc,use_campaign_dnc,use_other_campaign_dnc FROM vicidial_campaigns where campaign_id='BANHONDA';|EXTENDED_ONLY| CPFNOE NI DEC NA B NEW NANQUE XDROP FALHA PM PDROP LRERR ERI AM ADC A ADCT AL NENCON DROP AFAX AB AA N DC -|ADC|19890844|NONE| ==> THERE ARE 3 EXTENDED NUMBERS TO DIAL 2018-03-27 17:50:41||SELECT count(*) FROM vicidial_list_alt_phones where lead_id='19890844';|3| ==> GET 1ST EXTENDED NUMBER 2018-03-27 17:50:41||SELECT alt_phone_id,phone_number,active FROM vicidial_list_alt_phones where lead_id='19890844' and alt_phone_count='1';|83XXXXX9826|1|| 2018-03-27 17:50:41|-- VDH record inserted: |1| |INSERT INTO vicidial_hopper SET lead_id='19890844',campaign_id='BANHONDA',status='READY',list_id='2001',gmt_offset_now='-3.00',state='PB',alt_dial='X1',user='',priority='15',source='A';|X1|15282130|| 2018-03-27 17:50:42| VNA no-match, log processed: V3271750060019890844|1| ==> CALL 1ST EXTENDED 2018-03-27 17:50:45|| number call dialed|BANHONDA|V3271750450019890844|INSERT INTO vicidial_manager values('','','2018-03-27 17:50:45','NEW','N','191.1.1.81','','Originate','V3271750450019890844','Exten: 8368','Context: default','Channel: Local/9983XXXXX9826@default','Priority: 1','Callerid: V3271750450019890844','Timeout: 40000','','','','VDACnote: BANHONDA|19890844|55|83XXXXX9826|OUT|X1|0')|-3.00|X1|| 2018-03-27 17:50:56|| dead call vac deleted|923645|DISCONNECT|19890844|V3271750450019890844|1522183854|1||OUT|40|5|45|6|1|0E0|| 2018-03-27 17:50:56||SELECT result FROM vicidial_cpd_log where callerid='V3271750450019890844' order by cpd_id desc limit 1;|| ==> ON DB, RESULT FOR THIS QUERY IS: "|2001|2|", BUT IT'S EMPTY. 2018-03-27 17:50:56||SELECT list_id,called_count from vicidial_list where lead_id='19890844' limit 1;|| ==> NO MORE DIALING AFTER THIS POINT 2018-03-27 17:50:56|| dead NA call added to log 1522183848.1168981|19890844|83XXXXX9826|DISCONNECT|ADC|||0| 2018-03-27 17:50:56|| dead call vac lead marked ADC|19890844|83XXXXX9826|DISCONNECT|| 2018-03-27 17:50:56||SELECT auto_alt_dial,auto_alt_dial_statuses,use_internal_dnc,use_campaign_dnc,use_other_campaign_dnc FROM vicidial_campaigns where campaign_id='BANHONDA';|EXTENDED_ONLY| CPFNOE NI DEC NA B NEW NANQUE XDROP FALHA PM PDROP LRERR ERI AM ADC A ADCT AL NENCON DROP AFAX AB AA N DC -|ADC|19890844|| 2018-03-27 17:50:56| VNA no-match, log processed: V3271750450019890844|1|

by **blackbird2306** » Wed Mar 28, 2018 6:13 am

It's not only maybe it's more about surely one symptom of the problem I think. The system looks into alt_dial column on different tables and decides from this point, which alternative number to dial next. Somehow there is no X1 in alt_dial for the first extended number. So the system doesn't know, which one was dialed last time and which one to dial next and from there stops to dial. After a while you reset the lists and everything starts from the beginning. Perhaps there is something wrong with your import process in "vicidial_list_alt_phones" table (wrong numbers or whatever). Simply compare with the calls, where 2nd and 3rd extended number dialing was fine. You should find out, where it starts with the missing alt_dial flag.
My suggestion:
Make a test campaign with only one test list and one lead in it. Import the extended numbers and start to call with overdial 1. Look everytime what happens after hangup/dispose with a alternative number dialing status.
Especially look into these tables to find out where the problem starts:
1. vicidial_hopper for alt_dial column
2. vicidial_log also alt_dial column
3. vicidial_auto_calls also alt_dial column

What is the output for:
SELECT * FROM `vicidial_list_alt_phones` WHERE lead_id = '19890844'

If you are crazy enough change manually in database table vicidial_hopper (or after that the other tables I mentioned) the alt_dial column to "X1" (surely not any random row, the right one, where the X1 should be normally) and look what happens: does it proceed with "X2" ?

by **lmoreira** » Wed Mar 28, 2018 9:58 am

blackbird2306 wrote:What is the output for:
SELECT * FROM `vicidial_list_alt_phones` WHERE lead_id = '19890844'

Result:

Code: Select all: MariaDB [asterisk]> SELECT * FROM `vicidial_list_alt_phones` WHERE lead_id = '19890844'; +--------------+----------+------------+--------------+----------------+-----------------+--------+ | alt_phone_id | lead_id | phone_code | phone_number | alt_phone_note | alt_phone_count | active | +--------------+----------+------------+--------------+----------------+-----------------+--------+ | 15282130 | 19890844 | 55 | 83XXXXX9826 | | 1 | Y | | 15282131 | 19890844 | 55 | 83XXXXX4953 | | 2 | Y | | 15282132 | 19890844 | 55 | 83XXXXX0868 | | 3 | Y | +--------------+----------+------------+--------------+----------------+-----------------+--------+

I will try to manually chance one lead on database and see what happen.

by **mflorell** » Wed Mar 28, 2018 11:26 am

As a side note on this, since I haven't mentioned it in this thread yet, most of our debt collection clients use the MULTI_LEAD method of Auto-Alt-Dialing, since it gives much more control and allows for per-phone-number statuses and targeted phone-type calling.

http://vicidial.org/docs/ALTERNATE_NUMBER_DIALING.txt

by **lmoreira** » Wed Mar 28, 2018 12:26 pm

@mflorell,

Thanks for reply. Yes, I'm considering migrate to MULTI_LEAD near future for this campaign.

Meanwhile, I found the problem.

Code: Select all: MariaDB [asterisk]> describe vicidial_auto_calls; +----------------------+----------------------------------------------------------------------------------+------+-----+-------------------+-----------------------------+ | Field | Type | Null | Key | Default | Extra | +----------------------+----------------------------------------------------------------------------------+------+-----+-------------------+-----------------------------+ | auto_call_id | int(9) unsigned | NO | PRI | NULL | auto_increment | | server_ip | varchar(15) | NO | | NULL | | | campaign_id | varchar(20) | YES | | NULL | | | status | enum('SENT','RINGING','LIVE','XFER','PAUSED','CLOSER','BUSY','DISCONNECT','IVR') | YES | | PAUSED | | | lead_id | int(9) unsigned | NO | | NULL | | | uniqueid | varchar(20) | YES | MUL | NULL | | | callerid | varchar(20) | YES | MUL | NULL | | | channel | varchar(100) | YES | | NULL | | | phone_code | varchar(10) | YES | | NULL | | | phone_number | varchar(18) | YES | | NULL | | | call_time | datetime | YES | MUL | NULL | | | call_type | enum('IN','OUT','OUTBALANCE') | YES | | OUT | | | stage | varchar(20) | YES | | START | | | last_update_time | timestamp | NO | MUL | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP | | queue_priority | tinyint(2) | YES | | 0 | | | agent_only | varchar(20) | YES | | | | | agent_grab | varchar(20) | YES | | | | | queue_position | smallint(4) unsigned | YES | | 1 | | | extension | varchar(100) | YES | | | | | agent_grab_extension | varchar(100) | YES | | | | | alt_dial | enum('NONE','MAIN','ALT','ADDR3') | YES | | NONE | | +----------------------+----------------------------------------------------------------------------------+------+-----+-------------------+-----------------------------+

Then, I altered vicidial_auto_calls table to include X1,X2, etc... and all ALTERNATES NUMBERS are being dialed now.

Code: Select all: MariaDB [asterisk]> describe vicidial_auto_calls; +----------------------+--------------------------------------------------------------------------------------+------+-----+-------------------+-----------------------------+ | Field | Type | Null | Key | Default | Extra | +----------------------+--------------------------------------------------------------------------------------+------+-----+-------------------+-----------------------------+ | auto_call_id | int(9) unsigned | NO | PRI | NULL | auto_increment | | server_ip | varchar(15) | NO | | NULL | | | campaign_id | varchar(20) | YES | | NULL | | | status | enum('SENT','RINGING','LIVE','XFER','PAUSED','CLOSER','BUSY','DISCONNECT','IVR') | YES | | PAUSED | | | lead_id | int(9) unsigned | NO | | NULL | | | uniqueid | varchar(20) | YES | MUL | NULL | | | callerid | varchar(20) | YES | MUL | NULL | | | channel | varchar(100) | YES | | NULL | | | phone_code | varchar(10) | YES | | NULL | | | phone_number | varchar(18) | YES | | NULL | | | call_time | datetime | YES | MUL | NULL | | | call_type | enum('IN','OUT','OUTBALANCE') | YES | | OUT | | | stage | varchar(20) | YES | | START | | | last_update_time | timestamp | NO | MUL | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP | | queue_priority | tinyint(2) | YES | | 0 | | | agent_only | varchar(20) | YES | | | | | agent_grab | varchar(20) | YES | | | | | queue_position | smallint(4) unsigned | YES | | 1 | | | extension | varchar(100) | YES | | | | | agent_grab_extension | varchar(100) | YES | | | | | alt_dial | enum('NONE','MAIN','ALT','ADDR3','X1','X2','X3','X4','X5','X6','X7','X8','X9','X10') | YES | | NONE | | +----------------------+--------------------------------------------------------------------------------------+------+-----+-------------------+-----------------------------+

Thanks guys for all support. This issue really pushed me out to figure out the problem.

by **mflorell** » Wed Mar 28, 2018 1:01 pm

Thanks for posting your solution, but now I'm confused as to why I had no problems for the example I posted in the Issue Tracker ticket for this.

by **lmoreira** » Wed Mar 28, 2018 1:12 pm

mflorell wrote:Thanks for posting your solution, but now I'm confused as to why I had no problems for the example I posted in the Issue Tracker ticket for this.

Because in new versions, this column is "alt_dial| varchar(6)". My DB was installed from old Vicibox 7.0.3 then upgraded to lastest SVN code along the time, always applying sql update, but somehow this table remained on old format, or this modification is not on SVN upgrade.

by **mflorell** » Wed Mar 28, 2018 1:38 pm

Ah, that makes sense, although that column was changed 9 years ago in the upgrade_2.0.5.sql file, so not sure how you got that in VICIbox 7 unless you were importing the DB from a much older system.

by **lmoreira** » Wed Mar 28, 2018 1:44 pm

mflorell wrote:Ah, that makes sense, although that column was changed 9 years ago in the upgrade_2.0.5.sql file, so not sure how you got that in VICIbox 7 unless you were importing the DB from a much older system.

You're right! This 7.0.3 version was from server upgrade and DB was imported from older server... Don't know how old, but 9+ years is possible. All others modifications are there, but this alt_dial column...

Thanks for support. Ended up, it was my bad all the time.

vicidial.org

Not Dialing all Extended Alt Numbers

Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers [SOLVED]

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Re: Not Dialing all Extended Alt Numbers

Who is online