atcomsystems.ca/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems Partner Mail VS 5 can't play messages

Partner ACS R6
Partner Mail VS R5

All MB's can play messages fine except MB 13. Even MB 13 was working fine before the weekend. Now when pressing 0 to play the message (only in MB 13), the system says "transferring to operator" and extension 0 rings as though you were not even in the VM system. Same symptoms when checking from an extension or from remote using *7.

Any ideas short of deleting and recreating the mailbox? Just hate to lose the messages that she didn't yet retrieve. I already cycled the power on the system of course.

try this

press *3 and see if it says message deleted ... it may just be a message in the mailbox

can they log into 13?

After you press 2 to get messages and then press 0 if there is no messages then it will say trans to operator. Are you sure there are messages? Because if there isn't that's exactly what it's going to do.

Well, OK. Let's go through this a step at a time.

1) Is the message light on on x13?
2) Are you sure it actually is x13?
3) Are you able to log into the x13 mail box? Just to be sure that it is really x13 press # instead of the extension number AT THAT EXTENSION when logging in.
4) Does it say that you have messages after logging in before you press 2?

-Hal

Mail box message lights can sometimes be turned on by accident ( Feature 0913) just dial Feature 1013 to clear it.

Thanks, upstateny, it was in fact a corrupt message in the mailbox. Simple things first I guess, but I wasn't in the mindset to just delete that first message because it was new. Good catch though, as it saved the other messages from being wiped with a re-initialize and now she will get 1 frustrated call back instead of 13.

Just for reference on the other questions. Yes, there were 13 new messages in mailbox 13 (intercom 777, 13#, pwd from any extension or *7, etc remotely) and the concern was not with the message light as we knew there were new messages in the mailbox. Deleting the first message in the box fixed the problem so we have to assume that the first message was corrupt. Thanks for all the replies!

Good deal, glad you got it, we were just covering all the basis

the message wasn't corrupt .... someone hung up and that was recorded as the message before the line disconnected

so it was not an equipment issue .. just something that happens once in a while when a caller hangs up