Call Parking, can we get this fixed please!?!?

[jayg30]

The issue is pretty simple and reproducible. I've experienced it on all firmware versions for the past 2 years for all phones I've tried (T2x and T4x models). I am willing to bet it behaves this way for ALL Yealink phones. Other phones handle this differently/correctly.

Setup the "Call Park" DSS key as described in any Yealink phone manual.
Test Call Parking;

• Caller A dials Caller B
• Caller B presses "Call Park" DSS key
• Caller A is placed in the parking lot
• Caller B is disconnected
• Caller B never hears the parking lot slot
  

Everything is correct EXCEPT the last point (Caller B never hears the parking lot slot). For most people hearing the slot number is important. It appears as if the Dss Key is set to type "Call Park" on Yealink phones, it utilizes a blind transfer instead of attended transfer. Even if the "default transfer via Dsskey" is set to "attended transfer" it makes no difference.

So I assume the key type for Call Park must be hardcoded to complete using a blind transfer (feature code ##) instead of attended transfer (*2).

I would propose the default method change to attended transfer for Dss Key type "Call Park" so the person parking the call is announced the parking lot #. I'd also suggest creating an option to change this behavior between the two options (ie. feature option, "announce parking lot?: Yes/No).

The only workaround for this currently, that is not ideal, is to NOT use the call park key type at all. Instead to use set the Dss Key Type to transfer, and set the value to 70 (or whatever your parking lot is), and finally set the "transfer mode via dsskey" to attended transfer. This is not ideal because it imposes the restriction on "transfer mode via dsskey" just so call parking works correctly. It also requires more button presses. And finally (the biggest issue) it doesn't hang up the transferred calls and instead you end up with two active calls on your phone (the original call you are trying to park and the parking lot call which is playing MoH back to you) and you have to make sure to hang up these calls.

Testing on a up to date FreePBX system. This is an issue that has existed for a while from my understanding. See HERE.