(09-26-2017 09:43 PM)blakeflorin Wrote:  lol Just caught this line multiple times in the log file on my phone-

<131>Sep 26 21:28:57 FWUP[854]: FWE <3+error > 337.924.183:shit happed on check ROM info!

Must be a developer Easter egg. I'm trying to figure out exactly what the "shit" is...

Blake



<131>Sep 26 21:28:49 ATP [854]: ATP <3+error > tftp to file failed, code = -8, msg = Read Error, retry = 2
<131>Sep 26 21:28:54 LIBD[854]: TFTP<3+error > Error Select! errno 2
<131>Sep 26 21:28:54 ATP [854]: ATP <3+error > tftp to file failed, code = -8, msg = Read Error, retry = 3
<128>Sep 26 21:28:57 FWUP[854]: ANY <0+emerg > 337.862.315:FWUP log :type=1,time=1,E=3,W=4,N=5,I=6,D=7
<128>Sep 26 21:28:57 FWUP[854]: ANY <0+emerg > 337.862.680:ANY =3
<128>Sep 26 21:28:57 FWUP[854]: ANY <0+emerg > 337.862.879:libfwup build:4.0.0.0-release(Sep 23 2016,11:33:06).
<131>Sep 26 21:28:57 FWUP[854]: FWE <3+error > 337.923.846:give up installing for the same version:66.81.0.110
<131>Sep 26 21:28:57 FWUP[854]: FWE <3+error > 337.924.183:shit happed on check ROM info!
<131>Sep 26 21:28:57 FWUP[854]: UPD <3+error > 337.924.389:upgrade download check failed,err=-7,incompatible version
<131>Sep 26 21:28:57 ATP [854]: ATP <3+error > fwup_check Err(err_no = -7)

(09-27-2017 07:50 PM)blakeflorin Wrote:  Dont really have a major firmware problem other than Yealink still has a bug where autoprovision parameters are locked down and will not accept valid configuration parameters directly exported from a working phone.

Specifically-
distinctive_ring_tones.alert_info.#.ringer

Firmware supports as many # slots as memory allows. Autoprovision is incorrectly coded to only accept values 1-10. All custom ringtones start at #11. Stock ringtones can not be deleted. There should not be any restrictions for importing these keys. So its impossible to autoprovision uploaded ringers.

I have not previously seen "shit happened" in any of the log files these phones output from earlier phone firmwares. Not really appropriate for business phones... But its funny.

(09-28-2017 08:55 PM)blakeflorin Wrote:  I'm running V82 on these new T48s phones. The distinctive ring tones can still only be set to the stock firmware ringtones residing in slots 1-10.

There's over 300 parameters on these phones, wide open that will accept any value entered in them valid or not through autoprovision. But for some reason these specific keys are locked down only to values 1-10

distinctive_ring_tones.alert_info.1.ringer =
distinctive_ring_tones.alert_info.2.ringer =
distinctive_ring_tones.alert_info.3.ringer =
distinctive_ring_tones.alert_info.4.ringer =

Its a simple fix....remove the check/restriction in the auto provision function on these keys.

Yealink gives the parameters to upload custom ringtones through autoprovision using the key (ringtone.url =). You can not overwrite stock firmware ringtones, these automatically start at value 11. I can set a parameter (distinctive_ring_tones.alert_info.#.ringer =) higher than 10 in the web interface. I can export the config with a set value higher than 10. I can also import the config manually into the phone with values higher than 10. This is an autoprovision bug. Fix it

I really wish Yealink would give us root access to terminal into these phones...I'd sign off on any warranty coverage for direct access to make them do what I want them to do. Even if its not supported, it should be a simple fix to make it supported.

Blake