SIP-T20P Old Firmware doesnt upgrade in auto provisioning

[jcvh]

Helo folks, i am having trouble with some units of SIP-T20P, that have been in our warehouse for a while, so they came from factory with the 9.61.0.85 version firmware.
I usually deliver many units per month, so i have some provisioning infraestructure in place, and recently i had updated the scheme, so the phones, besides to load their configuration, upgrades the firmware to the last version (9.72.0.30, if im not wrong).
It has worked well for a while, but now i am getting this "old" phones, and the autoprovision firmware upgrade sometimes works and sometimes not (mostly not).
Right now i have a bunch of phones in stand-by, didn't wanted to do the upgrade manually, to have something to run tests with, in wait for some light from this forum.

The hardware version of the phones is 7.0.1.61.

I'm using the combined (M1+M7) version of the y file, with only the firmware upgrade part in the M1 section, as follows:

[ firmware ]
path = /tmp/download.cfg
server_type = tftp
server_ip = X.Y.Z.W
server_port = 53
#login_name =
#login_pswd =
#http_url = http://X.Y.Z.W/Firmwares/Yealink/Sip-T20P/
firmware_name = Firmwares/Yealink/SIP-T20P/9.72.0.30.rom

Already tried to change the "name" to an actual single name, without the path, without any sucess (in the tftp log it shows the phone downloading its y file, and mac-oriented file, but dosn't even try to load a firmware).

Thanks in advance, and regards!

[Raffles]

Is it possible that some of them already have a v7x firmware in them (meaning that the v61 method won't work)?

[jcvh]

(05-27-2014 05:36 PM)Raffles Wrote:  Is it possible that some of them already have a v7x firmware in them (meaning that the v61 method won't work)?

Nopes, i did specifically check what firmwere the phones are on, and is the above mentioned.
Nevertheless, it's true that some phones have arrived with a V70 firmware, but, since in the combined y000000000007.cfg file i have the firmware upgrade settings in both sections (M1 and M7), if the phone has firmware, lets say, 9.70.X.X, the upgrade works well.
Not the case with the 9.61.0.85, wich downloads the y000000000007.cfg file, but does not even try to download the new firmware file.

Can it be that such old firmware version can not be upgraded via autoprovisioning? I can't find the documentation for this version anymore...

Regards!

[jcvh]

BUMP!

Anybody?

Regards!

[Yealink Support]

Hi jcvh,

Please use M7 command to downgrade from V71/V72 to V61.

[ firmware ]
path = /tmp/download.cfg
server_type = tftp
server_ip = X.Y.Z.W
server_port = 53
#login_name =
#login_pswd =
#http_url = http://X.Y.Z.W/Firmwares/Yealink/Sip-T20P/
firmware_name = Firmwares/Yealink/SIP-T20P/9.61.0.85.rom

[jcvh]

(06-03-2014 07:12 PM)Yealink Support Wrote:  Hi jcvh,

Please use M7 command to downgrade from V71/V72 to V61.

Thanks for your reply! but...

I dont want to downgrade from V72 to V61, i want to upgrade from V61 to V72

Is this an neccesary intermediate step?

Regards!

[Yealink Support]

Hi jcvh,

You can upgrade from V61 to V72.
1. Please use the M1 template to upgrade to V72
2. Then use M7 template to auto provisioning in the future because we add many new features in V72 than V61.
NOTE: you can use configuration generation tool to generate M7 CFG template.

[JamesK]

for the firmware we using ftp instead of http. we have really great success with that.
when we do ftp there is only 1 line needed in the configuration file that way as well. it looks like this:

"ftp://userid:password@ftp.location.com/foldername/foldername/filename.xxx"

obviously you can use an ip address instead of the "ftp.location.xxx"
you can go several folders deep as well.
you can even use something like 2cdaemon to use as your ftp server if needed.

[jcvh]

(06-04-2014 04:59 PM)Yealink Support Wrote:  Hi jcvh,

You can upgrade from V61 to V72.
1. Please use the M1 template to upgrade to V72
2. Then use M7 template to auto provisioning in the future because we add many new features in V72 than V61.
NOTE: you can use configuration generation tool to generate M7 CFG template.

That's exactly what is described in the starting post, and... doesn't work...

Thaks anyway!

---

(06-04-2014 09:23 PM)JamesK Wrote:  for the firmware we using ftp instead of http. we have really great success with that.
when we do ftp there is only 1 line needed in the configuration file that way as well. it looks like this:

ftp://userid:password@ftp.location.com/f...lename.xxx

obviously you can use an ip address instead of the http://ftp.location.com
you can go several folders deep as well.
you can even use something like 2cdaemon to use as your ftp server if needed.

Thanks for your input JamesK, i will consider give it a try. I was hoping to achieve to have it working clean with tftp only.
I wonder why doesn't it work, do i have something misconfigured? or is it that the firmware upgrade using tftp simply doesn´t work in V61?

Thanks everybody!

[Yealink Support]

You should fill your IP URL in http_url such tftp://X.Y.Z.W:53/Firmwares/Yealink/SIP-T20P/
Then fill ROM name 9.61.0.85.rom in firmware_name.