04-09-2025 08:40 AM
Hi. I have a Jabber user, User A, with a contact in a federated XMPP domain, User B. When I sign out of Jabber (on Windows 10) User B still sees User A as online, up until a specific sequence of events until finally User A's presence is "offline". This is on Cisco Jabber 14.0.1, and CUCM server version 14.0.1.13900. Here are the steps to reproduce:
1) User A signs out of Jabber. However, on User B's side, User A is still "online". In the real time monitoring tool, I see a stanza sent to User B that has contained inside it an element: <im-status>available</im-status>
2) I click "sign in" on the jabber window that appeared after sign out, where it spins for ~30 seconds, while saying "finding services"
3) On the sign in menu, it says "Enter your username and password for Phone Services". I then enter my password, and it spins with the message "signing in" for about 1 minute and 25 seconds, before Jabber says "cannot communicate with the server. the connection has timed out". The sign in box now says "Enter your username and password for Phone Services and Instant Messaging" (why did it add the Instant Messaging part?)
4) Exactly two minutes after the failed sign in attempt, User B finally sees User A as offline. I also saw in the real time monitoring tool a stanza with the "type='unavailable'" element in it sent to User B (why didn't this happen immediately on sign out?)
5) I sign in again, this time it signs in successfully, and User A is back online.
I believe that there is some kind of mismatch between the Jabber client and the server when I sign out of Jabber. The client doesn't correctly inform the server it has signed out, which is why it never sends the "offline" presence status to the federated user. Moreover, when I try to sign in again, it fails because the server thinks the Jabber client is still online, yet it is requesting to sign in again. This causes an error internally and it removes all active sessions, which is when the "offline" presence stanza is sent to User B.
Has anyone else encountered this issue, or have a solution?
Solved! Go to Solution.
04-10-2025 06:30 AM
A property, HVDDisconnectSignout describes the behavior I was seeing. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_0/cjab_book_parameters-reference-guide-for-cisco-jabber-14_0/cjab_b_parameter-reference-guide-jabber-129_chapter_01000.html#reference_83B08879DC38C665FE1F82E1FE931182
04-10-2025 06:30 AM
A property, HVDDisconnectSignout describes the behavior I was seeing. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/14_0/cjab_book_parameters-reference-guide-for-cisco-jabber-14_0/cjab_b_parameter-reference-guide-jabber-129_chapter_01000.html#reference_83B08879DC38C665FE1F82E1FE931182
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide