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.
Re: How to get MWI working in CCM 4.2 and Unity 1.2
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.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...