The 3CX provisioning server (3CX Professional 16.0.9) is overwriting my custom-set NTP server address with "pool.ntp.org". eek!
I had an ongoing battle with NTP about 18 months ago where many of my network devices were really flaky when NTP was set to "pool.ntp.org". "au.pool.ntp.org" wasn't any better. Sometimes they'd be in sync. Other times they would say "no time source" and read the date as 1970 post-reboot and wouldn't ever sync up. Syslogs were all over the place. It got so bad that I ended up buying a commercial solution which utilises GPS satellite (stratum 1 for sub-microsecond accuracy), and put that on the network. Since then, every device has kept perfect time, and I've been one very happy sysadmin. Problem solved. Done and done!
So, you can imagine I felt a wave of NTP-induced PTSD come over me (NTPTSD?) when I discovered that the 3CX provisioning server is forcing "pool.ntp.org" over the top of my own NTP server! Now I am not saying that the previous problem was with "pool.ntp.org". Maybe it was, maybe it wasn't. That's not the point. The point is I have invested in an expensive, reliable, highly accurate and very capable NTP server solution on my internal network which I should be able to point my base stations to and have that stick. This is very much preferred to having base stations go out unnecessarily to the Internet to sync with a handful of random servers of unknown quality (and much lower stratum), as well as putting extra load on the firewall, and generating unnecessary Internet traffic (which I prefer to use for voice media).
3CX devs - are you able to help out? I know I could remove the provisioning server address, but that just makes management of extensions more difficult - so not ideal. Thank you.
I had an ongoing battle with NTP about 18 months ago where many of my network devices were really flaky when NTP was set to "pool.ntp.org". "au.pool.ntp.org" wasn't any better. Sometimes they'd be in sync. Other times they would say "no time source" and read the date as 1970 post-reboot and wouldn't ever sync up. Syslogs were all over the place. It got so bad that I ended up buying a commercial solution which utilises GPS satellite (stratum 1 for sub-microsecond accuracy), and put that on the network. Since then, every device has kept perfect time, and I've been one very happy sysadmin. Problem solved. Done and done!
So, you can imagine I felt a wave of NTP-induced PTSD come over me (NTPTSD?) when I discovered that the 3CX provisioning server is forcing "pool.ntp.org" over the top of my own NTP server! Now I am not saying that the previous problem was with "pool.ntp.org". Maybe it was, maybe it wasn't. That's not the point. The point is I have invested in an expensive, reliable, highly accurate and very capable NTP server solution on my internal network which I should be able to point my base stations to and have that stick. This is very much preferred to having base stations go out unnecessarily to the Internet to sync with a handful of random servers of unknown quality (and much lower stratum), as well as putting extra load on the firewall, and generating unnecessary Internet traffic (which I prefer to use for voice media).
3CX devs - are you able to help out? I know I could remove the provisioning server address, but that just makes management of extensions more difficult - so not ideal. Thank you.
