Hello,
My 3CX-system clock has a terrible problem.
I have the following configuration:
- 3CX v15.5 on debian 8.6, running in a virtual machine in Virtualbox on a Windows host.
- In the advanced parameters of 3CX, i have set the value of "TIME_NTP_SERVER" first to a time server in my domain, then to a public time server. This does not make any difference.
- in the 3CX Webconsole I can perfectly ping and do nslookup to my local time server or the public time servers. So connectivity or DNS is not the issue.
When I manually ask for 'Date' in the 3CX webconsole, it displays a date which is no less than 18 days behind.
On the other hand, today (june 29) 3CX finished a scheduled daily backup job, and sent a mail dated june 24.
All mails and call reports from 3CX feature wrong dates and times. A call report for Friday june 26 is dated june 8 and inside all calls carry the date june 8.
The activity logs in the dashboard for today are dated june 11.
Besides this timing problem, 3CX works perfectly.
This problem must have been present since installation. But so far I haven't paid much attention to it, since it does not seem to affect the main functions of the pabx.
It looks to me that 3CX or Debian is just not synching the clock.
Is there any setting that I have to adjust in Debian?
Another hypothesis of me is that the 3CX clock is synchronised just once per day, but it is lagging something in the order of 2 weeks or more per day. Depending on the moment of the day that you take a peek into 3CX, you see a date either 5 days, either 18 days behind.
Is there a possibility to reduce the synchronising interval? Since I can sync to a in-house time server, too high a sync rythm doesn't matter much.
Thanks for your help,
C@B@B
My 3CX-system clock has a terrible problem.
I have the following configuration:
- 3CX v15.5 on debian 8.6, running in a virtual machine in Virtualbox on a Windows host.
- In the advanced parameters of 3CX, i have set the value of "TIME_NTP_SERVER" first to a time server in my domain, then to a public time server. This does not make any difference.
- in the 3CX Webconsole I can perfectly ping and do nslookup to my local time server or the public time servers. So connectivity or DNS is not the issue.
When I manually ask for 'Date' in the 3CX webconsole, it displays a date which is no less than 18 days behind.
On the other hand, today (june 29) 3CX finished a scheduled daily backup job, and sent a mail dated june 24.
All mails and call reports from 3CX feature wrong dates and times. A call report for Friday june 26 is dated june 8 and inside all calls carry the date june 8.
The activity logs in the dashboard for today are dated june 11.
Besides this timing problem, 3CX works perfectly.
This problem must have been present since installation. But so far I haven't paid much attention to it, since it does not seem to affect the main functions of the pabx.
It looks to me that 3CX or Debian is just not synching the clock.
Is there any setting that I have to adjust in Debian?
Another hypothesis of me is that the 3CX clock is synchronised just once per day, but it is lagging something in the order of 2 weeks or more per day. Depending on the moment of the day that you take a peek into 3CX, you see a date either 5 days, either 18 days behind.
Is there a possibility to reduce the synchronising interval? Since I can sync to a in-house time server, too high a sync rythm doesn't matter much.
Thanks for your help,
C@B@B
