cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
51570
Views
15
Helpful
8
Replies

Jabber and calendar integration

Elena Pudge
Level 1
Level 1

Hi,

I've got two types of Jabber client deployment - on prem and cloud based (this is the old webex connect, not jabber for telepresence). Both have different issues with calendar integration.

On prem Jabber:

1. Presence status is passed to Outlook

2. Calendar appointment whilst they do show up within meeting tab on Jabber client, the status of the client doesnt change to "In a Meeting" during appointments.

Off prem Jabber:

1. Presence status is NOT passed to Outlook

2. Calendar appointments works fine - ie show up in the meeting tab, and status changes correctly.

I have modified AD attribute proxyaddress for on prem clients to SIP:samaccount@cupdomain, I've assumed that for off prem clients, it would be SIP:email@domain as used by login details. I cant seem to find any documentation about calendar integration with webex connect clients.

Any ideas?

Thanks

1 Accepted Solution

Accepted Solutions

Hi Elena,

Is it same machine where Outlook integration works with on-prem? If not, there are few things that you could check:

Uninstall other IM clients

Check if any other IM client with Outlook integration has been installed. Many other clients use the same api’s to integrate with Microsoft products and maybe blocking Jabber Click to X. If any other product is installed please uninstall and reboot your machine.

Some applications known to affect Jabber presence integration are: Cisco WebEx Connect, Microsoft Office Communicator, Microsoft Lync, CUCIMOC, CUCILync, Standalone Click to call, Cisco Unified Personal Communicator 8.x.

 

Registry settings

Confirm the following registry settings exist and are correct:

32-bit machines

Key: HKEY_CLASSES_ROOT\CLSID\{8885370D-B33E-44B7-875D-28E403CF9270}\TreatAs

value (REG_SZ): (Default) = {83CE44B6-A512-4199-9766-38357A9108E8}

-Jabber sets this on install; it replaces the existing class ID with ours

Key: HKCU\Software\Microsoft\Office\12.0\Common\PersonaMenu

value (REG_DWORD type): Enabled = 1, EnablePresence = 2, RTCApplication = 3, SetOnlineStatusLevel = 2, ShowStatus = 1

-Office creates these values on install.

Key: HKLM\Software\Microsoft\Office\Outlook\Call Integration\IMApplication

value (REG_SZ): IMApplication = CiscoJabber.exe

- Jabber sets this value on install, this key is created when office is installed

Key: HKCU\Software\Microsoft\IM Providers

value (REG_SZ): DefaultIMApp = Cisco Jabber

- Jabber sets this value on install

Key: HKCU\Software\IM Providers\ Cisco Jabber

value (REG_DWORD): UpAndRunning = 0 (not running), 1(starting), and 2 (running)

- This key is set by Jabber you do not need to create or manually edit this Registry Key.

- If jabber is running and this key is not set to 2 then there is problem, gather a prt.

64-bit machines

Key:HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{8885370D-B33E-44B7-875D-28E403CF9270}\TreatAs

value (REG_SZ): (Default) = {83CE44B6-A512-4199-9766-38357A9108E8}

-Jabber sets this on install; it replaces the existing class ID with ours

Key: HKCU\Software\Microsoft\Office\12.0\Common\PersonaMenu

value (REG_DWORD type): Enabled = 1, EnablePresence = 2, RTCApplication = 3, SetOnlineStatusLevel = 2, ShowStatus = 1

-Office creates these values on install.

Key: HKLM\Software\Wow6432Node\Microsoft\Office\Outlook\Call Integration\

value (REG_SZ): IMApplication = CiscoJabber.exe

Key: HKCU\Software\Wow6432Node\IM Providers\Cisco Jabber

value (REG_SZ): Friendly Name = Cisco Jabber

value (REG_SZ): GUID = {83CE44B6-A512-4199-9766-38357A9108E8}

value (REG_SZ): ProcessName = CiscoJabber.exe

Key: HKCU\Software\IM Providers\Cisco Jabber

value (REG_DWORD): UpAndRunning = 0 (not running), 1(starting), and 2 (running)

- This key is set by Jabber you do not need to create or manually edit this Registry Key.

- If jabber is running and this key is not set to 2 then there is problem, gather a prt.

If all is in order, then open a support case with Cisco TAC and provide logs as below:

Enabling Outlook logging

Setting this registry data enables logging for the presence features that integrate between Outlook and Jabber, and shows additional information in Outlook and Jabber. To set this registry key, do the following:

  • Click Start, and then click Run.
  • In the Open box, type REGEDIT, and then click OK to start Registry Editor.
  • Navigate to key: HKEY_CURRENT_USER\Software\IM Providers.
  • Create DWORD: OfficePresenceLogging with Value: 1.
  • If it does not exist already, manually create %userprofile%\Tracing directory, otherwise the log files will not be created.
  • Restart Outlook.

The log file is created in the %userprofile%\Tracing folder and the file name will be OfficePresence-#.log (where # is an integer). The last modified date will indicate which file is the latest.

Create a Jabber Problem Report (PRT)

  • Recreate the issue.
    • Do this by opening the email\SharePoint page that shows the problem, select an example user, show their contact card.
  • Take screenshots of the issue and record time stamps.
  • Take note of the User names and email address\IM address of the problem users.
  • Go to your Jabber client and select Help > Report a problem, and then follow the steps to produce the problem report.

Thanks,

Maqsood

Uninstall other IM clients

Check if any other IM client with Outlook integration has been installed. Many other clients use the same api’s to integrate with Microsoft products and maybe blocking Jabber Click to X. If any other product is installed please uninstall and reboot your machine.

Some applications known to affect Jabber presence integration are: Cisco WebEx Connect, Microsoft Office Communicator, Microsoft Lync, CUCIMOC, CUCILync, Standalone Click to call, Cisco Unified Personal Communicator 8.x.

View solution in original post

8 Replies 8

Jonathan Schulenberg
Hall of Fame
Hall of Fame
2. Calendar appointment whilst they do show up within meeting tab on Jabber client, the status of the client doesnt change to "In a Meeting" during appointments.

For this to work the Exchange integration must have been done on the CUP server. The Jabber client does not poll Outlook locally for Free/Busy information. Assuming the server-side integration is working the user would need to login to the /cupuser webpage and enable calender integration. You can see if they have done this with the Presence Viewer in CUP Administration. There is no admin-facing option to set this in bulk at present.

I don't have the answer for WebEx Connect; hopefully others can chime in on this front.

Please remember to rate helpful responses and identify helpful or correct answers.

Hi Jonathan,

As this is initial setup, I have access to user pages, so have already enabled calendar integration under cupuser pages. Its all coming up green within the dashboard, I'm assuming I dont need to restart any services on CUP.

Does the account you specify for exchange integration need any special permissions?

elena

Yes! There's a whole document dedicated to this. Please read and follow it closely:

Integration Guide for Configuring Cisco Unified Presence Release 8.5 and 8.6 with Microsoft Exchange

Please remember to rate helpful responses and identify helpful or correct answers.

Thanks Jonathan,

that the on-prem sorted.

Any one knows about the off-prem integration?

Hi Elena,

Is it same machine where Outlook integration works with on-prem? If not, there are few things that you could check:

Uninstall other IM clients

Check if any other IM client with Outlook integration has been installed. Many other clients use the same api’s to integrate with Microsoft products and maybe blocking Jabber Click to X. If any other product is installed please uninstall and reboot your machine.

Some applications known to affect Jabber presence integration are: Cisco WebEx Connect, Microsoft Office Communicator, Microsoft Lync, CUCIMOC, CUCILync, Standalone Click to call, Cisco Unified Personal Communicator 8.x.

 

Registry settings

Confirm the following registry settings exist and are correct:

32-bit machines

Key: HKEY_CLASSES_ROOT\CLSID\{8885370D-B33E-44B7-875D-28E403CF9270}\TreatAs

value (REG_SZ): (Default) = {83CE44B6-A512-4199-9766-38357A9108E8}

-Jabber sets this on install; it replaces the existing class ID with ours

Key: HKCU\Software\Microsoft\Office\12.0\Common\PersonaMenu

value (REG_DWORD type): Enabled = 1, EnablePresence = 2, RTCApplication = 3, SetOnlineStatusLevel = 2, ShowStatus = 1

-Office creates these values on install.

Key: HKLM\Software\Microsoft\Office\Outlook\Call Integration\IMApplication

value (REG_SZ): IMApplication = CiscoJabber.exe

- Jabber sets this value on install, this key is created when office is installed

Key: HKCU\Software\Microsoft\IM Providers

value (REG_SZ): DefaultIMApp = Cisco Jabber

- Jabber sets this value on install

Key: HKCU\Software\IM Providers\ Cisco Jabber

value (REG_DWORD): UpAndRunning = 0 (not running), 1(starting), and 2 (running)

- This key is set by Jabber you do not need to create or manually edit this Registry Key.

- If jabber is running and this key is not set to 2 then there is problem, gather a prt.

64-bit machines

Key:HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{8885370D-B33E-44B7-875D-28E403CF9270}\TreatAs

value (REG_SZ): (Default) = {83CE44B6-A512-4199-9766-38357A9108E8}

-Jabber sets this on install; it replaces the existing class ID with ours

Key: HKCU\Software\Microsoft\Office\12.0\Common\PersonaMenu

value (REG_DWORD type): Enabled = 1, EnablePresence = 2, RTCApplication = 3, SetOnlineStatusLevel = 2, ShowStatus = 1

-Office creates these values on install.

Key: HKLM\Software\Wow6432Node\Microsoft\Office\Outlook\Call Integration\

value (REG_SZ): IMApplication = CiscoJabber.exe

Key: HKCU\Software\Wow6432Node\IM Providers\Cisco Jabber

value (REG_SZ): Friendly Name = Cisco Jabber

value (REG_SZ): GUID = {83CE44B6-A512-4199-9766-38357A9108E8}

value (REG_SZ): ProcessName = CiscoJabber.exe

Key: HKCU\Software\IM Providers\Cisco Jabber

value (REG_DWORD): UpAndRunning = 0 (not running), 1(starting), and 2 (running)

- This key is set by Jabber you do not need to create or manually edit this Registry Key.

- If jabber is running and this key is not set to 2 then there is problem, gather a prt.

If all is in order, then open a support case with Cisco TAC and provide logs as below:

Enabling Outlook logging

Setting this registry data enables logging for the presence features that integrate between Outlook and Jabber, and shows additional information in Outlook and Jabber. To set this registry key, do the following:

  • Click Start, and then click Run.
  • In the Open box, type REGEDIT, and then click OK to start Registry Editor.
  • Navigate to key: HKEY_CURRENT_USER\Software\IM Providers.
  • Create DWORD: OfficePresenceLogging with Value: 1.
  • If it does not exist already, manually create %userprofile%\Tracing directory, otherwise the log files will not be created.
  • Restart Outlook.

The log file is created in the %userprofile%\Tracing folder and the file name will be OfficePresence-#.log (where # is an integer). The last modified date will indicate which file is the latest.

Create a Jabber Problem Report (PRT)

  • Recreate the issue.
    • Do this by opening the email\SharePoint page that shows the problem, select an example user, show their contact card.
  • Take screenshots of the issue and record time stamps.
  • Take note of the User names and email address\IM address of the problem users.
  • Go to your Jabber client and select Help > Report a problem, and then follow the steps to produce the problem report.

Thanks,

Maqsood

Uninstall other IM clients

Check if any other IM client with Outlook integration has been installed. Many other clients use the same api’s to integrate with Microsoft products and maybe blocking Jabber Click to X. If any other product is installed please uninstall and reboot your machine.

Some applications known to affect Jabber presence integration are: Cisco WebEx Connect, Microsoft Office Communicator, Microsoft Lync, CUCIMOC, CUCILync, Standalone Click to call, Cisco Unified Personal Communicator 8.x.

Brilliant, thanks.

These reg keys were missing, once added all is working fine

Thanks for all the help

Elena

Hi,

here is also interesting document describing MS Outlook not showing presence status:

http://www.cisco.com/c/en/us/support/docs/unified-communications/jabber-windows/118750-technote-jabber-00.html

 

Hi,

we facing this issue, and I did all the Configuration in Registry and checked the configuration. But no success, no presence in Outlook.

Jabber 11.5

CUCM / CIMP 11.1

Outlook 2010

Did I forget something?

How can I check in the Outlook Traces, if there is a connection to Jabber?

Thanks!

DrMxxxxx