This document describes the problem encountered where Microsoft (MS) Exchange does not journal messages that are Exchanged Web Services (EWS) when synced from Cisco Unity Connection, and offers solutions to the problem.
Single Inbox messages are not logged by the MS Exchange Journal feature when synched from Cisco Unity Connection.
Here is a suggested workaround. Create a separate mailbox on MS Exchange in order to accept messages from Unity Connection that must be logged by the Journal feature. Next, set up accounts to additional relay the messages to this mailbox. This relay allows messages to be Simple Mail Transport Protocol (SMTP)-delivered, which categorizes them as the type of message that is allowed to journal.
- Create a specific mailbox on MS Exchange in order to accept a separate copy of the MS Exchange message.
- Configure Unity Connection with a Smarthost address. On the Unity Connection Admin webpage, navigate to System Settings > SMTP Configuration > Smart Host. Enter the Exchange IP address or the hostname that accepts and relays messages from Unity Connection.
- Navigate to each user, choose Message Actions, and configure the relay. Navigate to User > <specific user> > Edit > Message Actions > Voicemail, and choose Accept and Relay the Message. In the Relay Address field, enter the MS Exchange Journal mailbox that you created.
The users still receive the messages that EWS synced to their mailbox by the Single Inbox feature, and the Message Actions SMTP-deliver the message to the mailbox you have created.
The only other workaround, which also follows the previous steps, is to create a secondary mailbox on MS Exchange for each user. Then, you must configure the Message Actions feature in order to relay to the secondary mailbox for each user. This is necessary because you cannot conduct EWS Syncronization (Single Inbox) and SMTP Relay to the same MS Exchange mailbox.
Contact Microsoft for more information on how to set MS Exchange to journal EWS-synced messages.