[W52P+W56P] Same base station with with different handset models - Auto-provisioning

[Asanka]

Hi Guys,

Just have a quick question. We've situation where we're in a mixed device deployment. We've got W52Ps and W56Ps all in one location.

As both models use the same base and basefiles, what is the process upgrading firmware for each type of handset model?

Ideally i would not want to add the firmware URL to each MAC-file as it would mean that there are more places to keep track of when it comes to maintenance.

Regards

[Lucia_Yealink]

Dear Sir,

Do you mean you want to upgrade the handset firmware of W52 and W56 in the same time, right?

In the wui, we can only upgrade W52H or W56H in one time. But we can use the parameter 'over_the_air.url' via auto provision to update the firmware at the same time. Please see the detail below:

1.upload the firmware of W52H and W56H, in my side,26.73.0.10 is for W52H,61.80.0.1 is for W56H

2.configure a cfg1 file, add this parameter in cfg1 file:
#!version:1.0.0.1

over_the_air.url = http://10.2.2.21:8099/26.73.0.10.rom

auto_provision.server.url = http://10.2.2.21:8099/cfg2.cfg

3.configure a cfg2 file, add this parameter in cfg2 file:
#!version:1.0.0.1

over_the_air.url = http://10.2.2.21:8099/61.80.0.1.rom

4. add the auto provision URL in server URL(in mt test, it is http://10.2.2.21:8099/cfg1.cfg) via web interface.
click on auto provision now, it will ask for the auto provision server, and download cfg1 file, upgrade W52H to 26.73.0.10, and it also ask for another provision server URL.

5.in this test,firstly,W52H will upgrade to 26.73.0.10, and base will obtain the second provision server URL after upgrading, and it will download cfg2 file, upgrade W56H to 61.80.0.1
then all is done. it may spend some time to upgrade. So we use a nested auto provision way to access it.

You can refer to the picture below:
   
   

[Asanka]

Hi Lucia,

Thanks for this. But i don't think this would work in a situation where a 52H and 56H gets connected to the same base. Also even if it's two different bases, firmware details are stored in the base file which would be the same file as the the bases are identical for the devices.

My suggestion is that in the next firmware update for the base, create a new OTA URL like below so that we can deploy the correct handset firmware according to the handset.

over_the_air.url.w52h = http://path_to_w52h_frimware/w52h-latest.rom
over_the_air.url.w56h = http://path_to_w56h_frimware/w56h-latest.rom

This would allow for customers with mixed deployment an easy way of updating firmware.

[Asanka]

Hi Lucia,

Thanks for this. But i don't think this would work in a situation where a 52H and 56H gets connected to the same base. Also even if it's two different bases, firmware details are stored in the base file which would be the same file as the the bases are identical for the devices.

My suggestion is that in the next firmware update for the base, create a new OTA URL like below so that we can deploy the correct handset firmware according to the handset.

over_the_air.url.w52h =path_to_w52h_frimware
over_the_air.url.w56h = path_to_w56h_frimware

This would allow for customers with mixed deployment an easy way of updating firmware.

[Lucia_Yealink]

Yes， thank you for your suggest.

We have already add the parameter before in V81:
over_the_air.url.w52h =
over_the_air.url.w56h =

Regards
Lucia

[SteveDavies]

(05-05-2017 01:12 AM)Lucia Wrote:  Yes， thank you for your suggest.

We have already add the parameter before in V81:
over_the_air.url.w52h =
over_the_air.url.w56h =

Regards
Lucia

Hi Lucia,

I have seen W56P v.81 base firmware mentioned a couple of times since the start for this year (2017) but still cannot see anywhere to download it. Is it possible to have a beta release to test in our office?

Thanks,
Steve