Yealink Forums

Full Version: Unable to bring up dial-pad in call (URGENT!)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I've just upgraded my client's four Teams phones to the latest firmware: CP960-73.15.0.45.rom

However, they have reported that once they have established a call, there is no way to get the dialler back so they can enter enter (for example) a conference code to join a meeting.

This is the screen: https://i.imgur.com/Y1HzgTd.png

How do they bring up the dial-pad during a call?? This means the phones are currently nearly useless as they are used primarily for conference calls.

My immediate thought was to downgrade the firmware to an older version CP960-73.15.0.38.rom but when I try this, it fails to upgrade with this error: https://i.imgur.com/tc8Qdsh.png
I've had to raise a ticket for this as my our Yealink phones are now effectively useless...
It's occurred to me today that there are lots of call controls missing from the in-call screen. I'm not based on-site so can't quickly check but according to the manual, there is this button from where you can access transfer, hold etc. But it's missing from the original screenshot.

[Image: hNGHg1j.png]

Not sure if makes any difference but these handsets are using a common phone license. And always have BTW and call controls were available in earlier firmware. It's a real flaw that you are unable to go back to an earlier firmware!
(10-11-2019 07:36 AM)helios.comms Wrote: [ -> ]It's occurred to me today that there are lots of call controls missing from the in-call screen. I'm not based on-site so can't quickly check but according to the manual, there is this button from where you can access transfer, hold etc. But it's missing from the original screenshot.

[Image: hNGHg1j.png]

Not sure if makes any difference but these handsets are using a common phone license. And always have BTW and call controls were available in earlier firmware. It's a real flaw that you are unable to go back to an earlier firmware!

I am having the same issue, were you able to fix this?
Reference URL's