Problem Description:
During the normal use of the IP phone , it is found that the phone cannot update the server time synchronously
solution:
-
Confirm whether the customer’s network environment is an internal network or an external network. If it is in the internal network, confirm whether it is possible to log in to the external network and the location of the NTP server; in general, the NTP server is on the external network. The time cannot be updated; (the screenshot shows the NTP server address)
-
Step 1 If the problem cannot be solved after confirmation; please provide the capture file, configuration file, system log; (For specific operations, see: http://support.yealink.com/faq/faqInfo?id=360) (Note: capture NTP Change the synchronization period (15~86400s) to 15S when packing, reduce the interval time of NTP messages, so as to capture NTP data packets more easily.)
-
If the NTP information can be filtered out in the capture file, check the Peer Clock Starum in the NTP capture. If it is 0, please change this parameter setting on the server to solve the problem: (Note: Stratum: The number of layers of the system clock , The value range is 1-16, which defines the accuracy of the clock. The clock with stratum 1 has the highest accuracy, and the accuracy decreases from 1 to 16. The clock with stratum 16 is in an unsynchronized state and cannot be used as a reference Clock. If this field is 0 in the message returned by the server, it will be directly discarded by our phone as an error message, causing the time to be unable to synchronize)
-
If the NTP server is not found in the capture file;
A: Re-capture after resetting the phone;
B: If step A does not take effect; filter the DNS messages in the captured file; if it does not, it is caused by the NTP server DNS being unable to resolve normally, please confirm whether the DNS server is normal; (whether the client has set a static DNS, but no Turn on the switch to use static DNS and let the customer confirm whether this is the cause;)
C: If it still doesn't work, try to directly configure the DNS server to 114.114.114.114