Accepted Solutions
Your thought that MWI operation is independent of Unified Messaging (i.e., Exchange) is incorrect. In fact, the first component of MWI notification requires that Unity and Exchange can communicate properly via the MAPI protocol. As I said in my first post, MAPI is the primary interface for Unity and Exchange and the MAPI protocol has changed between Exchange versions which leads to changes in compatibility for Unity and Exchange. In your case, Unity 4.x simply is not compatible with Exchange 2007 or 2010. Exchange 2010 integration requires a patch to the Unity server to update MAPI and you need to be on a compatible version of Unity (5.x or higher) for this integration to work. You could try any number of MWI troubleshooting procedures but the root of your problem would still trace to incompatibility between your version of Unity and Exchange.
Here is how MWI works:
Figure 9-1 Components That Turn MWIs On and Off
When a new message arrives in a subscriber Inbox, these components work together in the following sequence to activate the MWI on the phone of the subscriber:
1. 
The Exchange Monitor receives MAPI notification from the Exchange server each time a change occurs in the Inbox of each subscriber (when new voice messages arrive). When this happens, the Exchange Monitor sends an MWI activation message to the Notifier queue.
2. The Notifier queue adds the MWI activation message as an MWI activation request (with the activation code or extension) to send to the phone system.
3. The Notifier queries the Data Object Hierarchy (DOH) to determine the status of the MWI on the phone of the subscriber.
If the DOH responds that the MWI is turned off, the Notifier sends the MWI activation request in the Notifier queue to the phone system.
If the DOH responds that the MWI is turned on, the Notifier discards the MWI activation request.
4. The Miu—which includes the integration—enables Cisco Unity to communicate successfully with the phone system. The phone system receives the request and activates the MWI on the phone of the subscriber.
5. The phone system sends the new status of the MWI (activated) to the Notifier, which then sends the status to the DOH where Cisco Unity records the MWI status.
When there are no more new messages in the subscriber Inbox (all new messages have been listened to, deleted, or marked as read), the same four Cisco Unity components work together in the following sequence to deactivate the MWI on the phone of the subscriber:
1. The Exchange Monitor receives MAPI notification from the Exchange server each time a change occurs in the Inbox of each subscriber (all voice messages are listened to, deleted, or marked as read). When this happens, the Exchange Monitor sends an MWI deactivation message to the Notifier queue.
2. The Notifier queue adds the MWI deactivation message as an MWI deactivation request (with the deactivation code or extension) to send to the phone system.
3. The Notifier queries the DOH to determine the status of the MWI on the phone of the subscriber.
If the DOH responds that the MWI is turned on, the Notifier sends the MWI deactivation request in the Notifier queue to the phone system.
If the DOH responds that the MWI is turned off, the Notifier discards the MWI deactivation request.
4. The Miu—which includes the integration—enables Cisco Unity to communicate successfully with the phone system. The phone system receives the request and deactivates the MWI on the phone of the subscriber.
5. The phone system sends the new status of the MWI (deactivated) to the Notifier, which then sends the status to the DOH where Cisco Unity records the MWI status.
My first post may not have been the answer you wanted to hear, but I'm not just blindly telling you to upgrade your version of Unity or migrate to Unity Connection. To further my point, here is an except from a Cisco Q&A technote that discusses the combination of Unity and Exchange:
Q. Currently, I use Micosoft Exchange 2003 with Cisco Unity version 4.0(5) and I plan to update Exchange 2003 to Exchange 2007. Is this possible?
A. Unity 4.0(5) does not work with Exchange 2007. Your only option at this point is to upgrade to at least Unity 5.x in order to support Exchange 2007. Refer to Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version for information on how to upgrade to Cisco Unity 5.x.
The bottom line here is that MWI is more than just dialing an extension for on/off. Unity needs to be compatible with Exchange for it to function properly.
Hailey
Please rate helpful posts!
Your thought that MWI operation is independent of Unified Messaging (i.e., Exchange) is incorrect. In fact, the first component of MWI notification requires that Unity and Exchange can communicate properly via the MAPI protocol. As I said in my first post, MAPI is the primary interface for Unity and Exchange and the MAPI protocol has changed between Exchange versions which leads to changes in compatibility for Unity and Exchange. In your case, Unity 4.x simply is not compatible with Exchange 2007 or 2010. Exchange 2010 integration requires a patch to the Unity server to update MAPI and you need to be on a compatible version of Unity (5.x or higher) for this integration to work. You could try any number of MWI troubleshooting procedures but the root of your problem would still trace to incompatibility between your version of Unity and Exchange.
Here is how MWI works:
Figure 9-1 Components That Turn MWIs On and Off
When a new message arrives in a subscriber Inbox, these components work together in the following sequence to activate the MWI on the phone of the subscriber:
1. The Exchange Monitor receives MAPI notification from the Exchange server each time a change occurs in the Inbox of each subscriber (when new voice messages arrive). When this happens, the Exchange Monitor sends an MWI activation message to the Notifier queue.
2. The Notifier queue adds the MWI activation message as an MWI activation request (with the activation code or extension) to send to the phone system.
3. The Notifier queries the Data Object Hierarchy (DOH) to determine the status of the MWI on the phone of the subscriber.
If the DOH responds that the MWI is turned off, the Notifier sends the MWI activation request in the Notifier queue to the phone system.
If the DOH responds that the MWI is turned on, the Notifier discards the MWI activation request.
4. The Miu—which includes the integration—enables Cisco Unity to communicate successfully with the phone system. The phone system receives the request and activates the MWI on the phone of the subscriber.
5. The phone system sends the new status of the MWI (activated) to the Notifier, which then sends the status to the DOH where Cisco Unity records the MWI status.
When there are no more new messages in the subscriber Inbox (all new messages have been listened to, deleted, or marked as read), the same four Cisco Unity components work together in the following sequence to deactivate the MWI on the phone of the subscriber:
1. The Exchange Monitor receives MAPI notification from the Exchange server each time a change occurs in the Inbox of each subscriber (all voice messages are listened to, deleted, or marked as read). When this happens, the Exchange Monitor sends an MWI deactivation message to the Notifier queue.
2. The Notifier queue adds the MWI deactivation message as an MWI deactivation request (with the deactivation code or extension) to send to the phone system.
3. The Notifier queries the DOH to determine the status of the MWI on the phone of the subscriber.
If the DOH responds that the MWI is turned on, the Notifier sends the MWI deactivation request in the Notifier queue to the phone system.
If the DOH responds that the MWI is turned off, the Notifier discards the MWI deactivation request.
4. The Miu—which includes the integration—enables Cisco Unity to communicate successfully with the phone system. The phone system receives the request and deactivates the MWI on the phone of the subscriber.
5. The phone system sends the new status of the MWI (deactivated) to the Notifier, which then sends the status to the DOH where Cisco Unity records the MWI status.
My first post may not have been the answer you wanted to hear, but I'm not just blindly telling you to upgrade your version of Unity or migrate to Unity Connection. To further my point, here is an except from a Cisco Q&A technote that discusses the combination of Unity and Exchange:
Q. Currently, I use Micosoft Exchange 2003 with Cisco Unity version 4.0(5) and I plan to update Exchange 2003 to Exchange 2007. Is this possible?
A. Unity 4.0(5) does not work with Exchange 2007. Your only option at this point is to upgrade to at least Unity 5.x in order to support Exchange 2007. Refer to Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version for information on how to upgrade to Cisco Unity 5.x.
The bottom line here is that MWI is more than just dialing an extension for on/off. Unity needs to be compatible with Exchange for it to function properly.
Hailey
Please rate helpful posts!
