The purpose of this Blog is to start discussion regarding documentation/ideas/thoughts/requests regarding documentation related to Presence  Server (CUPS/IM&P). Documents  can be overwhelming when it comes to configuration or not have enough  information when it comes to troubleshooting. So the main purpose for  this discussion is to get the feedback from our community on what is  missing which you'd really like to get documentation on or  ideas/feedback on improving documentation to the level where you can  follow line by line and install/configure/troubleshoot any feature of  Presence. ... View more

TITLE Cisco Jabber for Windows MSI Transformation failing via MS Orca SYMPTOMS Trying to use MS Orca to edit the MSI file and add the configuration. Getting Error Message that "This MSI contains at least one embedded substorage which cannot be copied to the new package. You will need to manually import these substorages into the new file." ENVIRONMENT Cisco Jabber for Windows using MS Orca to edit the property values CAUSES This issue happens due to certain components, that are in the MSI. Orca is not capable of moving these components when using save as. RESOLUTION Create a copy of Jabber MSI file and rename it to any name you desire Open MS Orca and then open the renamed fileScroll down and click on the "Property" Table under the Tables Column on left hand sideOnce Property Table loads on the right hand side, right click an "Add Row"; you can also do CTRL+R In the Add Row Window enter the values listed in the following link:Presence Server Arguments     Save the file using the “SAVE” option ONLY. Close the file in MS ORCA Now you can successfully deploy this individually or via Group Policy Management. ... View more

TITLE Cisco Jabber for iPad getting error message "Failed to connect to specified server" when trying to login to Video/Voice Section SYMPTOMS Client getting "Failed to connect to specified server" when trying to authenticate with CUCM ENVIRONMENT On Premises Deployment using CUPS. CAUSES After following the COP file install, if you don't reboot the CUCM Server and then restart Tomcat, the client will not be authenticate with CUCM RESOLUTION Follow the procedure mentioned in the Installing Cisco Options Package (COP) file for devices Section on the Admin Guide http://www.cisco.com/en/US/partner/docs/voice_ip_comm/jabber/iPad/Admin_doc/output/b_Jabber_for_iPad_admin_guide_chapter_010.html#task_15D8898B81DF484EAF66ADBD27CA2C11 ... View more

TITLE How to enable status update in Cisco Jabber for Calendar Events SYMPTOMS Unable to set "Show status In a Meeting" from Cisco Jabber ENVIRONMENT Cisco Jabber for Windows (On Premises Deployment) CAUSES End Users cannot enable Calendaring Status Updates from the client itself. They now have to goto Cisco Presence User Options Page RESOLUTION To enable automatic updates of presence status for calendar events, Cisco Jabber for Windows users must individually enable a preference in the Cisco Unified Presence User Options interface. Important: This preference is disabled by default. As of this release, each Cisco Jabber for Windows user must enable the preference individually after deployment. Administrators cannot enable this preference for multiple users with a bulk task. Step 1       Log in to the Cisco Unified Presence User Options interface. Step 2       Select User Options > Preferences. The Preferences page opens. Step 3       Navigate to the Calendar Settings section of the Preferences page. Step 4       Select On from the drop-down menu for the Include Calendar information in my Presence Status field. Step 5       Select Save. Step 6       Log out and close the Cisco Unified Presence User Options interface. Presence status now integrates with your calendar. If a meeting is scheduled in your calendar, your status in Cisco Jabber for Windows is automatically set to In a meeting when that meeting begins. PREVENTION None RELATED TOPICS Admin Guide: http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_0_1/b_jabber_win_icg_chapter_010.html#task_FFB43FFD3E11403BA23C0DB08A6EBB6F ... View more

TITLE Cisco Jabber for Windows Not Connecting to Voice Mail SYMPTOMS Under File -> Options -> Phone Accounts -> Voicemail, getting "Invalid username or password" If no Voicemail section is being displayed, then on CUPS Admin Page -> Application -> Jabber -> Settings, "Credential Source for Voice Mail" is probably set to CUP ENVIRONMENT Cisco Jabber for Windows (CUPS Deployment) CAUSES User entering AD Password instead of Web Application password (If uses in UC are not integrated with LDAP) RESOLUTION If users in UC are not integrated with LDAP, when you goto UC Admin Page -> Users -> Settings -> Change Password, from the drop down, you'll notice "Web Application" password. Reset that and enter that in Cisco Jabber Voicemail Credentials section. If User is integrated with LDAP and it still fails, then OS Secure Mode is probably set to Enforcing on Unity Connection This will result in Defect CSCty05524 "UC 8.6.2.21009-1 IMAP Authentication failed when using LDAP directory." Then to resolve this     Switch the SELinux mode to permissive using the following CLI command:     utils os secure permissive     OR     Upgrade to the last version of CUC as it has been fixed in version 8.6.2.21900.5     Restart IMAP Server on UC PREVENTION N/A RELATED TOPICS CSCty05524 "UC 8.6.2.21009-1 IMAP Authentication failed when using LDAP directory." http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCty05524 ... View more

