Bobby Dole wrote: >My problem is more that the VM isn't lighting the >light on these extensions. So would this be a TVS or a >KXTD problem? > > MW is a basic extension feature of the kxtd, that cannot be disabled. It allows up to 10 mw's be stored per extension. MW's are set by another extension calling and pressing the message button. MW's can only be cleared by the messaged extension: 1. calling the extension that "set" the message AND being answered, 2. dialing the 700+[self ext #], or 3. dialing the extension all feature clear code.
MWs are not deleted by disconnecting the extension, or even system reset or power down. System initialization will delete them, as well as ALL programming. The tvs uses the kxtd feature by dialing 701+ext# to set the MW after it takes a message. That extension message button will light until the button is pressed, returning a call to the VM port. When the vm port answers, the MW is deleted and the button goes out. What goes wrong: Extension 200 calls ext 100 and presses message while 100 is still ringing (and 100 never answers) 100 now has a mw from 200 Later a vm arrives for 100, the vm sets a mw for 100. Owner of 100 shows up and sees message light. Presses button, rings but never answers. He is actually ringing 200 that left the OLDEST mw. He doesn't realize there is another mw stored, from the vm. The oldest mw (first displayed) stays there until it gets an answer or is cleared. A display phone can show this by pressing message while ON HOOK, successive presses will display each stored mw. The solution: 1. use the 700+# to clear all stored mw's 2. break fingers of person pushing message when calling another extension. That's as clear as i can make it. it happens, and folks forget why and how to fix it. -l _________________________________________________________________ KX-T Mailing list --- http://kxthelp.com/ Subscription changes: http://kxthelp.com/mailman/listinfo/kxt
