Page 1 of 1

Vicidial not working for 1 hour after the DST end?

PostPosted: Fri Oct 24, 2014 8:19 am
by pahonen
Hi,

I guess this is not a huge problem for the most of the Vicidial users, but for us, running a 24/7 operation here, this is kind of big deal.

Last October, when the DST ended here in our whereabouts, our contact center halted for an hour. Apparently this has something to do with the timestamps and turning the clock backwards..
Whatever was the cause, the Vicidial was not receiving or making any phone calls during that one hour when the were on the "already used time" zone. Nothing seemed to help, restarting vicidial, database, reboots on servers, workstations, still no phone calls.

Exactly one hour of the DST end everything started to work again.

Any ideas on how to prevent this from happening on next weekend?

thanks,
petteri

Currently we're running the vicidial version 2.8-439a, build 140515-1610, back then it was something older.

Re: Vicidial not working for 1 hour after the DST end?

PostPosted: Wed Nov 05, 2014 8:49 am
by Iz3k34l
Not sure if you found the solution or not, but it sounds like your Local Call Time settings... Set them to 24 hours... also check you system settings under Admin >> System Settings >> Default Local GMT, make it reflects YOUR local timezone settings.

Re: Vicidial not working for 1 hour after the DST end?

PostPosted: Tue Oct 29, 2024 6:06 pm
by taha12us
Exactly the same issue. Default Local GMT is correct.
Still having this issue and could not found the solution yet.

Re: Vicidial not working for 1 hour after the DST end?

PostPosted: Tue Oct 29, 2024 8:53 pm
by williamconley
Iz3k34l wrote:Not sure if you found the solution or not, but it sounds like your Local Call Time settings... Set them to 24 hours... also check you system settings under Admin >> System Settings >> Default Local GMT, make it reflects YOUR local timezone settings.


Good idea. But not sure that would block inbound calls.

Just like running the GMT script would only "fix" outbound calls.

Of course, it's entirely possible there are two problems at play here and inbound is just being blocked by the carrier (to avoid billing incongruities, screw the customer impact 8-) )

I wish we had CLI output from an inbound call from the previous year.