We have a system in a doctors office that has a clock that seems to act up a lot. Not just a few minutes or everyday, it happens spuratically. I understand it's a 24 hr clock, it should be the same every day. The day and night times are correct, and the ..now guys get this, Kvs-200 with a 220 hard drive in it. Just a few weeks ago, the kvs-200 died dead big time. We replaced it with a stock 200 that was a failure sent back for repair. What surprised me was the fact it came back with a 220 hard drive. Anyway, I set it to PBX control in the VM time section. The customer is complaining it worked all week except Thursday morning it came on a hour early. The day time for the PBX is set to 9:45Am. Now we had them force it back into night mode then to day mode at the proper time and lunch time worked fine as well as the evening time. I am baffled or my customer has bats in the beltry. I have checked it right on the phone with the office manager. Whats going on here. Could the upgrade to the 220 from a 200 be missing the PBX control lead/signal? That's really the only thing left that I can think of.
Any help would be appreciated.....Brad _________________________________________________________________ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
