vicidial.org

Hello All,

I need help on this particular issue , it says " NO LIVE CALLS WAITING" , our client has a server based in UK , 2 different offices logged in to Server to dial , one of the offices work is going smooth with out any issues, however when ever the 2nd office team logs in and starts taking calls after about different intervals we get a message "NO LIVE CALLS WAITING" and the server stops connecting the calls , every time this happens we have to restart the server and start dialing again, we have upgraded the systems (computers)changed the switch and the router , we have a 4 mbps leased line

I need help to get this fixed as it is effecting production and peace of mind

thanks in advance

Try looking database performance issues. Check if you have tables corrupted

Maybe it's a time syncronization problem?
Check the console output once that team logs in?
Let the other team login with the other teams accounts and vice versa?
Let the problematic team login from another location?

In other words isoloate the problem. Also please post your vicidial version information.

my turn:

Could be ... Illegal numbers!For instance (in the USA) any 10 digit number with a 0 or 1 in the 1st or 4th position or 11 digits or 9 digits.

If you have numbers that do not fit the dial pattern for your carrier, those calls are requested (and count as auto-calls, which block more calls being generated), but they don't actually appear in the asterisk CLI, so vicidial scripts never 'attach' and manage them. This includes the cancellation of the call after dial timout seconds. So the system loses track of these calls forever leaving them in the auto-calls table, blocking any more dialing. a reboot them dumps that table and calls fire up again.

We use an "s" extension in a general/catch-all carrier to be sure this doesn't happen. Any numbers that fit no dial pattern will auto-attach to the s extension, which merely initiates vicidial (call_log entry, line 1) and then hangs up (ordinarily line three) without bothering to dial since the number is invalid.

Possible.

But it doesn't make sense why this happens when the second team logs in and not sooner. Assuming they are logged in on the same campaign as the other team.

Assuming they are logged in on the same campaign as the other team

I never assume. Always verify.

By writing i'm assuming something i'm really hinting to the poster to clarify this...

passive aggressive much? lol