Applies to VoipNow 3 and higher! |
In some situations, reports in VoipNow display various time inconsistencies compared to the timezone of the location where VoipNow's web management interface is accessed. Although this behavior is not harmful, sometimes it can be annoying. On the other hand, VoIP calls can be affected by an incorrect timezone. This article will show you how to address this problem.
To do set the timezone on the server:
date
command. For example, if this is what you see in the interface:
Mar 14, 2016 15:45:52 UTC |
This is what you should see in shell:
[root@voip ~]# date |
To keep the time in sync with a NTP server:
Run the following commands:
|
Then sync the time using this command:
[root@voip~]# date |
Now, start the NTP server using this command:
|
The server resources may be another reason for which time is not properly synchronized. This can happen especially when virtualization is used, and the resources of one server are shared between multiple servers. This can affect audio streams also, so it's important for resources to be properly reserved. For example, CPU and memory should have the minimum VoipNow requirements reserved.
In the case of dedicated servers, providers may limit the power usage, i.e. they may use only a limited number of CPUs (e.g. 4 instead of 8), which is making the server two times slower.
For any questions, please contact Support. |
|