We consistently have inconsistent issues with our Jabber clients coming out of hibernate mode and/or a change in network connectivity. For simplicity I will narrow this to on-prem connectivity (happens over MRA as well). We've had this issue with J4W 10.x up to 11.5.1. The solution is to logout or close in task manager as the client "appears" to be not connected to CUPS and/or CUCM. From the user standpoint the client is dead but I will occasionally see CUPS connectivity w/o presence working correctly. Generally this happens after hours (not minutes) of inactivity. When the client can't connect to CUPS or CUCM we can ping both servers with no issues. I've opened TAC cases and the best I got was to reboot the CUPS server more often. I don't hear about this issue too often so I assume this isn't widespread but would love to know how to get this resolved permanently. All CUCM and CUPS servers are configured as FQDN.
Windows 7
Jabber4W - 10.x & 11.x (current version is 11.5.1)
CUPS - 10.5.2
CUCM - 10.5.2
