Jabber Phone mode only changing Default IM client from Skype for Business
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2015 08:45 AM - edited 03-17-2019 05:35 PM
We recently deployed Lync 2013 in our environment as part of a move from Lotus Notes to Microsoft Outlook for email. However, some of our management team like the fact that they can see and play back their voicemails through Cisco Jabber. I installed Cisco Jabber version 9.6.7 using the switch for phone mode only: misexec.exe CLEAR =1 /i ciscojabbersetup.msi CLICK2X=disable
The problem is, even with this switch, the registry key HKEY_Local_User\Software\IM Providers still gets a Cisco Jabber key created and the DefaultIMApp gets changed to Cisco Jabber. I change the key to Lync and it works until Jabber is launched. The key then changes back to Cisco Jabber. I changed the Cisco Jabber UpAndRunning default value to zero (0) and the Lync UpAndRunning default value to two (2) and restarted the machine. Everything stays with Lync until I launch Jabber again. The DefaultIMApp key gets changed to Cisco Jabber and the process starts all over again.
Has anyone found a way to get this to change and stay changed? I have a ticket open with Microsoft, but the responses I am getting is to supply them with more logs.
Thank you.
- Labels:
-
Jabber

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2015 02:58 PM
You need to put Jabber in Phone Mode (i.e. disable all IM&P functionality).
The installer command line switch is
PRODUCT_MODE=Phone_Mode
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/install_client.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2015 06:36 AM
Hi Jonathan,
You are correct, that does not affect the DefaultIMApp key when Jabber is installed using that switch on a machine that has never had Jabber on it before. However, even after deleting the Jabber client from Windows, deleting the Cisco Jabber files from C:\Program Data and removing all traces of Cisco Jabber from my registry, when I install with that switch on my PC that key is still affected. Is there somewhere that Jabber is retaining information value on my PC that I am unaware of that I need to remove before re-installing Jabber?
Thank you.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2015 08:04 AM
I believe you need to remove and reinstall the Lync app so it overwrites the registry keys of the MS Office Persona API, taking the proverbial ball back from Jabber. As I understand, the app that gets installed most recently "registers" to that API in the registry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2017 10:09 PM
we have a similar (had posted it here https://supportforums.cisco.com/discussion/13220646/sip-url-association-broken-jabber)
however, reinstalling of Lync did not solve the issue.
There should be some way of preventing Jabber from modifying the registry path each time Jabber is launched after Lync.
HKEY_CLASSES_ROOT\sip\shell\open\command
from
"C:\Program Files (x86)\Microsoft Office\Office15\Lync.exe" "%1"
TO
"C:\Program Files (x86)\Cisco Systems\Cisco Jabber\CiscoJabber.exe" -URI %1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2018 04:13 AM
Hey, did anyone find a way of getting round this issue?
TIA
Glyn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2019 07:12 AM
Yes.
I do have changed the permissions on the Registry Key (Computer\HKEY_CURRENT_USER\Software\IM Providers\DefaultIMApp) after having update the value to Lync
I have put everyone with Read only access, except admin local account having the rights to change permissions (using advance permissions).
