Presence Hot Issues from Cisco TAC

CUP GUI needs an option to update Client type, Fixed CSCtq15767

Symptom: This enhancement defects adds an option to update SOAP client types from Cisco Unified Presence web interface. The web based option has been added only in Cisco Unified Presence release 8.6.3 and would be available all releases upwards. New client types can be added into database using remote accounts for Cisco Unified presence releases 8.6.1 and 8.6.2 (pre 8.6.1 releases does not support this option)
Conditions: Cisco Unified Presence release 8.6.1 or 8.6.2
Workaround: Open a support case with TAC. TAC should follow the below mentioned guidelines 1) To add client-type "JABBERIPAD" for support of Cisco jabber for ipad Steps: Do this operation during low traffic hours due to the impact to client login a) Create a remote support account b) Follow the below mentioned procedure [remotesupport@cupnode ~]# su informix [informix@cupnode remotesupport]$ [informix@cupnode remotesupport]$ dbaccess $(dblutil -c) < insert into soapclienttypes values ("05c920dc-388d-4405-9d62-05501c476fa1","JABBERIPAD","f","f","f17f95a6-c185-41a8-872e-70bfac7e634d","0.0.0.0","f","Cisco Jabber for iPad","f","t"); > ! Database selected. 1 row(s) inserted. Database closed. c) Verify that the new entry has been added with the above below [informix@cupnode remotesupport]$ dbaccess $(dblutil -c) < select * from soapclienttypes where clienttype="JABBERIPAD"; > ! Database selected. d) Restart Cisco UP Client Profile Agent on ALL THE NODES in the CLUSTER [informix@gwydlvm107 remotesupport]$ exit exit [remotesupport@gwydlvm107 ~]# controlcenter.sh "Cisco UP Client Profile Agent" restart Note: Restarting the above service impacts client login, therefore restart the service only when suitable to the customer!

CUPS 9.1.1 does not accecpt AXL username/password changes in WebAdmin, Fixed CSCue79671

Symptom: "Error: 4092 Failed to verify if the CUMC and IM Presence Service version match" seen on the CUCM Publisher page of CUPS WebAdmin
Conditions: Attempting to change the AXL Username or password and after saving, causes the error seen above
Workaround: 1) Set the axl user password in Call Manager to something which does not contain special characters. 2) Obtain root access to the CUPS Server and run the following command (you may have to set os security to permissive): /usr/local/thirdparty/java/j2sdk/bin/java -classpath /usr/local/platform/jar/CCMEncryption.jar com.cisco.ccm.security.EncryptString This will return a hash value of the password which we need to use to update the database. 3) Obtain dbaccess via "su informix" (you may have to set os security to permissive) then "dbaccess" 4) Manually run the following query in dbaccess: update epassyncagentcfg set axlpassword ='' where axluser = ''; You can also update the axluserID if you've changed the CUCM user as well. It's in the epassyncagentcfg table as well as column "axluser". More Info:

CUP User Page Privacy Setting Doesn't Allow Space for UserID, Open CSCuh20912

Symptom: On end user page of IM&P, under Privacy Policy => User Settings, when a user trying to add Allow or Block a user by user ID, if the user ID contains space, the system won't allow it and an error message pops up saying "User ID - Allowed characters are alphanumeric (a-zA-Z0-9),period(.),hyphen(-),underscore(_),at sign(@), and single quote(')."
Conditions: IM & Presence 9.1.1.10000-8
Workaround: Remove space from user ID or add user from Jabber client More Info: The problem only happen to Privacy Section of end user page. User ID with space can still log into Jabber client, cup and ccm end user pages.

Feature services page not displaying correctly after DRF restore, Fixed CSCtf84913

Symptom: Service activation and feature services pages do not display properly; user cannot activate or start/stop services from the GUI.
Conditions: Upgraded CUP 6.x->7.x->8.0.1 on 7835-H1, then DRF restored on 8.0.1 on 7845- I2. 7835-H1 is unsupported hardware. 7845-I2 is supported hardware.
Workaround: Workaround 1. Instead of doing a bridge upgrade, the user can upgrade 6.x to 7.x on the old hardware, then do a DRF backup. Install 7.x on supported server, then do a DRF restore, then upgrade to 8.0.1. Workaround 2. If the user is already on the new H/W and encounters this issue. Do the following: 1. get remote access 2. perform the following at the shell prompt: cp /usr/local/platform/conf/activate.conf /usr/local/cm/conf/ccmservice/ActivateConf.xml cd /usr/local/cm/conf/ccmservice/ chown tomcat:tomcat ActivateConf.xml 3. Using Serviceability GUI, restart "Cisco Tomcat" service
Further Problem Description: The service activation and feature services pages should only be empty when the hardware is unsupported.

Troubleshooter page showed error message for SIP Publish Model, Fixed CSCsy42654

