vicidial.org

Hi,

I am using VICIDIALNOW 2.0.5, date time on linux shell is perfect. On agent dialing screen time is one hour ahead. In customer time field during LIVE CALL time is 6 hours ahead. In my Server setting Local GMT: is set to 1.0 as I am in UK. When I end the call, date and time stored in the vicidial_list table is 100% correct in both fields (modify_date and last_local_call_time). Any idea? I have already set my datetime at linux shell.

Best regards,

Are you in british summer time right now?

is your normal GMT offset +1?

have you checked the servers and phones gmt offset settings within ViciDial?

Hi Mflorell,

Thanks for your reply. Yes I am GMT+1.0 (due to day light saving). I already changed server GMT offset to 0.0 but my phone offset was -5.0. I changed phone offset to 0.0, after this on agent screen time is still one hour ahead and Customer Time: is now 2 hour ahead. I changed offset to 1.0 in both server and phone. There is no change on agent screen time but Customer Time: is 1 hour ahead. Then I changed server offset back to 0.0 and phone offset to 2.0. Again no change on agent screen time but this time Customer Time: is correct. With all these changes there is no change into vicidial_list table record update (Table entries are 100% correct, even before and after change). Any idea what to do to get all these time same?

Best regards,

Are your leads set to use 44 as the dial_code? If not, then they will not be automatically adjusted to the proper gmt_offset_now.

Hi Mflorell,

Yes, I am using 44 as dial code.

Best regards,

What is the server time zone scheme set to?

What are the gmt_offset_now of the leads?

Hi Mflorell,

My Server GMT Offset is 1.0 and gmt_offset_now of the leads is +1.0

Best regards,

You are not supposed to adjust for DST(or BST) when you set the server timezone and phone timezone. Those should be set to 0.00

Hi Mflorell,

I changed my server and phone time offset to 0.0. My Leads GMT OFFSET NOW (local time). Still time on Agent Screen is One hour ahead and Customer Time is two hour ahead. My local system date and time on shell is Wed May 27 11:54:06 GMT 2009, which is 100% correct.

Best regards,

Hi got the same problem how do you correct it..have you found resolutions on this..?

Please post the output of the following command after resettinging the hopper on one of your active campaigns:

/usr/share/astguiclient/AST_VDhopper.pl --debugX

----- DEBUG -----


----- SUPER DEBUG -----

TIME DEBUG: 0.00|0.00|0| GMT: 13:06
SELECT * FROM vicidial_lists where active='N';Inactive Lists: 3
Inactive List Leads Deleted: 0E0 |DELETE from vicidial_hopper where list_id IN('999','998','101');|
CALLBACK HOLD: 0|SELECT count(*) FROM vicidial_callbacks where callback_time <= '2009-05-28 13:06:46' and status='ACTIVE';|
CAMPAIGNS TO PROCESSES HOPPER FOR: 1|0

