Polycom 650 files missing config. reverted

[Squigley]

Hello,

I have 2 650s giving the error "files missing. config. reverted" when booting.

They are remote, so I don't know what version of the firmware is on them, but it's recent, because they are using the split firmware. (2345-12600-001.sip_uc.ld)

I logged one booting, 4 files it tries to download are missing from our server, returning 404s to the phone:

$mac-directory.xml

$mac-web.cfg

000000000000-license.cfg

$mac-license.cfg

I would have thought the above files would be optional, and the phone would boot and run without them, but they do not.

Our server generates the config files dynamically, so I need to know which of these files is necessary for the phone to operate, so I can have our server modified to generate the file.

Thanks.

[SteffenBaierUK]

Hello Squigley,

welcome back to the Polycom Community.

The communitys VoIP FAQ contains this post here:

Jan 18, 2013 Question: What does the message "Missing files, config reverted" mean ?

Resolution: Please check => here <=

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

[Squigley]

Hi Steffan,

I knew what it means, and had found that post previously, and the reference in the admin guide, that there were actually files referred to that weren't available, but I wanted to know which of the files that was missing was actually required, since they seem to me like they should be optional, and not required for the phone to function.

We hadn't specifically specified any files that were missing, the phone's firmware was requesting those files by default.

In the end, it turns out that the phone had the wrong credentials entered, there was a character in the wrong case in either the username or password (I'm not sure which yet), so strangely it was able to download the majority of required files, but not upload any (including the boot log), which may have helped to have identified the cause of the issue.

I'm continuing to investigate how the phone could authenticate with the wrong credentials, but that issue will be related to our specific environment, due to our provisioning server using a java application to dynamically generate and serve configuration files.

Thanks for your response.