This document describes a problem encountered when the Unity Connection Single Inbox feature is configured so that it works with Microsoft Exchange 2003, and also provides possible solutions to the problem.
Cisco recommends that you have knowledge of these topics:
- Cisco Unity Connection Releases 8.x and 9.x
- Windows Exchange Server
The information in this document is based on these software and hardware versions:
- Cisco Unity Connection Releases 8.5, 8.6, 9.0, and 9.1
- Microsoft Exchange 2003 and 2007
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Once you configure the Single Inbox feature so that Cisco Unity Connection works with Microsoft Exchange 2003, you might notice that messages are not delivered to Exchange. The tests for Unified Messaging Services "account" and "user" pass, but if you review the Connection Mailbox Sync traces you might see this message:
HTTP 500 - Internal server error
- It is also possible to receive this error message when a Device Access Verification (DAV) client tries to authenticate with an Exchange Server 2003 SP1 front-end server. For more information, refer to this Microsoft Article.