Page 1 of 1
lot of new called lead / don´t have any NA status

Posted:
Mon Nov 10, 2008 9:07 pm
by schernit
I have a predictive campaign. I don´t have any NA record on vicidial_list. What I see is a lot of NEW records with called_count = 1 and modify_date updated.
I see on logs and I see that those calls have received CANCEL with 16 status.
Timeout = 30 secs
Another strange think I have seen is that almost all records are mobile phones (In Argentina mobile phone has 12 digits). I have many 12 digits phones that are sent to agents well. I don´t if this can be a problem but I just want to comment it.
Please, tell me what log should I sent you.
Regards,
Sebastian

Posted:
Mon Nov 10, 2008 10:27 pm
by mflorell
Do you have the 'h' exten in your dialplan?
h extension

Posted:
Fri Nov 21, 2008 10:34 pm
by schernit
yes, i have

Posted:
Sat Nov 22, 2008 1:10 am
by mflorell
Do you have the 'h' exten in every context, and are all of the 'screen' applications (like ASTfastlog) running?

Posted:
Sat Nov 22, 2008 1:10 am
by mflorell
Do you have the 'h' exten in every context, and are all of the 'screen' applications (like ASTfastlog) running?
configuration

Posted:
Tue Nov 25, 2008 6:30 pm
by schernit
this are screen processes.
xen2:/# screen -r
There are several suitable screens on:
14143.ASTVDadapt (Detached)
14132.ASTlisten (Detached)
14146.ASTfastlog (Detached)
14126.ASTupdate (Detached)
14053.asterisk (Detached)
14140.ASTVDremote (Detached)
14135.ASTVDauto (Detached)
14129.ASTsend (Detached)
Remove dead screens with 'screen -wipe'.
Type "screen [-d] -r [pid.]tty.host" to resume one of them.
xen2:/#
NA

Posted:
Sun Nov 30, 2008 3:48 pm
by schernit
Can you tell me how vicidial understand there is a No Anser call and what id the proccess that update the NA status on vicidial_log / vicidial_list ?
Regards,
Sebastian

Posted:
Sun Nov 30, 2008 11:39 pm
by mflorell
Asterisk times out the call according to the timeout you set and the call then goes to the 'h' exten in the context of the dialplan that the call was in, then the FastAGI_log process assigns the proper status to the proper call.
Also, make sure you are not altering CallerID anywhere in your dialplan.