Symptom: On System Troubleshooter page, for "Verify SIP Publish Model", I saw following error messages: Problem: The Troubleshooter has encountered an internal error on this test Solution: The Troubleshooter was unable to perform this test due to an internal error
Conditions: When CUCM SIP trunk uses DNS SRV as the destination address. In this case, CUP troubleshooter page could not detect SIP Publish Model, but the SIP Publish Model actually worked fine.
Workaround: None. CUP administrator should ignore these error messages if CUCM SIP trunk uses DNS SRV as the destination address. This problem was fixed in later CUP releases.

Jabber for Mac keep prompting for 'use your confidential information', Fixed CSCub25263

Symptom: When launching Jabber for Mac, it prompts user 3 time to use confidential information stared in keychain. For example: Cisco Jabber wants to use your confidential information stored in "10.1.0.25" in your keychain. Do you want to allow access to this item? After clicking "Always Allow", expectation would be that the user would not be prompted for this after subsequent logins. However, user continues to be prompted.
Conditions: Affect only MacBook Snow Leopard, Lion works fine.
Workaround: None

Presence broken for user when username has apostrophe (single quote), Open CSCuh34193

Symptom: When a user logs into Jabber for windows, if their userID contains apostrophe, the user cannot change their presence from anything other than available. From Presence Viewer the user appears as unavailable.
Conditions: IM & P 9.1.1.20000-5 CUCM 9.1.1 Jabber 9.1.5 and 9.2.1 Occurs when the users CUCM userid contains an apostrophe (Single Quote)
Workaround: None More Info: Please see case description

Don't allow quotes in ldap profile search context field, Fixed CSCuc35088

Symptom: Upgrade from CUPS 8.6.4 to 9.0.1 Fails
Conditions: LDAP profile has Search context with special characters such as double quotes, single quotes, ampersand and less than and greater than symbols.
Workaround: Remove the special characters ( " ' $ < > ) in the search context of the LDAP profile. OR Delete the LDAP profile and re add it after the upgrade is completed.

DRS Restore Overwrites xcp_sequence table w/ Pub values on all Sub Nodes, Fixed CSCug21472

Symptom: End-users on system are reporting 1.) Random Empty Groups appearing on their Desktop clients (both CUPC and Jabber) 2.) On Jabber Clients contacts move to the default Jabber Grouping : Other Groups 3.) On CUPC clients contacts appear to be deleted from the client from time to time
Conditions: The version of CUP is running any release of CUP 8.0 up to and including 8.6.4 SU3 The CUP Server is running any release of IM/P 9.0 or 9.1.1 A DRF Restore was completed at any point during the lifetime of the server
Workaround: A full detailed workaround procedure is available but does require TAC to execute as remote access is required on the system. Please refer to CUP Triage post: http://cup-sustain/cups/viewtopic.php?f=96&t=1654&sid=6cc60bd50d0068d8424c9f1aa81037c6
Further Problem Description: To check if there are duplicate entries in the CUP rosters table the following query can be run against the CUP dtatbase: run sql SELECT COUNT(*), roster_id FROM rosters GROUP BY roster_id HAVING COUNT(*) >1

CUPS primary install wizard asks for NTP but doesn't use it, Open CSCuh42251

Symptom: During the install of a CUPS publisher node the install wizard asks for an NTP source however once the installation is complete it uses the CUCM publisher server.
Conditions: During the install of a Presence publisher node.
Workaround: Enter in a valid NTP source for the connectivity test to work however the value will be overwritten with the CUCM publisher IP address. More Info:

SELinux policies on the CUP server are denying outbound HTTP connections, Fixed CSCug51696

Symptom: Application unable to retrieve PWS presence status notification from CUP Server
Conditions: SELinux policies on the CUP server are denying the outbound HTTP connection attempt by the SIP Proxy service.
Workaround: Set selinux to permissive mode. From the admin CLI, run the following command: utils os secure permissive More Info:

Tomcat keystore generation issue post upgrade - Tomcat fails to start, Fixed CSCtx65298

Symptom: Tomcat fails to start post upgrade, shows the following when running "utils diagnose test" admin:utils diagnose test Starting diagnostic test(s) =========================== test - disk_space : Passed skip - disk_files : This module must be run directly and off hours test - service_manager : Passed test - tomcat : Passed test - tomcat_deadlocks : Passed test - tomcat_keystore : Failed - The Tomcat keystore has been corrupted. test - tomcat_connectors : Failed - The HTTPS port is not responding to local requests. Please collect all of the Tomcat logs for root cause analysis: file get activelog tomcat/logs/* Additionally when looking at the catalina.out log file (file view activelog /tomcat/logs/catalina.out), the following is seen: /usr/local/platform/.security/tomcat/trust-certs/tomcat-trust.keystore (No such file or directory)
Conditions: Has been found very intermittently post upgrade.
Workaround: Contact TAC to apply a workaround to fix Tomcat.

Presence Gateway error with DNS SRV configuration in Troubleshooter, Open CSCuh36248

Symptom: CUPS System Troubleshooter fails Presence Gateway test if CUPS Presence Gateway is configured for DNS SRV
Conditions: CUPS 8.6 DNS SRV configured in Presence Gateway System Troubleshooter diagnostic is run
Workaround: none More Info: