VM Pro is not going out of night service at 7:00am CDT. It shows as 1 hour behind on the phone displays. How do I get it to update the time? Time server is the server running VM Pro and Manager application.
you need to set the clock on the VM PC
also check the options to auto adjust for daylight savings this should be enabled.
The RTC on the IPO acts as follows
on boot the IPO looks for a NTS & asets its clock (NTS can be iether the VM or manager App, if Manager is running when VM starts vm WILL NOT act as NTS)
once the tiem is set the IPO will continue to check & reset its time at 1 hour intervals
Our 412 must not be checking time then. VM pro and Manager is running on XXX.XXX.XXX.8 and IP Office is XXX.XXX.XXX.9 and it still displays incorrect time even though the server is the correct time. Daylight savings is also correctly set.
There is another weird thing going on related to the time problem. In the morning when I called to see if VM Pro was directing the call to the Receptionist, it just anwered with hold music. At 08:00 CDT it directed the calls to the receptionist. It should have at 07:00 CDT. When I checked the previous evening to see if VM PRo night service was answering, it was. Why did night service not pick up between 07:00 and 08:00???
I have a similer time problem with an IP Office - the way I found was to take the IP Office of the network - have only the PC with Manage and voicemail on - set the time server address to the PC with the voicemail - manager on - send a reboot. Make sure the time is right before putting it back on the network.
Time settings work perfectly as long as the apps are started as specified in the manuals/help files. Have had one site though where the time would not update at all, time display on a 2050/30 phone would not tick over at all, just sat on same time, monitor would show same time, had to replace the 403
How do the I've shut down Manager app and restarted VM Pro services, then started Manager app. so that VM Pro was running before Manager and still no time change. It Is happening now in our Philadelphia office. They do not have a VM pro or Manager server there, do I need to specify the VM Pro server here as time server to get it to update their 406?
You might try checking the time zone is correct in the date and time properties on the VM PC. We had an instance where this was out - all was fine until daylight saving time came around and then we encountered the same sort of issue you describe here.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.