Contents

• Troubleshooting
• Verify connection status
• Obtain logs from Cisco Jabber
• Troubleshooting tips
• Setup issues
• Unable to create Cisco Jabber device in Unified CM
• Cisco Jabber registration fails
• Cisco Jabber cannot connect to Unified CM
• Directory server handshake error
• Changes to the device page do not take effect
• Changes to dial rules do not take effect
• Device icon is missing
• Device issues
• Cannot complete calls
• Unable to receive calls in Cisco Jabber
• Calls incorrectly sent to voicemail
• Unable to send calls to mobile device
• Unable to move calls from the mobile network to Cisco Jabber
• Unable to pick up active call after exiting Cisco Jabber
• Problems with voice quality
• Calls are dropped or interrupted
• Battery drains faster during Cisco Jabber calls
• Search issues
• No directory search
• Incorrect or missing caller identification
• Delayed caller identification
• Searches are slow
• Missing search results
• Voicemail issues
• Problems with voicemail

Troubleshooting

---

The following list describes how to troubleshoot Cisco Jabber.

• For solutions that users can perform without administrator assistance, and for tips and tricks about how the application works, see the user FAQs at http://www.cisco.com/en/US/products/ps11596/products_user_guide_list.html.
• See also the Release Notes for this product at http://www.cisco.com/en/US/products/ps11596/prod_release_notes_list.html.
• Verify the status of the connection to each enterprise server directly from the mobile device.
• For features that are not unique to this product (for example, conferencing or transferring calls):
  • Test the feature on existing configured desk phones. If it works, compare the working device configuration to your Cisco Jabber device configuration.
  • Check the Unified CM documentation for troubleshooting tips. See http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_troubleshoot_and_alerts.html.
• Make sure you entered the correct IP addresses, ports, paths, usernames, and passwords. If you entered hostnames instead of IP addresses, enter the IP address instead.
• If users experience problems that you are unable to solve and you need to contact Cisco for support, have the users send you the client log files that capture the problem. See the following topic about obtaining logs from the client.

• Verify connection status
• Obtain logs from Cisco Jabber
• Troubleshooting tips

Verify connection status

Verify your connection status using your mobile device.

Procedure

---

Step 1	Tap the Cisco Jabber icon to open application.
Step 2	Tap Settings > Troubleshooting > Connection Status.

---

Connection status is displayed.

Connected

Feature is configured and connected properly.

Connecting

Feature is currently making a connection attempt.

Disconnected

Feature is configured but is not currently connected. You might not be properly connected to the Wi-Fi or the server might be down.

Error

Feature is not currently configured or connected. You might have entered an incorrect password.

Unknown

Feature status is unknown. Contact your system administrator to verify your account settings.

Obtain logs from Cisco Jabber

Have the user follow this procedure to send you logs from Cisco Jabber.

Procedure

---

Step 1	Launch Cisco Jabber from your mobile device.
Step 2	Tap Settings > Troubleshooting.
Step 3	Set Detailed Logging to On.
Step 4	Try to reproduce the problem to capture the details in the logs.
Step 5	Tap Settings > Troubleshooting > Problem Reporting. If Cisco Jabber fails to register, tap About > Troubleshooting > Problem Reporting instead.
Step 6	Select the files to include. If you are not sure which files to include, include all files.
Step 7	Tap Email Problem Report.
Step 8	Enter the email address of a recipient such as yourself.
Step 9	Describe the problem in the body of the email message.
Step 10	Tap Send.

---

What to Do Next

Be sure the user sets Detailed Logging to Off when no longer needed.

Troubleshooting tips

Setup issues

Unable to create Cisco Jabber device in Unified CM

Problem    The user’s device type is not available as an option.

Solution    Make sure that you uploaded the device COP file and restarted Unified CM. See Install Cisco Options Package file for devices.

Cisco Jabber registration fails

Problem    Cisco Jabber registration fails or times out.

Solution    The following list describes different possible causes for and solutions to registration failure or timeout conditions:

