Chronicall is Logging Calls in the Wrong Time Zone

Issue

Chronicall is logging calls from a different time zone then it should. Is there a way to fix this? 

Solution 1

Adjust the OS timezone

1. Check the time zone of the server and adjust it to the correct time zone. On Linux servers, you can run the following commands:

   • date

   • hwclock

     • These commands check the software and hardware clocks of the Linux server.
     • If these are both correct, but Chronicall is still showing the wrong time, move onto Solution 2 or 3 depending on the version

Solution 2

Adjust Chronicall Timezone (Chronicall 4.0.10 and above)

1. Navigate to Admin (System) > System Settings > Advanced Settings
2. Find the "Server Timezone" option and click on the ellipsis
   
   
   
   
3. Select the timezone you wish Chronicall to use
   
   
   
   
4. Click "OK" and then click "Save"
5. Relaunch Chronicall Desktop to see changes in Cradle to Grave

Solution 3

Edit Java's timezone (Chronicall's older than 4.0.10)

If Chronicall was installed in a certain time zone, the embedded Java's time zone may stay the same even after the server's time zone has changed.

1. To resolve this, we need to add an argument to the ChronicallServer.cfg. 
   •  Windows
     •  32-Bit
       • C:\Program Files (x86)\Xima Software\Chronicall\bin\app\ChronicallServer.cfg
     •  64-Bit
       • C:\Program Files\Chronicall\bin\app
   •  Linux
     • /var/lib/Xima Software/Chronicall/bin/app/ChronicallServer.cfg
     • /var/lib/Chronicall/bin/app/ChronicallServer.cfg
2. Edit this file, and under the "JVMOptions" section, add

   • -Duser.timezone=America/Chicago

   • Depending on the time zone the server is in, the listed city will change. Eastern is New_York, Central is Chicago, Mountain is Denver, and Pacific is Los_Angeles.