Yealink Forums

Full Version: ehs36 firmware and newer t26 phones
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I just installed 15 t26's and am now trying to use the ehs36 with the Plantronics CS540 headset. we cannot get the headset to answer or hang up a call. we can place a call and do have voice during the call but if you hit the headset button it does not hang up the phone. it will not answer an incoming call just by pressing the button on the headset either. looking at the forums it looks like we need to upgrade the firmware in the ehs itself.

the t26's are hardware revision 4.0.1.44 running firmware 6.70.0.140 the ehs is hardware 48.0.0.0 and the firmware is 1.16.0.0.

the firmware needed (6.60.200.240) to upgrade the ehs firmware to 3.16.0.0. says specifically that it cannot be used with hardware newer than 4.0.1.38. in other words our phones are too new to use this firmware

is there another way to upgrade the ehs firmware? I don't have access to older phones.
Sorry. May be you can upgrade EHS36 to 2.16.0.0 using firmware 6.60.200.240.
http://www.yealink.com/Upload/Others/EHS...886442.pdf

NOTE: 6.60.200.245(Upgrade EHS36 to 3.16.0.0) can only be used in the hardware number smaller than 4.0.1.38.

Or you can ask your seller to upgrade EHS36 for you.
This will be possible soon to upgrade EHS36 by the new T26p ?

THanks in advance

PS : sorry my english is bad.
Sorry. Maybe you can ask your seller to upgrade EHS36 for you using T28/OLD T26/T46G.
Its the 3.5mm audio cable, this is happening with all CS540. Try pushing it into the plantronics base and answering a call. If this works, you need a new cable.

The yealink cables are slightly shorter than other brands.

Let me know how you go.
(05-30-2014 08:05 AM)commsys Wrote: [ -> ]Its the 3.5mm audio cable, this is happening with all CS540. Try pushing it into the plantronics base and answering a call. If this works, you need a new cable.

The yealink cables are slightly shorter than other brands.

Let me know how you go.

yes we fixed this sometime ago. we upgraded the firmware on the ehs boxes (probably was not necessary) and then discovered it is the cable.
Reference URL's