[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
T48S log file... "shit happed on check ROM info!"
Author Message
blakeflorin Offline
Junior Member
**

Posts: 12
Joined: Jun 2017
Reputation: 0
Post: #1
T48S log file... "shit happed on check ROM info!"
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-26-2017 09:43 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Aishion_Yealink Offline
Administrator
*******

Posts: 116
Joined: Mar 2017
Reputation: 1
Post: #2
RE: T48S log file... "shit happed on check ROM info!"
(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)
Dear Blake,

According to your log, it seems you meet the problem when you were failed to upgrade SAME firmware. Can you kindly make me clear what issue that you get this log? Is there any features affected?

Would you please reproduce this issue and share us the config.bin file, level 6 syslog and trace, after that I will let our R&D to check this.

About how to get these files, please refer below FAQ:

http://support.yealink.com/faq/faqInfo?id=311 [Situation 2]

Please note to set the system log to level6 and provide three of them at one time.

BR

Aishion
09-27-2017 02:55 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
blakeflorin Offline
Junior Member
**

Posts: 12
Joined: Jun 2017
Reputation: 0
Post: #3
RE: T48S log file... "shit happed on check ROM info!"
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-27-2017 07:50 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Aishion_Yealink Offline
Administrator
*******

Posts: 116
Joined: Mar 2017
Reputation: 1
Post: #4
RE: T48S log file... "shit happed on check ROM info!"
(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
09-28-2017 08:19 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
blakeflorin Offline
Junior Member
**

Posts: 12
Joined: Jun 2017
Reputation: 0
Post: #5
RE: T48S log file... "shit happed on check ROM info!"
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 Wink

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
09-28-2017 08:55 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Aishion_Yealink Offline
Administrator
*******

Posts: 116
Joined: Mar 2017
Reputation: 1
Post: #6
RE: T48S log file... "shit happed on check ROM info!"
(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 Wink

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

Hi Blake,

Sorry that we can't provide you root assess for security reasons.

I just test my side with the latest V82 firmware T46S(T48S,T42S,T41S)-66.82.0.20.rom

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

And try configured distinctive ring tone well through auto provision, please kindly find attached cfg file which I were successfully set distinctive ringtone for reference.

Would you please try to upgrade the firmware which I provided and test again, if the issue still exist, please kindly reproduce this issue and share us the config.bin file, level 6 syslog and trace that we can debug?About how to get these files, please refer below FAQ:

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

Any update, please feel free to let me know.

Best Regards
Aishion


Attached File(s)
.cfg  common.cfg (Size: 213 bytes / Downloads: 5)
09-30-2017 03:03 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  Yealink T48s Firmware update failed dangmoss 2 2,262 02-19-2022 03:09 AM
Last Post: dangmoss
  Add the Remote Phone Book via a .cnf file sfrazier 6 2,505 02-04-2022 04:02 AM
Last Post: sfrazier
  Problem Change Firmware T48s from SFB to SIP Lars Maschke 2 2,474 01-14-2022 10:22 AM
Last Post: kumagera
  T48s setting outbound caller ID thunderzhao 1 2,465 09-10-2021 04:08 PM
Last Post: complex1
  T48S Display Language change (Step by Step) schost 0 2,338 03-04-2021 04:02 PM
Last Post: schost
  Call-Info sip header for T46G sidjf3zhdu 9 21,919 02-22-2021 04:06 PM
Last Post: jiansong
  T48s - Missed calls Bernhard77 0 1,941 01-28-2021 04:10 PM
Last Post: Bernhard77
  T48S storage space jehanzebnavid 2 4,289 11-25-2020 01:05 AM
Last Post: jehanzebnavid
Question Switch account on T48S - Outgoing caller ID remains at default account puregin 0 2,310 09-30-2020 09:52 AM
Last Post: puregin
  T48S Frostie 2 4,171 07-29-2020 02:15 PM
Last Post: Yisroel_MongoTEL

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication