/
Switchvox - System clock suddenly stops keeping the correct time when using NTP fetching

Switchvox - System clock suddenly stops keeping the correct time when using NTP fetching

This guide only covers automatic NTP time fetching issues, if you have set the time manually and you are having problems then you need to follow this guide: Switchvox - Why is my manual time drifting?
 

  1. First you will need to be logged on to the Switchvox as an administrator. Then, navigate to Server-System Clock. Make sure that your system is set for the correct time zone and that the set method is using NTP time fetching.

    1. By default, the NTP server is set to 0.digium.pool.ntp.org, which is Sangoma’s NTP server. If the time zone is wrong or the NTP server address is wrong, you may want to change the settings before troubleshooting any further. Remember, if you make a change and click the Save System Clock button, the network will restart and any current calls on the system will be dropped! 

  2. If your system clock settings are correct and you are still having time issues then you will need to check your IP configuration and make sure that your DNS address is correct. You can find this information under Server-IP Configuration. 

    1. If you think you may be having an issue with DNS, then you can use a public DNS server address in place of your current DNS address. You can use 4.2.2.2, 8.8.8.8, 8.8.4.4, for testing or any other valid public DNS address that you have. Be careful,saving the IP configuration page will also reset the network and drop any current calls!​

  3. Another solution is to use a different NTP server address. You can find public NTP servers for testing on the NTP pool projects website, http://www.pool.ntp.org/zone/north-america . You can also use the IP address of the NTP server, instead of a fully qualified domain name. 

    1. You can use the dig command on Linux systems, and the nslookup command on windows systems to find the IP address of a domain name. On either operating system, you will run the command from the command line followed by the domain name. (Example: nslookup 0.digium.pool.ntp.org)

  4. If all else fails, check your network and firewall settings for possible causes.

 

Return to Documentation Home | Sangoma Support