Jabber for android drops registration after 12 min

[yositorati]

Hello,

We have a few clients using Jabber for android\iphone through MRA and VPN, both of them drops the registration after 12 minutes.

SIP profile and timers are configured by the documents and if we enlarge the keepalive to 14 minutes, it will lose the registration after 14 minutes.

CUCM 10.5.2.10000-5

Jabber for android 10.6.1

CSF on PC working perfect.

On the CUCM Logs it seems that the client drops the registration due to KeepAlive timer expiration:

An endpoint has unregistered Device name:BOTXXXX Device IP address:XXX.XXX.XX.XX Protocol:SIP Device type:575 Reason Code:13

On the capture from the CUCM we can see that the client didn't sent keepalives for 12 minutes and then the CUCM drops the connection.

Couldn't find any open bugs related to this.

Any suggestion?

Thanks!!

[Jonathan Schulenberg]

Do you see the keepalive being generated in the client-side Jabber logs? What about Expressway-E event logging (probably level 3 or 4)? If it makes it to -E, does Expressway-C see it (ie is it being tunneled through the Ascent connection successfully)?

[yositorati]

I don't think there is any problem with the Expressway servers because we lose registration even with WiFi on the lan.

And I don't see the keepalive being generated in the Jabber logs. these are the results If i filter the logs by csf.sip-call-control during the 12 minutes idle time:

    Line 57717: 03-29 14:58:39.736  1124  1388 D     csf.sip-call-control: [sip_platform_task.c(262)] [SIPMsgQWaitTask] - SIPCC-SIP_MSG_QUE: SIPMsgQWaitTask: 1 msg available on msgq
    Line 57719: 03-29 14:58:39.736  1124  1387 D     csf.sip-call-control: [ccsip_task.c(596)] [SIPTaskProcessListEvent] - SIPCC-SIP_EVT: SIPTaskProcessListEvent: cmd = 0x62
    Line 58578: 03-29 15:01:14.628  1124  1388 D     csf.sip-call-control: [sip_platform_task.c(262)] [SIPMsgQWaitTask] - SIPCC-SIP_MSG_QUE: SIPMsgQWaitTask: 1 msg available on msgq
    Line 58579: 03-29 15:01:14.628  1124  1387 D     csf.sip-call-control: [ccsip_task.c(596)] [SIPTaskProcessListEvent] - SIPCC-SIP_EVT: SIPTaskProcessListEvent: cmd = 0x0
    Line 58580: 03-29 15:01:14.628  1124  1388 D     csf.sip-call-control: [sip_platform_task.c(262)] [SIPMsgQWaitTask] - SIPCC-SIP_MSG_QUE: SIPMsgQWaitTask: 1 msg available on msgq
    Line 58581: 03-29 15:01:14.628  1124  1387 D     csf.sip-call-control: [ccsip_task.c(596)] [SIPTaskProcessListEvent] - SIPCC-SIP_EVT: SIPTaskProcessListEvent: cmd = 0x62
    Line 59198: 03-29 15:03:31.087  1124  1388 D     csf.sip-call-control: [sip_platform_task.c(262)] [SIPMsgQWaitTask] - SIPCC-SIP_MSG_QUE: SIPMsgQWaitTask: 1 msg available on msgq
    Line 59199: 03-29 15:03:31.087  1124  1387 D     csf.sip-call-control: [ccsip_task.c(596)] [SIPTaskProcessListEvent] - SIPCC-SIP_EVT: SIPTaskProcessListEvent: cmd = 0x0
    Line 59200: 03-29 15:03:31.087  1124  1388 D     csf.sip-call-control: [sip_platform_task.c(262)] [SIPMsgQWaitTask] - SIPCC-SIP_MSG_QUE: SIPMsgQWaitTask: 1 msg available on msgq
    Line 59201: 03-29 15:03:31.087  1124  1387 D     csf.sip-call-control: [ccsip_task.c(596)] [SIPTaskProcessListEvent] - SIPCC-SIP_EVT: SIPTaskProcessListEvent: cmd = 0x62