Below is the list of reboot reasons indicated by the SPA-Voice products. This information is provided by the SPA product debug trace.
Refer to the https://supportforums.cisco.com/docs/DOC-13059 if you want to know what provisioning parameters will cause the phone to reboot after being changed.
C means cold reboot
Wmeans warm reboot, won't redo dhcp
H means hardware reboot, usually caused by power or code reset
0x00000000 Boot due to power on, reported as "reboot reason:H0" in syslog
0x00000001 DHCP fail
0x00000004 parameter changes (through web, provisioning. For example when device's profile rule is changed...) syslog log will show "reboot reason:W4"
0x00000008 upgrade successfully
0x00000010 reboot requested by IVR or Web
0x00000016 parameter mismatch [example you are changing a parameter that should not be changed such as MWI]
0x00000020 upgrade backoff
0x00000040 reboot requested by SIP
0x00000080 upgrade failed
0x00000100 channel swap detected
0x00000200 Ethernet Link down
0x00000400 SIP Error
0x00000800 Slic Alarm detected
0x00001000 duplicate IP detected
0x00002000 Using last good known IP and reboot after 30 minutes
0x00004000 slic error
0x00008000 slic error
0x00010000 resource exhausted
0x00020000 pppoe failed
0x00040000 WAN and LAN subnet conflict
0x00080000 TDM error
0x00200000 reboot caused by DHCP auto sensing feature
0x00400000 reboot caused by remote customization
0x30300010 phone reboot caused by:
syslog will show "reboot reason:H30300010"
0x633a02d1 out of memory
0x73720168 code corruption [recover by performing a factory reset]
0x7372016c code corruption
0x737202d1 out of memory
0x7372092b IP address change due to DHCP lease expiring
Many thanks for this info.
I have one question:
How would the reboot code H633a02d1 be interpreted?
Is the rightmost 1 meaning "dhcp fail" while the following D (14 in dec) is equal to 8 (upgrade failed) + 4 (reboot requested by SIP) + 2 (upgrade backoff)?
Is the 2 (3rd from right) meaning Ethernet Link down?
BTW Many thanks for the great support in this forum
And I have a similar reboot reason from a SPA942 connected to a Broadsoft VOIP platform:
2009-11-16 13:34:39 Local0.Info 188.8.131.52 System started: email@example.com, reboot reason:H7372016c
Luca, I've upgraded the list to include the out of memory error.
boatanas, I've updated the list to include the code corruption error.
Sincerely thanks for this update, this is extremely useful support information.
Just one latest question though, what can cause the out of memory and code corruption?
And how to prevent/fix them?
I am getting H736c003d even after factory reset without making any changes at all. What does that mean?
This rare code indicates that the phone is having trouble starting/running. This is likely as a result of some physical trauma such as being dropped, lightning strike, or something similar. You will need to RMA the phone.
What is H73720168? My SPA3102 keeps rebooting with this code. See also https://supportforums.cisco.com/message/3096256#3096256.
I have a SPA921 that keeps rebooting with the same reboot reason every time. Reboot Reason H633a08fe any ideas of what that could be?
As Nelson says in the thread, it's due to a corruption in the code. Factory reset the device then upgrade it to the same version of firmware and try again. I've added this reboot reason to the master-list on this page.
We have some SPA-2102 that reboot like 2 or 3 times a day, and there are 2 reboot reasons not in the list on this page: H7372092b and H737202d1. The last one we saw it more than the other. Do you know what it could be? The units are connected either on DSL or Cable.
I've worked with Engineering to identify the reboot reasons and have update the list to include the codes you supplied.
I'm sending you a PM too.
Thank you for the fast reply, I really appreciate. Is it possible to know what can be the cause of the "out of memory" error? Is it hardware or can it be something in the configuration?
I think I have another information about the "out of memory" error. We are using the firmware 5.2.10. Is it protected against DoS? 1 hour ago there is a coworker unit that reboot with the reboot reason H737202d1 and in his router log, we saw an IP address in incoming by the port 5060 just before the unit reboots. The IP is not one of ours, so we are wondering if it's not a DoS attack. Could it be possible?
It certainly sounds like your devices are being subjected to denial of service attacks (DoS).
Be sure to set to yes, the Restrict Source IP parameter on your devices.
Setting to yes will cause the device to drop all SIP packets from untrusted sources.
Refer to the device's Administration Guide for additional information.