This document describes the steps used in order to troubleshoot softphone integration and registration issues with Cisco Unified Personal Communicator (CUPC) and Cisco Jabber for Windows.
Cisco recommends that you have knowledge of these topics:
- Cisco Jabber for Windows
- Cisco Unified Call Manager (CUCM)
- Cisco Unified Presence (CUPS)
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Troubleshoot CUPC and Cisco Jabber for Windows Softphone
On the CUCM Administration page, ensure that you have configured a Cisco Unified Client Service Framework (CSF).
Complete these steps in order to troubleshoot CUPC and Cisco Jabber for Windows softphone:
- Navigate to DEVICE > PHONE > Owner User ID, and ensure that the appropiate user ID is selected. Also, in the line configuration for this device, ensure that you associate this end user under Users Associated with Line. The softphone should be listed as a Controlled Device on the USER MANAGEMENT > END USER page.
- From the CUPS administration page, verify that the device is listed in the Device column on the right side of the PRESENCE VIEWER. TFTP is configured on CUPS under CUPS Admin > Application > Cisco Jabber > Settings. If this is an IM and Presence server version, such as Version 9.x, ensure that you have listed the TFTP option under Application > Legacy Clients > Settings.
- Ensure that the TFTP file download is not blocked on the desktop where CUPC is installed. In order to test this, complete these steps:
- Open the command prompt within Windows, and enter this command:
tftp ?i <tftpipaddress> GET <devicename>.cnf.xmlYou should receive a Transfer Successful message. If no message is received, then the local firewall or security software blocks TFTP. Disable this software and try again.
- If the TFTP test works, then open the <devicename>.CNF.XML file, and verify the CUCM name and if it is configured as HOSTNAME. This is tracked by a search for this field in the XML file:
- Ensure that the HOSTNAME from CUCM is resolvable through the Domain Name System (DNS) IP address that is mentioned in the local area network configuration for this desktop.
- If the softphone registration still fails, collect the standard TFTP server logs and detailed call manager traces - to include the node where this CSF is supposed to register - from the CUCM serviceability page.
- Collect the Problem Report from the CUPC /Jabber for Windows, and a sniffer capture during the attempted softphone registration - spanning the Network Interface Card (NIC) interface of the desktop where this application is installed - from the CUPC logs.