cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2194
Views
0
Helpful
3
Replies

Cisco Jabber Windows profile login failure

byronmcneil
Level 1
Level 1

Hello Guru's 

I have a department who uses 4 Destops with cisco Jabber Version 12.6.1.34405 Build 284405  running, The issue is the users for this 4 station department is 8. So each user moves around signing in to Windows LDAP sync , then Jabber loads automatically since they login already once.  We have a user who seems to have a corroupt Jabber profile now. The device never registers for her login but somone else Jabber profile is running. How is this issue resolved ? Do I delete IM Presence user profile, or do I delete the Jabber profile in CM and recreate it ?

3 Replies 3

TechLvr
Spotlight
Spotlight

@byronmcneil 
Make sure the user's Jabber is correctly configured in CUCM.
Make sure the user is not assigned another user's Jabber device under Enduser Management in CUCM.

Reset the user's Jabber client and clear the cache for Jabber in Windows, then have her log back in.

Here is how you would clear the cache for Jabber.
Go to, C:\Users\<select the correct username>\AppData\Roaming\Cisco\Unified Communications\Jabber
Delete the "Jabber" folder. 

Next, go to, C:\Users\<select the correct username>\AppData\Local\Cisco\Unified Communications\Jabber
Delete the "Jabber" folder. 

As soon as the user logs back in, the Jabber folder will be recreated under above directories. 

Thank you for this update , this was the 101 of what we always do with this issue. I did forget to inform the group has a shared extension on their jabber device and in the user page the line is selected as primary with the IPCC ext selected. Would this cause a conflict having a shared exten on all user / agents ?

Shared CCX agent extensions is not supported. However I don’t think that this is related to your issue with Jabber. It is likely caused by either corrupt Jabber cache or something incorrectly configured in CM for the CSF device. Clear the cache and verify the configuration in CM.



Response Signature