Error: DeviceUnregistered Reason Code 8

[fbeebe]

A great number of my phones are cutting off , disconnecting calls. This happens a couple times a day. I am recieved the following error.

Error: DeviceUnregistered - Device unregistered.

Device name.: SEP0017E0D8147B

Device IP address.: 172.29.24.30

Device type. [Optional]: 309

Device description [Optional].: Patrick Alton

Reason Code [Optional].: 8

App ID: Cisco CallManager

Cluster ID: StandAloneCluster

Node ID: 172.29.12.253

Explanation: A device that has previously registered with Cisco CallManager has unregistered. This event may be issued as part of normal unregistration event or due to some other reason such as loss of keepalives.

Recommended Action: No action is required if unregistration of this device was expected..

Any help is appreciated.

Thanks,

Fred Beebe

[sbilgi]

Reason Code 8 means device initiated reset. This usually happens when there is a connectivity problem on your network between the devices and the CM servers or when the CM server is too busy to reply to keepalives. In both cases, the problem is due to missed keepalives between the devices and the CM servers. The reason why you may be seeing the errors

on both servers is because the devices may be rehoming between Pub and Sub when unregistering, which is normal fallback behavior when connectivity is lost to the current CM server.

[sandonen]

I'm running into the same issue with a device. I'm not sure if it's a cabling issue or not. The switch is reporting no errors. Does anyone know how to adjust the keepalive timeout? Tx

[marcuscastellanos]

I'm having the same issue

One thing that we have been noticing when this happens, is multiple phones in the are are going down. After close inspection, the switch is not going down, but the gig port is.

No other phones at the location are (we have 300+ at this location), just the 4 phones at this switch.

Could this possibly be spyware on the computer freaking the switch out?

Error: DeviceUnregistered - Device unregistered.

Device name.: SEP000C307087B2

Device IP address.: 10.111.1.40

Device type. [Optional]: 8

Device description [Optional].:

Reason Code [Optional].: 8

App ID: Cisco CallManager

Cluster ID: SJCCALLMGR1-Cluster

Node ID: 10.11.0.7

Explanation: A device that has previously registered with Cisco CallManager has unregistered. This event may be issued as part of normal unregistration event or due to some other reason such as loss of keepalives.

Recommended Action: No action is required if unregistration of this device was expected..

[Irfan Tariq Javed]

hi

We are using Call Manager 8.5.1 SU4 and IP Communicator 8.6.1.13 we are facing this issue at very high frequency . anyone solved this issue

Regards

Irfan Tariq

[asafayan]

All -

Any resolution to this issue?

TIA,

Amir

[will.alvord]

Wow - resurrecting a really old thread.  As pointed out, this error typically indicates a network issue or congestion preventing timely acks to phone keepalives.  The resolution is to find and correct the root cause.  That said, a workaround would be adjusting the keepalive threshholds to prevent the phone from re-registering.  The down side is that on an actual failure/loss of connectivity, the phones will take longer to recover.

These are both callmanager service parameters:

Station and Backup Server KeepAlive Interval:	This parameter designates the interval between KeepAlive messages  that are sent from Cisco IP Phones to the secondary Cisco CallManager.
	This is a required field.
	Default:                  60
	Minimum:                  10
	Maximum:                  1000
	:                Reset affected IP phone(s) for the parameter change to take effect.
	Unit:                sec
Station KeepAlive Interval:	This parameter designates the interval between KeepAlive messages sent from Cisco IP Phones to the primary Cisco CallManager.
	This is a required field.
	Default:                  30
	Minimum:                  10
	Maximum:                  1000
	:                Reset affected IP phone(s) for the parameter change to take effect.
	Unit:                sec

[Jon Clark1]

Hello 5 years later.

So we have an Expressway User working at home in San Jose and when he puts an external caller on hold to transfer him the phone resets.

|AppInfo  |<--RISCMAccess::DeviceUnRegister(...)
 |AppInfo  |SIPStationD(4599) - shutdownDevice: dropping call,

|AppInfo  |SIPStationD(4599) - retryRegister: recycling

This happens every time and ever since we enabled call recording.  Any ideas on how to get this to stop so we can keep call recording?