Cisco Jabber for Android client is officially supported only in the below Android mobile phones.
Android Device Requirements
Cisco Jabber for Android supports Audio and Video Enabled mode in the following devices with respective version of Operating System provided in the table:
|
Device |
Device Model |
Operating System |
|---|---|---|
|
Cisco DX |
70 |
10.2.x version |
|
80 |
10.2.x version |
|
|
650 |
10.2.x version |
|
|
HTC |
One M7 |
Android OS 4.4.2 or later |
|
One M8 |
Android OS 4.4.2 or later |
|
|
One Max |
Android OS 4.4.2 or later |
|
|
Google Nexus |
5 |
Android OS 4.4 or later |
|
6 |
Android OS 5.0.2 or later |
|
|
7 |
Android OS 4.4 or later |
|
|
9 |
Android OS 5.0.2 or later |
|
|
10 |
Android OS 4.4 or later |
|
|
LG |
G2 |
Android OS 4.2.2 or later |
|
G3 |
Android OS 4.4.2 or later |
|
|
Motorola |
Moto G |
Android OS 4.4.2 or later |
|
Moto MC40 |
Android OS 4.1.11 |
|
|
Samsung Galaxy |
Note II |
Android OS 4.2 or later |
|
Note III |
Android OS 4.3 or later |
|
|
Note IV |
Android OS 4.4.4 or later |
|
|
Note Edge |
Android OS 4.4.4 or later |
|
|
Note Pro 12.2 |
Android OS 4.4.2 or later |
|
|
Rugby Pro |
Android OS 4.2.2 or later |
|
|
SII |
Android OS 4.1.2 or later |
|
|
SIII |
Android OS 4.2.2 or later |
|
|
S4 |
Android OS 4.2.2 or later |
|
|
S4 mini |
Android OS 4.2.2 or later |
|
|
S5 |
Android OS 4.2.2 or later |
|
|
S5 mini |
Android OS 4.2.2 or later |
|
|
Tab 3 8-inch |
Android OS 4.4 or later |
|
|
S6 |
Android OS 5.0.2 or later |
|
|
S6 Edge |
Android OS 5.0.2 or later |
|
|
Tab 4 7-inch, 8-inch, and 10.1-inch |
Android OS 4.4.2 or later |
|
|
Tab PRO 8.4-inch and 10.1-inch |
Android OS 4.4.2 or later |
|
|
Tab S 8.4-inch & 10.5-inch |
Android OS 4.4.2 or later |
|
|
Note 10.1-inch 2014 Edition |
Android OS 4.4.2 or later |
|
|
Sony Xperia |
M2 |
Android OS 4.3 or later |
|
Z1 |
Android OS 4.2 or later |
|
|
Z2 |
Android OS 4.4.2 or later |
|
|
Z2 tablet |
Android OS 4.4.2 or later |
|
|
Z3 |
Android OS 4.4.2 or later |
|
|
ZR/A |
Android OS 4.1.2 or later |
|
|
Z3 Tablet Compact |
Android OS 4.4.4 or later |
|
|
Huawei Ascend |
G6 |
Android OS 4.2.2 or later |
|
Mate 7 |
Android OS 4.4 or later |
|
|
Sonim |
XP7 |
Android OS 4.4.4 |
|
Xiaomi |
4 |
Android OS 4.4 or later |
Click here to view the list in J4A 11 release notes
Please refer the latest release notes for the updated list.
IM and Presence works fine in all Android phones, however Phone service fails to register in many unsupported Android Phones.
But I have noticed that the softphone works well in many unsupported phones if we change the device security mode to secure. Please find the below steps to enable secure profile in CUCM.
========================================================
There are two ways for changing CUCM cluster to mixed mode.
a) Using CTL Tokens which are bought from Cisco
b) Using CTL keys generated from CUCM CLI (CUCM v10.5 onwards support this)
1) Using CTL Tokens which are bought from Cisco
Link to CUCM Security Guide
Step1:Configure CUCM as Mixed mode, creates a CTL file using the Cisco CTL Client.
Step1.1 CTL client can be downloaded from CUCM —> Application —> Plugins
Once it's downloaded, double-click on the file to install it on a PC.
Step1.2 Run the CTL client.
During the process, a prompt will be displayed that states that one of the keys must be plugged into the computer. Once information has been copied to and from the key, a prompt will state that the first key must be removed and the other key must be plugged into the computer. If you have two USB ports on the computer DO NOT insert both keys at the same time. If, at any point, a password is requested for the key, then note that the default is “Cisco123” (case sensitive). Note: If at any time another individual set a different password for the keys, do not guess what that password may be. After 15 wrong attempts at guessing the password, the key locks and nothing will unlock it (this is part of the reason the keys come in pairs). If both keys get locked, another pair of keys must be obtained from Cisco.
Step1.3 Restart CUCM Server after installation.
2) Using CTL keys generated from CUCM CLI(CUCM v10.5 onwards support this)
Link to CUCM Security guide
Through the CLI, you can manage the cluster security mode without using the Cisco CTL Client.
Consider the following points:
- With this option, the CTL file is generated using a CLI instead of through the Cisco CTL Client.
- No hardware tokens are required.
- The CTL file is signed using the CallManager certificate private key.
The following command needs to be issued in the CUCM Publisher node.
utils ctl set-cluster mixed-mode
This command updates the CTL file and sets the cluster to mixed mode.
After performing Steps 1 or 2
Perform CUCM Server restart,
now, Go To: CUCM => System => Enterprise Parameters => Security Parameters
If "Cluster Security Mode" is 1, this means that the CUCM node is now operating in mixed mode.
Step3: Configuring android secure profile
Configure android secure profile and Device Security Mode is "Encrypted" or "Authenticated" and Transport Type is "TLS”.
Go To: CUCM => System => Security => Phone Security Profile
Step4: Applying the secure profile in device
Apply the secure profile "Cisco Dual Mode for Android encrypted null string" to the Android BOT account. Make sure Certificate Operation is "Install/Upgrade", then Jabber will download the Certificate while firstly login.
Go To: CUCM => Device => Phone => Choose BOT account
