SPA502G random reboots

aliullah1 · ‎12-08-2014

192.168.143.42Hi,

I recently edited my spacfg file and I have noticed that the phones (SPA502G) randomly reboots. I am wondering if what I added is the reason why. I basically configured the timezone and a dictionary server script to the provision.

<Time_Zone group="Regional/Miscellaneous">GMT-05:00</Time_Zone>

<Dictionary_Server_Script group="Regional/Miscellaneous">serv=tftp://ipaddress/;d0=English;x0=spa50x_30x_en_v756.xml;d1=French;x1=spa50x_30x_fr_v756.xml;</Dictionary_Server_Script>

<Language_Selection group="Regional/Miscellaneous">French</Language_Selection>

<Default_Character_Encoding group="Regional/Miscellaneous">ISO-8859-1</Default_Character_Encoding>

I am wondering if any of this is the reason why the random reboots happen.

I checked the logs and found this:

Dec 8 14:39:21 192.168.143.42 request reboot type=4 reason=SIP Triggered(40)
Dec 8 14:39:21 192.168.143.42 request reboot type=4 reason=SIP Triggered(40)
Dec 8 14:39:21 192.168.143.42 ####[0]Start UnRegister
Dec 8 14:39:21 192.168.143.42 ####[0]Start UnRegister
Dec 8 14:39:21 192.168.143.42 start TMR K
Dec 8 14:39:21 192.168.143.42 last message repeated 3 times
Dec 8 14:40:11 192.168.143.42 SCCPTCP:ERR:Can't bind to a01342a:5060 errno=49
Dec 8 14:40:11 192.168.143.42 SCCPTCP:ERR:Can't bind to a01342a:5060 errno=49
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Idle key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Idle key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Idle key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Idle key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Progressing key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Progressing key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Progressing key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Progressing key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Releasing key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Releasing key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Releasing key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Releasing key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Hold key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Hold key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Hold key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Hold key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Shared Active key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Shared Active key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Shared Active key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Shared Active key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Shared Held key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkcfwd in Shared Held key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Shared Held key list is not defined
Dec 8 14:40:11 192.168.143.42 PGSK: chkdnd in Shared Held key list is not defined
Dec 8 14:40:11 192.168.143.42 [0]Reg Addr Change(0) 0:0->a017933:5060
Dec 8 14:40:11 192.168.143.42 [0]Reg Addr Change(0) 0:0->a017933:5060
Dec 8 14:40:11 192.168.143.42 start TMR K
Dec 8 14:40:11 192.168.143.42 last message repeated 3 times
Dec 8 14:40:11 localhost in.tftpd[30003]: RRQ from 192.168.143.42 filename logo_1b.bmp
Dec 8 14:40:11 192.168.143.42 content len =830
Dec 8 14:40:11 192.168.143.42 content len =830
Dec 8 14:40:11 192.168.143.42 Embedded Msg>: save param: 550 = 1 551 save param: 551 = 0 551
Dec 8 14:40:16 192.168.143.42 Timer K Fires
Dec 8 14:40:16 192.168.143.42 last message repeated 3 times
Dec 8 14:40:30 192.168.143.42 resync rule: tftp:// 192.168.143.145/spae8edf36b4e54.xml
Dec 8 14:40:30 192.168.143.42 resync rule: tftp:// 192.168.143.145/spae8edf36b4e54.xml
Dec 8 14:40:30 192.168.143.42 ++ j=0 sip=0a017933
Dec 8 14:40:30 192.168.143.42 ++ j=0 sip=0a017933
Dec 8 14:40:30 192.168.143.42 SPA502G e8:ed:f3:6b:4e:54 -- Requesting resync tftp://192.168.143.145:69/spae8edf36b4e54.xml
Dec 8 14:40:30 localhost in.tftpd[30036]: RRQ from 192.168.143..42 filename /spae8edf36b4e54.xml
Dec 8 14:40:30 192.168.143.42 SPA502G e8:ed:f3:6b:4e:54 -- Requesting resync tftp://192.168.143.145:69/spae8edf36b4e54.xml
Dec 8 14:40:30 192.168.143.42 SPA502G e8:ed:f3:6b:4e:54 -- Successful resync tftp://192.168.143.145:69/spae8edf36b4e54.xml
Dec 8 14:40:30 192.168.143.42 SPA502G e8:ed:f3:6b:4e:54 -- Successful resync tftp://192.168.143.145:69/spae8edf36b4e54.xml
Dec 8 14:40:30 192.168.143.42 request reboot type=2 reason=Provisioning(4)
Dec 8 14:40:30 192.168.143.42 request reboot type=2 reason=Provisioning(4)
Dec 8 14:40:30 192.168.143.42 ####[0]Start UnRegister
Dec 8 14:40:30 192.168.143.42 ####[0]Start UnRegister
Dec 8 14:40:30 192.168.143.42 start TMR K
Dec 8 14:40:30 192.168.143.42 last message repeated 3 times
Dec 8 14:40:35 192.168.143.42 Timer K Fires
Dec 8 14:40:35 192.168.143.42 Timer K Fires
Dec 8 14:40:35 192.168.143.42 Timer K Fires
Dec 8 14:40:35 192.168.143.42 Timer K Fires
Dec 8 14:41:27 192.168.143.42 SCCPTCP:ERR:Can't bind to a01342a:5060 errno=49
Dec 8 14:41:27 192.168.143.42 SCCPTCP:ERR:Can't bind to a01342a:5060 errno=49
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Idle key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Idle key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Idle key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Idle key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Progressing key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Progressing key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Progressing key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Progressing key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Releasing key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Releasing key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Releasing key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Releasing key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Hold key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Hold key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Hold key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Hold key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Shared Active key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Shared Active key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Shared Active key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Shared Active key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Shared Held key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkcfwd in Shared Held key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Shared Held key list is not defined
Dec 8 14:41:27 192.168.143.42 PGSK: chkdnd in Shared Held key list is not defined
Dec 8 14:41:27 192.168.143.42 [0]Reg Addr Change(0) 0:0->a017933:5060
Dec 8 14:41:27 192.168.143.42 [0]Reg Addr Change(0) 0:0->a017933:5060
Dec 8 14:41:27 192.168.143.42 start TMR K
Dec 8 14:41:27 192.168.143.42 last message repeated 3 times
Dec 8 14:41:27 localhost in.tftpd[30131]: RRQ from 192.168.143.42 filename logo_1b.bmp
Dec 8 14:41:27 192.168.143.42 content len =830
Dec 8 14:41:27 192.168.143.42 content len =830
Dec 8 14:41:27 192.168.143.42 Embedded Msg>: save param: 550 = 1 551 save param: 551 = 0 551
Dec 8 14:41:32 192.168.143.42 Timer K Fires
Dec 8 14:41:32 192.168.143.42 last message repeated 3 times

