JAbber for Windows signout auto sign out intermittenly

[Shalid Kurunnan Chalil]

Hi Guys,

one of my customer Jabber for windows is intermittently signing out. its occuring for large number of users.

the Jabber Problem report give the alarm 113 and socket errors. i couldnt get the bottom of it. highly appreciate any guidlines.

 [\core\sipstack\ccsip_platform_tcp.c(910)] [csf.sip-call-control] [sip_tcp_set_reason_for_active_connfailed] - SIPCC-SIP_TCP_MSG: sip_tcp_set_reason_for_active_connfailed: Disconnected from Active Server ().  unRegReason:113 Errno:140, Cause:1, Reason:[Unknown error]

 [tiveapp\sipcc\core\ccapp\cc_alarm.c(816)] [csf.sip-call-control] [setUnregReason] - SIPCC-PLAT_API: setUnregReason: setting unreg reason to=113

2020-05-05 12:32:15,027 INFO  [0x0000149c] [tiveapp\sipcc\core\ccapp\cc_alarm.c(880)] [csf.sip-call-control] [setUnregReason] - SIPCC-PLAT_API: setUnregReason: value of first_oos_alarm_set=1 [sipstack\sip_transport_connection.c(282)] [csf.sip-call-control] [sip_transport_connection_on_socket_error] - [SIP][CONN][] socket(14096) error:140

Jabber is connected over MRA.

CUCM 12, Jabber 12.6 and/or 12.8.1, Expressway X12.5.7

[sudaggar]

please check CUCM event viewer application/sys logs (from RTMT), and check with jabber device-name if there is any unregister event in logs. Check for reason-code. There could be network issue.

[Shalid Kurunnan Chalil · Accepted solution]

Further analysis observed that huge number of IM presence status change messages in the Jabber logs which in turn spike the CPU leading to Cisco Jabber stuck or sign out. Contact TAC and they confirmed its a IM and PResence Bug

CSCvh58391 and CSCvf80487

So update the IM and P 12.0.1.21000-10..

Now we are waiting to get feedback from business.

Regards

[Shalid Kurunnan Chalil]

marking this as the solution, The business confirmed that the solution worked. the bug was the culprite. :)