Yealink Custom DSS Keys

Status
Not open for further replies.

PanagiotisK

Gold Partner
Advanced Certified
Joined
Feb 26, 2019
Messages
11
Reaction score
1
3cx Version 16.0.1078
Yealink t29 firmware version 46.83.0.130

Minor issue but i thought it was worth asking.
Before updating to the latest version of 3cx we had 3 yealink exp20 connected to the device (3rd one with external power supply)


First two expansion received blf provisioning through 3cx
The third one we had to do it through phones web interface.
Because the default template for 3cx is displaying the names of the blf keys only by first name last name, it wasn't easy to use for the end user, so we deleted all extra blf keys from 3cx and entered them manually from phones web interface.
First 10 dss keys were provisioned by 3cx and all expansion keys were configured on the web interafce of the phone.
After last update we were informed that the user lost all blf keys from the expansions.
We managed to export the configuration from the phone and by adding expansion_module.1.key.1.type = 16 before each entry and importing the file we managed to make all expansions work.
But the next day again the blf keys of the expansions were lost. We made some tests and we realized that even if the BLF tab in 3cx for that specific extension was empty (no BLFs at all), after reboot or reprovisioning of the phone, 3cx overwrites the dss key values set from the web interface.
I tried comparing the old template with the new one but i could not figure out which option does that.
Please note that the firmware version of the phone hasn't changed with the update, only the template.
Before the update we had 10 blf keys (that were located on each side of the phone's screen) provisioned from 3cx and 3*20 keys from 3 expansions configured from the device's web interface.
To work around, we provisioned all bfl from 3cx but i was wondering if there is some setting i can change in the template to have the same functionallity again.
I am attaching old and new templates.
 

Attachments

Hi @PanagiotisK

3CX takes care of provisioning for you, this means it will overwrite anything that is included in our template (that would include all BLFs).

The only way to avoid this is to either remove the provisioning link from the phone (so it will stop reprovisioning itself) or to create a custom template that omits all the expansion module sections.

Custom templates do not get overwritten by 3CX, but they don't get updated either. You have to recreate them from the latest version by yourself. Also, we do not provide support for custom templates, so if you begin to face issues with the phone, you will need to either figure them out by yourself, or return to default provisioning. With the disclaimer out of the way, you can now check out this link:

https://www.3cx.com/docs/custom-ip-phone-templates/
 
Hi John,
thank you for your reply.
I don't want to mess around with custom templates either. I already configured the BLF keys through 3cx itself, and though the format is not customizable ("extension number | Last Name" instead of "First Name | Last name") it works for the customer. I tried comparing the two templates but i don't see any specific setting that could be responsible for the altered behavior of overwriting the BLF keys even though no BLF is set on a device.
I will keep that in mind on future installations
 
  • Like
Reactions: JohnS_3CX
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,990
Messages
590,161
Members
164,925
Latest member
batarong