Showing results for 
Search instead for 
Did you mean: 
Rising star
Rising star



This document describes the steps required to configure Cisco Jabber on CUCM.




CUCM 8.x

Jabber for Android 8.6




Perform the following procedures in order


  • Set up and test voicemail for the extension you will assign to this device, following standard procedures for any device. Make sure you set up the voicemail number as a regular phone number so users can call in to the voicemail system using an Enterprise VoIP or mobile call.


  • Verify that the Device Pool that you will assign to the Cisco Jabber device is associated with a region that includes support for the G.711 codec.


  • Determine whether you want to enable or disable usage and error tracking for each user.



Steps to configure Jabber on CUCM



Step 1   Login in to Cisco Unified Communications Manager Administration.



Step 2 Goto Device-> Phone and  Add a new phone device with Cisco Dual Mode for Android as the Phone Type.





Step 3            Enter settings for Device-Specific Information.



a. Enter the Device Name. The Device Name:


  • Must be uppercase
  • Must start with BOT


  • Can contain up to 15 characters
  • Can include only the following characters: A to Z, 0 to 9, dash (-), or underscore (_)



We recommend that the device name include the username of the user so it is easily remembered. 


For example the device name of user jsmith would be BOTJSMITH.



b. Choose Standard Dual Mode for Android for the Phone Button Template.



c. Configure the following settings to prevent confusion for the person the user calls.


  • Media Resource Group List
  • User Hold MOH Audio Source
  • Network Hold MOH Audio Source



d. Choose desk phone as the Primary Phone if the user has a desk phone.


Step 4  Enter settings for Protocol Specific Information.


In the Device Security Profile drop-down list, select Cisco Dual Mode for Android - Standard SIP Non-Secure Profile.





In the SIP Profile drop-down list, select the appropriate SIP profile.





Values that are not described in this document are not specific to Cisco Jabber but may need to be entered for the device to work properly.



Step 5  Enter settings for the Product Specific Configuration Layout section.



a. Select the appropriate level of usage tracking in the Cisco Usage and Error Tracking drop-down list. See Usage and error tracking


b. In the Application Dial Rules URL field:-


  •    For Cisco Unified Communications Manager Release 8.6 and later, leave this field blank.


  • If you are using Cisco Unified Communications Manager Release 8.5 or earlier and you want Cisco Jabber devices to apply Application Dial Rules, you must specify the path to these dial rules files, including the filenames. Use the following format: tftp://ip address of TFTP server/pathname to the XML file/XML filename.


c. If your directory server requires authentication, enter LDAP username and password; otherwise leave these fields blank.


These credentials can be for a single read-only account for all users. These credentials are sent to the client in clear text in the TFTP file. Therefore, we strongly recommend that LDAP directory administrators generate a directory query account that has no other rights. Create this account with a value that is low enough to ensure that its credentials are semi-public (available to anyone on the local network).


d. Enter any designated emergency numbers in the Emergency Numbers field.


You can enter a comma-separated list of additional emergency numbers that will always be dialed direct for this user. These numbers must contain only numerical digits. No spaces, dashes, or other characters are permitted.


Emergency numbers as defined on the device are always dialed direct using the mobile network (never dialed using Enterprise VoIP) to allow the location of the caller to be sent automatically to emergency services personnel where this service is available. Direct-dial numbers can be useful for users who frequently travel to countries other than the country of their mobile network provider, if the emergency number differs depending on the users' location, or if your company has a dedicated security number.


e. Enter your domain in the Domain Name field if the Cisco Unified Communications Manager setting in System > Server is a hostname that does not include the domain name.


f. Enter a list of up to three SSIDs separated by forward slashes (/) in the Preset Wi-Fi Networks field.


Cisco Jabber attempts to connect to Cisco Unified Communications Manager only after the mobile device is connected to an SSID that you list here, or one that the user selects in the client. Cisco Jabber must be able to reach Cisco Unified Communications Manager when it is connected to these SSIDs. Typically, these are your corporate Wi-Fi SSIDs. SSIDs can be up to 32 characters long and are case-sensitive.


Step 6  Select Save.


