Page 1 of 1

GMT Offset Problem

PostPosted: Wed Oct 07, 2009 11:56 am
by mstopkey
Greetings all,
I have searched and cannot find a solution to our exact problem. I have read the purchased manuals, purchased the NANPA list, followed the instructions with the NANPA list and here is my problem. When we run the GMT offset script, it sets the majority of the leads in vicidial_list gmt_offset_now to 0.00. This of course stops leads from loading into the hopper because of incorrect GMT on the leads. (+0)
We are in -6 GMT. Server set to -6. Hardware and OS set correctly. Country codes on all lists are set to 1. Complete call times settings are in place by state. Our call time for campaign is setup. Most states are set to start calling at 8am and stop at 9pm. We need the fine tuning of zones by NANPA capability.

Specs:
Viciboxserver: 1.0.0-rc2 (did I post in wrong section?)
AstguiClient: 2.05-173
Asterisk: 1.2.26.2

BTW.
When I run the GMT offset script and watch it in the cli, the first few records of the NANPA_prefix-latest.txt file goes fine then all the rest of the file GMT gets set to 0.

PostPosted: Mon Oct 12, 2009 11:08 pm
by williamconley
You posted in the right place alright, and I just wanted to say THANKS for actually posting both the Vicibox version and the Vicidial version and build!

Unfortunately, I don't have a solution for you, but I do have a suggestion: can you post the results of the script (and have you read the comment section of the script to see if you can get a debug command in there when it runs ....)?

PostPosted: Tue Oct 13, 2009 12:58 am
by gardo
The GMT of the leads should be automatically set everytime you load them. Unless the phone numbers are not in the right format. What country are the leads from?

Please post the result of "/usr/share/astguiclient/AST_VDhopper.pl --debugX".

GMT Offset

PostPosted: Tue Oct 13, 2009 7:28 am
by mstopkey
Well it looks like I got it fixed. I was running the script after initial run and skewing the numbers on existing lists. Thanks for your replies. I will keep an eye on it and if I see time zone problem again, I will sub out the fix.

Mark