Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Reason codes for LastOutOfServiceInformation

Problem

  • CUCM 8.5.1.14044-2 installed on vmware
  • 9951 phones use firmware: sip9951.9-2-3ES-5
  • Intermittently, phones lost connection to CUCM and was not able to re-register.
  • No error msg on the phone display. Reset the phones resolved the issue.
  • phone log showed "UnifiedCMIPAddress=null", ReasonForOutOfService=14

phone log example:

7:36:27a LastOutOfServiceInformation DeviceName=SEP64D989C3C22F

DeviceIPv4Address=10.190.76.73 IPv4DefaultGateway =10.190.76.1 DeviceIPv6Address=

IPv6DefaultGateway= ModelNumber=CP-9951 NeighborIPv4Address=10.190.76.53

NeighborIPv6Address= NeighborDeviceID=SEP000830314331 NeighborIPortID=Port 1

DHCPv4Status=1 DHCPv6Status=3 TFTPCfgStatus=1 DNSStatusUnifiedCM1=4 DNSStatusUnifiedCM2=4

DNSStatusUnifiedCM3=4 VoiceVLAN=858 UnifiedCMIPAddress=null LocalPort=197342968

TimeStamp=1340451387 ReasonForOutOfService=14 LastProtocolEventSent=

LastProtocolEventReceived=Rcvd:SIP/2.0 200 OK Cseq:4834 REGISTER

CallId:64d989c3-c22f007e-15cfb562-790d6ffe@10.190.76.73

Resolution

ReasonForOutOfService=14 

TCPucmClosedConnection - The Cisco Unified Communication Manager closed the TCP connection

Reason 14 : MalformedRegisterMsg - (SIP only) A SIP REGISTER message could

not be processed because of an illegal format. Possible causes include a

missing Call-ID header, a missing AoR in the To header, or an expires value

that is too small. Check the REGISTER message for any of these issues and if

you find one, correct the issue.

Configuration Mismatch (SIP only) The configuration on the device does not

match the configuration in Unified CM. This can be caused by database

replication errors or other internal Unified CM communication errors.

First go to the Cisco Unified Reporting web page,

Generate a Unified CM Database Status report

verify "all servers have a good replication status".

You can also go to the Real-Time Reporting Tool (RTMT) and check the Replication

Status in the Database Summary page. If status shows 2, then replication is

working. If this device continues to unregister with this reason code, go to

the Device Configuration page in Unified CM Administration for the device

identified in this alarm and click Save. This generates a change

notification message to the Cisco CallManager and TFTP services and rebuilds

a new configuration file. If the problem still persists, restart the TFTP

service and Cisco CallManager service.

Here is the listing of reason codes for "lastoutofserviceinformation"

10 - The TCP connection to the Cisco Unified Communication Manager experienced a timeout error

12 - The Cisco Unified Communication Manager reset the TCP connection

13 - The Cisco Unified Communication Manager aborted the TCP connection

14 - The Cisco Unified Communication Manager closed the TCP connection

15 - The device closed the connection due to a SCCP KeepAlive failure

16  - The connection closed due to the IP address being lost.  This  may be  due to the DHCP Lease expiring or the detection of IP address   duplication.  Check that the DHCP Server is online and that no   duplication has been reported by the DHCP Server.

17 - The device closed the TCP connection due to a registration timeout.

18 - The device closed the TCP connection in order to reconnect to a higher priority Cisco Unified CM

20 - The device closed the TCP connection due to a user initiated reset

22 - The device closed the TCP connection due to a reset command from the Cisco Unified CM

23 - The device closed the TCP connection due to a restart command from the Cisco Unified CM

24 - The device closed the TCP connection due to receiving a registration rejection from the Cisco Unified CM

25 - The device has initialized and is unaware of any previous connection to the Cisco Unified CM

26 - The device closed the TCP connection due to reconfiguration of IP on a new Voice VLAN.

27 - The device closed the TCP connection in order to enter Power Save Plus mode

100 - The device detected a version stamp mismatch during registration Cisco Unified CM.

104 - The device closed the TCP connection to restart triggered internally by the device to apply the configuration changes.

105  - The device closed the TCP connection due to a restart triggered   internally by the device because device failed to download the   configuration or dial plan file.