• Have the user check the troubleshooting tips in the FAQs for users at http://www.cisco.com/en/US/products/ps11596/products_user_guide_list.html.
• Verify that the phone can reach Unified CM: Try using the browser on the phone to connect to the Unified CM Administration portal.
• If registration is rejected with error 503, go to the Cisco Dual Mode for iPhone device page in Unified CM and select Reset, and then try again.
• Make sure your DNS server can resolve the hostname of the Unified CM server that is used as the TFTP server address.
• Enter the IP address instead of the hostname of the Unified CM server into the TFTP Server Address setting in Cisco Jabber.
• Registration failure with the error message "Verification Timed Out" indicates that you did not reboot all Unified CM servers in the cluster after you installed the device COP file. Make sure you reboot all Unified CM servers after you install the device COP file.
• Make sure you have enough licenses to accommodate your deployment.
• If you are attempting to connect over VPN:
  • Verify that the phone can reach internal resources independently of Cisco Jabber: Try accessing an intranet web page or other resource behind the firewall.
  • If your Cisco Jabber deployment includes Directory Services, try accessing the directory from within Cisco Jabber.
  • If the phone is unable to connect over VPN, contact the provider of your VPN technology for assistance.
• If you enabled SIP digest authentication, make sure you entered the credentials correctly.

Related Tasks

Install Cisco Options Package file

Cisco Jabber cannot connect to Unified CM

For deployments in which Cisco Jabber is coresident on the iPhone with the Cisco Unified Mobile Communicator client (also known as 7.1) that runs in conjunction with a Cisco Unified Mobility Advantage server.

Problem    After you change the device pool that is associated with the Mobile Identity, Cisco Jabber can no longer connect to Cisco Unified CM.

Solution    Have the user exit both client applications, and then relaunch the client application that runs in conjunction with a Cisco Unified Mobility Advantage server before launching this Cisco Jabber application.

Directory server handshake error

Problem    When the client attempts to connect to the directory server, the connection fails with an SSL Handshake error.

Solution    Change the Enable LDAP SSL setting on the device page in Unified CM and relaunch the application.

If you have allowed end-user configuration editing on the client, delete the directory account in Cisco Jabber and set it up again.

Changes to the device page do not take effect

Problem    Changes in the Product Specific Configuration Layout section of the Cisco Dual Mode for iPhone device configuration page in Unified CM are not taking effect on the client.

Try one of the following:

• See the description earlier in this document for the Allow End User Configuration Editing setting on the Cisco Dual Mode for iPhone device page for important information about making changes to settings.
• If you have allowed end-user configuration editing, delete the relevant account on the client and then set up the account again.

Related Tasks

Add user device

Changes to dial rules do not take effect

Problem    Changes to the Application Dial Rules or the Directory Lookup Rules in Unified CM are not taking effect.

Solution    Run the COP file again to make the changes available to Cisco Jabber, and then restart the TFTP service. The updated rules will be available to Cisco Jabber the next time the user restarts the application. See Use of dial rules with Cisco Jabber.

Device icon is missing

Problem    The device icon in the Unified CM Administration pages does not appear.

Solution    Try the following:

1. Restart the Tomcat service as described in Install Cisco Options Package file for devices.
2. Reload the device page in your browser.
3. Clear the browser cache if necessary.

Device issues

Cannot complete calls

Problem    Numbers that should be dialable cannot be connected. Users hear a network busy tone or error message.

Solution    Try the following:

• If you made changes to the Application Dial Rules, make sure you ran the COP file to make the changes available to Cisco Jabber, and that you restarted the TFTP service.
• If you modified the dial rules and specified an alternate location for the dial rules in the Product Specific Configuration Layout section on the device page, make sure that you updated the custom file before you restarted the TFTP service.
• Make sure that you set the Call Forward Unregistered settings on the device page.

Unable to receive calls in Cisco Jabber

Problem    An incoming call arrives briefly in Cisco Jabber while it is running, but then the call is terminated and diverted to the native mobile phone number using Mobile Connect instead.

Solution    In Unified CM, set the SIP Dual Mode Alert Timer as described in Increase SIP Dual Mode Alert Timer value.

Calls incorrectly sent to voicemail

Problem    Calls are routed directly to voicemail.

Solution    In Unified CM, modify the call timer values on the Mobile Identity page. For more information see Add Mobile Connect and Mobile Identity.

Unable to send calls to mobile device

Problem    User cannot send an active call from Cisco Jabber to the mobile phone number.

Solution    Try one of the following:

• Verify that Mobile Connect works by exiting Cisco Jabber and dialing the extension. If you hear a fast busy signal, make sure you entered the Mobility Identity phone number in a routable format.
• In Unified CM, adjust the call timers on the Mobile Identity page. See the online help in Unified CM for more information. Make sure that the No Answer Ring Duration on the Primary DN page is greater than the value you specified for Answer Too Late Timer on the Mobile Identity page.

Note

The Answer Too Late Timer starts when Unified CM receives an acknowledgment from the mobile network that the call was accepted. Some mobile networks subsequently send a separate alert that the dialed number is ringing; in those cases, the Answer Too Late Timer restarts when Unified CM receives that alert.

