CUCM 10.0(1) and Jabber for Android 9.6.1: unable to set up secure phone capabilities!
we have an UC infrastructure with a CUCM 10.0(1) and a CUP 10.0(1).
Furthermore, we have some Jabber for Android 9.6.1.
We have successfully configured the non-secure devices, by using the "Create BOT Software Phone Devices" section of the "Cisco Jabber for Android 9.6 Server Setup Guide" (http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Android/9_6/JABA_BK_J97FCF70_00_jabber-android-server-setup-9-6/JABA_BK_J97FCF70_00_jabber-android-server-setup-9-6_chapter_0110.html#JABA_TP_CE9D2429_00).
Now, we would like to add the security, by following the "Set Up Secure Phone Capabilities" section of the same document linked above (http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Android/9_6/JABA_BK_J97FCF70_00_jabber-android-server-setup-9-6/JABA_BK_J97FCF70_00_jabber-android-server-setup-9-6_chapter_0110.html#JABW_TK_SD3E22A7_00), but we have an issue.
The weird thing is in the Step 3 of the procedure under the "Configure BOT Devices" section; in fact, we can't find the phone security profile (created in the Step 1 of the "Configure the Phone Security Profile" section) from the "Device Security Profile" drop-down list!
See if there is a default security profile specifically for the Android device type. If there is, copy it and update accordingly. It's possible that you've found a documentation error and the database is looking at BOT as unique from a generic CSF (even though they are the same thing in practical terms).
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...