Standard Provisioning File

Discussion in '3CX Phone System - General' started by vitaminc, Nov 22, 2016.

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

    Joined:
    Feb 1, 2016
    Messages:
    18
    Likes Received:
    7
    I'm using Custom Provisioning Files for our Yealink Phones because of several Remote Adressbooks we need for Groups/Branches.

    I've now upgraded to V15.

    Reprovision a phone using the standard provisioning file means that it's not overwrite the remote adressbooks in the yealink phones. Is it any bug or is it some new feature? :)
     
  2. aberry

    aberry New Member

    Joined:
    Jan 13, 2015
    Messages:
    118
    Likes Received:
    7
    From what I've been able to tell, v15 has supported, and unsupported(aka modified) provisioning templates, even for supported devices.

    "ProgramData\3CX\Instance1\Data\Http\Templates" is the location that official supported templates are stored and downloaded to.

    "ProgramData\3CX\Instance1\Data\Http\Interface\provisioning\xxxxxxxxxx\CustomTemplates" is where it has been saving templates that I have made changes to.

    My original solution was just to make changes to the official templates that reside in the first location that I mentioned above. At some point though, 3CX reset all the changes that I had made and set the templates back to default. I got around that by removing modify permissions from the templates that I modded for all except my service account.

    You should be able to do the same. Add your custom address book info to the default template that is being used, and remove permissions for that file so that you are the only one that can edit it.

    Personally I'm not a big fan of the way that templates are managed now. I get that 3CX wants to cover itself when things go poorly with custom templates. At the same time, there are very few people that will be satisfied with the setting in a default template. Compound that with the lack of an option to choose a template when assigning a phone, which really sucks. And the final cherry on top is the unsupported template warning...

    Some changes need to be made to this process.
     
Thread Status:
Not open for further replies.