Cisco Jabber 11.5(4) and Google Chrome

[Joel Lallemand]

Hi

We observed a strange behavior using the tel: function in cisco jabber. If the Chrome Browser is installed on the same computer, its not possible to dial the number with cisco jabber, because the function tel: opens a new chrome browser window. It seems that Chrome overwrites the windows registry entry for that protocol handler. Does anyone knows this problem?

Thanks for your help.

[Jitender Bhandari · Accepted solution]

Hi Joel.

This is a known issue, where Chrome uses a non-default way of registering itself as a protocol handler.

Jabber uses the HKEY_CLASSES_ROOT\tel\shell\open\command registry keys to register itself as the default TEL protocol handler:
 http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide_appendix_01111.html#JABW_TP_PF21EDAF_00

Chrome seems to set itself as the default handler in the "Control Panel\All Control Panel Items\Default Programs\Set Associations" and not allow any other program to be set.

Workaround is to use ciscotel: links instead of tel: links, as Jabber is also registered as the default protocol handler for ciscotel:

JB

[Joel Lallemand]

Hi JB

Unfortunately we can not change the protocol header to ciscotel, but thanks anyway for your fast response! Have a good day. 

[Jitender Bhandari]

Hi Joel,

Happy to help.

have a good one.

JB

[xfthsdtyjstghadfgafgadfhsdhsdh]

This is a remarkably poor response to the question at hand - you are seriously suggesting that an entire organisation change its thousands of web pages on hundreds of web servers to pander to faulty client computer configuration?  Yeah, right.  How about this in a reg file:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\tel\UserChoice]
"Progid"="CiscoJabber"