hosted Posted July 25, 2007 Report Share Posted July 25, 2007 why does the date reset on reboot? is there no battery on board? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 26, 2007 Report Share Posted July 26, 2007 No battery included. Because it is a network device, IMHO it is okay to use NTP to fetch the latest time. Quote Link to comment Share on other sites More sharing options...
hosted Posted July 26, 2007 Author Report Share Posted July 26, 2007 No battery included. Because it is a network device, IMHO it is okay to use NTP to fetch the latest time. ntpdate is not installed in the image. because of this the system starts at 1970 Jan1 00:00 which means you MUST ssh into the box to set the date or your day/night tables will never work properly! you should have a set time on the IP page or something.. and have ntpdate run upon boot. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 26, 2007 Report Share Posted July 26, 2007 The PBX has a built-in NTP client that calculates the current time. Running NTP while the PBX is running screws up all internal callbacks, so if you must run ntpdate do it on startup, but then not again. Complain to the authors of the pthread library, they don't wait for the CPU time, they wait for the "real" time. Quote Link to comment Share on other sites More sharing options...
hosted Posted July 27, 2007 Author Report Share Posted July 27, 2007 The PBX has a built-in NTP client that calculates the current time. Running NTP while the PBX is running screws up all internal callbacks, so if you must run ntpdate do it on startup, but then not again. Complain to the authors of the pthread library, they don't wait for the CPU time, they wait for the "real" time. so your saying that sense it says 1970 pbxnsip has its own ntp time and it doesnt matter? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 27, 2007 Report Share Posted July 27, 2007 Yes, isn't that cool? But in the next version we will set the time right after startup, so that the file system has more realistic timestamps. Quote Link to comment Share on other sites More sharing options...
hosted Posted August 1, 2007 Author Report Share Posted August 1, 2007 I can not get the service flag to work. I do 8:00-5:00P and it says SET.. when it should be CLEAR Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 1, 2007 Report Share Posted August 1, 2007 Check what the log uses for time stamps. Then you can see what the PBX thinks the time is. Quote Link to comment Share on other sites More sharing options...
hosted Posted August 1, 2007 Author Report Share Posted August 1, 2007 Check what the log uses for time stamps. Then you can see what the PBX thinks the time is. pbxnsip - 2007/08/01 04:02:43 real - 2007/08/01 17:02:00 Quote Link to comment Share on other sites More sharing options...
hosted Posted August 1, 2007 Author Report Share Posted August 1, 2007 pbxnsip - 2007/08/01 04:02:43 real - 2007/08/01 17:02:00 Cool if i set the timezone to China its only 1 hour fast... Quote Link to comment Share on other sites More sharing options...
hosted Posted August 2, 2007 Author Report Share Posted August 2, 2007 Cool if i set the timezone to China its only 1 hour fast... how do i fix? Quote Link to comment Share on other sites More sharing options...
hosted Posted August 8, 2007 Author Report Share Posted August 8, 2007 im dying here. hate pissy customers! how can i fix this? PC date is: 04:19 UTC pbxnsip date: 19:05 REAL date: 18:05 however the Service Flag clear time = 05:05 I narrowed down the service flag time but elimination. now check this out. I update the time zone and the log time dates... BUT the service flag is still 5:05. now i updated the time in linux.. and the service zone says its now saturday sometime between 00:00 and 01:00 restart pbxnsip.. service flag is now on the right day between 5-6AM But hey this works: 00:00-5:00 16:00-23:59 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 8, 2007 Report Share Posted August 8, 2007 Well the service flag is "set" when it is "night"... Does the ntpdate work? Make sure that you call if before the PBX gets started - otherwise the NTP in the PBX will interfere with the NTP on the OS level. Quote Link to comment Share on other sites More sharing options...
hosted Posted August 8, 2007 Author Report Share Posted August 8, 2007 wow that actually did something cool. ok so i installed ntpdate, shutdown pbxnsip, ran ntpdate which updated correctly, then started pbxnsip. and the service flag and the log time is in sync! BUT my software is still set to China/Taiwan which makes the service flag/log time only 1 hour off. If I set it to MST then its waaaaaaaaaa off. am i really the only person having this problem with the CS410? I would think most companies used day/night mode. Quote Link to comment Share on other sites More sharing options...
hosted Posted August 9, 2007 Author Report Share Posted August 9, 2007 seems like the clock skew 18seconds per hour. dunno if this matters to the internal ntp client in pbxnsip. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 9, 2007 Report Share Posted August 9, 2007 Whow. That is quite a lot. it would be 18/3600 = 5 per mille. Even receiving Ethernet packets would be difficult if it is drifting that much. Quote Link to comment Share on other sites More sharing options...
hosted Posted August 9, 2007 Author Report Share Posted August 9, 2007 so what about the time, how do it fix it so its in the proper time zone? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 10, 2007 Report Share Posted August 10, 2007 The way to go is: When the PBX starts up, call ntpdate to get the PBX into a reasonable time zone. For this step, ntpdate must be on the box and the startup script must be adjusted.Then the PBX will perform a internal NTP date lookup every hour to adjust the differences to the hardware clock in the PBX. For this step we must make sure that the setting ntp_server in the PBX is set properly. We will include that in the next software patch for the appliance. Quote Link to comment Share on other sites More sharing options...
hosted Posted August 17, 2007 Author Report Share Posted August 17, 2007 why is it the log is showing me 19:00 but the service clock is thinking its 07:00 (12 hours off) Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 17, 2007 Report Share Posted August 17, 2007 If you like, please try http://www.pbxnsip.com/cs410/update-2084.tgz. This tarball includes the ntpclient and also makes sure that it is called after startup. Other things it does is AGC on the FXO side, which should improve the audio quality and reduce problems with echo. To load that image, just follow the steps in http://wiki.pbxnsip.com/index.php/Applianc...the_PBX_version. Quote Link to comment Share on other sites More sharing options...
hosted Posted August 18, 2007 Author Report Share Posted August 18, 2007 fixed! thanks a TON! Quote Link to comment Share on other sites More sharing options...
hosted Posted August 21, 2007 Author Report Share Posted August 21, 2007 ok so it froze up once so far. today the service time went out of sync and the night message kicked in I rebooted it and it was fine. could it be that i have a faulty box? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 21, 2007 Report Share Posted August 21, 2007 Any change to use SNMP to monitor the uptime of the box? Quote Link to comment Share on other sites More sharing options...
hosted Posted August 23, 2007 Author Report Share Posted August 23, 2007 I installed nagios to ping it every so often. it hasnt crashed again. But today the service flag timer is wacked again. so it lasted 2 days.. seems to be a pattern. Suppose i could cron reboot it every night :/ Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 23, 2007 Report Share Posted August 23, 2007 Ping tells you that the OS is still alive. SNMP tells you that the application is still alive. Rebooting is not an attractive option. Maybe you are suffering from the memory leak in the head branch (2.1 beta), we are trying to isolate it. Check from time to time how much memory it allocated. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.