This document describes the troubleshooting issues on Cisco Jabber for Windows.
Issue:- Configuration File Does Not Download
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.
The name of the configuration file is case sensitive.
The global configuration filename must be jabber-config.xml.
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:
Open the Cisco Unified OS Administration interface.
Select Software Upgrades > TFTP File Management.
Select Upload File.
Select Browse in the Upload File section.
Select the configuration file on the file system.
Leave the value of the Directory text box empty to host the configuration file in the default directory of your TFTP server.
Select Upload File.
Issue:- Cisco Jabber for Windows Does Not Read the Configuration File
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:-
Use utf-8 encoding.
Contain only valid XML character entities. For example, use & instead of &.Open your configuration file in Microsoft Internet Explorer to determine if any characters or entities are not valid. If Internet Explorerdisplays the entire XML structure, your configuration file does not contain invalid characters or entities. If Internet Explorer displays only part of the XML structure, your configuration file most likely contains invalid characters or entities.
Contain a valid structure. Ensure parameters are nested under the correct elements. The following XML snippet shows the basic structure of a configuration file in an on-premises deployment:
<?xml version="1.0" encoding="utf-8"?>
Issue:- Cisco Jabber for Windows Uses Old Configuration Settings
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.
Issue:- Group Chat Does Not Start
You attempt to start a group chat. The group chat does not start and the following message is written to the log files:
[XmppSDK.dll]: CXmppMUCRoom::GetGroupChatServer , no MUC_SERVICE is available, please check the configure of server, bPersistent:0
To resolve this issue, do the following:
Ensure at least one of the group chat participants is online. Cisco Jabber for Windows requires a minimum of one online participant to create a group chat.
Activate and start the Multi User Chat Room service on Cisco Unified Presence.
Activate and start the Text Conference Manager service on Cisco Unified Presence.
Issue:- Jabber Windows cannot control phone device from client
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.
Verify the CCMCIP service is in a "Running" state on the CUCM server
(Cisco Unified Serviceability > Tools > Control Center - Network Services > CM Services > Cisco CallManager Cisco IP Phone Service)
Verify the device in question is associated with the end-user
(Cisco Unified CM Administration > User Management > End User > username > Device Information > Device Association)
Verify the line appearance in question is associated with the end-user and device
(Cisco Unified CM Administration > Device > Phone > dn_in_question > line appearance > User Associated with Line)
Verify the CCMCIP Profile in CUPS is configured and associated with the end-user and is configured for the correct CCMCIP Host
DearI have an imagicle stonefax and 2911 as voicegateway and no cucm used here.I configure direct sip trunk from voicegateway to imagicle. but fax not sending!!!I configure this scenario so many time on 2811 router but don't know what should be the proble...
Dear Team,We have a call center setup where the callers will be calling a support number and choose options (like 1 for sales, 2 for technical support, etc.). The callers will be connected to the agents. And the agent may do a blind transfer call to the i...
Hello, I know I have done this before, but am having trouble finding where and how to disable the "press any digit to be connected" when answering a Single Number Reach call. On CUCM 11.5.1SU6. Have a situation where it needs to just answ...
Hi All, We have a CMS cluster and one of the devices developed a h/w fault and was RMA'd. The replacement came with 2.1 s/w and was upgraded to 2.5.3 and a backup was restored. The device was sitting in our office during our COVID lockdow...