Everytime I message a co-worker for the first time every day I get this error
Then when he responds it doesn't have his name listed. i.e. (his responce is "just once")
To which I said hrm!!
Very odd. It seems that he is the only person that this happens to.
We have rebuilt his cisco framework softphone. (Razor blade icon)
I deleted my win 7 profile cache in both local and roaming.
If this is cloud deployment (WebEx) and you see following statements in log file for the failed message, then it is a known issue:
If it is On-Prem (CUP) deployment, this will need further investigation via a TAC case.
We were able to test an upcoming version in our shop for Cisco and it seems to correct this problem. Hopefully will release right after Xmas. I believe the 9.1.2 release.
I am running 9.1.2 Jabber and still get this issue with an On-prem deployment....8.6.4 CUPS...
Any Ideas? IT isn't consistent.....
This is actually a bug in CUPS. It has to do with the IM forking that happens if you have multiple devices using chat.(Iphone, ipad and windows clients for instance) once you reply to the mesage then the chat is unicast to the one specific device and the issue dissapears. The current workaround is stopping the SIP Proxy service on your CUPS server. The only thing this affects is web based stuff in the administration pages. This is supposed to be fixed in v8.6.5 CUPS.
We ran into the same issue with one individual user, we were able to resolved it by going to Call Manager and remove the user license capability and re-enable it.
I would recommend you through a CLI run the command "utils service list" and see if the following services are running:
Cisco SIP Proxy Cisco Sync Agent Cisco XCP Authentication Service Cisco XCP Connection Manager Cisco Presence Engine
Also some times this can be related to the "Persistent Chat" being enabled, you might be able to check that in CUPS under Messaging > Group Chat and Persistent Chat Settings, if you're not using it you might want to disable it.
Is anyone getting this on CUPS 9.1 specifically in HA with user assignment set to Balanced mode vs. using the secondary node as a hot standby? I seem to only see this issue between users that are not on the same node, and TAC gave me some dodgy reasoning around assigning all users to a single node that I didn't really buy into.