Function keys overwritten after reprovisioning

Discussion in '3CX Phone System - General' started by pks-team, May 6, 2015.

Thread Status:
Not open for further replies.
  1. pks-team

    Joined:
    Dec 7, 2012
    Messages:
    24
    Likes Received:
    0
    Hello,

    to avoid that phone reprovisioning overwrites the setting one has made in his fkeys (using the web UI), I commented out the Section from "<functionkeys" to "</functionkeys>" in snom.ph.xml.

    I assumed this would avoid the fkeys being overwritten.

    This morning though most phone's Functionkeys where back to Standard (with fkey 0 and 1 having "line" assigned and all other empty).

    Which other files need to be changed to avoid this situation?

    Regards

    Norbert
     
  2. pks-team

    Joined:
    Dec 7, 2012
    Messages:
    24
    Likes Received:
    0
    I found part of the answer here: http://www.3cx.com/sip-phones/snom-710-720-760/

    There it is desribed how to configure the function keys within the 3CX PBX. This at least allows me to set some Standard keys for each user.

    Problem is, that this only allows very few type of Settings. Most available Types that you can choose in the web UI of the phone are not available here.

    Example: all users at the particular site have one desk phone (Snom 760) and one portable phone (Snom M65). Tehy often walk away from their desk and take theportable phone with them. So, the hit a function key that Forward their Extension to another one. They type of Action is then "Forward to".

    So, I still Need a solution on how to avoid overwriting of the function keys.

    Norbert
     
  3. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    In many cases, the needs of the phone are fairly routine/simple and can be handled by the 3CX provisioning files and process. However, given the large number of makes and models of phones that 3CX does support and the various different configuration that each has, it is not possible for 3CX to have a comprehensive set of unique templates for each phone that would address every potential option that one might want to use. As a result, there is a compromise to have a generic web interface that then writes the selected options into the applicable provisioning file.

    In most cases, when you begin using phone features that are not included in the generic template, you have two options -
    1) Go into the phone itself and turn off the configure/provisioning options and erase the provisioning path. This prevents the phone from trying to seek its configuration whenever its slated time to check arises or when rebooted. This may not prevent the phone from being re-provisioned if done from the 3CX server. So, you might consider removing the extension and re-adding, but without using the model and MAC address. This is then manually provisioning the phone from this point forward.

    2) FInd the template for the extensions in the 3CX folders and editing them to your need. In some cases, the template itself will have more or even a full set of attributes (that could not be imported or shown in the generic 3CX provisioning GUI). You can edit the file to your need for a given extension and then save with a unique name (if not then all phones of this type will inherit the new entries) that you can then select in 3CX. IN this manner you can edit the common features found with 3CX and still use 3CX provisioning routines.

    The downside to the latter is that as new templates are released, you will need to make sure to compare your old modified version(s) to the new to see what, if any, changes have been made that may cause you to consider needing to migrate your changes to the new generic version and again save with the generic same name as before.

    Phone manufacturers oftentimes modify their firmware which may impact the template as sometimes they have new features.
     
Thread Status:
Not open for further replies.