Provisioned phones keep rebooting/refreshing

[sourceminer]

My SPA525G2 phones keep stating its refreshing Voice Component.

It keeps doing this over and over.

I have enabled syslog debuging and note that it states:

"request reboot type=16 reason=16"

What does this mean and why perhaps might my phone be refreshing all the time?

The file I am using to provision these phones with is something we have been working on below:

http://www.provisioner.net/user_uploads/1297815425-data.txt

Pretty basic XML file.

[sourceminer]

Hello, Echo...Echo...Echooo

Bump

[rvaltier]

Hi Kevin

Seems that you need to adjust your code as sentence "{$line}" is not working as you spected in this block:

{line_loop}
{$displayname}
{$ext}
{$ext}
{$pass}
{/line_loop}

xml file is not readable due this, but rest of the file is good.

Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

---

A name contained an invalid character. Error processing resource 'file:///C:/Documents and Settings/rvaltier/Desktop/data2....

 {$displayname}
---------------^

Regards,

Rogelio V.

[sourceminer]

Alas, a reply thank you I will look at this, meanwhile where do I find the documet for these codes:

"request reboot type=16 reason=16"

[rvaltier]

Take a look on this, also applies for phones:

https://supportforums.cisco.com/docs/DOC-9889

0x00000016                    parameter mismatch [example you are changing a parameter that should not be changed such as MWI]

Rogelio V.

[sourceminer]

Super thank you, So as to this XML file I am not sure how to go around this..

This is a variable that is assigned by my provisioner system, what would you recommend on how to prevent the XML from reading this variable as an invalid section?

[sourceminer]

Wait a minute... Your assuming that this XML is what the phone is actually reading.. Thats not correct.

Our Provisioning system builds the xml for each phone:

Example of the output the phone sees:

http://dl.dropbox.com/u/13876126/spa525G2.cfg

http://dl.dropbox.com/u/13876126/spac471fe2ede22.xml

[rvaltier]

Kevin

Thanks for share your files, this issue is related to Resync_Periodic timer, it is set to 60 secs.

resync typically takes place when the voice lines are idle. In case a voice line

is active when a resync is due, the IP Telephony Device delays the resync

procedure until the line becomes idle again.

However, it waits no longer than

Forced_Resync_Delay  14400 secs by default.

Have you set to 60 for any special reason?

Regards

Rogelio V.