________________________________________ From: [email protected] [[email protected]] On Behalf Of [email protected] [[email protected]]
>?Get the sipregistrar.log from one of your failure windows and post it >?somewhere to which you can provide a URL, then post that URL here with http://www.devdoode.com/sipregistrar.log ________________________________________ Wow. The times in that log are like nothing I've ever seen before -- they're totally ******. Since people were talking about clock problems, I did a quick check: cut -c 13-17 sipregistrar.log | uniq The results were amazing: At about 1 minute after the hour (at least for the first few hours of the log), the time jumps abruptly ahead about 1 hour 10 minutes. After 5 minutes, the time jumps back to the previous timebase. This happens every hour. Since registration expirations are recorded as absolute times, every time the time jumps forward, most or all of your phone registrations will expire. (If the registrations don't happen to get erased from the database, when the time jumps back, they might become valid again!) "grep ntpd /var/log/messages" will probably reveal something. In the long run, you need to get a better timebase source than whatever you're using now. In the short run, it will suffice to simply disable NTP -- the various logs might have incorrect times, but that doesn't interfere with making calls, etc. Until your timebase is stable, I can *guarantee* that you will have problems with registrations. Dale _______________________________________________ sipx-users mailing list [email protected] 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/
