SPA122 Firmware download

[samfiller]

I am having issues with the devices downloading firmware from http.

I have the following set

<Upgrade_Enable ua="na">Yes</Upgrade_Enable>

<Upgrade_Rule ua="na">http://myserver.com/spa122.bin</Upgrade_Rule>

And none of my devices ever contact for new firmware-

I took a test device set it up to

  <Upgrade_Enable ua="na">Yes</Upgrade_Enable>
  <Upgrade_Rule ua="na">tftp://myserver.com/spa122.bin</Upgrade_Rule>

And I see when using tftp in the logs random request for new firmware-

Any thoughts why http would not work?

(On a side note i have 1000's of  SPA2100 SPA2102 SPA1001 PAP2t that work without an issue)

Thanks!

[Dan Lukes]

1. so old firmware ...

or

2. device wish it's current firmware IS the one named http://myserver.com/spa122.bin already. So no reason to load it again. Rename firmware, change Upgrade_Rule and try again.

[samfiller]

My current test device is  Version 1.3.5 (004p) that is pretty new :-)

I do not even see in my servers logs the request for the firmware-

So its not an issue of same firmware-

Any other thoughts?

[samfiller]

I got it to work-

There is a bug- http://myserver.com/spa122.bin will not work.

Anything else will even http://myserver.com/SPA122.bin

As its a GET case will not matter-

Very strange!

[Dan Lukes]

Glad to hear you solved it. But your's "Very strange!" disclosed my attempt to explain you how it works has failed.

I will try to be more descriptive.

You should know the phone remembers the URL used for last firmware download. As long as the URL is still the same, it assume the firmware is the same as well. It doesn't try to load it to check version.  So once there has been burned firmware downloaded from http://myserver.com/spa122.bin phone will not attempt to download the same file again.

As you changed Upgrade_Rule to something different - http://myserver.com/SPA122.bin - and voila - the firmware has been downloaded.

Now you have firmware loaded from http://myserver.com/SPA122.bin and phone remembers it.

With next firmware you will face the same issue again. Phone will not try to download firmware from http://myserver.com/SPA122.bin as it assume it's the same as the current one.

Firmware name and Upgrade_Rule shall change with every firmware if you wish for upgrade. It will not work with constant Upgrade_Rule.

[samfiller]

Dan,

Thanks for the very informative post-

Its interesting as the past ATA's did not have that "feature". As well there is no mention of it in the provisioning documentation.

Any thoughts on a way of having the device always look for newer firmware with out "re" provisioning a new URL?

In the past I would replace the bin file on the server when the device would resync it would auto upgrade if there was a new file.

Any way of pointing the device to a "file" that will give it the new file path?

There for leaving the <Upgrade_Rule> constant.

For example

<Upgrade_Rule ua="na">http://myserver.com/spa122.xml</Upgrade_Rule>

[Dan Lukes · Accepted solution]

In the fact, I described you the behavior of PAP2T - e.g. very old ATA. I didn't tried it on SPA122 as I have no one there.

Any thoughts on a way of having the device always look for newer firmware with out "re" provisioning a new URL?

Reset to factory default.

I have no idea why it's important to have Upgrade_Rule constant, but you are trying to administer the device in uncommon way.

The common way is to configure periodic download of provisioning file not firmware file (moreover it's not possible). It's matter of file size - provisioning file is small, firmware file so large.

Change of firmware name in provisioning file is as simple as edit of such file. Once new provisioning become downloaded by ATA, the download of firmware will be triggered.