Time and Date not Synchronizing with 3CX

[gregory.b]

Dear Support,

I would like to know if there is a way to help me with a strange issue.

We have a 3CX at a Client Site installed on a Mini PC, with Over 50 Phone Set installed Model Yealink T31P, T30P and T43U.
Hence we are having issue as soon as the Phone is unplug from the Network and plugged back in it seems to lose it's time and date.
As the Phone date the Configuration for the User Well. Only Date and Date not Synchronized.


As additional Information, we are From Mauritius Island.
Hence our time zone is +4
And as shown below the Time good.




I will like to know if anyone has encountered such issue and was able to solved it.
To temporarily resolved it we've entered the Phone Web Page and modify it Manually.
Setting it in DHCP, with Proper Time Zone, We Disable Daylight Saving Mode. We even tried Manual Time but as soon as the Phone is unplug from POE point and Plugged back it seems to lose its Date and Time.


Is there any way to permanently resolved this ?

Note that we are already to Version 20.

The NTP on the Main Network also gives the Proper Time.
We even tried to Set the Ntp Pool to the IP of 3CX Server, Issues persisted.
Please Advise

 

[gregory.b]

Here are Additional Info I just saw this



Why is my Default set to china as we did set it as +4 Russia ?
As Yesterday we even saw that it now has Mauritius in it's Time Zone : +4 Port Louis

 

[OlegR_3CX]

Hi there.
Your phone will get the time from the global pool.ntp.org and not from the 3CX system directly.
Can you ensure that when a phone is making requests, it is able to get the time?

 

[gregory.b]

Hi there.
Your phone will get the time from the global pool.ntp.org and not from the 3CX system directly.
Can you ensure that when a phone is making requests, it is able to get the time?

How can i check that please ?

 

[OlegR_3CX]

Hi there.
Do the capture on the phone directly and see if it gets any reply from your ntp server.

 

[circle]

We experanced a similar thing recently and after a bit of research is seems that recent Yealink firmware update switched to using DCHP Options 100 & 101 to set the handset time. I think I just had to set option 101 to solve the issue.