Solved Yealink T28P not getting provisioned

[George Ts]

Hello,

I tend to believe that Yealinks cannot be provisioned via HTTP, but only via PnP.
A Yealink in the LAN was successfully added as a "New" entry under the Phones tab, which waited for approval (i.e. "Assign Ext" or "Add Extension")

The same MAC address, when requested via HTTP even from the same LAN, did not return any file.
It is the Yealink's PnP request that triggered the 3cx to create a cfg file.
The HTTP GET never triggered 3cx to create a .cfg file.
Besides, HTTP is never mentioned on 3cx's documentation on how to provision Yealink T2x here: https://www.3cx.com/sip-phones/yealink-t20p-t22p-t26p-t28p/

Anyone willing for a brief test, can try on their own. Please create an extension, assign a dummy MAC address under that extension, give it the Yealink T28 default template and try to fetch it over HTTP via a browser.
Are you able to do that?

Regards,
George

 

[YiannisH_3CX]

The only cases i have seen the 3CX server replying with a 404 message to a provisioning request in if the mac address is miss-configured under the extension settings or when the provisioning link is not correct meaning the IP or the random folder has changed.
So i believe that either something is miss-configured on the server or something is corrupted which is causing the error.

tend to believe that Yealinks cannot be provisioned via HTTP, but only via PnP.

You do not need PnP for the server to generate a config file. Once you add a phone to an extension and click OK you are able to send a request to the server for the config file.

Anyone willing for a brief test, can try on their own. Please create an extension, assign a dummy MAC address under that extension, give it the Yealink T28 default template and try to fetch it over HTTP via a browser.
Are you able to do that?

Just tried and yes i am able to get the file.

 

[George Ts]

@YiannisH_3CX , just to make sure:
The file requested by the Yealink is http://3cx_IP_address:5000/provisioning/xxxxyyyy/001565123456.cfg
Does the path look correct?
I know that this path works for Polycoms, but I have not tried with a Yealink before.

For example, is there any chance that the Yealink provisioning files are saved in a subdirectory under xxxxyyyy? (for example xxxxyyyy/yealink/001565123456.cfg)
Or are they under the link above?

If the link is correct, then i can guarantee that the MAC has been configured ok.
In fact, we tried with different MACs.

What else might be misconfigured on the server?

Regards,
George

 

[Blake Carter]

Out of curiosity, if you navigate to the file location:

C:\ProgramData\3CX\Instance1\Data\Http\Interface\provisioning\(interface name)

are you able to find the mac.cfg file here? If you can, try moving it out of the folder and readding the mac to the extensions and see if it will recreate a new copy when requested.

 

[George Ts]

Gone baby gone (a feature that honestly I do not like)
See here https://www.3cx.com/blog/docs/v15-finding-provisioning-files/

Regards,
George

 

[Blake Carter]

I was not aware of that. I had an issue with a yealink not pulling the cfg file when we were on V15.5 SP1 and I was able to move that cfg file and it recreated and solved the issue

 

[YiannisH_3CX]

@YiannisH_3CX , just to make sure:
The file requested by the Yealink is http://3cx_IP_address:5000/provisioning/xxxxyyyy/001565123456.cfg
Does the path look correct?
I know that this path works for Polycoms, but I have not tried with a Yealink before.

Yes the path looks correct and is what Yealink phones should use to get the file from the PBX.

I just had a thought about what may be causing this issue. Please navigate to Settings / Templates and locate the Yealink template that contains your models name. It should be "yealink.ph.xml"
Let me know of the version number. If you have a new version of the template it might contain variables that do no exist in your version of the PBX so the file cannot be generated. If that is the case then updating the PBX to the latest version will solve your issue.

 

[George Ts]

Hi @YiannisH_3CX
The version number of the yealink.ph.xml template is 80502.
3cx is running 15.5.6354.2.
The Yealink phone is running 2.73.0.60.

Regards,
George

 

[YiannisH_3CX]

The version number of the yealink.ph.xml template is 80502.

This is most likely what is causing the issue. Upgrade the phone system to the latest version and try to provision the phone again. The issue should be resolved.

 

[George Ts]

Thank you @YiannisH_3CX , really useful to know.
This brings one more question, please:
Aren't the templates (and as a result, the template version) upgraded together with the 3cx version?
I mean, how can we be using a newer template version for an older 3cx release?
Is there a chance that our 3cx administrators had installed a newer version of a Yealink template in an existing 3cx version?
Silly question maybe, but I have not happened to install another template version than the one already supported by the current 3cx's version.

Regards,
George

 

[YiannisH_3CX]

Some times template updates come out after a service pack has been released to fix a specific issue. The new template will then be visible in your management console if you are running these phones. If you download it then it will apply.

 

[George Ts]

@YiannisH_3CX , just wanted to thank you for your finding and confirm that this was the root cause.
We switched back to template version 71354 and everything works like a charm.
This case was really interesting to discuss. It may be closed.
Again, many thanks.

Regards,
George

 

[YiannisH_3CX]

Glad i could assist and thank you for updating the thread with your solution.