Known Issue: Exchange Hosted Solution Issue

From DocWiki

Jump to: navigation, search

Back to Exchange Calendaring Main Page: Known Issues: Exchange Calendaring

Cisco Unified Personal Communicator may fail to show calendar status updates.

If, however, you disable and reenable the calendar feature on Cisco Unified Personal Communicator, or you restart the Presence Engine on cIsco Unified Presence, Cisco Unified Personal Communicator may show calendar status again - but will not reflect further calendaring updates.

What Caused it?

More and more service providers deliver an "Exchange Hosted" solution, which allows the Exchange servers to be located at the premises of the service provider instead of onsite in your organization. While this solution is convenient, it can cause problems with Exchange calendaring integration if not configured properly.

Note that when the calendaring feature is enabled for a user for the first time (or when the Presence Engine restarts), the Presence Engine sends SUBSCRIBE messages to the Exchagne OWA server via the TCP protocol. Exchange always responds to this initial request with the TCP protocol.

Whenever there's a calendar update, the update is sent from the mailbox server to Cisco Unified Presence via the UDP protocol (which you cannot change)

You can change the Microsoft Exchange Notification port if required in Cisco Unified Presence Administration (select System > Service Parameters > Microsoft Exchange Notification Port). The default port is 50020.

What Can You Do?

Capture packets on Cisco Unified Presence and on the Exchange mailbox server to determine the following:

- has the mailbox server attempted to send UDP packets and has the Cisco Unified Presence server not received those packets?
- is the firewall preventing communication between the mailbox servers and Cisco Unified Presence?
- is the Microsoft Exchange Notification port correct?

Rating: 0.0/5 (0 votes cast)

Personal tools