SNOM phone provisioning with custom templates

[briasull]

Hello, has anyone had any issues with custom Snom templates when provisioning a phone?

I tired this on multiple models and can get past this screen:



The default template seems to work fine, but the logic with custom Snom template does not work when provisioning a Snom phone.

=====================================

Version 20.0 Update 6 (Build 724 Release) Enterprise license.
Previous versions this was working on: Last V18 build 25 and before v20 Update 6 (unknown which build the issue started)

=====================================

Is there a problem in the latest current version (v20 U6) of 3cx that will not allow you to provision custom template for snom phones?

I just copied the default template (no changes, just saved) and it still did not work and gets stuck at adding the phone.
Looking at a HAR file here is the error when trying to provision the phone of an existing or newly provisioned user.

We have other customers that need to move off v18 but this may prevent the upgrade to v20. Please let me know if there is a workaround or a patch to fix this issue. Thanks!

Here is what we are getting as error on the phage when trying to get this processed:

1. {@odata.context: "https://customer.example.com/xapi/v1/$metadata#Users(Phones,Phones())/$entity",…}
   1. @odata.context: "https://customer.example.com/xapi/v1/$metadata#Users(Phones,Phones())/$entity"
   2. Phones: []
      
2. {error: {code: "", message: "Phones[0].Settings.Codecs:↵WARNINGS.XAPI.INVALID",…}}
   1. error: {code: "", message: "Phones[0].Settings.Codecs:↵WARNINGS.XAPI.INVALID",…}
      1. code: ""
      2. details: [{code: "", message: "WARNINGS.XAPI.INVALID", target: "Phones[0].Settings.Codecs"}]
      3. message: "Phones[0].Settings.Codecs:\nWARNINGS.XAPI.INVALID"

 

[briasull]

I was able to solve this issue. The templates were not updating consistently via restart of the system to update the custom templates.

This was a CODEC issue in the custom template. I had multiple Codecspriority defined, but was only calling out one codec_priority_list. This use to work in previous versions, but does not seem to work anymore. So I matched it and it worked properly for previsioning the phones.

...
<Codecspriorities>
<Codecspriority variableName="codec1" priority="1">
<!--The first entry is the selected entry in management console-->
<option value="pcmu">G711u</option>
</Codecspriority>
...
<!--# The fields "codec1_name", "codec2_name", "codec3_name", and codec4_name" specify the codec preference order (with "codec1_name" being the first preference). Valid values are 0==G711u, 2==G726-32, 3==GSM, 4==G723, 8==G711a, 9==G722, 18==G729. The provisioning template sets the preference order to G711u, G711a, G729, GSM.-->
<codec_priority_list idx="1" perm="">%%codec1%%,telephone-event</codec_priority_list>
...

I also updated the template in this location and it did not update, even after a OS restart.
/var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioningi/xxxxxxxxxx/CustomTemplates/phones

There is some caching causing issue, but I them modified the custom template in the GUI under advanced settings to match it. Once this was done the running template and the file saved on the filesystem matched.

No further custom template issues with provisioning Snom phones after the changes. Issue resolved!