106 - The device failed to setup a secure TCP connection with Cisco Unified CM

107 - TCPclosedDeviceReset - The device closed the TCP connection to set the inactive partition as active partition, then reset, and come up from the new active partition

108 -VpnConnectionLost - The device could not register to Unified CM because VPN connectivity was lost

200 - The device was unregistered because the client application was closed.

201 - The device was unregistered because the OS was put in standby mode.

202 - The device was unregistered because the OS was put in hibernate mode.

203 - The device was unregistered because the OS was shut down.

204 - The device was unregistered because the client application crashed.

205 - The device was unregistered in the previous session because the system did not allow sufficient time for cleanup.

206 - The device was unregistered because the client requested to switch from softphone to deskphone control.

207 - The device is being registered because the client requested to switch from deskphone control to softphone.

208 - The device is being unregistered because the client detected a change of network.

209 - The device is being unregistered because the device has exceeded the maximum number of concurrent registrations.

210 - The device is being unregistered because the client has exceeded the maximum number of concurrent logons.

Related Information

Version history
Revision #:
1 of 1
Last update:
‎10-26-2012 02:19 AM
Updated by:
 
Labels (1)
Everyone's tags (3)
Comments
New Member

Thank you for this post.  I have 3 questions:

1. Is there a document partners can reference with all these codes?

2. I have a code 107 for a 9971 IP phone that is not in this list.  Any ideas?

3. Reason code 12: Why would CUCM reset the TCP connection with no user intervention?

Thank you.

Cisco Employee

1. This document should suffice. This is also presented/translated in RTMT. The ReasonForOutOfService enum value *usually* uses the same values as the Last= reason documented elsewhere in the StationAlarm message. Note these messages report from the phone perspective.  2. 107 - The device closed the TCP connection to set the inactive partition as active partition, then reset, and come up from the new active partition.  3. The wording on 12 is sketchy at best. 12 means the phone received a TCP RESET. This may come from UCM or any transit network device such as a firewall, proxy, or inspection device.  *Most* of the time phones and UCM will properly negotiation unregistration and the close a TCP session. If the protocol stacks (SIP/H.323/MGCP) get out of sync and cannot properly negotiate unregistration then RESET is used. Typical TCP rules, implementations, and uses apply.

New Member

I get reason 16 on the phones, the phones are registered now but  how can i determine from the CallManager if there was a duplicate ip on the CallManager's ip?

Cisco Employee

16 from the phone side means the phone detected a duplicate IP on its local subnet. This would be largely irrelevant of the CallManager server.

New Member

As far as i see, RTMT syslog messages do not translate these codes with specific explanations, all alerts have a generic message, which goes on like this:

Description:  Information related to the last out-of-service event

Explanation:  The device has lost communication with Unified CM, due to a reason such as a network connectivity issue, Unified CM outage....


New Member

Can somebody add ReasonForOutOfService=108 please.

Cisco Employee

Support Team,

ReasonForOutOfService=108

"VpnConnectionLost - The device could not register to Unified CM because VPN connectivity was lost."

Regards,


Ryan

New Member

@rkotulak Thanks for the prompt reply.

New Member

Where do you find the Last out of service reason codes. No luck finding them in the system error messages

Cisco Employee

yamleague,

If you're trying to view them via RTMT you'd navigate to "System -> Tools -> SysLog Viewer" then expand "Application Logs -> CiscoSyslog" where you can filter on the Message "LastOutOfServiceInformation".

Below I'm attaching an example from my lab setup:

Also, if you open up the message and scroll down on the description on the right you'll see all the other ENUM's and their definitions:

Regards,

Ryan

New Member

Thanks a lot for the info Ryan.

Cisco Employee

All,

FYI that defect CSCvd71818 - Update RTMT Alarm Reason Code ENUM's For All "LastOutOfServiceInformation" has been raised to include the following ENUM Definitions to the ""System Error Messages for Cisco Unified Communications Manager" Versions 11.5(1), 11.0(1), & 10.0(1).

Alarm_LastTimeVPNConnectivityLost = 108
Alarm_LastTimeIpAddressChanged = 109
Alarm_LastTimePhoneRequestedStop = 110
Alarm_LastTimePhoneRequestedDestroy = 111
Alarm_LastTimeCrash = 114

Ryan