|GMT-DAY-HOUR| |13.00-5-206||12.75-5-151||12.50-5-136||12.25-5-121||12.00-5-106||11.75-5-51||11.50-5-36||11.25-5-21||11.00-5-6||10.75-4-2351||10.50-4-2336||10.25-4-2321||10.00-4-2306||9.75-4-2251||9.50-4-2236||9.25-4-2221||9.00-4-2206||8.75-4-2151||8.50-4-2136||8.25-4-2121||8.00-4-2106||7.75-4-2051||7.50-4-2036||7.25-4-2021||7.00-4-2006||6.75-4-1951||6.50-4-1936||6.25-4-1921||6.00-4-1906||5.75-4-1851||5.50-4-1836||5.25-4-1821||5.00-4-1806||4.75-4-1751||4.50-4-1736||4.25-4-1721||4.00-4-1706||3.75-4-1651||3.50-4-1636||3.25-4-1621||3.00-4-1606||2.75-4-1551||2.50-4-1536||2.25-4-1521||2.00-4-1506||1.75-4-1451||1.50-4-1436||1.25-4-1421||1.00-4-1406||0.75-4-1351||0.50-4-1336||0.25-4-1321||0.00-4-1306||-0.25-4-1251||-0.50-4-1236||-0.75-4-1221||-1.00-4-1206||-1.25-4-1151||-1.50-4-1136||-1.75-4-1121||-2.00-4-1106||-2.25-4-1051||-2.50-4-1036||-2.75-4-1021||-3.00-4-1006||-3.25-4-951||-3.50-4-936||-3.75-4-921||-4.00-4-906||-4.25-4-851||-4.50-4-836||-4.75-4-821||-5.00-4-806||-5.25-4-751||-5.50-4-736||-5.75-4-721||-6.00-4-706||-6.25-4-651||-6.50-4-636||-6.75-4-621||-7.00-4-606||-7.25-4-551||-7.50-4-536||-7.75-4-521||-8.00-4-506||-8.25-4-451||-8.50-4-436||-8.75-4-421||-9.00-4-406||-9.25-4-351||-9.50-4-336||-9.75-4-321||-10.00-4-306||-10.25-4-251||-10.50-4-236||-10.75-4-221||-11.00-4-206||-11.25-4-151||-11.50-4-136||-11.75-4-121||-12.00-4-106||-12.25-4-51||-12.50-4-36||-12.75-4-21|
|SELECT * FROM vicidial_call_times where call_time_id='24hours';|
LocalCallTime No-Call Gap: |0|2400(24 00)|0000(00 00)|4|3|
Starting hopper run for TESTCAMP campaign- GMT: 24hours HOPPER: 100 ORDER: DOWN
hopper DONE cleared: 0E0
|DELETE from vicidial_hopper where campaign_id='TESTCAMP' and status IN('DONE');|
hopper GMT BAD cleared: 0E0
|DELETE from vicidial_hopper where campaign_id='TESTCAMP' and ((gmt_offset_now IN('99') ) );|
hopper READY count: 45
|SELECT count(*) from vicidial_hopper where campaign_id='TESTCAMP' and status='READY';|
hopper too low (45|100) starting hopper dump
campaign lists count: 1 | '111'
|SELECT list_id FROM vicidial_lists where campaign_id='TESTCAMP' and active='Y';|
no lead filter defined for campaign: TESTCAMP
|NONE|
|SELECT count(*) FROM vicidial_list where called_since_last_reset='N' and status IN('NEW') and list_id IN('111') and ((gmt_offset_now IN('13.00','12.75','12.50','12.25','12.00','11.75','11.50','11.25','11.00','10.75','10.50','10.25','10.00','9.75','9.50','9.25','9.00','8.75','8.50','8.25','8.00','7.75','7.50','7.25','7.00','6.75','6.50','6.25','6.00','5.75','5.50','5.25','5.00','4.75','4.50','4.25','4.00','3.75','3.50','3.25','3.00','2.75','2.50','2.25','2.00','1.75','1.50','1.25','1.00','0.75','0.50','0.25','0.00','-0.25','-0.50','-0.75','-1.00','-1.25','-1.50','-1.75','-2.00','-2.25','-2.50','-2.75','-3.00','-3.25','-3.50','-3.75','-4.00','-4.25','-4.50','-4.75','-5.00','-5.25','-5.50','-5.75','-6.00','-6.25','-6.50','-6.75','-7.00','-7.25','-7.50','-7.75','-8.00','-8.25','-8.50','-8.75','-9.00','-9.25','-9.50','-9.75','-10.00','-10.25','-10.50','-10.75','-11.00','-11.25','-11.50','-11.75','-12.00','-12.25','-12.50','-12.75','99') ) ) ;|
leads to call count: 45
|SELECT count(*) FROM vicidial_list where called_since_last_reset='N' and status IN('NEW') and list_id IN('111') and ((gmt_offset_now IN('13.00','12.75','12.50','12.25','12.00','11.75','11.50','11.25','11.00','10.75','10.50','10.25','10.00','9.75','9.50','9.25','9.00','8.75','8.50','8.25','8.00','7.75','7.50','7.25','7.00','6.75','6.50','6.25','6.00','5.75','5.50','5.25','5.00','4.75','4.50','4.25','4.00','3.75','3.50','3.25','3.00','2.75','2.50','2.25','2.00','1.75','1.50','1.25','1.00','0.75','0.50','0.25','0.00','-0.25','-0.50','-0.75','-1.00','-1.25','-1.50','-1.75','-2.00','-2.25','-2.50','-2.75','-3.00','-3.25','-3.50','-3.75','-4.00','-4.25','-4.50','-4.75','-5.00','-5.25','-5.50','-5.75','-6.00','-6.25','-6.50','-6.75','-7.00','-7.25','-7.50','-7.75','-8.00','-8.25','-8.50','-8.75','-9.00','-9.25','-9.50','-9.75','-10.00','-10.25','-10.50','-10.75','-11.00','-11.25','-11.50','-11.75','-12.00','-12.25','-12.50','-12.75','99') ) ) ;|
NO SHUFFLE-NEW-LEADS INTO HOPPER DEFINED FOR LEAD ORDER
Getting Leads to add to hopper
|SELECT lead_id FROM vicidial_hopper where campaign_id='TESTCAMP';|
NO RECYCLE-LEADS INTO HOPPER DEFINED
lead call order: order by lead_id asc
|SELECT lead_id,list_id,gmt_offset_now,phone_number,state,status,modify_date,user FROM vicidial_list where called_since_last_reset='N' and status IN('NEW') and list_id IN('111') and lead_id NOT IN('97','96','95','94','93','92','91','90','89','88','87','86','85','84','83','82','81','80','79','78','77','76','75','74','73','72','71','70','69','68','67','66','65','64','63','62','61','60','59','58','57','56','55','53','54','0') and ((gmt_offset_now IN('13.00','12.75','12.50','12.25','12.00','11.75','11.50','11.25','11.00','10.75','10.50','10.25','10.00','9.75','9.50','9.25','9.00','8.75','8.50','8.25','8.00','7.75','7.50','7.25','7.00','6.75','6.50','6.25','6.00','5.75','5.50','5.25','5.00','4.75','4.50','4.25','4.00','3.75','3.50','3.25','3.00','2.75','2.50','2.25','2.00','1.75','1.50','1.25','1.00','0.75','0.50','0.25','0.00','-0.25','-0.50','-0.75','-1.00','-1.25','-1.50','-1.75','-2.00','-2.25','-2.50','-2.75','-3.00','-3.25','-3.50','-3.75','-4.00','-4.25','-4.50','-4.75','-5.00','-5.25','-5.50','-5.75','-6.00','-6.25','-6.50','-6.75','-7.00','-7.25','-7.50','-7.75','-8.00','-8.25','-8.50','-8.75','-9.00','-9.25','-9.50','-9.75','-10.00','-10.25','-10.50','-10.75','-11.00','-11.25','-11.50','-11.75','-12.00','-12.25','-12.50','-12.75','99') ) ) order by lead_id asc limit 100;|
Adding to hopper: 0
DONE with this campaign
DONE. Script execution time in seconds: 0

