This topic describes how different mobile devices are added in Cisco Unified Communications Manager.
To add Cisco Jabber on a mobile device, add the following in Cisco Unified Communications Manager:
- Device name must be all capitalized
|Device Hosting Cisco Jabber||Device to Add in Unified Communications Manager||Naming Convention|
|iPhone||Cisco Dual Mode for iPhone||TCT+NAME|
|iPad||Cisco Jabber for Tablet||TAB+NAME|
|Android||Cisco Dual Mode for Android||BOT+NAME|
To add Cisco Jabber for Mobile in Cisco Unified Communications Manager, you must select the correct device depending on the hardware that you want to support. If you want to add an iPad, for example, you must add the device Cisco Jabber for Tablet. The name of the device has to start with TAB plus the name in all capital characters—for example, TABJDOE. The table shows the other devices and naming conventions for iPhone and Android devices.
Cisco Jabber User Configuration XML File
This topic describes how to create the Cisco Jabber XML configuration file.
Service profiles do not provide access to all settings.
- Download the Cisco Jabber configuration file.
- Keep the XML file simple.
- Only specify things you need.
- Do not specify default values.
Download the Jabber Config File Generator at https://supportforums.cisco.com/docs/DOC-25778 to create a new XML configuration file.
If the Service Profile does not provide access to the settings, the client will download the jabberconfig.xml file. You can view the current jabberconfig.xml file at http://<Unified-CM-IPaddress>:6970/jabber-config.xml.
The Jabber configuration file provides an increasing number of customization settings, including the following:
- Enable persistent chat
- Enable URI dialing
- Load on operating system start
- Docked window
- Enable screen capture
- File transfer controls
- Enable video
- Enable chat history
Cisco Jabber Configuration Sources
This topic describes how Cisco Jabber builds its operating configuration files.
- During start-up, Cisco Jabber clients will take configuration information from multiple sources.
- Cisco Jabber builds a local configuration that is populated from different sources.
- Configuration sources have different priorities, with the service profiles as the highest priority.
The Cisco Jabber operating configuration is built from different configuration sources. The configuration can also be created at the parameter level:
- LDAP host from jabber-config.xml
- LDAP user ID from the service profile
- LDAP password from the service profile
Consider the following when deploying Cisco Jabber:
- Clients that are running service discovery currently check for the Cisco Unified Communications Manager IP Phone (CCMCIP) profile on the Cisco Unified Communications IM and Presence server. If the profile does not exist, then telephony is disabled in the client. Create a CCMCIP profile or CTI profile for softphone and deskphone mode users. The CTI profile is the only option if the client is running in phone-only mode.
- All Cisco Jabber clients use Voicemail Representational State Transfer (VMREST) for access to Cisco Unity Connection. VMREST does not use a mailstore. However, Cisco Jabber will enable voicemail only if both the mailstore and voicemail profiles are defined.
- Service profiles have higher priority than the Jabber XML file.
As of Cisco Jabber version 10.6, you can delete all locally cached information using the client menu option: File > Reset Cisco Jabber.
To delete all local cached information for earlier versions of Cisco Jabber, on a Microsoft Windows system, go to the following Cisco Jabber installation folders:
C:\Users\<username>\AppData\Local\Cisco\Unified Communications\Jabber\CSF C:\Users\<username>\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF
If there is a Jabber folder, delete it to clear all locally cached information.
For different operating systems and versions, the folders to cache configuration information may be found in other locations.