Next Agent Call Not Working
Posted: Sat Sep 24, 2016 3:59 pmHello 
This sounds like a silly issue, but it is getting really frustrating. First this is my setup:
Version: 2.12-565a Build: 160827-0917
Installation Method: Vicibox 7.0.2
Cluster Setup: 1 x DB/Web + 2 x Dialers
So this is the problem, My campaign is dialing as expected, but it is assigning calls on a very weird way. I have already try with longest_wait, oldest_call_finish, oldest_call_start, fewer_calls but it keeps "ignoring some agents".
Already check the database for corrupted tables, and the load of system is perfect 0.89 load on a Xeon E3 Quad Core
Eventually, they will get calls, like when nobody else is available, but i wonder why it is ignoring the campaign option for next agent call.
This happen with 3 o 4 agents on a 50 agents campaign, so not really sure whats going on, there is no option for Threshold, and as far as i know, even if there was a Threshold it should not affect the next agent call option.
any ideas on where to keep looking ?
This sounds like a silly issue, but it is getting really frustrating. First this is my setup:
Version: 2.12-565a Build: 160827-0917
Installation Method: Vicibox 7.0.2
Cluster Setup: 1 x DB/Web + 2 x Dialers
So this is the problem, My campaign is dialing as expected, but it is assigning calls on a very weird way. I have already try with longest_wait, oldest_call_finish, oldest_call_start, fewer_calls but it keeps "ignoring some agents".
Already check the database for corrupted tables, and the load of system is perfect 0.89 load on a Xeon E3 Quad Core
Eventually, they will get calls, like when nobody else is available, but i wonder why it is ignoring the campaign option for next agent call.
This happen with 3 o 4 agents on a 50 agents campaign, so not really sure whats going on, there is no option for Threshold, and as far as i know, even if there was a Threshold it should not affect the next agent call option.
any ideas on where to keep looking ?