You mention when you delete the message it doesn't toggle MWI, what about just marking the message read? Does that work? One quick way to try and cut the problem in half would be to leave a message and have user login to Outlook Web Access (have their Outlook client shut down) and mark the message read or delete it and see if MWI updates. This eliminates any client to server communication anomalies we've seen in the past between Outlook and the Exchange server(s). If you directly ask the Exchange server via OWA to make the change, this will tell you if WebDAV notifications are leaving Exchange headed for UC properly and that something between the client/server could be going on. You may also want to try disabling cached mode on an Outlook client to see if that's contributing to the symptoms too.
The delayed fashion that you're seeing is most likely when Unity does it's scheduled full mailbox sync behind the scenes, and updates everyone at that time.
Thanks for the reply! When I checked and deleted the message from OWA the MWI on my phone did not turn off. You believe this is a WebDav issue? Are there specific things I should check for on Exchange?
Sounds like the WebDAV communication between UC and Exchange isn't working. I would make sure you've followed all of the necessary steps in the documentation with regards to Exchange 2003 integration/permissions. Here is the step to make sure WebDAV is enabled in IIS:
It's hard to tell without seeing the logs, I would open a TAC case to get some eyes on them if nothing sticks out. Jetty isn't directly used for Exchange 2003 integrations with WebDAV. It's used in 2007/2010 environments.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...