Yealink Forums
Call Park - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: Call Park (/showthread.php?tid=41722)



Call Park - VOIP - 04-17-2018 06:37 PM

Hi there,

Any thoughts of having Call Park Code and Park Retrieve Code would be a "prefix" of the "call park" button.

For example

Call Park Code = *
Park Retrieve Code = **

DSS/Line key

Line Key4 = Type PARK Value 700

The blf light will reflect "700" When hitting it it will transfer the call to *700 and when retrieving it will dial **700

(It would be based on BLF States
Prefix when BLF is idle
Retrieval based on proceeding or confirmed)


RE: Call Park - Paul_Yealink - 04-19-2018 02:15 AM

Dear Customer,

Greeting. This is Paul from Yeaink Technical Support Team, nice to meet you.

We will follow up this issue in below ticket:
https://ticket.yealink.com/index.php/bug/66265

BR
Paul


RE: Call Park - VOIP - 04-19-2018 02:02 PM

Thank you Parl,

I was unfortunately unable to reply to your ticket as the ticket system gives a Error 400 Required URL cannot be found or permission denied. (tried with my account as well)

So I will paste my reply here:

Thanks!

But this does not answer my question :-) You replied with the basic park function. The issue with that method is we need TWO button for each park spot
1) to Park
2) to retrieve.

My question was more along the BLF multi function for call Pickup. When you have a BLF button and have pickup set then that button will "watch the extension" but prefix ONLY on pickup based on the BLF status <state>proceeding</state> or <state>Confirmed</state>

If you would apply the same principles to the "park" where is would "watch 700" but use the Prefix of Park when its STATE = <state>idle</state> and retrieve prefix when state = <state>proceeding</state> or <state>Confirmed</state>

no?


(04-19-2018 02:15 AM)Paul_Yealink Wrote:  Dear Customer,

Greeting. This is Paul from Yeaink Technical Support Team, nice to meet you.

We will follow up this issue in below ticket:
https://ticket.yealink.com/index.php/bug/66265

BR
Paul