We have implemented an on-premises version of Cisco Jabber which we use for presence and chat etc.
In general it works fine, but for several users they are unable to connect to certain individuals, who are indicated as being offline. Others are able to see presence and connect to the same user. Also if the 'bad' user initiates a chat their presence is indicated and they can be added as a contact.
As this is isolated to certain individuals connecting with certain others it really looks like some (but not all) are detecting an incorrect/invalid user account.
This does not appear to be a server/AD issue as different people have different results. It is almost like the client is detecting a contact on the individual PC and trying to use the first it finds (although we are pointing to our user OU in AD).
Has anyone witnessed this issue and know of a fix?