Cisco Unified Presence, Release 7.x -- Cisco Unified Presence Knowledge Base

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Issue with Deskphone Control and/or Contact Search)
Line 21: Line 21:
There are two possible situations that this applies to:
There are two possible situations that this applies to:
-
1) CUPC deskphone control is not working. Show server health shows the status of "Not Connected - Stopped"
+
1) Cisco Unified Personal Communicator deskphone control is not working. Show server health shows the status of "Not Connected - Stopped"
-
2) Searching in CUPC is not returning all results.
+
2) Searching in Cisco Unified Personal Communicator  is not returning all results.
   
   
'''Conditions:'''
'''Conditions:'''
Line 36: Line 36:
2) If you are using Windows Active Directory, use the Global Catalog port 3268 instead of the standard LDAP port of 389.
2) If you are using Windows Active Directory, use the Global Catalog port 3268 instead of the standard LDAP port of 389.
-
 
==Issues for Signed In Users after Change to Proxy Domain==  
==Issues for Signed In Users after Change to Proxy Domain==  

Revision as of 08:48, 16 June 2010

Main page: Cisco Unified Presence, Release 7.x

Welcome to the Knowledge Base for Cisco Unified Presence! See below for articles, tips, tricks and workarounds for the Cisco Unified Presence components, features and clients.




Issue with Deskphone Control and/or Contact Search

Release: Cisco Unified Presence 7.x

Symptom:

There are two possible situations that this applies to:

1) Cisco Unified Personal Communicator deskphone control is not working. Show server health shows the status of "Not Connected - Stopped"

2) Searching in Cisco Unified Personal Communicator is not returning all results.

Conditions:

When you have a large user base and the LDAP server does not respond in a timely manner to queries from Cisco Unified Presence.

Workaround:

You can use either of these workarounds:

1) Index the telephoneNumber field on the LDAP server.

2) If you are using Windows Active Directory, use the Global Catalog port 3268 instead of the standard LDAP port of 389.

Issues for Signed In Users after Change to Proxy Domain

Release: Cisco Unified Presence 7.x

Symptom:

If you change the Proxy Domain settings on Cisco Unified Presence while users are signed into Cisco Unified Personal Communicator, all operations (including availability status and Instant Messaging (IM)) fail and users cannot sign into the updated domain.

Conditions:

This condition occurs if Proxy Domain settings change on Cisco Unified Presence while users are signed into Cisco Unified Personal Communicator.

Workaround:

Before you change the Proxy Domain settings on Cisco Unified Presence, make sure that all users are fully signed out of their Cisco Unified Personal Communicator client.

Rating: 0.0/5 (0 votes cast)

Personal tools