Table Of Contents
Troubleshooting Exchange Calendaring Integrations
Troubleshooting Exchange Server Connection Status
Troubleshooting SSL Connection/Certificate Status
Issues Known to Impact Microsoft Exchange Integrations
Scale Limitations for Calendaring Integrations
Calendaring State Does Not Update if a User Moves between Exchange servers
LDAP User Removal Takes At Least 24 Hours to Replicate on Cisco Unified Presence
Localization Caveat with WebDAV Calendaring Integrations
Exchange Server URL Must Contain Localized Word for "Calendar"
Verifying Presence Gateway Configuration on Cisco IP Phone Messenger-enabled Phones
Applying Microsoft HotFix KB841561
Calendar Integration Fails with "HTTP 503 Service Unavailable" Error from Exchange 2007
Support for Meeting Notifications and Cisco IP Phone Messenger
Troubleshooting Exchange Calendaring Integrations
Revised: November 30, 2012
•Troubleshooting Exchange Server Connection Status
•Troubleshooting SSL Connection/Certificate Status
•Issues Known to Impact Microsoft Exchange Integrations
Troubleshooting Exchange Server Connection Status
Exchange Server connection status displays in Cisco Unified Presence Administration after you configure the Exchange Presence Gateway for either a WebDAV or EWS calendaring integration (select Presence > Gateways). The Troubleshooter on the Presence Gateway configuration window reports the status on the connection between Cisco Unified Presence and the Exchange server.
Note You can add, update or delete one or more EWS servers with no maximum limit. However, the Troubleshooter on the Presence Gateway window is designed to only verify and report status of the first 10 EWS servers that you configure.
.
Troubleshooting SSL Connection/Certificate Status
SSL Connection/Certificate Verification status displays in Cisco Unified Presence Administration when you configure the Exchange Presence Gateway for a either a WebDAV or EWS calendaring integration (select Presence > Gateways). The Troubleshooter on the Presence Gateway configuration window will indicate if there is a certificate Subject CN mismatch or a SAN mismatch.
Note You can add, update or delete one or more EWS servers with no maximum limit. However, the Troubleshooter on the Presence Gateway window is designed to only verify and report status of the first 10 EWS servers that you configure.
Issues Known to Impact Microsoft Exchange Integrations
The following section describes known issues that are common or specific to versions of Microsoft Exchange Server (2003, 2007, 2010)
•Scale Limitations for Calendaring Integrations
•Calendaring State Does Not Update if a User Moves between Exchange servers
•LDAP User Removal Takes At Least 24 Hours to Replicate on Cisco Unified Presence
•Localization Caveat with WebDAV Calendaring Integrations
•Exchange Server URL Must Contain Localized Word for "Calendar"
•Verifying Presence Gateway Configuration on Cisco IP Phone Messenger-enabled Phones
•Applying Microsoft HotFix KB841561
•Calendar Integration Fails with "HTTP 503 Service Unavailable" Error from Exchange 2007
•Support for Meeting Notifications and Cisco IP Phone Messenger
Scale Limitations for Calendaring Integrations
Cisco Unified Presence and Exchange calendaring integrations have been validated with up to X% of the users subscribing to calendar presence and with up to Y% of the users doing simultaneous calendar transitions (for example, joining or leaving meetings simultaneously). See Table 6-1 for percentage values pertaining to specific releases of Cisco Unified Presence Release.
Table 6-1 Scale Limitations for Specific Cisco Unified Presence Releases
Calendaring State Does Not Update if a User Moves between Exchange servers
Problem
If an Exchange administrator moves a user from one Exchange server to another in an Exchange integration, the calendaring state change will not update for that user.
Cause
The condition occurs because the Exchange server does not signal when a user is moved from one server to another.
Solution
The Cisco Unified Presence administrator or user must disable and then reenable calendar integration for that user after the Exchange administrator has moved the user from one Exchange server to another.
LDAP User Removal Takes At Least 24 Hours to Replicate on Cisco Unified Presence
Problem
If a user is deleted from LDAP, the user state changes to Inactive on Cisco Unified Communications Manager and user authentication on client applications will subsequently fail. However, it has been observed during testing that once Cisco Unified Communications Manager synchronizes the change from LDAP, the user will not be removed for 24 hours after the synchronization occured (either by the Administrator forcing the sync or scheduling it to occur at a specific time).
The Cisco UP Sync Agent on Cisco Unified Presence will not synchronize any user state change until the user is removed. In the interim period, that user still exists on Cisco Unified Communications Manager and all Cisco Unified Presence capabilities (including Exchange calendaring subscriptions) remain licensed for that user for 24 hours. This delay means that users who were signed into Cisco Jabber before the user was removed from LDAP are not signed out automatically. The user's pre-exisitng calendar state (Available, Busy) will persist for that user on Cisco Unified Presence until the user signs out of the client.
Cause
The condition occurs when Cisco Unified Communications Manager is set up and LDAP authentication is used. When a user is deleted from LDAP, calendaring subscriptions continue to be established and updated for that user on Cisco Unified Presence for a period of at least 24 hours.
Solution
If a user is removed from LDAP, you can manually remove the license for that user so that Cisco Unified Presence ends the Exchange calendaring subscriptions with immediate effect and signs the user out of the client application. Otherwise, be aware that there may be a 24 hour time delay.
Localization Caveat with WebDAV Calendaring Integrations
Problem
If you set the default language (English) on the user's Exchange Mailbox when a different language/locale is installed on Cisco Unified Communications Manager, the Exchange server maintains the default calendar name (in English) and you cannot change the language/locale for that user. A 404 error returns for calendaring subscriptions.
Cause
This condition only occurs in localized Exchange 2003/2007 integrations over WebDAV. The issue does not affect EWS integrations.
Solution
•To prevent this issue occurring, we recommend that you set languages correctly during the Exchange setup. Install the appropriate language/locale on Cisco Unified Communications Manager and select the appropriate language/locale on the Exchange server the first time the user signs in.
•If the language on the user's Exchange Mailbox is set to English when a different language/locale is installed on Cisco Unified Communications Manager, you must switch the language/locale on Cisco Unified Communications Manager back to English for that user. To do this, see Setting User Locales for Multilingual Calendaring Integration.
Exchange Server URL Must Contain Localized Word for "Calendar"
If you are localizing your Calendaring integration, verify that the Exchange server URL contains the localized word for "Calendar".
Procedure
Step 1 Install the same language locales (load the locale installer) on both Cisco Unified Presence and the Cisco Unified Communications Manager. For more information about installing locales on Cisco Unified Presence, see [Optional] How to Configure Multilingual Support for Calendaring Integration.
Step 2 Restart the Cisco Unified Presence server, and sign into Cisco Unified Presence Administration.
Step 3 Find and delete the existing Exchange Presence Gateway that supports a different locale for calendaring (select Presence >Gateways).
Step 4 Add a new Exchange Presence (Outlook) gateway. Select Add New.
Step 5 Verify in the database (pebackendgateway table) that the 'localecalendarname' attribute is in whichever language locale you have installed.
Step 6 Ensure the user locale is set after the locale is installed on both the Cisco Unified Presence and Cisco Unified Communications Manager, toggling the user locale on the Cisco Unified Communications Manager, if necessary.
Verifying Presence Gateway Configuration on Cisco IP Phone Messenger-enabled Phones
If you correctly configure the Receive-As account credentials and certificate exchange, desk phones enabled with Cisco IP Phone Messenger will display the scheduled meetings of users. To verify that the Outlook Presence Gateway is configured correctly, perform these steps on an appropriately configured phone.
Procedure
Step 1 Select Services.
Step 2 Press PhoneMessenger.
Step 3 Sign into the IP Phone Messenger Service.
Step 4 Select 1 Today's meetings.
Step 5 Verify that the user's meetings for the day are listed.
Applying Microsoft HotFix KB841561
Note that this issue is specific to Microsoft Exchange 2003 only. Apply Microsoft HotFix KB841561 if you encounter problems with the Exchange 2003 server and it returns a "500 Internal Server Error".
Procedure
Step 1 Uninstall SP2 for Windows Server 2003 and for Microsoft Exchange 2003.
Step 2 Install SP1 for Windows Server 2003 and Exchange 2003.
Step 3 Download and install KB841561 from the following URL: http://www.microsoft.com/downloads/details.aspx?familyid=050be883-11fc-4045-b988-c737e79c65d0&displaylang=en
Step 4 Install SP2 for Windows Server 2003 and for Microsoft Exchange 2003.
Calendar Integration Fails with "HTTP 503 Service Unavailable" Error from Exchange 2007
Note that this issue is specific to Microsoft Exchange 2007 only.
Problem
Since Exchange 2007, Microsoft changed the Outlook Web Access URL from /exchange to /owa, which is the virtual directory that OWA uses to access mailboxes on Exchange 2007 mailbox servers. Cisco Unified Presence, however, always sends SUSCRIBE requests to the /exchange virtual directory, which is the URL that is still used for WebDAV integration with Exchange 2007. During testing with Exchange Server 2007 (SP1), it has been observed that if you change the http://<server>/exchange URL to redirect to http://<server>/owa URL, an error (HTTP 503 Service Unavailable) displays on the Internet Information Services (IIS) Manager console in Exchange 2007.
Cause
The condition occurs when Exchange 2007 SP1 is in use, and the Exchange virtual directory target address is modified to redirect to the default OWA directory for webmail.
Solution
If the "503 Service Unavailable" error message displays, perform the steps in this procedure:
Procedure
Step 1 From Administrative Tools, open Internet Information Services.
Step 2 Delete the Microsoft Exchange virtual directory in IIS.
Step 3 Review the warning that displays, and run the recommended cmdlet in the Exchange Management Shell (EMS) :
Step 4 Run this cmdlet in the EMS to ensure that the Exchange virtual directory is set up correctly and to add the directory again in IIS.
SyntaxNew-OwaVirtualDirectory -name exchange -OWAVersion Exchange2003or2000 -VirtualDirectoryType mailboxesStep 5 Wait for the Exchange server to populate the virtual directory into IIS.
Step 6 Restart the IIS.
Step 7 Test your http://<server>/exchange/<user email address>/calendar URL, using the full target address for example, http://mail.contoso.com/exchange/user@contoso.com/calendar
Step 8 Ensure that you are prompted for a username and password. This indicates that WebDAV is enabled and configured correctly on the virtual directory. Enter your Active Directory credentials.
Step 9 Check the IIS logs that display for Cisco Unified Presence.
Step 10 If the logs indicate that there is a 401 authentication issue, add the domain to authenticate access.
Step 11 Restart the IIS.
Step 12 Select Cisco Unified Serviceability > Tools > Service Activation and restart the Cisco UP Presence Engine.
Step 13 Check the IIS logs again and verify that the SUBSCRIBE messages are present and correct for your calendar.
Troubleshooting Tips
This procedure also applies to Apple MAC users who require WebDAV to view their emails using Microsoft Entourage 2008.
Support for Meeting Notifications and Cisco IP Phone Messenger
Note that the Meeting Notification and Cisco IP Phone Messenger features will only work if your network integration is over WebDAV. Therefore, this issue is specific to Microsoft Exchange 2003 or 2007 only. These features are not supported with EWS integrations.