MWI mysteriously appearing on Extension

[janney]

Unity Connection 8

Hello all,

I have a user who has one ext. assigned to her and does not have a voice mailbox assigned. However, on occassion the MWI will appear and remain on for an indefinite amount of time (could be a few minutes, hours, days). Then, by no action of her own, it will go out.

Again, there is no mailbox or call handler defined. What I'm thinking is that there may be an instance (alternate ext, second MWI definition) defined under another mailbox. (?) If so, would anyone know of a method to search for this without having to go into every individual mailbox in the system?

Thank you for any assistance that you may provide!

Janney

 

[MitelInMyBlood]

Do you possibly have another (legacy) phone system attached that uses inband signalling to control MWI or "Callbacks" ? If so, look on that system for a matching mailbox but no matching extension). Some of these systems (ie., Octel) have a very nice CDR logging utility that you can use to filter on specific events. Q.Sig trunks will easily pass these MWI events to interconnected systems.

During migration of approx 1700 users from our Mitel phone system over to Cisco CM, we had many MWI problems until everyone was finally transitioned.

Original MUG/NAMU Charter Member

 

[slp123]

Even without a mailbox have you tried pressing the Message button on that phone to see if you have any other prompt options. Just a thought as I had two incidents recently whereas a user A's mailbox had no new messages to cause the MWI to be stuck on however:
*The previously the user had composed a vm to SEND to B's mailbox but the recipients mailbox was full and could not be delivered. I pressed users message button and listened to all the prompts eg to listen to vm press one; fax press two; e-mail press three; OTHER press four. The UNSENT message report was in selection four. I followed the prompts to delete it and the MWI went off.

*A couple of days later another users MWI was on but no new messages. I did as above and it turned out that sender had sent a message to mailbox B and she had prompted the system to send her back a RECEIPT once the vm had been heard. Again this was in the last option; I followed prompts to delete.

 

[janney]

Found it!!! ...and thank you both for your replies and getting me on the right track. Five months ago another site was brought onto our enterprise, of which there was a conflicting extension range. I found that there was an alternate extension assigned to a mailbox which was still using the legacy number. I just removed it and it's now working beautifully. Thank you so much!