To test this for a particular mobile device, dial the mobile phone number (the mobile network) from an office phone and track the amount of time that passes between the time you dial the last digit and the time the call goes to voicemail.

If you increase the No Answer Ring Duration, see related cautions for this setting in the online help in Unified CM.

Unable to move calls from the mobile network to Cisco Jabber

Problem    User is unable to transfer a call from the mobile network to Cisco Jabber.

Solution    Users can transfer calls to the mobile network from Cisco Jabber, but not in the other direction.

Unable to pick up active call after exiting Cisco Jabber

Problem    When users exit Cisco Jabber during an active call, they should be able to retrieve the call when they relaunch Cisco Jabber, assuming the other person is still on the call. If users are unable to retrieve the parked call, it may have timed out.

Solution    In Unified CM, increase the park timeout time. See information about the " Park Monitoring Forward No Retrieve Timer" in the Cisco Unified Communications Manager Features and Services Guide, http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.

Problems with voice quality

Problem    Voice quality is poor.

Solution    Voice quality cannot be guaranteed because of variable network conditions.

However:

• For actions the user can take, see the FAQs for users at http://www.cisco.com/en/US/products/ps11596/products_user_guide_list.html.
• For general information about optimizing your corporate Wi-Fi network for voice transmission, see the "Network Requirements" section of the Release Notes for Cisco Jabber at http://www.cisco.com/en/US/products/ps11596/prod_release_notes_list.html.

Note	Because network issues outside your enterprise are neither under the control of nor specific to Cisco Jabber, the Cisco Technical Assistance Center (TAC) does not troubleshoot these issues.

Calls are dropped or interrupted

Problem    Calls are unexpectedly dropped or interrupted.

Note	Bluetooth headsets may worsen these problems.

Solution    Because Bluetooth-related issues and network issues outside your enterprise are neither under the control of nor specific to Cisco Jabber, Cisco TAC does not troubleshoot these issues.

• For actions the user can take, see the FAQs for users at http://www.cisco.com/en/US/products/ps11596/products_user_guide_list.html.
• If these problems are frequent while users are on the corporate premises, make sure your Wi-Fi meets the network requirements that are specified in the Release Notes at http://www.cisco.com/en/US/products/ps11596/prod_release_notes_list.html.

Battery drains faster during Cisco Jabber calls

Problem    The device battery seems to drain more quickly during Cisco Jabber calls than during standard mobile calls.

Solution    VoIP calls may use slightly more battery power than standard mobile calls. For actions the user can take, see the FAQs for users at http://www.cisco.com/en/US/products/ps11596/products_user_guide_list.html.

Search issues

No directory search

Problem    Directory search and caller identification are not available.

Solution    If you do not enter an IP address for a directory server in the device page in Unified CM, Cisco Jabber does not include Directory Services. Enter this information, save and reset the device, and then relaunch Cisco Jabber.

If you have allowed end-user configuration editing, delete the Directory account in Cisco Jabber, and then add it again.

Incorrect or missing caller identification

Problem    Some callers are not identified correctly.

Solution    Consider the following:

• When you add users or change user information in Microsoft Active Directory, correct identification of callers in Recents or Voicemail in Cisco Jabber may take up to 24 hours. This delay minimizes synchronization activity that could affect performance.
• If a number does not match a contact using Directory Lookup Rules, Cisco Jabber displays the phone number as passed by Unified CM, unmodified by any Directory Lookup Rules.
• If you have made changes to the Directory Lookup Rules, make sure you have run the designated COP file to make those changes available to Cisco Jabber, and then restarted the TFTP service.

Related Information

Use of dial rules with Cisco Jabber

Delayed caller identification

Problem    Users experience delays in identifying callers, dialed numbers, and voice messages, when caller contact information comes from the corporate directory.

Solution    Verify that LDAP port settings are correct in the Product Specific Configuration Layout section of the Device page in Unified CM.

Searches are slow

Problem    Search results are returning slowly.

Solution    Verify that LDAP port settings are correct in the Product Specific Configuration Layout section of the Device page in Unified CM.

Missing search results

Problem    Directory search does not find known employees.

Solution    If you have made changes to the Directory Lookup Rules, make sure you have run the designated COP file to make those changes available to Cisco Jabber, then restarted the TFTP service.

Related Information

Use of dial rules with Cisco Jabber

Voicemail issues

Problems with voicemail

Problem    User repeatedly receives "Incorrect username or password" error when attempting to access voicemail.

Solution    Check the voicemail server to determine the user account is locked as a result of too many incorrect attempts to sign in.