PDF(43.3 KB) View with Adobe Reader on a variety of devices
ePub(116.9 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(100.6 KB) View on Kindle device or Kindle app on multiple devices
Updated:January 8, 2014
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes an issue with the Single Inbox feature in Cisco Unity Connection. With the Single Inbox feature you are able to sync messages to Microsoft Exchange and then receive notification from Exchange when the message is marked read or deleted. Upon receipt of this notification from Exchange, Unity Connection changes the status of the local copy of the message. At times there are issues where notifications are not received from Exchange and thus the Message Waiting Indicator (MWI) and Unity Connection's local copy of the message are not in the proper status.
In order to troubleshoot this issue, check the application log on the Exchange Client Access Server (CAS) for warnings or error messages created when the message was marked as read or deleted in Outlook. Generally these warnings are sourced from MSExchange Web Services. An example of the warning that might be seen is shown here:
Log Name: Application Source: MSExchange Web Services Date: 11/25/2013 11:12:41 AM
Unable to send a notification for subscription HQBqb2huZXhjYXAwMS5jb3JwLmZtZ2xvYmFsLmNvbRAAAAAgUx5NOPjRQoqT+menP2j1. (Send attempts: 3)
It is also suggested to take a Network Capture on Exchange CAS in order to see if it sends out notifications to Unity Connection.
In the capture, check to see if there is any traffic on TCP port 7080. This is the port which Unity Connection requests Exchange to send the notification of message status change.
If you receive a capture, you can filter it with 'tcp.port==7080'. If you apply the filter and then do not see any traffic, Exchange did not put any traffic on the wire on that port.
Should you see something similar to the example warning and also not see any 7080 traffic on the network capture, it is possible a proxy setting on the CAS server is the cause of the issue. Traffic might instead be routed to a proxy setting which is set for http://<unknown IP address>:80.
In order to correct the issue, complete these steps:
Check the proxy settings on the CAS server. The proxy settings are mostly applied through group policy and sit in this registry: HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Proxy Server.
In order to test the issue, disable the default proxy in Exchange Web Services (EWS) web.config.
Possible Path: C:\Exchsrvr\ClientAccess\exchweb\EWS