Deny overriding customer key/button changes and additions when provisioning

[USA Phoneman]

We have several customers that will change the keys/button on their GXP 2170 phones( But this question is not just a GXP 2170 issue.) It may something as simple as a name change or adding a BLF. Yet when the phone is re-booted power cycled the programming in Fusion overrides the on-site changes.
Can this be solved ?

Thanks to the community, we are new to Fusion, but so far we are impressed.

Thanks

 

[DigitalDaz]

Hi,

Everything is probably working as expected. I'm not familiar with Grandstream but it looks like the phones are set to autoprovision at boot.

Ideally, you want the BLFs etc set in the device config so that the server provisions the buttons otherwise you will always face this situation when you reprovision. ie the server does not know about custom configuration.

If you really want the users to have this sort of control then it may be better just to do an initial provision, then turn off provisioning for the phone on reboot.

This is probably a setting in the template for that particular model.

Alternatively, go on the phone and disable the provisioning there.

You will need to do this anyway to prevent their keys being wiped.

Try to get into a position where all the keys are set at the server, it should be easier on support in the long run as then if you do reprovision or do a factory reset then all the keys are set.

 

[USA Phoneman]

DigitalDaz & Community

Thanks for the time in responding. Your advise makes good sense. Perhaps we need to take a harder line in what we let customers change on the phone.

We are trying to learn how much control the Fusion template has in making setting changes to a phone, for example, if we want in a Yealink TXX to turn on/off the "Auto Answer" option to work with Order 195 in the Dial Plan. We have to access the devise directly using a browser. We have just assumed that the Fusion template does not have this type of control. Is this a correct assumption ? I hope we are wrong in this assumption.

We have several questions that we are working on. We would be interested in working directly with a community member to establish a financial arrangement for more direct support if interested. I hope this is not poor forums eqiquite.

Thanks to all for adding your knowledge in helping us newbies.

 

[DigitalDaz]

What is this order 195 you are referring to? Your 195 may not be the same as mine.

Everything that you can set in the webui should be available to set in provisioning, variables may need to be added to the template if they are not already there but it is doable. The gui helps with this.

For example, by clicking the question mark next to the setting in the gui, you get the required configuration setting for the provisioning file.

In the image below, for auto answer you will see that to enable autoanswer in the config file, we would need to set:

 account.X.auto_answer = 1

Where X is the account number eg 1, 2, etc.



If we now examine the provisioning template for the phone, I'm using a yealink t46 so:

fusionpbx/resources/templates/provision/yealink/t46s/{$mac}.cfg at master · fusionpbx/fusionpbx

Official FusionPBX - A full-featured domain based multi-tenant PBX and voice switch for FreeSwitch. - fusionpbx/fusionpbx

github.com

account.1.auto_answer =

There is no variable there to populate the provisioning template field, unlike further down where we see, for example:

account.1.missed_calllog = {$yealink_missed_calllog}

What we need to do is create a variable and add it to the template, we can then populate that variable and in devices, set it for the relevant extension.

For that, I'll make you a video...

 

[USA Phoneman]

Digital Daz
Thanks for sharing your knowledge. I had a delay in getting back and responding. IF it is OK, We have multiple questions we are trying to answer. But I would like to focus on one at a time. I would like offer some type of thank you for your time. Please let me know what is proper.
Creating an extension and getting the extension registered seems to be a straight forward process. Under Extension >Device Provisioning > Keys, building how we want to key/s to operate is straightforward. I am trying to use the same "Keys" programming for multiple extensions and then be able to customize each extension's Keys as needed.
Our programmer may respond and add comments and questions if that is Ok as we proceed.
A video would be much appreciated. We install Yealink, Fanvil and Grandsteam phones. I can use a Yealink to follow your video. IF you would like I would be happy to provide a Grandstream for you personal use.
Thanks