Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Voicemail Ports Leaving Callback Messages 1

Status
Not open for further replies.

mhawk

Technical User
Mar 21, 2012
14
CA
At a site that is full AA on embedded, MCD 8.
I have a user who every morning comes into a voicemail light, Calls into the mailbox and there are no messages after calling the voicemail the lamp is shut off.
I have determined that this is a callback message left by the embedded voicemail ports.

I can't seem to recreate the issue with my test set. I have set the "disable message send" in the COS of the users. But i believe this is necessary in the COS for VM ports. My COS for VM Ports is basically straight out of the MICW tool.

I am able to shut the light off by putting my test set in the VM Group with a DND always COS and dialing the feature code etc.. etc.. but it comes back on every day.

I'm sure I'm missing something easy.
 
Search this forum. Has been a common issue for years. I think even the online helpfile might have a description of the problem.
Has something to do with vm appearance buttons I've I remember correctly
 
Thanks, I have done some searching but I'll dig a little deeper.
I've had my share of battles with callback messages. This is the first I've seen where they are actually left by the embedded ports and not a user hitting the key by mistake.

This user doesn't have any VM appearances or special mailboxes.
Ext 221 and mailbox 221

The only thing that makes this unique is she is that 0 is a transfer only mbx to 221.
 
I was going to ask if she is zero but I see that you've already confirmed that.

Have you checked mailbox zero to see if it has any messages?

If you do not actively support MB zero, you should make it a transfer only mailbox to prevent "Lost" calls leaving messages there.

If mailbox Zero does not have any messages, use export to view all mailboxes and find all mailboxes that have at least 1 unplayed message. From there you can see if any of those mailboxes might be associated with 221 in any shape of form.

Failing that avenue, we can pull the 3:00am logs from the VM to see what messages are being refreshed but that would be last ditch.

My bet is on MB 0

**********************************************
What's most important is that you realise ... There is no spoon.
 
As usual i believe kwbMitel is correct.
Mailbox 0 is not a transfer only (my bad) and had 1 new message.

I've now logged in, deleted the message and changed to transfer only.
I'll have to wait and see tomorrow A.M. but I'm confident it's solved.
 
Customer reports no light this morning.
Thanks again!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top