Custom template name not shown after upgrading to version 18 update 5

[CP_Mike]

We use customized Yealink templates for our phone provisioning as we require adding phone books form 3 different 3CX sites. After upgrading from v18 update 3 to v18 update 5, the names of a custom template no longer appear in the phone provisioning drop down list. In the past when provisioning a phone to an extension, we would be able to see T42S (customtemplatename). As of v18u5 it only shows T42S for example under the custom category, but it actually appears to use the default Yealink template to provision the T42S phone (we assume because they share the exact model name). It also no longer shows as using a custom template under the Phones menu. This is causing our phone books to not work as intended. Phones previously provisioned with the correct custom template still show the correct model and template name in their extension, but when adding new phones we don't appear to be able to use our custom templates due to the described issue.

If you copy an existing custom template it renames the models within the copied template to include the template name, such as T42S-customtemplatename. While this can be seen as a work-around, it would require redeploying hundreds of phones.

Is there a way to get the custom template name to show in the provisioning drop down list or any other solution rather than redeploying phones?

Thanks,

Mike

 

[PierreS_3CX]

Hi,
Which version of 3cx do you use (Standard/pro/enterprise) ?

 

[CP_Mike]

We use Pro - perpetual on all 3 sites.

 

[PierreS_3CX]

You have to copy template in Parameters>models "yealinkT4x.ph.xml", then :

https://www.3cx.com/docs/custom-ip-phone-templates/

Map to an already provisioned IP Phone​

1. Go to the “Management Console → Extensions” → double-click on the extension you want to apply the template to → “Phone Provisioning” tab.
2. In the “Your phones” drop-down, select the IP Phone you want to apply the custom template to.
3. Copy the MAC address of the existing device.
4. Press the “Delete” button next to the “Your phones” drop-down.
5. Press the “Add” button and in the new window that opens:
6. Select the custom template name from the drop-down
7. Paste the MAC address you copied in step #3.

1. Press OK, then OK again to save the extension.
2. Go to the “Phones” node, highlight the phone and press reprovision.

Important Note

Depending on the changes you have made in your custom template, it may be required to first Factory Reset the IP Phone, then provision it directly with the custom template.

 

[CP_Mike]

Thanks for your reply.

To clarify, the custom template names no longer appear in the drop down list. Only the name of the model defined in the parameter of the template. I am assuming this was changed by design and, even though we have used custom templates for years, our existing templates are no longer valid due to this change.

Unfortunately, we were trying to avoid reconfiguring all of the phones but based on your response it seems that is the only option after this version update.

 

[sob]

I just had the same issue
this appears to be a Bug(!)
the custom templates are still in the dropdown (at the very bottom)
the dropdown has new sections now

• preferred
• supported
• 3rd party
• custom

but the issue is: although you can select the custom template, it does not use it, instead it uses the default template
the reason is: the model description in the custom template is identical to the description in the original template

in the old 3CX version it would show the template file name, like: <template.ph.xml>
this is no longer the case
it detects the custom template, you can select it, but it uses the default template

if you rename the model description in the custom template, it will show the file name again
DO NOT RENAME, IF YOU HAVE PHONES PROVISIONED WITH THAT TEMPLATE!
because renaming the description:

• would set all provisioned phones to UNPROVISIONED
• remove the MAC address from the user
• revert to the first template entry (Fanvil H2S)

so in order to provision new phones with a custom template, you would need to create a new file and rename the model descriptions.

@3CX Devs: please fix that
I understand that you don't officially support custom templates (for whatever reason, idk/idc, does not make sense imho)
but that has to be a BUG

thank you

 

[PierreS_3CX]

Devs are aware of this problem, and already fix it in next update.

 

[JSar]

Is an update available? Any workaround?

 

[Inxss]

Devs are aware of this problem, and already fix it in next update.

Still no changes...
we are use PRO v18 update 7
over 250 ip phones Yealink t19 and t21 - is unprovisioned... because yealink.ph is out

 

[JohnS_3CX]

Still no changes...
we are use PRO v18 update 7
over 250 ip phones Yealink t19 and t21 - is unprovisioned... because yealink.ph is out

Hi @Inxss

Were you using a custom template for those or the default one that we used to have before we removed the EOL models?

 

[Inxss]

We are used yealink.ph.xml
This is sample from official file:

<?xml version="1.0" encoding="utf-8"?>
<doc xmlns:tcx="http://www.3cx.com">
  <header>
    <type>phone-template</type>
    <version>139112</version>
    <time>2022-02-10 11:00:00</time>
    <name>Yealink T2X</name>
    <url>https://www.3cx.com/sip-phones/yealink-t20p-t22p-t26p-t28p/</url>
    <templatetype>deleted</templatetype>
    <models>
      <model ua="SIP-T19P" defaultlogo="yealinkt22.dob" logowidth="132" logoheight="64" logobitdepth="1">Yealink T19</model>
      <model ua="SIP-T20P">Yealink T20</model>
      <model ua="SIP-T21P" defaultlogo="yealinkt22.dob" logowidth="132" logoheight="64" logobitdepth="1">Yealink T21</model>
      <model ua="SIP-T22P" defaultlogo="yealinkt22.dob" logowidth="132" logoheight="64" logobitdepth="1">Yealink T22</model>
      <model ua="SIP-T26P" defaultlogo="yealinkt22.dob" logowidth="132" logoheight="64" logobitdepth="1">Yealink T26</model>

and we are used our custom for 1st generation Yealink t46
now it's impossible, but t46 is compatible with newer t46, and... we are apply newer stock template...

so you may to try copy any stock template - save as <another name>, and after apply - its dissapeared