Your server is not set to DST according to this output. What linux timezone settings exactly are you using?

Linux timezone settings are GMT

Hello,

I have a similar problem. My system settings, phone settings and server all have Local GMT set to +1 which is appropriate for Nigeria. However upon receipt of an inbound call the Customer time (on the agent screen) is always 6 hours behind local time and in the default inbound list the gmt_offset_now value for the lead is set to -5.00. I do not understand why this happens.

I have run this script (/usr/share/astguiclient/ADMIN_adjust_GMTnow_on_leads.pl) to update the gmt_offset on the leads in the list and this updates fine. But when i try a new call the gmt_offset_now value reverts to -5.00

Kindly help

Regards

Ore

Vicibox 7
VERSION: 2.12-556a
BUILD: 160514-1437

What do you have the phone_code field set to on those leads?

Being an inbound list the lead entries are only entered after an inbound call. I specified the in-group phone code (under DID) as 234. And this is recorded appropriately in the list for every lead
here's a link to a recently exported list

The previous leads had their gmt_offset_now set to +1 after i ran the above script but subsequent calls still show -5.00

https://drive.google.com/open?id=0B2Vjq ... kkxRVJfcm8

It's got to be a configuration issue somewhere then.

oreb wrote: ...My system settings, phone settings and server all have Local GMT set to +1 ...

Please specify all these settings. Precisely. Given the odds, you are missing one or two.

those were 3 specific locations (Admin>Phones>my phone, Admin>System Settings, Admin>Server>My server)

I've gone over it, again and again to make sure, hence my bringing it here.

I've attached screenshots of these pages hopefully they can help shed some light on this.

https://drive.google.com/folderview?id= ... sp=sharing

Those are the Vicidial gui settings. What about the rest? How do you suppose mysql and the web server get the time zone information?

The Gui is all I've accessed as this is a fresh install of Vicidial I'm preparing for a client. This anomaly is absent on outbound calls. I also checked a previous installation and noticed the same thing.

If you could share what other details/configs I would need to provide to facilitate a fix. I'll do my best to provide.

Thanks

i had same problem ide set all settings in vicidial/admin section but i still had time date was rong it wasent until i did this then i got a fix that worked

Phase 1.5 – Configure Time Zone
Recommended
1.
If not already, login as the root user by typing 'root' at the login prompt and 'vicidial' at the
password prompt.
If you changed the root password, or someone else has, you will need it to
login. The password can not be recovered easily and requires offline intervention.
2.
Type 'yast timezone' to enter the time zone configuration screen
3.
Type ALT-R to move to the region selection window.
4.
Using the up and down arrow keys, select the appropriate region for this server's location.
5.
Type ALT-Z or press TAB to move to the Time Zone window
6.
Using the up and down arrow keys, select the appropriate time zone for this server's location.
7.
Type ALT-O when finished to accept the configured region and time zone for this server

the above methord was noted in http://download.vicidial.com/iso/vicibo ... nstall.pdf

but what was not menchend was this once you do yast timezone
then do tab butten to move to the advance part bottom right and ither set time date manually or setup the NTP server address as the defalt one dont work
then do reboot and you should be all good
best regards

