Cisco Unity: Exchange 2007 Disclaimer Transport Rule Causes MWI to Fail

[Tray Stoutmeyer]

Introduction

The disclaimer transport rules in Exchange 2007 put a disclaimer on incoming emails. This causes message-waiting indication (MWI) to fail on Unity voicemails. This document provides information on how to troubleshoot this issue.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Active Directory

• Exchange 2003/2007 Administration

• Cisco Unity 5.x and 7.x

Components Used

The information in this document is based on these hardware and software versions:

• Cisco Unity 5.x/7.x versions, with Exchange 2007 Server as the partner mail store

Conventions

For more information on document conventions, refer to Cisco Technical TipsConventions.

Problem

Users experience lack of MWI lights on their system when a voicemail is left. If you are using Unified messaging, you will receive the voicemail .wav file attached email. There will be a disclaimer in the email body portion of the message when you view the email in an Outlook Client or Outlook Web Access. This can also be verified by using the DohPropTest on an example user and viewing the attribute AVP_MESSAGE_CLASS to see IPM. Note (email) instead of the IPM.Note.Voice.Unity that should be there.

Usual voicemail message with voicemail attribute:

The disclaimer transport rule in Exchange 2007 adds the disclaimer to the incoming email message body, which converts the voicemail attribute to the IPM.

Note: The email attribute causes MWI to not be triggered:

Solution

In order to resolve this issue, you must stop the incoming emails from getting the disclaimer added by adjusting the transport rule in Exchange 2007 which causes this issue.

Go to the Exchange 2007 server console and change the transport rule in order to restrict the incoming emails from having the disclaimer attached. Complete these steps:

1. Login to the Exchange 2007 server console and open the Exchange Management Console.

2. Expand Orgainization Configuration.

3. Click Hub Transport in the tree. In the right pane, go to the Transport Rules tab to view the current rules in place.

4. Look at the Properties of the rule that adds the disclaimer and make sure to remove any action checkboxes that cause it to add the disclaimer to incoming messages.

   5.   Test after adjusting the transport rule in Exchange 2007 by leaving the same user a new voicemail message. You need to verify if the MWI light works.

[Tray Stoutmeyer]

I wanted to add that the change of the attribute to IPM.Note will also cause messages to not show as voicemail when checking voicemail via TUI (via the phone voicemail button). Messages in a Unified Messaging environment will show up in Outlook clients just fine and look normal but, upon logging in via the phone, TUI conversation will state "there are no new messages" because Unity logs into the mailbox and thinks there is only email in it due to the attribute change. This results in a voicemail message count of zero. The symptom for those affected will be the following complaint...

"I have 5 new messages in my inbox on Outlook but when I login to my voicemail, it tell me I have no new messages. Why?"

[PETER NEBLETT]

Good Morning,

This is great information that your posting . I'm not that familiar with the workings of Microsoft Exchange but would you know if the Exchange 2007 disclaimer transport rule also causes issues when using Unity Connection 8.5?