Page 1 of 1
gmt_offset_now Questions
Posted:
Tue Jun 16, 2009 8:48 am
by scottgutman
I noticed that when load leads in to vicidial, the gmt_offset_now is 1 less than the actual GMT of the area. i.e. area code 954 which is GMT (-5) has a gmt_offset_value of -4. Is this correct?
If this is correct, then what happens in 6 months when we are not in DST, will the system autocorrect?
Posted:
Tue Jun 16, 2009 8:56 am
by mflorell
The GMT offset now field is the current offset from Zulu(or Greenwich Mean) Time, not the timezone of the lead. Yes it does auto-adjust according to the area-code that you are in, and it checks it every night.
Posted:
Tue Jun 16, 2009 9:28 am
by scottgutman
what what should the gmt_offset_now field be for New York?
Posted:
Tue Jun 16, 2009 12:01 pm
by scottgutman
so now that we are in DST, the gmt_offset_now is -4, and after november it will be -5.
is there a script that corrects all the leads in the table?
or does the vicidial internally calculate when the lead was inserted to adjust for times when we are not in DST?
Posted:
Tue Jun 16, 2009 12:12 pm
by mflorell
exactly.
The ADMIN_adjust_GMTnow_on_leads.pl script that is run every night is what makes sure that the leads are at their proper gmt offset.
Posted:
Tue Jun 16, 2009 3:35 pm
by scottgutman
thanks, i feel more confident about it's usage now.