Problems T28P+EXP38

[Yealink Support]

Hi Mauro,

Sorry for the late reply.
Our document is old and we will update a new one which can upgrade EXP38 to the version 5.17.0.0.
You can refer to below ROM and the latest upgrade guide.
ftp://yealinkftp:yealinkftp@ftp.yealink.....0.202.rom
ftp://yealinkftp:yealinkftp@ftp.yealink....rmware.pdf

[Mauro]

Thank you very much. Following the new document, I managed to update EXP38 to 5.17.0.0.

(In short: flash T28 with 2.60.0.202, then reboot and stay focused because there are only 5 seconds to answer when the phone asks if you wish to upgrade an EXP. Then, connect EXP and it will be upgraded. Then, flash T28 again with current firmware -at the moment 2.71.0.165-, and you will see EXP firmare version listed in the main Status screen of the web interface).

To sum up:
T28 0.0.0.206.rom --> EXP38 3.17.0.0
T28 2.60.0.202.rom --> EXP38 5.17.0.0

I'm happy I successfully upgraded the EXPs, however this has not fixed the issues. Maybe the issues are more caused by the phone than by the EXPs themselves...

- For the problem of being unable to use an EXP button intercept a call of a phone which is ringing, it was still there. The phone continued to send **221221 instead of just **221 to the PBX when trying to pickup a call directed to 221. I can guess firmware V7x do manage EXT BLF function differently than V6X: when trying to intercept a call, V6x just sent the command specified in the "Extension" field (so I had to write **221 there), and V7x sends "Extension"+"Value" fields together ("Value" field contains 221)... So now I solved the problem by just placing ** in the "Extension" field (for all EXT buttons). I can guess an alternative may have been to switch back to V6x firmware (Yealink support said it's possible to downgrade firmware).
I tried to do the same also a few days ago, but that time it did not save the change... I don't know the reason (maybe the other day, some incoming call prevented the phone from saving settings? I don't know). However now this seems solved.

- For the problem of BLF lamps which do not work correctly (and the phone in general which acts weird) for half hour after phone reboot... well first I re-attached the newly upgraded 5.71.0.0 EXP38s to the already upgraded 2.71.0.165 T28 (which was powered on since several days), and the BLF seemed to instantly work correctly (except the "intercept call" thing I explained above)... so after a short time, I tried to reset the phone, to see what happens. And it happens the same as before EXP update: BFL lamps turn on and off randomly: after 2 minutes they are all lit, after 3 minutes a few of them are off, after 10 minutes a third of them are off... and in the meanwhile the phone LCD menus respond slowly, and a few voice calls seem to have problems like the other person not hearing sound (this seems to continue even if I disconnect the EXPs). So, this problem is not really solved. However I may live together with it, considering at the end it does start to work as it should. But it's annoying.

PS: Don't forget to add the most recent firmware to EXP38 support page, at the moment it does still contain the old version only.

[Yealink Support]

Hi Mauro,

1. Do you test another T28 to connect with the same EXP38? Does the issue happen again?
2. Do you test the T28 to connect with other EXP38? Does the issue happen again?
3. Which PBX do you use now?

[Mauro]

(12-23-2013 05:17 PM)Yealink Support Wrote:  Hi Mauro,

1. Do you test another T28 to connect with the same EXP38? Does the issue happen again?
2. Do you test the T28 to connect with other EXP38? Does the issue happen again?
3. Which PBX do you use now?

Happy new year everybody!

Well..
I have not tested 1) and 2) yet... the two T28 do have different configurations, so I would have to do careful backup-and-restore operations for such tests. Maybe I may try something in the next week...
About 3), our PBX is a KalliopePBX, a PBX from from an Italian manufacturer, (loosely?) based upon Asterisk.

[Yealink Support]

Hi Mauro，

If you subscribe many BLF message to server in short time, your issue may happen.

Enter the webpage->Account->Advanced, so you can increase the time of the SIP Session Timer T1 (0.5~10s), such 1 or 2 seconds.

Can you take a try?

[Mauro]

(01-09-2014 05:33 PM)Yealink Support Wrote:  Hi Mauro，

If you subscribe many BLF message to server in short time, your issue may happen.

Enter the webpage->Account->Advanced, so you can increase the time of the SIP Session Timer T1 (0.5~10s), such 1 or 2 seconds.

Can you take a try?

Before making changes, I will report here some of the current settings I find in that page:
- Keep Alive Interval(Seconds): 30
- SIP Session Timer T1 (0.5~10s): 0.5
- SIP Session Timer T2 (2~40s): 4
- SIP Session Timer T4 (2.5~60s): 5
- Subscribe Period(Seconds): 1800
- BLA Number: (empty)
- BLA Subscription Period: 300
- SIP Registration Retry Timer(0~1800s): 30

By changing that "SIP Session Timer T1" value, should I notice some kind of change in phone's behavior (e.g. more time before a call starts, or a BFL button action is taken, or similar things)? Except maybe fixing the issue we are talking about, of course...

[Yealink Support]

Hi Mauro,

If you increase time of SIP Session Timer T1, it means that every time of BLF subscribe will increase. So if the monitored phone change its state in the T1 time, the monitor can't see the state change until the next subscribe.

[Mauro]

I tried increasing T1 from 0.5 to 1, to 1.5 and even to 10.0.
It did not solve the problem (maybe even worse: with it set to 10, I was not able to access the web gui after some mintues since the reboot).
So I restored the value to 0.5.

The only workaround which seems to have some effect is detaching EXPs from the phone, then booting the phone up, and after it's ready, attaching EXPs...

[Yealink Support]

Hi Mauro,

Do you upgrade your T28 to the latest version but not T28 0.0.0.206.rom or 2.60.0.202.rom?

Those two version can't be used for everyday using.

[Mauro]

T28 firmware is 2.71.0.165.