01-13-2009 09:00 AM - edited 03-18-2019 10:17 PM
Hi,
I have Cisco Call Manager 4.2 and Cisco Unity connection 1.2. Voicemail is configured properly and I can leave messages and manage the voicemail inbox normally but I cant get the the message waiting indicator working.
Any manual or help to see what I am doing wrong?
Thanks in advance for you help
Luis
01-13-2009 11:08 AM
Hi Luis,
Here are a couple of related docs for MWI. Also, make sure that at least some of your Ports are set for MWI,OUTDIAL etc.
Step 1 In Cisco Unified CallManager Administration, click Feature > Voice Mail > Message Waiting.
Step 2 On the Find and List Message Waiting Numbers page, click Add a New Message Waiting Number.
Step 3 On the Message Waiting Configuration page, enter the following settings for turning MWIs on.
Settings for Turning MWIs On
Message Waiting Number
Enter the unique extension that turns MWIs on.
Description
Enter DN to turn MWIs on or another description.
Message Waiting Indicator
Click On.
Partition
Click the name of the partition that you set up for the voice mail pilot number. For example, click "VMPilotNumberPT."
Calling Search Space
Click a calling search space that is used by user phones.
Step 4 Click Insert.
Step 5 Click Add a New Message Waiting Number.
Step 6 Enter the following settings for turning MWIs off.
Settings for Turning MWIs Off
Message Waiting Number
Enter the unique extension that turns MWIs off.
Description
Enter DN to turn MWIs off or another description.
Message Waiting Indicator
Click Off.
Partition
Click the name of the partition that you set up for the voice mail pilot number. For example, click "VMPilotNumberPT."
Calling Search Space
Click a calling search space that is used by user phones.
Step 7 Click Insert.
Integration with Cisco Unified Communications Manager
Log on to Cisco Unity Connection Administration.
Settings for the Set Up Port Group Page
MWI On Extension
Enter the extension that you specified in Cisco Unified CallManager Administration for turning MWIs on.
MWI Off Extension
Enter the extension that you specified in Cisco Unified CallManager Administration for turning MWIs off.
Hope this helps!
Rob
01-19-2009 04:03 AM
Hi Rob,
Thanks a lot for your replay. The information's been very helpful and now its working perfect.
Just one quick question. How many extensions can I add in Cisco Unity for MWI? I have 2 extensions (2 for MWI on and 2 for MWI off). Is there a limit for this?
Thanks again
01-19-2009 05:26 AM
Hi Luis,
You are most welcome! There is no hard limit for the number of MWI Ports.
Some of the guidelines are listed below;
Determining How Many Voice Messaging Ports to Install
The number of voice messaging ports to install depends on numerous factors, including:
â¢The number of calls Cisco Unity Connection will answer when call traffic is at its peak.
â¢The expected length of each message that callers will record and that users will listen to.
â¢The number of users.
â¢The number of ports that will be set to dial out only.
â¢The number of calls made for message notification.
â¢The number of MWIs that will be activated when call traffic is at its peak.
â¢The number of TRAP connections needed when call traffic is at its peak. (TRAP connections are used by Cisco Unity Connection web applications to play back and record over the phone.)
â¢The number of calls that will use the automated attendant and call handlers when call traffic is at its peak.
It is best to install only the number of voice messaging ports that are needed so that system resources are not allocated to unused ports.
Determining How Many Voice Messaging Ports Will Answer Calls
The calls that the voice messaging ports answer can be incoming calls from unidentified callers or from users. Typically, the voice messaging ports that answer calls are the busiest.
You can set voice messaging ports to both answer calls and to dial out (for example, to send message notifications). However, when the voice messaging ports perform more than one function and are very active (for example, answering many calls), the other functions may be delayed until the voice messaging port is free (for example, message notifications cannot be sent until there are fewer calls to answer). For best performance, dedicate certain voice messaging ports for only answering incoming calls, and dedicate other ports for only dialing out. Separating these port functions eliminates the possibility of a collision, in which an incoming call arrives on a port at the same time that Cisco Unity Connection takes the port off-hook to dial out.
Determining How Many Voice Messaging Ports Will Only Dial Out, and Not Answer Calls
Ports that will only dial out and will not answer calls can do one or more of the following:
â¢Notify users by phone, pager, or e-mail of messages that have arrived.
â¢Turn MWIs on and off for user extensions.
â¢Make a TRAP connection so that users can use the phone as a recording and playback device in Cisco Unity Connection web applications.
Typically, these voice messaging ports are the least busy ports.
--------------------------------------------------------------------------------
Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity Connection that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Send MWI Requests, do not send calls to it.
Hope this helps!
Rob
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide