Yealink Forums
LineKey label - 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: LineKey label (/showthread.php?tid=1943)



LineKey label - Nevox - 06-24-2014 04:27 PM

Hello,
I would like to change the label of the linekey (phone: T48G, and certainly T46G also).
Right now, I use to configure the 3 first linekey as "Line" (type=15), pointing to the same account. Then I get the label of the account repeated on the first lines. It should be good to be able to change the label on the buttons; I'd like to show something like Line 1, Line 2, Line 3 (even if it's the same account). This is easy to understand for users and less confusing with BLF keys. I saw another thread with quite the same question, but the answer (defining 3 different accounts) is not what I'd like to do, as I don't want to have several registration for the same account! And this solution doesn't work, as it's always the 3rd line (the last registration on the account) which is called. On the server side, I'm using an asterisk based server.

Is there a way to do it? With autoprovisionning, the parameters are not taken into account, and with GUI, the field is greyed. If it's not possible, do you plan to include that in the next firmware?

Thanks


RE: LineKey label - Yealink Support - 06-24-2014 05:30 PM

Hi Nevox,

You can set it via webpage ->Account->Register->Label even if it's the same account.
Please refer to the below pictures.

[Image: attachment.php?aid=804]
[Image: attachment.php?aid=805]

thanks


RE: LineKey label - Nevox - 10-30-2014 07:04 PM

Hi,
I think there is a misunderstanding. I have only one account, but several key defined as "Line" pointing to the same account. And I'd like to have different label for the SAME account on different keys (by exm. line1, line2, line3... like old PABX systems).
Is this possible?

Thanks,


RE: LineKey label - Wilson_Yealink - 10-31-2014 08:23 PM

Hi Alban,

Sorry for my misunderstanding. We have fixed it in new V73 version. Please upgrade the firmware to the V73 beta and try again. You can download the firmware from this announcement.

V73 Beta2 Version Firmware And Release Notes of Version 73 Release

thanks