Although the issue is inconsistent you may want to verify the following bug
Jabber for Windows stops registering it's CSF softphone client with CUCM, after a laptop sleeps then resumes.
This will be experienced if it's first TFTP server is not pingable immediately upon resuming and if it has a second TFTP server that will never be pingable from that particular network location.
It fails because it does not ever loop back to the earlier TFTP, but instead continues to attempt to ping the last TFTP in it's list.
Remove secondary/tertiary TFTP servers that are unable to be pinged. The last TFTP server must be pingable from every network location where Jabber for Window's CSF client is expected to function.
- Do rate helpful posts -
While this may be a viable solution for some, it does not help me. I have to VPN into my company's network before any ping could work. Obviously, I can't authenticate to the VPN before a ping is initiated by Jabber. What is being done long-term to fix this issue? It is extremely frustrating. If I forget to reset it upon resuming, I receive no calls or Jabber messages even though it appears that I am online. Like the OP, I have to go into Task Manager is kill the process, which is unacceptable for what is supposed to be enterprise-grade communication software!
I had this issue until we upgraded. We are now at Cisco Jabber 11.8.2 and I no longer have issues with Jabber freezing after hibernating / sleeping my laptop.