Use your working setup as a template for setting up devices for
See Bulk Configuration.
Send an email message with the information that users need to set
up Cisco Jabber.
The settings you
entered on the device page in Unified CM are
automatically entered into the application on the device. Users enter
passwords as applicable. Point users to the FAQs in the Cisco Jabber for Android user guide list.
You need the following files to set up and use Cisco Jabber.
You can collect them all now or obtain them when you are ready to use them.
Table 1 Required Files for all Cisco Unified
Communications Manager Releases
Locate and download cmterm-android_9.1.1v1.cop.sgn.
Cisco Jabber application for your device
Use the Google Play application (formerly known as Google Android Market) on your device to obtain the Cisco Jabber for Android application. Search for "Jabber"
on Google Play.
Table 2 Additional Required Files for Cisco Unified Communications
Manager Release 8.5 and Earlier
To Obtain This File, See
Cisco Options Package (COP) file required to make Application Dial Rules available to
This file is required for Unified CM 8.5 and earlier. For Unified CM 8.6 and later, the Application Dial Rules are integrated into the application, so you do not need to install an additional COP file to see the applicable fields.
Cisco Jabber for Android uses the same COP file as Cisco UC Integration for Microsoft Office
Communicator to make Application Dial Rules available.
Go to the
Software Downloads page for
Cisco UC Integration for Microsoft Office
Communicator. Download and unzip the Administration Toolkit bundle. Within this bundle, you need only the following file: cmterm-cupc-dialrule-wizard-0.1.cop.
To make Cisco Jabber available as a device in Unified CM, you must install a
device-specific Cisco Options Package (COP) file on all your Unified CM servers.
If you upgrade your Unified CM, you may need to reinstall the COP file to retain the correct version. To verify if you have the correct COP version, see Verify device COP file version.
Perform this procedure at a time of low usage; it can interrupt service.
General information about installing COP files is available in the
"Software Upgrades" chapter in the Cisco Unified Communications
Operating System Administration Guide for your release, available from the maintenance guides list.
Note the MD5 checksum.
You will need this information later.
Proceed with Download and follow the
Place the COP file on an FTP or SFTP server that is accessible
from your Unified CM servers.
Install this COP file on the Publisher server in your Unified CM cluster:
From the Navigation list box in the top-right corner of the
Unified CM Administration portal, choose
Cisco Unified OS Administration and select
Upgrades > Install/Upgrade.
Specify the location of the COP file and provide the required
For more information, see the online help.
Select the device COP file.
Follow the instructions on the screen.
Wait for the process to complete. This process can take
Reboot Unified CM at a time of low
Let the system fully return to service.
To avoid interruptions in service, make sure each server returns to active service before you perform this procedure on another server.
Install the COP file on each Subscriber server in the cluster.
Use the same process you used for the Publisher, including
rebooting the server.
Verify Device COP File Version
Use the following procedure to verify that you are using the correct device COP file for this release of Cisco Jabber.
Sign in to the Unified CM Administration portal.
Choose Device > Phone.
Click Add New.
From the Phone Type drop-down list, choose Cisco Dual Mode for Android.
Scroll down to the Product Specific Configuration Layout section, and verify that you can see the Dial via Office drop-down list.
If you can see the Dial via Office drop-down list, the COP file is already installed on your system.
If you cannot see the Dial via Office drop-down list, locate and download the correct COP file. For more information, see Required Files.
Dial Rules Setup
Application Dial Rules
Because people are accustomed to dialing numbers differently
from a mobile device than from a desk phone, consider setting up Unified CM to accommodate the different number patterns
that mobile device users dial.
You can create these rules in Unified CM so that they apply to all calls and devices; or edit an XML file,
described later, so that the rules apply only to users of Cisco Jabber or so
that different rules apply to devices in different countries or area codes.
For example, users sometimes dial numbers as follows:
Mobile device users may not be in the habit of dialing 9 before
they dial a number outside the company.
If the mobile device number is in a different area code than the
desk phone number, users may dial area codes when using their mobile device even though
they do not include the area code when dialing from work phones, and vice
Mobile device users who dial an international number sometimes begin the
number with a plus sign (+).
You can set up Application Dial Rules to successfully
connect the types of calls that are described in these examples.
For complete information about setting up Application Dial
Rules, see the online help in Unified CM.
Use of Dial Rules with Cisco Jabber
Perform this series of procedures to make all your existing
dial rules available to Cisco Jabber.
These procedures apply only to Unified CM
Release 8.5 and earlier. For Unified CM 8.6 and later, the Application Dial Rules are integrated into the application, so you do not need to install an additional COP file to see the applicable fields. You can access the Application Dial Rules settings in Unified CM 8.6 and later by choosing Call Routing > Dial Rules > Application Dial Rules. For information about Application Dial Rule setup, see the related chapter in the Cisco Unified Communications Manager Administration Guide for your release, available from the Unified CM maintenance guides list.
The COP file that you use for dial rules is different than the device COP file that is described
elsewhere in this document.
Other Cisco products can use this same COP file for dial rules.
With this series of procedures, you install required XML files in a
CUPC at the root level of the Unified CM TFTP server. If you need different rules for Cisco
Jabber than you need for other clients that use this file, use the optional procedure to
copy and modify the XML file to create a dedicated file for Cisco Jabber.
If you set up other Cisco telephony clients and
integrations, you may have performed this series of procedures already.
Every time you update the dial rules on Unified CM, you must repeat this series of procedures to make the changes
available to clients, including Cisco Jabber.
Cisco Jabber for Android uses the same COP file as Cisco UC Integration for Microsoft Office Communicator to make Application Dial Rules available.
Next to the Administration Toolkit bundle, click
Follow the instructions on the screen.
Unzip the downloaded file.
Locate the following dial rules COP file in the
CUCM folder: cmterm-cupc-dialrule-wizard-0.1.cop.sgn.
You do not need any other files in this download.
Place the dial rules COP file on a server that is accessible by
FTP or SFTP.
Copy Dial Rules
Use this procedure to create copies
of dial rules in the Unified CM application.
Sign in to the Publisher server in your Unified CM cluster.
In the top-right corner of the Unified CM Administration portal, choose Cisco
Unified OS Administration and select
Software Upgrades > Install/Upgrade.
Specify the location of the
Dial Rules COP file in the
Software Installation/Upgrade window.
Available Software drop-down list, select the
Repeat this procedure for every Unified CM server that runs a TFTP server.
Locate Copy of Dial Rules
the Cisco Unified Operating System Administration
Software Upgrades > TFTP
TFTP File Management window, search for a
directory that begins with CUPC.
Verify that the dial rules are present.
Modify Dial Rules
Use this optional procedure only if you want to modify the dial rules file for use by Cisco
Jabber. For example:
You may require rules that
are unique to Cisco Jabber and are not used for other clients.
You may need to create
multiple files and assign different rules to the Cisco Jabber device of each
user. One example is if users have mobile devices that are issued in different
countries or area codes, and your existing rules do not accommodate
the way users may dial numbers from mobile devices based in multiple
countries or area codes.
Cisco Unified Communications Manager Operating System
Administration Guide. See the instructions for managing TFTP server files in the
“Software Upgrades” chapter.
Command Line Interface Reference Guide for Cisco Unified
Navigate to the
CUPC folder at the root level of the Unified CM TFTP server.
Copy the rules file you want to modify for Cisco Jabber.
Example:Using the built-in TFTP client on a PC or
Mac, enter the following commands:
Rename the file as needed.
Open the file in a text editor.
Following the example of the existing rules, modify or add rules
Save your changes.
Upload the modified file.
Note the path and filename. You will need this information
From the drop-down list at the top-right corner of the window, select Cisco
Unified OS Administration.
Software Upgrade > TFTP File Management.
Select the file on your hard drive.
Specify the folder on the TFTP server.
Repeat this procedure for any other rules files that you need to customize.
What to Do Next
After you complete and upload all customized dial rules
files, continue with the next procedure in this section.
If you use Unified CM 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.
If you move or rename these files, make sure you update
this path in the Application Dial Rules URL field
on the configuration page for each deployed device.
Restart TFTP Service
Perform this procedure at a time of low usage; it can
For more information, see
"Starting, Stopping, Restarting, and Refreshing Status of Services in
Control Center" in the
Cisco Unified Serviceability Administration Guide in the maintenance guides list.
In the top-right corner of the Unified CM Administration portal, choose Cisco Unified Serviceability and select
Tools > Control
Choose the server and select
Repeat this procedure on every server on which you ran this Application Dial Rules COP
Increase SIP Dual Mode Alert Timer Value
Increase the SIP Dual Mode Alert Timer value to ensure that calls
to the Cisco Jabber extension are not prematurely routed to the mobile-network
Before You Begin
Cisco Jabber must be running to receive work calls.
Sign in to the Unified CM Administration portal.
System > Service
Select the server.
Cisco CallManager (Active) service.
Scroll to the
Clusterwide Parameters (System - Mobility)
Increase the SIP Dual Mode Alert Timer value to 4500 milliseconds.
If, after you increase the SIP Dual Mode Alert Timer value, incoming
calls that arrive in Cisco Jabber are still terminated and diverted using Mobile
Connect, you can increase the SIP Dual Mode Alert Timer value again in increments of 500 milliseconds. The 4500 millisecond value is the lowest recommended value.
Create Dedicated SIP Profile
Create a dedicated SIP profile that allows Cisco Jabber for Android to
stay connected to Unified CM while Cisco Jabber
for Android is running in the background.
In Unified CM, select
Device > Device
Settings > SIP Profile.
Create a new SIP profile, or copy an existing SIP profile.
In the new SIP profile, set the following values:
Register Delta to
Register Expires to
Keep Alive Expires to
Subscribe Expires to
Subscribe Delta to
Save the changes.
Device > Phone
and select the device that you want to configure.
Protocol Specific Information section, change
the SIP profile to the profile you just created.
Save and then select
What to Do Next
Select this SIP Profile for all Cisco Dual Mode for Android
devices that are running Cisco Jabber for Android.
Make sure your system meets the following prerequisites:
Standard SIP and phone features such as the following are set up and
working independently of Cisco Jabber for Android:
Music on hold
Music for network hold
Cisco Jabber for Android does not support Multicast Music on Hold. Ensure that the Media Resource Group List that you apply to the Cisco Jabber for Android device does not contain multicast-enabled Media Resource Groups.
Midcall features are set up and working, including:
Add a call
The ability to handle RFC 2833, Key Press Markup Language
(KPML), and dual-tone multifrequency
(DTMF) tones for IVR
call routing, allowing users to use the keypad to route to the correct extension
Conferencing functionality is set up and working. The functionality varies, depending on your system setup.
If you use software-based conference bridges, all
participating endpoints must use G.711.
If you use hardware-based conference bridges that use
digital signaling processing (DSP), participants can use either G.711 or G.729. The hardware-based conference bridge does
not require a transcoder to provide this functionality.
Usage and Error Tracking
Cisco Jabber relies on a third-party service, Google
Analytics, to collect and generate aggregated usage and error-tracking data
that Cisco uses to discover defects and improve product performance. In
compliance with the Google Analytics privacy statement, Cisco does not store
personal identifying information.
All information that Google Analytics stores and collects is
confidential. Only Cisco has access to this information. This functionality is
not currently available as a reporting tool for administrators.
You can enable or disable usage reporting for each user when
you set up each Cisco Jabber device in Unified CM.
Depending on the setting, Cisco collects the following
Table 3 Usage and Error Tracking
Usage and Error Tracking Setting
Screen views in
Cisco Jabber (for example, how often users view their list of voice messages)
(for example, how often users add a contact)
IP address of the TFTP server to which Cisco Jabber connects
geographic location, based on mobile service provider activity
The first time users open Cisco Jabber, they see an
agreement that describes the data that Cisco collects. Users must accept this
agreement to use the application, whether or not the usage tracking
feature is currently enabled.
For more information about the reporting tool, see: