+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: Wishlist (/forumdisplay.php?fid=13)
+--- Thread: Ability to use DSS keys with BLF keys more flexibly (/showthread.php?tid=1396)
Pages: 1 2
Ability to use DSS keys with BLF keys more flexibly - nicknomo - 03-11-2014 11:58 AM
This suggestion comes from the following thread:
http://forum.yealink.com/forum/showthread.php?tid=1395
I am using asterisk with the T46G. Asterisk uses many feature codes to perform vital functions, and on many legacy phone systems the function keys would be used with BLF keys. For instance, I'd have a transfer to voicemail button that worked with a BLF key for an extension. Transferring to voicemail was a two key press process. Hit the button, choose the corresponding BLF key/extension, and its done. Yet, I can't do this with the Yealink DSS keys.
From what I can see there is no easy way to chain DSS keys together, so it appears that its very difficult for yealink phones to perform these types of tasks.
For my above scenario, where I wish to transfer a call to directly VM, asterisk requires me to transfer to *<extension number> . So, to transfer to extension 221's voicemail, I have to hit: "Transfer * 221" . "##*221" also works for this task. The problem is that while I can bind a key to "transfer *" or "##*", and a BLF key to "221", I cannot use them in sequence.
It looks to me that the problem is that there is no way to wait for more input. Binding a key to "transfer *" executes it immediately, never giving me an opportunity to hit the BLF and add "221" onto this.
Binding a key to DTMF with the value of "##*" works great, but then when I hit the BLF 221 key it opens a new line and dials 221.
Off the top of my head, I can think of a quick and dirty solution to fixing this. If we were able to enter something into the "value" field that told the phone to wait for more input before executing the parameter, it would be an easy way to chain things together.
For instance, lets say we choose the ampersand ("&") as our special character. I make a DSS key for transfer, and give it a value of "*&". This would initiate a "transfer*", but wait for more input (or optionally just hit the "send" key). For more input, you could then hit a BLF with a value of "221", and then you'd have a combined function of "transfer*221".
You could do this with any of the feature codes, by doing things like binding DTMF values ("##*&") with BLF keys ("221") to combine them to make something like: "##*221".
Without some sort of feature like this, the operator panels aren't quite as useful. We simply aren't able to take advantage of the functions within asterisk that rely on feature codes..
RE: Ability to use DSS keys with BLF keys more flexibly - Yealink Support - 03-11-2014 03:39 PM
Hi We will add this feature in major version in near future.
RE: Ability to use DSS keys with BLF keys more flexibly - TheShniz - 03-15-2014 04:55 AM
+1 ... me too!
RE: Ability to use DSS keys with BLF keys more flexibly - elementpbx - 03-15-2014 11:15 PM
YES!!
RE: Ability to use DSS keys with BLF keys more flexibly - rlsabin - 03-16-2014 12:04 AM
+1
RE: Ability to use DSS keys with BLF keys more flexibly - IPTelecom - 05-09-2014 02:03 PM
We're also using Asterisk based system and want the ability to use BLF keys for attended transfer, currently we have to press transfer and then dial the number manually or go through the directory, it would be far more efficient to press transfer and the BLF key however when you do this it initiates a blind transfer. Could this be corrected too please?
RE: Ability to use DSS keys with BLF keys more flexibly - Yealink Support - 05-13-2014 02:43 PM
Yes. We will add this scenario to V73.
RE: Ability to use DSS keys with BLF keys more flexibly - timalex - 06-20-2014 09:14 PM
+1 !!!
RE: Ability to use DSS keys with BLF keys more flexibly - bazzacad - 07-09-2014 12:43 AM
Any ETA on V73?
RE: Ability to use DSS keys with BLF keys more flexibly - Yealink Support - 07-15-2014 03:06 PM
Hi bazzacad,
Sorry for my mistake, we gave up this feature in the V73.
We will add it in the next big version called V80.
Sorry for the inconvenience.