Solved Unable to provision phones

[dynam1c]

Hi All,
I have a new 3CX installation running on Amazon Lightsail.
I have a SBC with static IP address ( Rasperry Pi )
I have three phones Yealink T26P / Yealink T27P and Snom 320

I have managed to get one of the phones ( T27P ) to provision, this was done by using the mac address and provisioning code.
I can see the other two phones in the PBX but I can not get them to provision for the life of me.
The firmware is up to date, the T26P firmware was not in the 3CX download so have loaded the T27P firmware.
I have SSL Transport and Ciphers unticked
Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked) & Block Remote Tunnel Connections (3CX Client connections with Tunnel enabled & SBC will be blocked) are both unticked.

If I add the phone to an extension and add in the SBC IP address it should provision once I hit OK but nothing happens, even after hours and a reboot there is no configuration.
If I try the MAC address and Config URL it still will not connect.
if I remote into the phone and set it up manually - it works.
I am gearing up for a 40 phone rollout and dont want to provision phones and BLFs by hand. ( the SBC will be updated to windows in the rollout )

I have tried another router & even another network connection to no avail.

I have also tried option 66 but this has not helped.

Getting really frustrated as it should just work, this is the fist time I have done a lightsail install but as there is a SBC and we know it is working as I can see phones that are not allocated to an extension.

Look forward to any flashes of inspiration.


Regards
John
Auckland NZ

 

[cobaltit]

So not sure what I used the mac address and the provisioning URL means but the way you SHOULD be provisioning the phones with at SBC is the PnP method outlined here:

https://www.3cx.com/sip-phones/yealink-t20p-t22p-t26p-t28p/

Since you said the the T27P would provision but the T26 would not I would confirm you turned off the 'SSL Transport and Ciphers' setting. You say you turned it off but that's pretty much the only difference between those two phones as far as provisioning goes (assuming you have them on the correct firmware)

Also, you can leave 'disallow use outside of LAN' checked. Devices that connect via tunnel are considered to be inside the LAN.

 

[dynam1c]

Thanks for the reply.
The T27P was provisioned before I installed the SBC using direct SIP, I dont know how I got it to work but took me several hours and lots of factory resets.
I have just factory reset the phone and it re-provisioned as it should.
SSL transport is unticked - see attachment.

The T26P firmware is 6.73.0.50 reading online 3CX has its own firmware 6.73.0.60 but I cant install this as the phone is not provisioned.

In some cruel twist of fate I have assigned the Snom to an extension for the umpteenth time and it has worked. I dont know why, now I am updating the firmware on that.but that had resisted my charms for so long.

John

 

[cobaltit]

So if the phone is not on the current firmware that is the problem. The .60 firmware has support for the LE certificate. The idea is you are supposed to have the phone on the correct/current firmware before provisioning and then going forward you can update it via 3CX. The firmware guide link only has the supported phones but you can download required firmware from here:

https://www.3cx.com/support/phone-firmwares/

 

[eddv123]

Despite it now working (sort of) a side note to consider for the future should be that you will need port 5001 open on your firewall for provisioning of the phones, 5090 you have as you can see the phones.

 

[cobaltit]

@eddv123 I didn't see where it looked like the HTTPS port wasn't open but I would state rather that the HTTPS port needs to be open which could be 5001 or 443 since PBXExpress deployments use the 80/443 port combo.

 

[dynam1c]

So if the phone is not on the current firmware that is the problem. The .60 firmware has support for the LE certificate. The idea is you are supposed to have the phone on the correct/current firmware before provisioning and then going forward you can update it via 3CX. The firmware guide link only has the supported phones but you can download required firmware from here:

https://www.3cx.com/support/phone-firmwares/

Thanks for that, I have now applied the firmware.
I now get a prompt for username when I try and provision the phone, I put in the extension and then it prompts me for the username, after a few more times the IP address gets blocked by the portal.
I can manually set up the phone but still will not Autoprovision like it should.

As for opening ports 5001 / 80 / 443 I thought the SBC took care of that.

John

 

[dynam1c]

We have progress.
I have now been able to provision the phone.
I re-read the instructions and once entering the username I had to press the down arrow to enter the password.
The phone is now provisioned.
I have even been able to reprovision it.
Looks like the firmware was the big key, shame 3CX hid it, should have been on the provisioning page.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.

Please note that we make guides for phones for this reason. I believe the guide is clear enough on what you need to do to provision a phone. STEP 1: Upgrade to the Required firmware.