Yealink Keep Local DSS Key Setting when reprovisioning

[MannyL]

I need to program some of my Yealink t46 with HTML and XML type buttons and I can't do that via 3CX BLF setup, but I don't want to completely abandon the use of provisioning phone and regular BLFs via 3CX

My solution up till now has been to use a modified provisioning template which just has a couple of lines modified to keep local phone settings when reprovisioning.

Unfortunately, I didn't document which lines need to be changed in the template and now I need to modify the latest template that 3CX put out

TLDR: Anyone know what sections of Yealink template need to be changed to keep local phone DSS setting?

 

[cobaltit]

If you are modifying the template you can just put your changes in the template vs 'keeping' them. But the template is pretty self explanatory as far as the buttons go. You would basically want to to either blank out or hard code your button values in there.

 

[MannyL]

I found it easier to manage the DSS keys on the phone side rather than manage multiple custom templates, especially, when employees request rearranging them

 

[MannyL]

I think I found it:


### It enables or disables the phone to protect personalized configuration settings even after auto provisioning.
### If it is set to 1 (Enabled), personalized configuration settings via web/phone user interface will be protected and remained after auto provisioning.
### 0-Disabled, 1-Enabled. The default value is 0.
auto_provision.custom.protect = 0

 

[cobaltit]

Looks like it. The Yealink forums or more specifically the Yealink provisioning guide will probably be more helpful. The 3CX template is just standard Yealink provisioning mixed with some 3CX specific variables.