05-07-2013 12:06 PM - edited 03-16-2019 05:11 PM
Hello,
I have run across a couple instances of this - we have office users each with their own phone, extension, and voicemail box. In addition to this, all of their phones have a second extension that goes to a general voicemail box. The problem that we are having is that when a voicemail comes in through the general voicemail box, there is no indicator on the phones saying so. In our Call Manager 8.6.2.2000-2, the Visual Message Waiting Indicator Policy is currently set to Prompt Only for each of their phones.
Any feedback is appreciated, thanks.
05-07-2013 12:11 PM
Hi there,
Is the general mailbox number actually a shared line
on these phones?
Cheers!
Rob
"Talk about a dream
Try to make it real"
- Springsteen
05-07-2013 02:16 PM
Yes. Let me give an example though to make sure I understand the question. There is a general voicemail box in Unity with the extension 1234. Within the Call Manager, there is a second line on each of the office phones with the extension 1234.
05-07-2013 04:18 PM
You may need to change the policy on the shared lines to light and promtp
Device>Phone>Directory Number
(change from use system policy)
From one of Rob's great posts..
https://supportforums.cisco.com/thread/2093309
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
05-08-2013 06:20 AM
It is currently set to 'Prompt' and not 'Use System Policy'. Testing Light and Prompt did not work either.
05-08-2013 06:43 AM
Hi there,
Could be a CSS/Partition issue on the "shared" line 1234.
To test;
Go to the phone or have the user dial the MWI-On number
from the proper "shared" line button;
To find the MWI-On and MWI-Off numbers from CUCM admin;
Feature> Voicemail> Message Waiting> Find and List
Cheers!
Rob
"Talk about a dream
Try to make it real"
- Springsteen
05-08-2013 06:53 AM
The MWI on and off numbers actuate and deactuate the envelope on the shared line.
05-08-2013 08:26 AM
Hi There,
-Was it working before?
-What was the last change that you made before it stop working?
-How many servers do you have?
-Please try checking the dbreplication:
utils dbreplication runtimestate
-Is Unity running on Windows or linux? Full version?
-Please try doing a test call and leave a message, after that try collecting CallManager Traces via RTMT.
If any question let us know.
Melina J.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: