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 126.96.36.199 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.
Wow!! Thank you very very much for this info!!
I hope for your help in the below issue.
Cu got 3 SPA922 phones which are rebooting at the same time , the reboot reasons in the log are “reboot reason:W4" and “reboot reason:H0" .
From the above reboot reason list seems that those are normal reboots , is that correct ? can you give some light on it
Thanks in advance ---- Jolis
One of our customers has 4x SPA962 each with 2xSPA932. They randomly restart with various reboot reasons.
C4 is one I cannot find in the list.
Strangely enough, even when H0 is the reason, the syslog shows:
<date> <time> <IP address> OP ALLOC ERROR 7 641 (last number varies).
after that, logging stops and 10 seconds later I see a DHCP request coming in and the phone comes up, giving reboot reason H0.
This seems more than just a regular power on reason (we checked power supplies, switched them, use PoE etc etc). Any idea?
Are the phones connected to the internet directly or behind a Nat/firewall ?
They have public IP addresses, but are behind a firewall and only register at an Asterisk 1.6 server. In Asterisk, they're defined using NAT=no.
Try to configure the address of the Asterisk server in the restricted Access Domain parameter, the maximum is five domains. the Cisco IP phones will respond to SIP messages only from the entered servers. So it will improve phone security.
If it doesn't help and the phones still reboots move them off of the public facing WAN behind NAT with private IPs , of course you need to Forward the specific port range of SIP and RTP in the router to the phones.
Thanks for thinking along and for the suggestions. I now realize that the only difference between this deployment and many others I did is that the phones have public IP addresses. Would be weird, though, if that would upset them. And it would cost me a lot of convincing power to move them behind NAT. Anyway, the first suggestion is in place on a test phone now. Too bad it will take while to see if it helps. Will keep you informed.
Well, the restricted Access Domain parameter didn't help. Some research shows that this is meant to lock out unwanted resync sources when the devices would be customized. They were and are not, however.
Putting them behind NAT is my last resort, since it has quite some impact on the production environment.
Meanwhile I tried:
still no luck. Any idea what the alloc error means? Does it have to do with BLF subscriptions?
The restricted access domain will improve the security (will let the phones to respond to sip messages only from the entered serverss but it will not element other attacks as HTTP or ICMP Flooding)
So please try the last resort and put the phones behind NAT
Hi, pls add explanation of H633a0176.Received from a PAP2T (v5.1.6).
I have one spa509 that reboots about every 5 minutes.
How can i see that reboot codes so i can see what the reason is of that reboots?
Actually your original post in the discussion area is the correct place to ask this question instead of the document area here which is supposed to be for comments not questions. Please go back to your original post: https://supportforums.cisco.com/message/3269484#3269484 and erase the comment that you posted in the wrong area so that people can help answer your question.
Cisco Small Business Support
Christian, I am seeing the same reboot reason on my PAP2T (H633a08fe). Did you ever get a response or find out what that reason code means?
See also my query here: https://supportforums.cisco.com/thread/2067636
Ok, we have a phone rebooting periodocally with error C8000 - I presume that's an 'slic error'?
What is the cause/remedy?
This phone is one of 30, the rest do not have this issue.
Please add an explanation of "reboot reason:H73720931".
I see this with a SPA-2102 running firmware 5.2.12.
is asking about code
What does mean 0x00008000 slic error, I got it trying to use dictionaries with a spa504g on v 7-5-5, the phone continuously reboot.
SLIC may mean "subscriber line interface card" here. It may be the card or IC that connects analog handset and hook switch to digital part of the phone.
Just guessing - I have no access to internal Cisco documentation nor the phone schema.
I found a workaround. It seems that when loading dictionaries and bitmap image using tftp the phone continuously reboots.
loading the dictionaries using tftp and bitmap image using http works well. The firmware is buggy.
The firmware is buggy.
With no doubt, all the times ;-)
But I'm not sure it your problem is symptom. And even in the case it is symptom of broken firmware, nobody will spent a time to such problem without logs. Please catch the packets for both cases (e.g. tftp as well as http method) together with syslog&debug (level 3 at least) messages, create new thread describing the problem and workaround and attach them to such thread. May be, the Cisco will analyze the issue then patch the firmware.
I opened another discussion with the logs, you can find them here :
I got this:
Reboot Reason 2: System 4
what is this mean?
Wrong forum. SPA5xx device is not ATA device but SPA IP Phone. This document doesn't apply to it.
Does anyone have an interpretation for reboot reason:H643a02d1?