Why SPA122 reboots itself every hour after reprovisioning

Question

The problem we're detecting is that this phone adapter reboots itself
when it takes the provisioning file from the server after 3600 seconds.
That should not be necessary (or at least we think it should be possible
to deactivate it), and sometimes it can cause further networking problems
if there are some other devices connected to the Ethernet port. Moreover,
when it takes between 2 or 3 minutes to recover itself from restart.
Is there any chance development team would take this under consideration?
Thanks in advance.

Answer 1

Once you set up logging, there will be a reboot reason in the log.  (syslog setup below)
You can look up the reboot reason here
https://supportforums.cisco.com/docs/DOC-9889
Some reasons the ATA might reboot.
- reboot reason: provisioning:  something changed in the provisioning file, this can be caused by a script tagging the date and time on the file, a serial number, or changing a feature, then changing back (as Dan Lukes mentioned).
- reboot reason: firmware update.
your device may be requesting firmware from the server, then downloading the firmware, once the firmware is installed, it reboots.  then the upgrade rule kicks in after the upgrade_error_delay (3600 in this case).
3600
http://XXXXX_my_ip_address_XXXXX/$PN.bin
To fix this put a conditional statement in the upgrade rule saying (if software version is 1.3.1 don't upgrade)
($swver != 1.3.1)? http://XXXXX_my_ip_address_XXXXX/spa122.1.3.1.bin
(verify this in the provisioning guide)
https://supportforums.cisco.com/docs/DOC-9894
Or remove the upgrade rule and see if that fixes the issue.
in terms of sending the factory default config out to the ATA each time.
Best practise is to  test your config with factory default + minimal config.
send the minimal config for device/network (in this case spa112.cfg is the default)
send the user/phone specific config as the $ma.cfg file ( cfg-88755604a1fa.txt in this case) as minimum config.
that way the configuration and provisioning server load will be less, configuration is simpler to troubleshoot, etc.
It's really not a good idea to send the same config parms to different  devices, or different firmware versions, as the parms or features may  have changed.  Most may work, but I've seen syntax differences between  device types and firmware cause all kind of wierd errors.  You can download the SPC tool for each firmware and device, use that to create a FDefault profile, then pull your config lines from there.
Much more exciting reading the provisioning guide.
If it's still rebooting post the syslog of a boot cycle, and we'll review. 
or contact  the support center at  866-606-1866.  You can create a case first, then call in with an existing Service Request number.  Just make sure you have a descriptive problem description, logs, etc attached.
To enable logging on the spa go to
Voice --> system 
add the IP address of your log server  in the debug and syslog, set debug level =3
Go into the extension  --> sip settings  --> sip debug option  to full
This will allow you to get all the sip messages between the call manager and the ATA.  Might not be required for this issue.
To set up syslog and debug through provisioning add these lines to the config
  ip.add.ress.of.server
  ip.add.ress.of.server
3
  full
  SPA1x2 device:
3
IP.OF.LOG.SRV
IP.OF.LOG.SRV
full
! like TFTPD64.exe, but there are other free syslog tools
dlm...