At the first, 5minutes for PAP2T is so long for me. So I developped procedure to minimize the delay that works for PAP2T. Now, it works for SPA112 as well for me with no modification, I ha snot been affected by problem your described.
I can describe my procedure to you, it may help you to solve your problem.
Following data are taken from SPA configured to "factory default" via IVR, then disconnected. Time is in format M:SS
SPA in question has 1.2.1 firmware, but if I remembered correctly, it worked even with 1.0.2 for me.
----------------------------------------------------------
+0:00 - device powered on
+0:40 - DHCP started by device
+0:49 - DHCP handshaking completed, device has IP address and option 66 with TFTP server name
+1:04 - NTP query started from device, got reply from server, completed
+1:08 - DNS query with TFTP server name, got reply from server
+1:08 - TFTP RRQ /spa112.cfg, data transfer
content of first-time configuration file downloaded from TFTP:
Yes
30
30
Yes
No
Yes
https://test-provisioning...cz/Cisco/Provisioning.php?PRVST=-2
The trick is "flip/flop" of Enable_CDP. As this attribute require rebot on change, this force device restart. You can use any other attribute that force restart on change. As Resync_On_Reset is set to Yes, new provisionign request will be issued after reboot.
In advance, there is Resync_Periodic and Resync_Error_Retry_Delay set to 30s, just to be sure.
+1:09 - first-time configuration download complete
+1:54 - DNS request for test-provisioning...cz, resolved succesfully
+1:55 - HTTPS request
final device configuration downloaded from HTTP server
+1:55 - device reboot
+2:43 - DHCP started
+2:54 - DHCP completed
+3:02 - NTP started & completed
+3:52 - SIP REGISTER sent, registration completed, device ready for call
-----------------------------
You can compare my results with yours. It may help you to solve the problem.
