Yealink Forums

Full Version: firmware upgrade through autoprovisioning
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I'm trying to upgrade a w52p basestation through autoprovisioning, using the configuration directive as provided in the autoprovisioning guide:

firmware.url = http://domain.org/path/to/25.73.0.25.rom

I started by downgrading the firmware to 25.40.0.15 . When I try to provision now, the config is fetched, but the basestation is kept in the resetted state, without applying the configuration. No status indicator or anything that suggests what went wrong. Then I moved to 25.73.0.20.rom and tried the same autorprovisioning method with firmware upgrade directive. Now the django testserver returns a broken pipe, which suggests the basestation doesn't close the connection properly. I then put an nginx proxy in-between. The firmware is requested without error now, but it keeps the Yealink basestation's power button in a blinking state. After half an hour I decided to cut power and reboot the basestation. Same thing is happening again.

The lack of feedback from the device and the sparse documentation is very frustrating. Does anyone have any positive experiences with firmware upgrades through autoprovisioning? (w52p)
The firmware is updated when i use tftp(tftpd on archlinux):
firmware.url = tftp://domain.org/path/to/25.73.0.25.rom

It seems that firmware upgrades over http just fail silently.
Reference URL's