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
We are low on extensions and licenses so if some one has not used their 7925g or 8821 in 90 days we will take that extension. Is there a better way to find out how many days an endpoint is inactive for than entering in the MAC one by one in ISE and then f...
For CUCM the document below has a list of "Recommended Ciphers" that can be set up From Cisco Unified OS Administration, choose Security > Cipher Management.https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/security/12_5_1SU3/cucm_b_security_gui...
Sometimes you want to use Wireshark to capture packets On Cisco Meeting Server to troubleshoot and investigate video call issues, quality issues, or may be Expressway integration, WebRTC Connections, or why not, understand how the communication and the ca...
When we talk about Stun Protocol used for NAT traversal in voip environment, the common term used when talking about the Type of NAT that is compatible with Stun is “Full Cone NAT”, then when we explain why Turn Protocol is developped to replace Stun Prot...