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.
