Yealink T48

Discussion in '3CX Phone System - General' started by ccomley, May 9, 2015.

Thread Status:
Not open for further replies.
  1. ccomley

    Joined:
    Apr 6, 2011
    Messages:
    92
    Likes Received:
    4
    Nice phone. But 3CX makes a really botch job of configuring the BLF array - which is a pity as the screen of 30 touch panels is the biggest draw for the screen. 3CX is OK if you want a BLF but if you want a speed-dial, 3CX doesn't really allow you to put it where you want, the main problem is it doesn't let you *label* the speed-dial. You need TWO parameters for a speed dial, the number, and the NAME. If you program it via the phone's GUI it's all fab. But you lost that config as soon as 3CX tries to re provision the phone. Short of manually backing up the phone config and then logging in to restore it if for any reason 3CX over-writes it, can I stop 3CX from changing the DSS key section of the config.

    (Or any sign of 3CX fixing this?)
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    Many have made similar observations about how the 3CX provisioning is lacking when it comes to using all the various features that a phone may have. The issue is that there are simply too many makes and models and the manufacturers may, at any time, modify their firmware which may entail other modifications to the feature set and the associated provisioning. As a result, theirs is a generic GUI form that is used regardless of phone make/model. For many this will suffice as their needs may not be as complex or the phone may not support. A T46 may support key labeling whereas a T22 may not.

    To get around the issue, 3CX allows for the modification of templates so that you can tailor the file to your needs. Of course, this requires manual effort as each file may be unique to the extension and the variables will still not show in the GUI, so any changes will have to be done at the provisioning file level. 3CX will only overwrite the values that are present on the web GUI, so if you modify a template using fields that are not present, then 3CX will not overwrite those value. This may not be of much convenience in your case as you could change the BLF key functionality, but might still need to modify the template to correlated to the desired key labeling.

    The other option is, as you suggested, to manually provision the phone and then turn off the re-provisioning aspect in the phone web interface. This will not necessarily prevent 3CX from provisioning the phone should someone elect to do so from the web console; so you will have to be careful going forward but, it should prevent the phone from doing so on its own when rebooted or at a scheduled time as you have observed.

    Simply delete the extension and then re-add without specifying the model/MAC. In the phone, eliminate the provisioning path and/or turn off the feature if that option is available.
     
  3. ccomley

    Joined:
    Apr 6, 2011
    Messages:
    92
    Likes Received:
    4
    I realise that all features of all phones can never be catered for, but 3CX have claimed to work very closely with Yealink, and the ability to "label" function keys on phones, sidecars, etc., is becoming more and more widely available on phones from many manufacturers, even on "basic" and standard models, so perhaps it's time that went in to the ToDo list!

    Pending that more information on how to find and block out sections of a template so they don't get re-introduced accidentally in later updates wouldn't hurt! :)
     
  4. CentrexJ

    CentrexJ Member

    Joined:
    May 5, 2009
    Messages:
    441
    Likes Received:
    71
    There is a very easy change to the template so that if you set a BLF key in 3CX it will add it to the Yealink phone but if there is no programming of that BLF key in 3CX it will leave what the phone has manually configured alone (won't over-ride it with blank key)

    If you open the template file for the Yealink phones and scroll down to the BLF section (as below)

    {IF blf1}
    linekey.3.line = %%Line%%
    linekey.3.value = %%blf1%%
    linekey.3.pickup_value = %%PickupValue%%
    linekey.3.type = %%DKtype%%
    linekey.3.label = %%blffirstname1%% %%blflastname1%%
    linekey.3.extension = %%PickupValue%%
    ## {ELSE}
    ## linekey.3.type = 0
    {ENDIF}

    If you comment out the two lines above that I did ({ELSE} and linekey type = 0) you will accomplish that goal.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.