TITLE End Users not able to Edit their Profiles from Cisco Jabber SYMPTOMS The option "Edit My Profile" is missing from the File Menu ENVIRONMENT Cloud Deployment. WebEx Node CAUSES Edit my profile feature will only appear if the user has the appropriate WebEx policy. RESOLUTION In the WebEx Connect Administrator Tool the admin needs to assign the user the "Allow user to edit profile" policy. PREVENTION Make sure users are part of the WebEx policy "Allow user to edit profile" RELATED TOPICS N/A ... View more

TITLE Jabber displays cached contact photo SYMPTOMS Cisco Jabber for Windows Client does not automatically update contact picture that has been updated in Active Directory Photos are cached in the following location: Win 7/Vista: C:\Users\<userid>\App Data\Local\Cisco\Unified Communications\Jabber\CSF\Photos XP: C:\Documents and Settings\<userid>\Local Settings\Application Data\Cisco\Unified Communications\Jabber\CSF\Photos Since the contact list images are cached locally on the PC, if the image is updated in AD, the user's old image still displays in contact list.  ENVIRONMENT Cisco Jabber for Windows pulling contact images from AD CAUSES Jabber client is currently unable to address this dynamically of updating the contact images. Once the images are retrieved, they are stored locally. RESOLUTION -Exit Cisco Jabber and make sure jabber.exe is not running in Task Manager -Delete the Locally Cached images under the following location:     Win 7/Vista: C:\Users\<userid>\App Data\Local\Cisco\Unified Communications\Jabber\CSF\Photos     XP: C:\Documents and Settings\<userid>\Local Settings\Application Data\Cisco\Unified Communications\Jabber\CSF\Photos -Log back into Cisco Jabber and it'll now retrieve the latest contact images. PREVENTION None RELATED TOPICS This issue was initially noticed in Cisco Unified Personal Communicator and the following feature enhancement request is created address this functionality CSCtu25084  CUPC Contact Picture Cached and not updating dynamically http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtu25084 ... View more

TITLE Custom Emoticons not displaying correctly in IM SYMPTOMS When an end user who has created Custom Emoticon on their PC sends IM to any other user and enters that emoticon, the receiver only gets the DefaultKey and not the IMAGE itself of the Custom Emoticon created. -User A defines a custom emoticon in emoticonDefs.xml. The custom emoticon definition exists only on User A's local file system. -User A sends that custom emoticon to User B. -User B receives only the default key for the custom emoticon. User B does not receive the icon. ENVIRONMENT Cisco Jabber for Windows CAUSES Individual user modified the "emoticonDefs.xml" and placed it in Custom Emoticon %USERPROFILE%\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\CustomEmoticons The emoficonsDef.xml file only applies to the local machine, not to remote parties. RESOLUTION Place that same emoticonDefs.xml in the receivers %userprofile% folder PREVENTION Make sure that the emotionDefs.xml is the same across the deployment RELATED TOPICS http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_0_1/b_jabber_win_icg_chapter_0110.html#task_90A8AB231F47483B9A1C6F5CB5D314F8 To enhance this functionality, the following feature enhancement request has been created so that we can allow our individual users to use unique Emoticons not deployed company wide: CSCtz87726 Cisco Jabber for Windows should allow Custom Emoticons Unique to Users http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtz87726 ... View more

TITLE Cisco Jabber unable to login SYMPTOMS Client stuck at "Connecting" at the login window. ENVIRONMENT On Premises Deployment using CUPS. CAUSES Even if an IP address is entered for Login Server on Cisco Jabber, if CUPS Node name (CUPS Admin Page -> System -> Cluster Topology) is configured as HOSTNAME rather than IP Address and that Host name is not resolvable, Cisco Jabber will be unable to connect to that server. Notice in the logs where even if we had entered IP address of CUPS, Cisco Jabber will try to connect to the Hostname: 2012-05-01 11:18:52,937 INFO  [0x00000e88] [ied\featuresets\adapters\imp\Log.cpp(33)]  [JabberWerx] [IMPStackCap::Log::log] - [LoginMgr.dll]: login, jabber, serv:<cupsHostName> 2012-05-01 11:18:52,937 DEBUG [0x00000e88] [ied\featuresets\adapters\imp\Log.cpp(32)] [JabberWerx] [IMPStackCap::Log::log] - [XmppMgr.dll]: Enter CXmppClientMgr::SignOn 2012-05-01 11:18:52,937 DEBUG [0x00000e88] [ied\featuresets\adapters\imp\Log.cpp(32)] [JabberWerx] [IMPStackCap::Log::log] - [XmppSDK.dll]: CXmppClient::SignOn  2012-05-01 11:18:52,937 DEBUG [0x00000e88] [ied\featuresets\adapters\imp\Log.cpp(32)] [JabberWerx] [IMPStackCap::Log::log] - [XmppSDK.dll]: Connect result is:1 RESOLUTION Have DNS Entry to resolve CUPS FQDN and also make sure the workstation is part of the AD domain. If workstation is not part of the Domain, the Hostname will not be resolvable, only the FQDN would be, in that case we will have to either make that workstation part of the domain or create a local host entry on that workstation by editing the "hosts" file located in C:\WINDOWS\system32\drivers\etc and then log back into Cisco Jabber. PREVENTION When DNS server has an entry for CUPS FQDN, make sure that the workstations, where Cisco Jabber for Windows is deployed on, are part of the domain. ... View more