09-10-2015 10:14 PM - edited 03-21-2019 08:46 AM
Hi - I have a bunch of SPA504G handsets that provision via tftp. I notice them reboot every hour even when there has been no change in the XML file hosted on the TFTP server. XML options re. provisioning are:
<Provision_Enable group="Provisioning/Configuration_Profile">Yes</Provision_Enable>
<Resync_On_Reset group="Provisioning/Configuration_Profile">Yes</Resync_On_Reset>
<Resync_Random_Delay group="Provisioning/Configuration_Profile">2</Resync_Random_Delay>
<Resync_At__HHmm_ group="Provisioning/Configuration_Profile"/>
<Resync_At_Random_Delay group="Provisioning/Configuration_Profile">600</Resync_At_Random_Delay>
<Resync_Periodic group="Provisioning/Configuration_Profile">3600</Resync_Periodic>
<Resync_Error_Retry_Delay group="Provisioning/Configuration_Profile">300</Resync_Error_Retry_Delay>
<Forced_Resync_Delay group="Provisioning/Configuration_Profile">14400</Forced_Resync_Delay>
<Resync_From_SIP group="Provisioning/Configuration_Profile">Yes</Resync_From_SIP>
<Resync_After_Upgrade_Attempt group="Provisioning/Configuration_Profile">Yes</Resync_After_Upgrade_Attempt>
<Resync_Trigger_1 group="Provisioning/Configuration_Profile"/>
<Resync_Trigger_2 group="Provisioning/Configuration_Profile"/>
<Resync_Fails_On_FNF group="Provisioning/Configuration_Profile">Yes</Resync_Fails_On_FNF>
<Profile_Rule group="Provisioning/Configuration_Profile">/xml/spa$MA.xml</Profile_Rule>
What am I doing wrong ? I thought they should only provision themselves if something int he XML has changed.
Solved! Go to Solution.
09-11-2015 01:48 AM
Note you should consider the provisioning file format rather XML-like than full XML. The internal parser capability is rather limited. Thus be very conservative with syntax used within.
If you will fail to identify duplicate, remove the commented sections at all.
09-10-2015 11:06 PM
You didn't disclosed complete file.
Reboot is triggered once a critical option has changed. Note that almost all options are considered critical. Also note that "changed" condition apply even in the case an option is changed twice within provisioning file (so resulting value is still the same).
So, check your file for duplicates nd remove them.
Rate useful advices. It will help others to found solutions ...
09-10-2015 11:49 PM
Ok I'll have a look. I know the file isn't changing so there must be a duplicate. I do have a <!-- commented --> section that duplicates an xml value but it should not be parsed unless there is a bug in the provisioning code.
Ill go go through the xml and try to find any other duplication.
I can post the full xml once I take out sensitive data.
09-11-2015 01:48 AM
Note you should consider the provisioning file format rather XML-like than full XML. The internal parser capability is rather limited. Thus be very conservative with syntax used within.
If you will fail to identify duplicate, remove the commented sections at all.
09-11-2015 02:03 AM
I have removed all commented lines and re provisioned. I will see what happens in the next hour.
09-11-2015 02:46 AM
Set "Resync Periodic" to something like 300 or so for the purpose of the test and you will need not to wait full hour ...
09-11-2015 02:46 AM
Yes - that is a smarter option :D I'll do that !
09-11-2015 03:58 AM
Removing the commented lines worked. It seems that even if a duplicate config block is commented the phone still parses it. Seem like a bug to me.
Anyway, phone is not continually provisioning any longer. Thanks Dan for your pointer.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide