SPA-Voice Debug - Reboot Reason List

[Alberto Montilla]

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:

• selecting "reboot" on phone's interface [example: Setup > 12]
  
  
• http://<IP_of_SPA>/admin/reboot
  
  

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

<end>

[moisansyl20]

Hi Patrick,

Wow!! Thank you very very much for this info!!

Regards,

Sylvain

[djmohame]

Hello Patrick,

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

[erik]

Hi,

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?

[djmohame]

Are the phones connected to the internet directly or behind a Nat/firewall ?

[erik]

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.

[djmohame]

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.

[erik]

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.

[erik]

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:

• increasing SIP T1 timer
• leave out the custom background picture
• increase the max registration on asterisk to 4000s
• decrease the max registration on Linksys phones to 3600s

still no luck. Any idea what the alloc error means? Does it have to do with BLF subscriptions?

Erik

[djmohame]

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

[Nick Leo]

Hi, pls add explanation of H633a0176.
Received from a PAP2T (v5.1.6).

Thanks, Nick

[westlandict]

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?

[cindy toy]

Hi Danny,

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.

Regards,

Cindy Toy

Cisco Small Business Support

Community Manager

[CraigBosCisco]

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

[daniel.stevens]

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.

[jps-dilbert]

Please add an explanation of "reboot reason:H73720931".

I see this with a SPA-2102 running firmware 5.2.12.

thx