I am fairly new to the IP phone system and trying to figure this out.

Thanks for the help.

Dan Lukes · ‎12-08-2014

Your log show two reboot reasons. The first one:

Dec  8 14:39:21 192.168.143.42 request reboot type=4 reason=SIP Triggered(40)

This reboot has not been random, it has been triggered by remote request (SIP NOTIFY packet). You need to identify who has sent such request and why.

The second one:

Dec  8 14:40:30 192.168.143.42 request reboot type=2 reason=Provisioning(4)

This reboot has not been random, it has been caused by provisioning. (Re-)provisioning is either triggered by remote request or periodic (if configured) or triggered by boot. I assume the boot is the reason for provisioning in such particular case. Provisioning results in (another) reboot when a parameter has been changed by it.

Provisioning may trigger reboot everytime if a value of particular option has been changed twice within the provisioning file. It may trigger reboot if an option is set to invalid value as well.

aliullah1 · ‎12-09-2014

The thing is these random reboots have occurred for every telephone that is configured under this template. None of our other phones have done it (they are using a standard template).

Dan Lukes · ‎12-09-2014

My response has been based on log records disclosed by you. As I claimed above, there are two reboots recorded. The first one has been caused by remote request to reboot, the second one has been caused by provisioning file.

May be your phone reboots with no apparent reason, but your log contain no such case. You need to catch log with random reboot recorded.

If you wish that no remote request to reboot should arrive, you need to catch such SIP request and analyse who sent it and why. Your phone just followed the orders.