>Use the ntp.conf configuration created for you by the setup script - >someone send him a copy
Copy of what? The ntp servers are in the ntp file. > network - your firewall may need to be configured). A quick google > search will tell you how to check whether or not it is working (and/or > others here will help). Make sure that your system is configured to > always run ntpd. Remote phones have ntp.org on them and local phones had the network ntp server I had until recently. Meaning, I never used the time server on sipx and one of the very first things I do when I build a server is to put a timeset script on it to make sure it's always got the same time as other servers. Yes, the firewall allows remote ntp access which is why ntpdate could reach ntp servers. > Running ntpdate can set your clock _back_, which seriously messes up > sipXecs - it assumes that time only ever goes forward, which is also > true if the the ntp daemon is controlling your clock. I wasn't aware of the above so something new learned and perhaps once and for all fixes the strange problem. I'll keep an eye on it and see how things go. I still want to get my merge-logs and regtimes working and I'll get back on those once this is confirmed. Mike
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