Step 7  Select Apply Config.


Step 8  Select [Line n] - Add a new DN.


Step 9 Enter the Directory Number of this device.


This can be a new DN; a desk phone with the same DN is not required.


Step 10 If this device is a standalone device (not sharing a DN with a desk phone), configure these settings to forward calls when Cisco Jabber is not running and connected to the network, so callers do not receive an error message:


Forward Unregistered Internal

Forward Unregistered External


Step 11  Set the No Answer Ring Duration to 24 seconds to allow time for Cisco Jabber to ring before calls go to voicemail.



Step 12  Select Save.


Step 13  Navigate to the User Management -> End User page for the user


Step 14  Associate the Cisco Dual Mode for Android device that you just created for this user.



The device should now appear in the Controlled Devices box in either the Device Information or Device Associations section (depending on your release of Unified CM).



Step 15  If this user has a desk phone, select the desk phone as the Primary User Device.


Step 16  If the device is a standalone device that runs without an associated desk phone, you may need to enter other information that is standard for all devices in your system.



Test your configuration


  • Make sure the mobile device is connected to the corporate network. Verify that you can access a web page on your corporate intranet using the browser on your device.



  • Launch Cisco Jabber and complete the setup wizard. Enter the IP address of your TFTP server (generally the IP address of your Cisco Unified Communications Manager server) and the Device Name (BOTXXXX) of the device you just added.


  • Wait for a notice that the device is registered. The Cisco Jabber icon in the status bar turns black when the device is connected to Cisco Unified Communications Manager.


  • Test basic telephony features in Cisco Jabber, such as the ability to make, hold, and transfer calls.



Changes to user device


If you change settings on the Cisco Unified CM Administration pages (for example, LDAP, call control, dial plan), Cisco Jabber reregisters after you click Save and then click Apply Config. The application reregisters again 30 seconds later. If the user is on a call when the application reregisters, the call drops and the application restarts automatically.



If the device is out of coverage at the time you apply the changes, it is updated when it reregisters to Cisco Unified Communications Manager.

If you delete the device from Cisco Unified Communications Manager, Cisco Jabber drops any active calls and after several reregister attempts the user receives an error message that it cannot connect. Client information is not erased from the device. To remove all client information (for example, if the employee leaves the company), use the appropriate device management solution, such as Active Sync.



Related Links

Cisco Jabber for Android

Configuration example of Jabber for Android


Does Jabber work with CME now?

Rising star
Rising star
Unfortunately,we don't have a solution for Android phones which can be integrated to the CCME.The 
solution for Apple iPhone is supported for the CCME though. 




Is there an update to this document addressing:

- CUCM 9.x

- Jabber for iPhone/iPad (Apple iOS)?


I want the same

Is there an update to this document addressing:

- CUCM 9.x

- Jabber for iPhone/iPad (Apple iOS)?

Please I need this for a long time, i will be very grateful


Unfortunately the Call Forwarding Unregistered does not work in my CUCM 9.1 environment!

When configured - the caller gets a fast busy tone (5 times only) and the call is dropped.


Any suggestions?

Thank you



I followed those steps and my jabber Client is working now
Very helpful with CUCM Version 8.6



Its been an old post but I am facing strange issue related to jabber call transferring:

Jabber windows client (10.5.2) are selected to "Use My Computer for calls" option to make/receive and transfer calls.


User A call User B (windows jabber 10.5.2) to transfer call to User C. When User B call User C from jabber (By default User A should go on hold) but call converts into conference between User A-User B-User C. Not sure why conference is activating automatically. This is happening with Jabber client only.

Transfer is working successful with IP Phones 7821, 7962.

We upgraded Jabber to latest version 11.0 but still facing same issue.

CUCM 10.5.2, IM&P 10.5.2

Any idea ?



Hello Shalushar, Congratulations for your great post !

I want to ask you about the minimal permissions users (group an roles) in order to enable Jabber Windows (Android and iPhone) on UCM.


Hi All,


Could anyone help me, Why Cisco Jabber profile is configured using SIP Protocol? 

Is anything like B2B purpose? or Can we configure using SCCP Protocol!





Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links