Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
With Cisco CallManager, when a 7900 series IP phone is reset, a DeviceUnregistered - Device unregistered error message is displayed in the Application Event Viewer
For every issue that causes a phone to reset or restart, Cisco CallManager logs an error in the Application Event Viewer, as shown:
Event Type: Error Event Source: Cisco CallManager Event Category: None Event ID: 3 Date: 1/6/2004 Time: 3:10:17 PM User: N/A Computer: Description: Error: DeviceUnregistered - Device unregistered. Device name.: Device IP address.: Device type. [Optional]: 7 Device description [Optional].: Auto 2002 Reason Code [Optional].: 9 App ID: Cisco CallManager Cluster ID: CRBNPUB-Cluster Node ID: 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.>
This message is a result of IP phone reset or restart. These are the possible reasons:
Admin reset or restart (An administrator resetting the IP phone through the admin interface)
In the message from the Application Event Viewer, Device type 7 indicates a Cisco 79xx series phone. Reason code 9 is CallManagerReset. Reason Code 9 is a normal condition.
Device reset is typically done with this sequence:
The device unregisters from Cisco CallManager.
At this time, the DeviceUnregistered event is generated. The reason code indicates why the device is unregistered. Reason code 9 indicates it is due to the device reset.
The DeviceUnregistered event is for all devices that register to Cisco CallManager, including Media Gateway Control Protocol (MGCP), gateways, phones, H.323 trunks, and media devices.
The device re-registers to Cisco CallManager. At this time, the DeviceRegistered event is generated.
Note: There is no guarantee that the device will re-register.
This issue is also documented in Cisco bug ID CSCed38302.