I would be willing to bet that you used the console to set the OS time zone (Thus you DID set the OS time zone ... to something) and of course the system time itself.

php.ini has a setting for time zone as well.

Then there's time zone for each lead which depends upon several factors to set the TZ during creation of the lead. This data set is provided for US phone numbers, but I'm not sure how accurate (if at all) the system will be for NonUS time zones without adding more data for other countries.

ya ither right on the termanal or thue putty over ssh login then run yast timezone right in the command line

Please set "Local GMT" in Administrator -> "Phones", "Servers" & "System Settings" to 0.00 & relogin in agent screen. The customer time will show same as the server hardware time.
Also if the agent page time is wrong, then please enable the timezone in /etc/php.ini & set the timezone accordingly. It should work after the changes.

Hi my server time and date are ok but on the admin panel it is shown 6 hours behind.
can you please give me some help

i RESOLVED THIS ISSUE VERY EASY,

IT DEPENDS HOW THE SERVER IS SETUP ON THE INSTALLATION
IF IT IS SETUP WITH A WRONG TIMEZONE IT WILL ALWAYS KEEP IT WRONG EVEN IF YOU CHANGE BY COMMANDS ON PUTTY
THE ONLY SOLUTION IS TO CHANGE IT ON THE SERVER FILES WERE YOU CAN FIND THE TIME ZONE DELETE IT AND PUTT IT RIGHT

ERVINSULA wrote:i RESOLVED THIS ISSUE VERY EASY,

IT DEPENDS HOW THE SERVER IS SETUP ON THE INSTALLATION
IF IT IS SETUP WITH A WRONG TIMEZONE IT WILL ALWAYS KEEP IT WRONG EVEN IF YOU CHANGE BY COMMANDS ON PUTTY
THE ONLY SOLUTION IS TO CHANGE IT ON THE SERVER FILES WERE YOU CAN FIND THE TIME ZONE DELETE IT AND PUTT IT RIGHT

where can i find it? i mean the file to delete?
can you pls provide me with the command

i have this version ViciBox v.8.1.2 181002 i have installed it from the iso provided on vicibox.org not from scratch

i have traied this ntpdate -u 0.europe.pool.ntp.org it works for the mom but as soon as i reboot the server it shows the server 6 hours early that it is in Realtime
even in yast timezone the zone is correct but it shows dhe wrong time

can you pls help me


thnx in advance

If setting the time works, but the server loses time when it reboots, you likely need to swap out your CMOS battery. That's the purpose of the battery: Keeping the clock accurate during off-time. CMOS batteries usually cost about a quarter (and are about the size and shape of a nickel). Easy to swap. Directly on the motherboard. Look for something that appears to be a nicked kept in place with a tiny wire. Push the wire out of the way and the battery should "pop up". Put the replacement battery in with the same side up as the one you took out.

You will likely also need to set the "hardware clock" after you do this, which can be set from the running OS clock after you get the OS set to the right time. For Vicibox 7 & 8:

Code: Select all

hwclock --show
service ntpd stop
ntpdate time2.google.com
hwclock -w --localtime --debug
hwclock --show
date
service ntpd start
sleep 20
ntpq -p

Alternately, you can set the date every time you reboot as part of your startup routine.

williamconley wrote:If setting the time works, but the server loses time when it reboots, you likely need to swap out your CMOS battery. That's the purpose of the battery: Keeping the clock accurate during off-time. CMOS batteries usually cost about a quarter (and are about the size and shape of a nickel). Easy to swap. Directly on the motherboard. Look for something that appears to be a nicked kept in place with a tiny wire. Push the wire out of the way and the battery should "pop up". Put the replacement battery in with the same side up as the one you took out.

You will likely also need to set the "hardware clock" after you do this, which can be set from the running OS clock after you get the OS set to the right time. For Vicibox 7 & 8:

Code: Select all

hwclock --show
service ntpd stop
ntpdate time2.google.com
hwclock -w --localtime --debug
hwclock --show
date
service ntpd start
sleep 20
ntpq -p

Alternately, you can set the date every time you reboot as part of your startup routine.

Hi there

i don't think it is a problem with the CMOS batterie because if it were so the date and time would be something like 01.01.2000 but it only goes 7 hours earlier
for example if where i live the exact time is 22:30 after the reboot the server time is 15:30 .

any idea

Verify your system and php.ini files are both set to the correct time zone. post your settings for both. Consider using the previously supplies "hardware setting" commands. It may be that the hardware clock is just "way off" and the ntp system will not correct it because it's so far off.

Also post the ntpq -p output from before you resolve the issue in the morning.

And of course, as a duct tape solution, put whatever lines of code you run to fix it in your startup routine. Then this will be an "interesting oddity" your system used to have and you can fix it at your leisure.