Solved Auto Provisioning with Yealink T19

[phoanglong]

Dear all,

I'm trying to get the auto provision working but without success, could someone please help.

I have been able to auto-provision my Yealink on Local but when I tried 3CX remote SCB the IP Phone (Yealink T19) only show “operation is completed” but it does not actually work.

- Ports are opened: 5060, 5061, 5090, 9000-10999, 5001 and forwarded accordingly

- Provision on 3CX Mobile App is working, I have been able to make call from my mobile (through 4G connection) to internal SIP.

Many thanks

 

[Saqqara]

Have you checked limitations https://www.3cx.com/sip-phones/yealink-t1-series/

you need to disable ‘accept only trusted certificates’ on the phone - http://support.yealink.com/faq/faqInfo?id=13

also under options for the extension , have you unticked the option to allow sbc setup (cannot remember the full text for the option, but you will see it)

 

[phoanglong]

Thank you for your response but i have "Only Accept Trusted Certificates " & unticked "Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked)" but my IP Phone is not Provisioning. The strangest thing is that i have been able to auto provisioning them before and they worked like a charm, i have just reinstall the system (and restored from backup) but everything now is no longer working.

P/s: when i tried to get the "cfg" file by typing https://xxx.xxx.xx:5101/provisioning/orh60zmo9y7zrc.cfg, it shows a blank page.

 

[complex1]

I have several remote T19's all provisioned using STUN and working fine.
To get the "cfg" file please type https://FQDN.3cx.com:5001/provisioning/orh60zmo9y7zrc/<MAC-address>.cfg

 

[phoanglong]

I have several remote T19's all provisioned using STUN and working fine.
To get the "cfg" file please type https://FQDN.3cx.com:5001/provisioning/orh60zmo9y7zrc/<MAC-address>.cfg

Many thanks for your reply. But I still have not been able to get the Auto-Provisioning working but strangely enough, if I change the Provisioning Method to STUN and manually enter authentication details, extension number, server url, account etc... to Yealink T19, it shows “registered” and I have been able to make call through the IP Phone (w/ PBX Delivers Audio option enabled). I could not figure it out the reason why I could not make Auto-Provision to work eventhough everything else seem to be working fine.

 

[complex1]

Which T19 do you use? The SIP-T19P or SIP-T19(P) E2
Please reset the phone to factory default and try provisioning again.
If you use the SIP-T19P then take note of the limitations as @Saqqara replied earlier.

 

[JohnS_3CX]

What firmware is the phone running currently?

 

[phoanglong]

Which T19 do you use? The SIP-T19P or SIP-T19(P) E2
Please reset the phone to factory default and try provisioning again.
If you use the SIP-T19P then take note of the limitations as @Saqqara replied earlier.

My Yealink is T19P and I have been factory reset it a few times, re-upgraded the firmware but nothing seem to be working

What firmware is the phone running currently?

It is currently running 31.72.0.105

 

[JohnS_3CX]

Ok Then, based on your model, all these limitations do indeed apply because it's too old and cannot support the latest encryption https://www.3cx.com/sip-phones/yealink-t1-series/#h.8owp0itk5r99

You will have to not only disable trusted certificates on the device, but also reduce the PBX security ciphers from Settings > Security > SSL/SecureSIP Transport and Ciphers, otherwise it will not autoprovision

 

[phoanglong]

Ok Then, based on your model, all these limitations do indeed apply because it's too old and cannot support the latest encryption https://www.3cx.com/sip-phones/yealink-t1-series/#h.8owp0itk5r99

You will have to not only disable trusted certificates on the device, but also reduce the PBX security ciphers from Settings > Security > SSL/SecureSIP Transport and Ciphers, otherwise it will not autoprovision

OMG, thank you so much for your help, it is working like a charm, for anyone who is facing the same problem, the solution is as follow:

(1) Disable trusted certificates on the device;
(2) Disable SSL/SecureSIP Transport and Ciphers (Settings > Security, scroll down to the bottom of the page and untick)

Case closed, many thanks.

 

[JohnS_3CX]

Glad to hear it was resolved