Yealink Forums

Full Version: Call ended when answered
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have problem with one phone. When call is recived and handset is in charging credle, while picking up handset call is answered and immediately ended with message charging.
When call is answered on handset not in charging credle, everything is ok.

Battery is fully charged, phones are 2 days old.

What am I missing here?
Dear,

This seems odd. Please help to check:

1. How many handsets that have such issue?
2. The issue happens on every call when handset is on charging credle?

Please upgrade the firmware to the latest one and test again.
Base Firmware: http://www.yealink.com/Upload/W52P/V73/F...3.0.27.zip

Handset firmware: http://www.yealink.com/Upload/W52P/V73/F...3.0.11.zip

Upgrade Guide: http://www.yealink.com/Upload/W52P/20131...rmware.zip

If problem still, please refer to the guide below to catch the config.bin, syslog(level6) and pcap and send it to support@yealink.com

http://forum.yealink.com/forum/showthrea...og#pid5356
Regards
Elaine
(06-19-2015 02:25 PM)Marijo Wrote: [ -> ]I have problem with one phone. When call is recived and handset is in charging credle, while picking up handset call is answered and immediately ended with message charging.
When call is answered on handset not in charging credle, everything is ok.

Battery is fully charged, phones are 2 days old.

What am I missing here?

Hi Marijo,
Same thing happens to our W52P. Are you using your W52P with RingCentral Office@Hand? I noticed if the unit is fully charged, it tends to happen less when you lift up the handset from the cradle. We have two W52P transmitter bases with 2 handsets paired to each base. They all seem to exhibit the same problem. Eventually, after heated discussions with RingCentral Level 2 support over issue and a helping email-response from Yealink support to upgrade the old firmware, Level 2 connected remotely to our 2 bases and upgraded to the latest firmware 25.73.0.40 (base) and 26.73.0.11 (handset). Still testing to find out if random problem will resurface since the upgrade late yesterday.

I kind of suspect that if the handset is not lifted "cleanly" from the cradle to answer a call, the contacts on the bottom of the phone touches the base contacts again to register as a hangup. Just a theory.

We are still within the 30 days trial period of RingCentral. Not sure we are going to keep the phones & RingCentral service, due to this unreliable fail. My client depends on cordless phones at their location and RingCentral only supports the W52P.
Reference URL's