Solved Yealink T46S Custom Template Not Pushing to Phone

Status
Not open for further replies.

aaronl

Platinum Partner
Advanced Certified
Joined
May 20, 2021
Messages
22
Reaction score
4
Hi,

I'm am creating a custom template for a Yealink T46S so that I can add a Action URL easily across multiple hadsets. So far I have copied the existing 3CX template, renamed it and added in my change. Below is the change I have added into the template. Everything after the equals sign is what I have added.

action_url.call_established = http://172.18.76.2:8888/help.xml?event=answ_new_incall&local=$local&remote=$remote

However when I push this out to the handsets and log into the Web GUI this field is blank and when I export the CFG Configuration File the change is not there. If I add it manually via the Web GUI it will then show up in the CFG file.

Screenshot_9.png

Can someone please help figure out why this is not pushing via 3CX? I need to be able to do this via the template as I cannot access all phones via the Web GUI. I have also made sure the firmware is
 

Attachments

  • Screenshot_8.png
    Screenshot_8.png
    65.6 KB · Views: 4
Last edited:
Hi!

In case you are not aware, Custom Templates aren't recommended and before troubleshooting in case of a problem, always Factory Reset your device and reprovision with the default template and try again.

Moving on though:
 
  • Like
Reactions: Evolute IT
OK, then please try this.

If you have copied the default template, comment out the "action_url.call_established =" on line 1011 by putting a '#' in front.
Then go to line 1285 and put in this line:
action_url.call_established = http://172.18.76.2:8888/help.xml?event=answ_new_incall&local=$local&remote=$remote

The end result should look like this:
1637661174529.png


Save template, reprovision phone and that should work.

There is currently a small issue with custom Yealink templates, where the y0000000000xx.cfg file is not generated (with default it is OK).
This is why you were having this problem. The current solution though is to just place the configuration you want in the <MAC>.cfg section of the template.
 
  • Like
Reactions: aaronl
There is currently a small issue with custom Yealink templates, where the y0000000000xx.cfg file is not generated (with default it is OK).
This is why you were having this problem. The current solution though is to just place the configuration you want in the <MAC>.cfg section of the template.
That has done the trick. I've tested this on several phones now and they have all worked. Thanks for the help NickD.
 
  • Like
Reactions: NickD_3CX
Glad we could help! :)
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK