Yealink Forums

Full Version: [BUG?]Screen backlight turn on on SIP Keep alive
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,
I upgraded a YEALINK T21P-e2 firmware to latest one ( 52.81.0.110 ) and the backlight bug suddenly appeared (referring to http://forum.yealink.com/forum/showthrea...ode=linear ).

Going deep to the problem, i put syslog to level 6 and noticed:
Quote:<132>Jul 13 14:54:43 sys [967]: POFF<4+warnin> PC Cable connected
<134>Jul 13 14:54:43 sys [967]: SRV <6+info > get port 2 speed 10
<133>Jul 13 14:54:43 ipvp[1286]: IPVP<5+notice> 683.402.278:Message=0x00020000(0x00000001+0x00000002+0)
<134>Jul 13 14:54:43 ipvp[1286]: IPVP<6+info > 683.402.607:unknown msg,0x00020000,from 0xd28f9304 0x00000001, 0x00000002
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > BackLightManager::AddEvent [1]
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > objEvent.eType == BACK_LIGHT_DEFAULT || objEvent.brightTimer == 0
<134>Jul 13 14:54:43 Log [1313]: IDLE<6+info > [Network] OK
<134>Jul 13 14:54:43 sua [1151]: APP <6+info > [SIP] <IPC_rcv >:msg:0x00020000, wparam:0x00000001, lparam:0x00000002, id:Undefied on dspg
<134>Jul 13 14:54:43 Log [1313]: IDLE<6+info > CStatusManager: Notify Status Changed m_isOn=[1] [0]
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > BackLight Earse Event(4)
<134>Jul 13 14:54:43 Log [1313]: DIR <6+info > Directory: message(0x20000), wparam(0x1), lparam(0x2)
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Operation[1] to power saving
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]CPowerSavingManager::GetTimeoutOfOperation(1, 1499964883)
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Time[1499964883]: day=3, hour=16
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Time range: 1499929200~1499972400 type=0
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout to power saving: 1500022483, interval=57600
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Time[1499972400]: day=3, hour=19
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Next time range: 1499972400~1500015600 type=1
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout to power saving: 1499965483
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout to power saving: 1499972400
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout[1499972400] less than original timeout[1499972400], will not change.
<134>Jul 13 14:54:57 sua [1151]: DLG <6+info > [000] cb_nict_kill_transaction (id=358)
<134>Jul 13 14:54:57 sua [1151]: FSM <6+info > [000] free transaction ressource 358 0b8444c6210f580409e6ff6e5c60e718
<134>Jul 13 14:54:57 sua [1151]: FSM <6+info > [255] free nist ressource
<134>Jul 13 14:54:58 sua [1151]: DLG <6+info > [255] SIP: 192.168.4.2:5060 Keep Alive sent on UDP!
<134>Jul 13 14:55:03 Log [1111]: WEB <6+info > URI: /servlet?p=login&q=loginForm&jumpto=status
<134>Jul 13 14:55:03 Log [1111]: WEB <6+info > such session have invalidate,will to create a new session
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > URI: /servlet?p=login&q=getsessionid&Rajax=0.966261073536159
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > such session have invalidate,will to create a new session
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > such session have invalidate,will to create a new session
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > sessionNum: 6
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > URI: /servlet?p=login&q=login
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > Crypto get plain data : session id is equal
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > ip:192.168.4.99 Login at time=1499957706
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > ip:192.168.4.99 The password is right!
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > ip:192.168.4.99 Login in Success At time: [17035]
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > URI: /servlet?p=status&q=load
<134>Jul 13 14:55:06 Log [1313]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 2. result[2]
<134>Jul 13 14:55:06 Log [1111]: ETLL<6+info > mkit_call return(2,0)
<134>Jul 13 14:55:06 Log [1313]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 65537. result[65537]
<134>Jul 13 14:55:06 Log [1111]: ETLL<6+info > mkit_call return(65537,0)
<134>Jul 13 14:55:06 Log [1313]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
<134>Jul 13 14:55:06 Log [1111]: ETLL<6+info > mkit_call return(0,0)
<134>Jul 13 14:55:08 Log [1111]: WEB <6+info > URI: /servlet?p=settings-preference&q=load
<134>Jul 13 14:55:09 Log [1111]: WEB <6+info > URI: /servlet?p=settings-config&q=load
<134>Jul 13 14:55:12 Log [1111]: WEB <6+info > URI: /servlet?p=settings-config&q=exportLocalLog&type=1
<134>Jul 13 14:55:12 Log [1111]: WEB <6+info > Partition free(byte): /tmp/ [32448512], /config/ [86016], /data/ [86016]
<134>Jul 13 14:55:13 Log [1313]: BKLT<6+info > OnTimerOut InactiveLevel[0]
<134>Jul 13 14:55:13 Log [1313]: BKLT<6+info > PowerSaving_IsInPowerSavingMode [0]
<134>Jul 13 14:55:13 Log [1313]: BKLT<6+info > BackLight Set light(0)

So, what can be the problem that turn on and off backlights?

Thk!
(07-13-2017 03:06 PM)Kaya84 Wrote: [ -> ]Hi,
I upgraded a YEALINK T21P-e2 firmware to latest one ( 52.81.0.110 ) and the backlight bug suddenly appeared (referring to http://forum.yealink.com/forum/showthrea...ode=linear ).

Going deep to the problem, i put syslog to level 6 and noticed:
Quote:<132>Jul 13 14:54:43 sys [967]: POFF<4+warnin> PC Cable connected
<134>Jul 13 14:54:43 sys [967]: SRV <6+info > get port 2 speed 10
<133>Jul 13 14:54:43 ipvp[1286]: IPVP<5+notice> 683.402.278:Message=0x00020000(0x00000001+0x00000002+0)
<134>Jul 13 14:54:43 ipvp[1286]: IPVP<6+info > 683.402.607:unknown msg,0x00020000,from 0xd28f9304 0x00000001, 0x00000002
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > BackLightManager::AddEvent [1]
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > objEvent.eType == BACK_LIGHT_DEFAULT || objEvent.brightTimer == 0
<134>Jul 13 14:54:43 Log [1313]: IDLE<6+info > [Network] OK
<134>Jul 13 14:54:43 sua [1151]: APP <6+info > [SIP] <IPC_rcv >:msg:0x00020000, wparam:0x00000001, lparam:0x00000002, id:Undefied on dspg
<134>Jul 13 14:54:43 Log [1313]: IDLE<6+info > CStatusManager: Notify Status Changed m_isOn=[1] [0]
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > BackLight Earse Event(4)
<134>Jul 13 14:54:43 Log [1313]: DIR <6+info > Directory: message(0x20000), wparam(0x1), lparam(0x2)
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Operation[1] to power saving
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]CPowerSavingManager::GetTimeoutOfOperation(1, 1499964883)
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Time[1499964883]: day=3, hour=16
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Time range: 1499929200~1499972400 type=0
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout to power saving: 1500022483, interval=57600
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Time[1499972400]: day=3, hour=19
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Next time range: 1499972400~1500015600 type=1
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout to power saving: 1499965483
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout to power saving: 1499972400
<134>Jul 13 14:54:43 Log [1313]: BKLT<6+info > [1313]Timeout[1499972400] less than original timeout[1499972400], will not change.
<134>Jul 13 14:54:57 sua [1151]: DLG <6+info > [000] cb_nict_kill_transaction (id=358)
<134>Jul 13 14:54:57 sua [1151]: FSM <6+info > [000] free transaction ressource 358 0b8444c6210f580409e6ff6e5c60e718
<134>Jul 13 14:54:57 sua [1151]: FSM <6+info > [255] free nist ressource
<134>Jul 13 14:54:58 sua [1151]: DLG <6+info > [255] SIP: 192.168.4.2:5060 Keep Alive sent on UDP!
<134>Jul 13 14:55:03 Log [1111]: WEB <6+info > URI: /servlet?p=login&q=loginForm&jumpto=status
<134>Jul 13 14:55:03 Log [1111]: WEB <6+info > such session have invalidate,will to create a new session
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > URI: /servlet?p=login&q=getsessionid&Rajax=0.966261073536159
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > such session have invalidate,will to create a new session
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > such session have invalidate,will to create a new session
<134>Jul 13 14:55:05 Log [1111]: WEB <6+info > sessionNum: 6
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > URI: /servlet?p=login&q=login
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > Crypto get plain data : session id is equal
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > ip:192.168.4.99 Login at time=1499957706
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > ip:192.168.4.99 The password is right!
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > ip:192.168.4.99 Login in Success At time: [17035]
<134>Jul 13 14:55:06 Log [1111]: WEB <6+info > URI: /servlet?p=status&q=load
<134>Jul 13 14:55:06 Log [1313]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 2. result[2]
<134>Jul 13 14:55:06 Log [1111]: ETLL<6+info > mkit_call return(2,0)
<134>Jul 13 14:55:06 Log [1313]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 65537. result[65537]
<134>Jul 13 14:55:06 Log [1111]: ETLL<6+info > mkit_call return(65537,0)
<134>Jul 13 14:55:06 Log [1313]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
<134>Jul 13 14:55:06 Log [1111]: ETLL<6+info > mkit_call return(0,0)
<134>Jul 13 14:55:08 Log [1111]: WEB <6+info > URI: /servlet?p=settings-preference&q=load
<134>Jul 13 14:55:09 Log [1111]: WEB <6+info > URI: /servlet?p=settings-config&q=load
<134>Jul 13 14:55:12 Log [1111]: WEB <6+info > URI: /servlet?p=settings-config&q=exportLocalLog&type=1
<134>Jul 13 14:55:12 Log [1111]: WEB <6+info > Partition free(byte): /tmp/ [32448512], /config/ [86016], /data/ [86016]
<134>Jul 13 14:55:13 Log [1313]: BKLT<6+info > OnTimerOut InactiveLevel[0]
<134>Jul 13 14:55:13 Log [1313]: BKLT<6+info > PowerSaving_IsInPowerSavingMode [0]
<134>Jul 13 14:55:13 Log [1313]: BKLT<6+info > BackLight Set light(0)

So, what can be the problem that turn on and off backlights?

Thk!

Hi,

T22P is a really old model and already end of line, As we can see, there are several "power saving" messages on syslog, but T22 doesn't have such feature, so I believe this is the different issue. would you please describe the issue detail happen on T21PE2 once again?

Please kindly reset the phone to factory and test again, if the issue still remain, please provide me all THREE trace files:
please kindly offer us trace files for further analysis as below:
a. Level 6 syslog
b. PCAP trace
c. Config.bin
You can get the guide from this link to see how to export the issue data(trace files):
http://support.yealink.com/faq/faqInfo?id=311

Wait for your update.

Regards,
Travis
(07-14-2017 09:45 AM)Travis Wrote: [ -> ]
(07-13-2017 03:06 PM)Kaya84 Wrote: [ -> ]Hi,
I upgraded a YEALINK T21P-e2 firmware to latest one ( 52.81.0.110 ) and the backlight bug suddenly appeared (referring to http://forum.yealink.com/forum/showthrea...ode=linear ).

Hi,

T22P is a really old model and already end of line, As we can see, there are several "power saving" messages on syslog, but T22 doesn't have such feature, so I believe this is the different issue. would you please describe the issue detail happen on T21PE2 once again?

Please kindly reset the phone to factory and test again, if the issue still remain, please provide me all THREE trace files:
please kindly offer us trace files for further analysis as below:
a. Level 6 syslog
b. PCAP trace
c. Config.bin
You can get the guide from this link to see how to export the issue data(trace files):
http://support.yealink.com/faq/faqInfo?id=311

Wait for your update.

Regards,
Travis

Is a T21P-e2 phone, not T22 !
(07-14-2017 09:52 AM)Kaya84 Wrote: [ -> ]
(07-14-2017 09:45 AM)Travis Wrote: [ -> ]
(07-13-2017 03:06 PM)Kaya84 Wrote: [ -> ]Hi,
I upgraded a YEALINK T21P-e2 firmware to latest one ( 52.81.0.110 ) and the backlight bug suddenly appeared (referring to http://forum.yealink.com/forum/showthrea...ode=linear ).

Hi,

T22P is a really old model and already end of line, As we can see, there are several "power saving" messages on syslog, but T22 doesn't have such feature, so I believe this is the different issue. would you please describe the issue detail happen on T21PE2 once again?

Please kindly reset the phone to factory and test again, if the issue still remain, please provide me all THREE trace files:
please kindly offer us trace files for further analysis as below:
a. Level 6 syslog
b. PCAP trace
c. Config.bin
You can get the guide from this link to see how to export the issue data(trace files):
http://support.yealink.com/faq/faqInfo?id=311

Wait for your update.

Regards,
Travis

Is a T21P-e2 phone, not T22 !

Hi,

I know it, but you said, (referring to http://forum.yealink.com/forum/showthrea...ode=linear ) this forum is about T22P.

regards,
Travis
Oh yes, you're right, my fault.

Btw You can find the two attachment with log and configuration
(07-14-2017 10:13 AM)Kaya84 Wrote: [ -> ]Oh yes, you're right, my fault.

Btw You can find the two attachment with log and configuration

Hi,

can I have the decription of this issue please?

Regards,
Travis
(07-17-2017 03:32 AM)Travis Wrote: [ -> ]
(07-14-2017 10:13 AM)Kaya84 Wrote: [ -> ]Oh yes, you're right, my fault.

Btw You can find the two attachment with log and configuration

Hi,

can I have the decription of this issue please?

Regards,
Travis

The issue is simple:
I have about 20 T21PE2 Voip phone. The last week I upgraded the firmware to the latest one (52.81.0.110).
Now the phone turn the backlight on without motivation during the week. I precise that there are no BLF field enabled on the phone.
(07-17-2017 06:37 AM)Kaya84 Wrote: [ -> ]
(07-17-2017 03:32 AM)Travis Wrote: [ -> ]
(07-14-2017 10:13 AM)Kaya84 Wrote: [ -> ]Oh yes, you're right, my fault.

Btw You can find the two attachment with log and configuration

Hi,

can I have the decription of this issue please?

Regards,
Travis

The issue is simple:
I have about 20 T21PE2 Voip phone. The last week I upgraded the firmware to the latest one (52.81.0.110).
Now the phone turn the backlight on without motivation during the week. I precise that there are no BLF field enabled on the phone.

Hi,

I imported the configuration file you provided to my local T21PE2 for testing purpose, however, I've observed for several hours without same issue happens.

Just double confirm with you something:
1. If the issue happen on each of your phones?
2. how often this issue happen on your site? e.g. every two mintues?
3. before you upgrade the firmware, everything works fine? what's the previous firmware version?
4. did you reset the phone to factory after firmware upgrading? (we recommend to do this)

If you could help to record a short video, that would be much helpful to locate the issue.

Thanks for your cooperation in advance.

Regards,
Travis
Reference URL's