AUTO ALT NUMBER DIALING stats returns call to primary number

[MShulev]

We use predictive dialing with Adapt_Average setting
We have configured about 10 custom statuses for this campaign.

3 of them we configure in "AUTO ALT NUMBER DIALING FOR THIS CAMPAIGN" for example "NonPerson Contact"

Non of them are in "LEAD RECYCLING WITHIN THIS CAMPAIGN" and we use only N and NEW like "Dial Status 1" and "Dial Status 2".

After the agent connects on primary number, and set status "NonPersonalContact", which one is in the "AUTO ALT NUMBER DIALING FOR THIS CAMPAIGN", sometimes next dial is again on the first number, but not on Alt.

Any ideas are appreciated.

[MShulev]

for example:
from vicidial_log:
uniqueid, lead_id, list_id, campaign_id, call_date, start_epoch, end_epoch, length_in_sec, status, phone_code, phone_number, user, comments, processed, user_group
1189693657.2365, 40917, 207, SOFT_C, 2007-09-13 17:28:00, 1189693680, 1189693748, 68, CRNP, 1, 0896332099, agent1, AUTO, N, Agents
- the lead was called on 0986332099 and the call finished with status CNRP, which is in Auto Dial Alt Numbers Status list.

From Hopper report:
... | LEAD_ID | PHONE NUM | STATE | STATUS | COUNT | GMT | ALT
32| 40917 | 0896332099 | ....... | CRNP | 1 | -4.00 | ALT

I interpret that this way , even the ALT field is filled up corectly with "ALT" next time hopper will use the SAME number 0896332099 to dial.
Im i right?

Our result is : we disturb twice on the pri number, before we start call on alt and 3rth (address3) number.

Please, HELP!

p.s. sorry for my poor english :/

[mflorell]

Could you post the vicidial_log entries for that lead as well as the phone_number and alt_phone for the vicidial_list entry of that record?