02-29-2012 12:50 AM - edited 03-16-2019 09:50 AM
Does anyone got any informaton of the meaning on the code of ReasonForOutOfService from the debug display on the Cisco Phone web page?
Solved! Go to Solution.
12-10-2013 07:09 AM
Here is a List of the reason codes for LastOutOfServiceInformation
ReasonForOutOfService=10 -- TCPtimedOut - The TCP connection to the Cisco Unified Communication Manager experienced a timeout error
ReasonForOutOfService=12 -- TCPucmResetConnection - The Cisco Unified Communication Manager reset the TCP connection
ReasonForOutOfService=13 -- TCPucmAbortedConnection - The Cisco Unified Communication Manager aborted the TCP connection
ReasonForOutOfService=14 -- TCPucmClosedConnection - The Cisco Unified Communication Manager closed the TCP connection
ReasonForOutOfService=15 -- SCCPKeepAliveFailure - The device closed the connection due to a SCCP KeepAlive failure
ReasonForOutOfService=16 -- TCPdeviceLostIPAddress - 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
ReasonForOutOfService=17 -- TCPDeviceRegsistrationTimedOut - The device closed the TCP connection due to a registration timeout
ReasonForOutOfService=18 -- TCPclosedConnectHighPriorityUcm - The device closed the TCP connection in order to reconnect to a higher priority Cisco Unified CM
ReasonForOutOfService=20 -- TCPclosedUserInitiatedReset - The device closed the TCP connection due to a user initiated reset
ReasonForOutOfService=22 -- TCPclosedUcmInitiatedReset - The device closed the TCP connection due to a reset command from the Cisco Unified CM
ReasonForOutOfService=23 -- TCPclosedUcmInitiatedRestart - The device closed the TCP connection due to a restart command from the Cisco Unified CM
ReasonForOutOfService=24 -- TCPClosedRegistrationReject - The device closed the TCP connection due to receiving a registration rejection from the Cisco Unified CM
ReasonForOutOfService=25 -- RegistrationSuccessful - The device has initialized and is unaware of any previous connection to the Cisco Unified CM
ReasonForOutOfService=26 -- TCPclosedVlanChange - The device closed the TCP connection due to reconfiguration of IP on a new Voice VLAN
ReasonForOutOfService=27 -- TCPclosedPowerSavePlus - The device closed the TCP connection in order to enter Power Save Plus mode
ReasonForOutOfService=100 -- ConfigVersionMismatch - The device detected a version stamp mismatch during registration Cisco Unified CM
ReasonForOutOfService=104 -- TCPclosedApplyConfig - The device closed the TCP connection to restart triggered internally by the device to apply the configuration changes
ReasonForOutOfService=105 -- TCPclosedDeviceRestart - 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
ReasonForOutOfService=106 -- TCPsecureConnectionFailed - The device failed to setup a secure TCP connection with Cisco Unified CM
ReasonForOutOfService=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
ReasonForOutOfService=108 -- VpnConnectionLost - The device could not register to Unified CM because VPN connectivity was lost
ReasonForOutOfService=200 -- ClientApplicationClosed - The device was unregistered because the client application was closed
ReasonForOutOfService=201 -- OsInStandbyMode - The device was unregistered because the OS was put in standby mode
ReasonForOutOfService=202 -- OsInHibernateMode - The device was unregistered because the OS was put in hibernate mode
ReasonForOutOfService=203 -- OsInShutdownMode - The device was unregistered because the OS was shut down
ReasonForOutOfService=204 -- ClientApplicationAbort - The device was unregistered because the client application crashed
ReasonForOutOfService=205 -- DeviceUnregNoCleanupTime - The device was unregistered in the previous session because the system did not allow sufficient time for cleanup
ReasonForOutOfService=206 -- DeviceUnregOnSwitchingToDeskphone - The device was unregistered because the client requested to switch from softphone to deskphone control
ReasonForOutOfService=207 -- DeviceUnregOnSwitchingToSoftphone - The device is being registered because the client requested to switch from deskphone control to softphone
ReasonForOutOfService=208 -- DeviceUnregOnNetworkChanged - The device is being unregistered because the client detected a change of network
ReasonForOutOfService=209 -- DeviceUnregExceededRegCount - The device is being unregistered because the device has exceeded the maximum number of concurrent registrations
ReasonForOutOfService=210 -- DeviceUnregExceededLoginCount - The device is being unregistered because the client has exceeded the maximum number of concurrent logons
02-29-2012 02:07 AM
Hi,
Found a bug
Regards
Alex
02-29-2012 02:15 AM
Thanks for your information. I noticed this bug too.
The information I am looking for is I would like to know if there is any referance on the ReasonForOutOfService. There is always a code follow by, and I would like to know the meaning behind them.
I tried search from internet, but there seems not much information about this.
02-29-2012 02:42 AM
Hi,
Did some searching.
Looks like Cisco are keeping this info for TAC use only
Example web page for 6911
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/6901_6911/8_5/english/admin_guide/6911web.html
The following device logs hyperlinks on a phone's web page provide information you can use to help monitor and troubleshoot the phone. To access a device log area, access the web page for the phone as described in the "Accessing the Web Page for a Phone" section.
•Console Logs—Includes hyperlinks to individual log files. The console log files include debug and error messages received on the phone.
•Core Dumps—Includes hyperlinks to individual dump files. The core dump files include data from a phone crash.
•Status Messages—Displays up to the 30 most recent status messages that the phone has generated since it was last powered up. You can also see this information from the Status Messages screen on the Web page of the phone. Table 6-6 describes the status messages that may be displayed.
•Debug Display—Displays debug messages that might be useful to the Cisco Technical Assistance Center (TAC) if you require assistance with troubleshooting.
Regards
Alex
Please rate useful posts
03-01-2012 09:05 AM
Thanks!
I might try to ask TAC if there is a case next time.
12-10-2013 07:09 AM
Here is a List of the reason codes for LastOutOfServiceInformation
ReasonForOutOfService=10 -- TCPtimedOut - The TCP connection to the Cisco Unified Communication Manager experienced a timeout error
ReasonForOutOfService=12 -- TCPucmResetConnection - The Cisco Unified Communication Manager reset the TCP connection
ReasonForOutOfService=13 -- TCPucmAbortedConnection - The Cisco Unified Communication Manager aborted the TCP connection
ReasonForOutOfService=14 -- TCPucmClosedConnection - The Cisco Unified Communication Manager closed the TCP connection
ReasonForOutOfService=15 -- SCCPKeepAliveFailure - The device closed the connection due to a SCCP KeepAlive failure
ReasonForOutOfService=16 -- TCPdeviceLostIPAddress - 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
ReasonForOutOfService=17 -- TCPDeviceRegsistrationTimedOut - The device closed the TCP connection due to a registration timeout
ReasonForOutOfService=18 -- TCPclosedConnectHighPriorityUcm - The device closed the TCP connection in order to reconnect to a higher priority Cisco Unified CM
ReasonForOutOfService=20 -- TCPclosedUserInitiatedReset - The device closed the TCP connection due to a user initiated reset
ReasonForOutOfService=22 -- TCPclosedUcmInitiatedReset - The device closed the TCP connection due to a reset command from the Cisco Unified CM
ReasonForOutOfService=23 -- TCPclosedUcmInitiatedRestart - The device closed the TCP connection due to a restart command from the Cisco Unified CM
ReasonForOutOfService=24 -- TCPClosedRegistrationReject - The device closed the TCP connection due to receiving a registration rejection from the Cisco Unified CM
ReasonForOutOfService=25 -- RegistrationSuccessful - The device has initialized and is unaware of any previous connection to the Cisco Unified CM
ReasonForOutOfService=26 -- TCPclosedVlanChange - The device closed the TCP connection due to reconfiguration of IP on a new Voice VLAN
ReasonForOutOfService=27 -- TCPclosedPowerSavePlus - The device closed the TCP connection in order to enter Power Save Plus mode
ReasonForOutOfService=100 -- ConfigVersionMismatch - The device detected a version stamp mismatch during registration Cisco Unified CM
ReasonForOutOfService=104 -- TCPclosedApplyConfig - The device closed the TCP connection to restart triggered internally by the device to apply the configuration changes
ReasonForOutOfService=105 -- TCPclosedDeviceRestart - 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
ReasonForOutOfService=106 -- TCPsecureConnectionFailed - The device failed to setup a secure TCP connection with Cisco Unified CM
ReasonForOutOfService=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
ReasonForOutOfService=108 -- VpnConnectionLost - The device could not register to Unified CM because VPN connectivity was lost
ReasonForOutOfService=200 -- ClientApplicationClosed - The device was unregistered because the client application was closed
ReasonForOutOfService=201 -- OsInStandbyMode - The device was unregistered because the OS was put in standby mode
ReasonForOutOfService=202 -- OsInHibernateMode - The device was unregistered because the OS was put in hibernate mode
ReasonForOutOfService=203 -- OsInShutdownMode - The device was unregistered because the OS was shut down
ReasonForOutOfService=204 -- ClientApplicationAbort - The device was unregistered because the client application crashed
ReasonForOutOfService=205 -- DeviceUnregNoCleanupTime - The device was unregistered in the previous session because the system did not allow sufficient time for cleanup
ReasonForOutOfService=206 -- DeviceUnregOnSwitchingToDeskphone - The device was unregistered because the client requested to switch from softphone to deskphone control
ReasonForOutOfService=207 -- DeviceUnregOnSwitchingToSoftphone - The device is being registered because the client requested to switch from deskphone control to softphone
ReasonForOutOfService=208 -- DeviceUnregOnNetworkChanged - The device is being unregistered because the client detected a change of network
ReasonForOutOfService=209 -- DeviceUnregExceededRegCount - The device is being unregistered because the device has exceeded the maximum number of concurrent registrations
ReasonForOutOfService=210 -- DeviceUnregExceededLoginCount - The device is being unregistered because the client has exceeded the maximum number of concurrent logons
12-10-2013 07:09 AM
I have the same problem, but I'm see this ReasonForOutOfService 18 on CP-9951 SIP Phones.
Has anyone more information of this case or a workaround for it ?
Also, I can see more other Reason in the same IP Phone how bellow:
09:59:49 ReasonForOutOfService=18
10:15:52 ReasonForOutOfService=12
10:17:53 ReasonForOutOfService=18
10:45:27 ReasonForOutOfService=12
10:45:29 ReasonForOutOfService=100
21:00:39 ReasonForOutOfService=0
11:14:52 ReasonForOutOfService=23
It is a historical of ReasonForOutServices on last 24 hours on the same IP Phone.
09-28-2016 08:32 AM
Hello Jason,
in the logs of a CUCM 11.0.1.20000-2, we have found several "ReasonForOutOfService=109", whose numeric code is not present in your list above.
Do you know what's its meaning?
If it can be useful as a piece of information, the logs mentioned above were related to a Cisco Jabber for Android connected over WLAN.
TIA and egards.
10-06-2016 08:00 AM
Hi
Looks like the web page (CUCM Serviceability --> Alarm --> Definition --> Select CallManager Alarm Catalog then Phone --> Click Find and click LastOutOfServiceInfo) was not updated after adding the new reason codes. There has been a documentation defect that was just opened for this (CSCvb63000 CUCM 11.5 missing complete list of alarm definitions).
I'm not sure if it is external yet, but when it is you should be able to find the reason codes there. Once the defect is resolved and included in an ES or SR that version will have the updated codes.
Regards,
Jason
02-08-2018 05:25 AM
Hi Guys,
In the RTMT was verified the follow reason code:
ReasonForOutOfService=101
Any have idea about this?
Thanks,
Regards,
Wilson
12-21-2018 06:52 AM
I currently have an 8861 wireless phone deployed and it is re-registering every 30 minutes. ( ReasonForOutOfService=14 )
Is there a timer that needs adjusting on either the Call Manager or the Wireless controller to prevent this from occurring? Thanks
03-12-2019 05:51 AM
SOLVED !!!!
There is a setting on the Wireless Controller:
WLANs > (WLAN ID profile name) > Advanced > Enable Session Timeout
This was set for 1800 seconds (30 Minutes).
Once this was disabled, the re-registering stopped.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide