cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1033
Views
5
Helpful
7
Replies

Phone re-provisioining ever hour

brantwinter2004
Level 1
Level 1

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.

 

1 Accepted Solution

Accepted Solutions

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.

View solution in original post

7 Replies 7

Dan Lukes
VIP Alumni
VIP Alumni

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 ...

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. 

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.

I have removed all commented lines and re provisioned. I will see what happens in the next hour.

Set "Resync Periodic" to something like 300 or so for the purpose of the test and you will need not to wait full hour ...

Yes - that is a smarter option :D I'll do that !

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.