Cisco Jabber for Windows SIP REGISTER Expires=0

[marco_81]

Hi all,

in a production environment there are some jabber SDK with Standard SIP Profile applied (all parameters are left to theit default), one of those parameters is Timer Register Expires (seconds) = 3600.

Jabber sends periodic SIP REGISTER with Expires=3600, but there is something in place that triggers jabber to send REGISTER with Expires=0, as the message shown below:

REGISTER sip:cucm_ip SIP/2.0
Via: SIP/2.0/TCP jabber_ip:49219;branch=z9hG4bK00001fc7
From: <sip:8078@cucm_ip>;tag=41cef0da388f00da00000a04-00007c90
To: <sip:8078@cucm_ip2>
Call-ID: 41cef0da-388f0003-000073d9-00007215@jabber_ip
Max-Forwards: 70
Date: Mon, 18 Sep 2017 10:16:56 GMT
CSeq: 208 REGISTER
User-Agent: Cisco-CSF/9.3.2
Contact: <sip:c8a4dc9c-ce80-6887-8645-a1277f357e50@jabber_ip:49219;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-41cef0da388f>";+sip.instance="<urn:uuid:00000000-0000-0000-0000-41cef0da388f>";+u.sip!devicename.ccm.cisco.com="ECP8078";+u.sip!model.ccm.cisco.com="503"
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-6.0.2,X-cisco-xsi-8.5.1
Content-Length: 0
Reason: SIP;cause=200;text="cisco-alarm:25 Name=ECP8078 ActiveLoad=image_a InactiveLoad=image_b Last=initialized"
Expires: 0

Jabber SDK are installed on virtualized desktop, it seems my customer cannot retrieve jabber logs, so i have to investigate only by means of cucm sdl traces.

Any help wuold be great!

regards

[Alok Jaiswal]

Register with Expires value "0" is sent for deregistration. Normally i haven't seen why an UAC will send a deregistration request to an UAS. Its hard to tell from the message why jabber is doing it.

Rgds,

Alok

[Jonathan Unger]

Hi There,

It is normal for the jabber client to send a registration message with an Expires=0 to the secondary CUCM server in the CM Group. This acts as a keepalive mechanism if the primary CUCM should go down. 

This article explains the keepalive mechanism further.
https://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/unified-ip-phone-7900-series/200410-Troubleshoot-IP-Phone-Unregistration-A.html#anc13

Is the Expires=0 going towards your primary UCM or secondary UCM?

*** Please mark posts as helpful and/or correct if appropriate

[marco_81]

Hi, thank you for reply,

my concern is about jabber sending expires=0 both to primary and secondary, this is what i can see from jabber logs:

every 120 sec jabber sends expires=3600 to primary cucm and expires=0 to secondary, suddenly jabber sends expires=0 to primary also and nothing else, so jabber gets ureachable as expected from its expiration.

I'm going to investigate about it and i'll keep update this argoment. Do you think increasing Timer Keep Alive Expires is an idea?

[marco_81]

Update for the opened topic.

The registration with Expires=0 it's not sent "suddenly" as i said, this is not an appropriate term.

Before the REGISTER with Expiration=0 is sent from jabber, i see this line in jabber logs:

[recv] {"ciscoChannelMessage":{"ciscoSDKClientMessage":{"messageId":"1505903033469429","name":"logout"},"client":{"id":"855108.101","url":"http://"reserved URL"/portal/users/108/dashboard","hostname":"covered for privacy","name":"covered for privacy"}}}.

Cisco jabber SDK registers after the operator perform a login against a web portal. In this case i suppose jabber de-register because of a logout received.

I'll keep the topic updated once the issue is solved.

thanks

[lior look]

Hey, I have same issue in 11.9.1 version, how did u resolve that?