registration time of Cisco Phone

[ccg-collab1]

Is there a registration time per model of Cisco phone? Because we encountered wan issue/intermitent and there were some phones that went unregistered, however we noticed that most of this phones are 8811 model(SIP). We have other phones on the same network withe 8811 model, like 7942 model(SCCP), however they were not went unregistered.

Here are the other model that went unregistered:

9971

8941

9951

8945

9951

7821

Appreciate your inputs. Thank you

[Vivek Batra]

There is a registration timer for SIP phones, but not per model. Please check the registration timer under SIP Profile and following is an excerpt from doc. You can try shorting the duration and see if it works for you.

This field is intended to be used by SIP endpoints only. The SIP endpoint receives the value via a tftp config file. This field specifies the value that the phone that is running SIP sends in the Expires header of the REGISTER message. Valid values include any positive number; however, 3600 (1 hour) specifies the default value.

If the endpoint sends a shorter Expires value than the value of the SIP Station Keepalive Interval service parameter, Cisco Unified Communications Manager responds with a 423 "Interval Too Brief".

If the endpoint sends an Expires value that is greater than the SIP Station Keepalive Interval service parameter value, Cisco Unified Communications Manager responds with a 200 OK that includes the Keepalive Interval value for Expires.

Note	For mobile phones that are running SIP, Cisco Unified Communications Manager uses the value in this field instead of the value that the SIP Station KeepAlive Interval service parameter specifies to determine the registration period.

Note	For TCP connections, the value for the Timer Register Expires field must be lower than the value for the SIP TCP Unused Connection service parameter.

[Deepak Rawat]

Adding to what Vivek said, I believe SIP Keep alive mechanism does not work the way it works for SCCP that once phone misses 3 KeepAlives then it try secondary CM and so on that increases the total time for a Skinny phone to go in Unregistered state opposed to the SIP Phone that starts looking for secondary CM as soon as the TCP connection breaks with CM. Look at below thread:

https://supportforums.cisco.com/discussion/12241331/sip-keepalive-cucm

Regards

Deepak

[gstechteam]

We are seeing the exact same behavior in our environment.  We have deployed a large number of 8841 phones at remote branches that will unregister and SCCP phones will not.

Did you find a resolution to your problem yet?

[ccg-collab1]

Hi gstechteam,

Actually the main reason for the encountered issue of unregistered of phones was due to network issue. The only weird part is that not all phones went unregistered and most of the phones that went unregistered are 8811 IP Phones.

[alap84]

Hello

We have almost same issue with 8861 newly deployed, one thing which i noticed is if i ping phone ip it suddenly reaches to 700ms than to normal, 

Is it because of network thng or somethng else but it happens intermittently after 2 or 3 days, and phone comes back again without any hard reset