T48S log file... "shit happed on check ROM info!"

[Aishion_Yealink]

(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.

Dear Blake,

Thanks for your feedback about the "shit log", I test on my side and reproduce the same issue, I have feedback this issue to our R&D, and it will be fix on V83, sorry for the improper parameter in the log.

For auto provision issue,

Do you mean you want to do a auto provision directly auto-p with valid configuration parameters directly exported from a working phone instead of import it to the phone, if so, our phone don't support that ,please kindly find auto-p parameter in administrator guide in below link:

http://download.support.yealink.com/down...V81_90.pdf

If not, please kindly send us the config.bin on your side and "valid configuration parameters directly exported from a working phone", I will test on my side to debug.

Below is the FAQ about how to get the config.bin:

http://support.yealink.com/faq/faqInfo?id=313

For distinctive ring tones,

It's an known bug, which were fixed in the latest V82, please kindly upgrade firmware in below link:

http://download.support.yealink.com/down...2.0.20.rom

Any misunderstandings, please feel free to let me know.

Best Regards
Aishion