Struggling to Provision Phones and Upgrade Firmware After V15.6

Status
Not open for further replies.

Wendelspanswick

Joined
Jan 11, 2016
Messages
178
Reaction score
10
We have upgraded a site to V15.6 and compiled new custom templates but we cannot get the Yealink T23g phones to provision through the management console or upgrade the firmware to 44.83.0.55 even if we use a standard Yealink template.
The management console goes through the motions and says that the update will be downloaded and the phone will reboot but nothing happens.
This is in the Management Log:
2018/10/30 11:21:17.175|3612|0023|Inf|PRV: Requested file '/provisioning/uniqueInstance/yealink_phonebook.xml' cannot be generated
2018/10/30 11:21:19.515|3612|0016|Inf|PRV: Requested file '/provisioning/uniqueInstance/0015659ccab6.boot' cannot be generated
2018/10/30 11:21:19.515|3612|0016|Inf|PRV: Requested file '/provisioning/uniqueInstance/0015659ccab6.boot' is not found in file system also
2018/10/30 11:21:19.558|3612|0026|Inf|PRV: Requested file '/provisioning/uniqueInstance/y000000000000.boot' cannot be generated
2018/10/30 11:21:19.558|3612|0026|Inf|PRV: Requested file '/provisioning/uniqueInstance/y000000000000.boot' is not found in file system also
2018/10/30 11:21:19.654|3612|0023|Inf|PRV: Requested file '/provisioning/uniqueInstance/y000000000044.cfg' will be generated
2018/10/30 11:21:20.001|3612|0038|Inf|PRV: Requested file '/provisioning/uniqueInstance/0015659ccab6.cfg' will be generated
2018/10/30 11:21:24.256|3612|0023|Inf|PRV: Requested file '/provisioning/uniqueInstance/logo/yealinkt22.dob' cannot be generated
2018/10/30 11:21:24.299|3612|0026|Inf|PRV: Requested file '/provisioning/uniqueInstance/Directory_setting.xml' cannot be generated
2018/10/30 11:21:25.739|3612|0023|Inf|PRV: Requested file '/provisioning/uniqueInstance/dialing.xml' cannot be generated
2018/10/30 11:21:26.163|3612|0038|Inf|PRV: Requested file '/provisioning/uniqueInstance/firmware/yealink/patchT23-44.83.0.55.rom' cannot be generated
 
Compare the provision path that is in the phones with the one shown in 3cx management console, extensions, extension #, provisioning. If the provision path differs (including port numbers) then that would be why provisioning and firmware upgrades fail.
 
Provisioning seems to work now (not sure why as there are 3 of us working on it) but the firmware upgrade keeps failing?
 
So If we manually upgrade the firmware to the Yealink phone it works but not if we do it from the management console.
Where does the 3CX store the firmware on the server as I cannot see it under Program Data/3CX/Instance1 ?
 
Status
Not open for further replies.