This document describes the troubleshooting issues on Cisco Jabber for Windows.
Cisco Jabber for Windows does not download the configuration file from the TFTP server. The configuration file is not available in the installation directory after you start Cisco Jabber for Windows.
1. Restart your TFTP server.
2. Check the name of your configuration file.
3. Ensure your corporate firewall does not prevent Cisco Jabber for Windows from downloading the configuration file.
4. Host the configuration file on your TFTP server as follows:
You host a global or group configuration file on your TFTP server. Cisco Jabber for Windows downloads the configuration file and saves it in the appropriate installation directory. However, Cisco Jabber for Windows does not apply any settings you specify in the configuration file.
Ensure the XML in the configuration file is valid. Cisco Jabber for Windows configuration files must do the following:-
<?xml version="1.0" encoding="utf-8"?>
Cisco Jabber for Windows is not using the current configuration settings. You change settings in a configuration file and host it on your TFTP server. However, Cisco Jabber for Windows uses the settings from the previous version of the configuration file.
1. Restart your TFTP server.
2. Open the configuration file in your browser to verify the settings. Typically, you can access the configuration file at the following URL: http://
If restarting your TFTP server does not resolve this issue, it is likely that Cisco Jabber for Windows uses the cached configuration file because it cannot download the current version. See the troubleshooting steps to resolve the Configuration file does not download issue.
You attempt to start a group chat. The group chat does not start and the following message is written to the log files:
WARN [0x000021c0] [PME(0)] [cpve] [<ctxt:GStreamer,thread:8640>] - pipeline0 [gstbin.c(2399),
gst_bin_do_latency_func()]-> failed to query latency" and the it is generating 10+ log files per minute.
If you then restart Cisco Jabber for Windows, the following message is written to the log files:
ERROR [0x000004fc] [ied\featuresets\adapters\imp\Log.cpp(35)] [JabberWerx] [IMPStackCap::Log::log] -
[XmppSDK.dll]: CXmppMUCRoom::GetGroupChatServer , no MUC_SERVICE is available, please check the configure of server, bPersistent:0
To resolve this issue, do the following:
User can authenticate to Jabber Windows, and IM/Presence functions correctly, but the phone control does not. When going into Options > Phone Accounts, all you see is a spinning wheel.
Jabber for Windows will authenticate with the CUPS server, then attempt to locate the authenticated users CCMCIP profile to download the list of associated devices that user is allowed to control. If this service is not activated, or if this user has no devices associated with them, than phone control will not work.
(Cisco Unified Serviceability > Tools > Control Center - Network Services > CM Services > Cisco CallManager Cisco IP Phone Service)
(Cisco Unified CM Administration > User Management > End User > username > Device Information > Device Association)
(Cisco Unified CM Administration > Device > Phone > dn_in_question > line appearance > User Associated with Line)
(Cisco Unified Presence Administration > Application > Cisco Unified Personal Communicator > CCMCIP Profile > profile > Primary CCMCIP Host & Users in Profile)
(Cisco Unified Presence Administration > Application > Cisco Unified Personal Communicator > Audio Profile > profile > Users in Profile)
Below is the path for chat history :-
When you use Jabber for making calls you need to configure a CSF (Client Service Framework) on CUCM.
Similiar CUPC 8.X to Jabber
Other thing under end user config at Device Information section, add the UDP on the field CTI Controlled Device Profiles. For more information refer