Phones not provisioning

[Chad Yost]

I'm running V16 in Google Cloud, SBC on site. I have 3 versions of phones. Yealink 42s, 46s and an old 22P (I had it working) I flashed them with the correct firmware per 3cx, patchT4XS-66.83.0.55 for the newer phones, factory reset them, and plugged them in. They show up just like they should, I added the extensions to each of them. All seems good. The phones flash, get their settings, but don't provision. All the settings in the phone look correct, the provisioning URL is correct, the account status-account1 name is the extension specified. On the status page of the phones they have "Register Failed". The only thing I did notice is that there is no username in the phone Auto Provision settings. I tried putting the correct username in there, and no go. I also have made sure that the "SSL Transport and Ciphers" is disabled. But in trying to remember if it was that setting or the "Secure SIP/TLS" on the next page I have wiped out all the Certificate info. I don't think that is related to the problem, they were not provisioning before I unchecked the "Secure SIP/TLS" in the Security Settings, Secure SIP tab.

 

[Saqqara]

Make sure the wan IP address has not been blacklisted.

Untick 'Block Remote Tunnel Connections (3CX Client connections with Tunnel enabled & SBC will be blocked)' under the options Tab for the extension

Check that you allow port 5001 outbound from the firewall protecting the SBC.

There is no username and password use for the provisioning url,

 

[Lee Cramman]

Make sure you download your firmware from the 3CX site rather than Yealink themselves.

Are you using PNP provisioning or manually adding the phones using the MAC addresses?

If you've done a factory reset on the the 22P don't forget you will have to manually disable the certification check using the phone's web UI (but that doesn't explain the problem with the ther phones).

 

[JohnS_3CX]

Hi Chad,

Firstly make sure that under the extension's Provisioning tab, you have 3CX SBC Remote selected as the provisioning method, and under the Options tab that Block Remote Tunnel Connection is not enabled.

The default provisioning URL port is 5001 so the phones will need firewall access to the HTTPS port for provisioning purposes (that does not go through the tunnel). Next, i would reset the phones again, and see if they appear under the Phones section.

At this point, can you tell me if you are using a 3CX FQDN or your own?

PS: The T22 is Incompatible with secure "SSL Transport and Ciphers" setting so you can disable that in the PBX Security settings

 

[Chad Yost]

@Saqqara
No Blacklisted IP's
Block Remote Tunnel Connections was unmarked
5001 Egress is open
(good to know about the no username/pass)

@Lee Cramman
Firmware was from 3cx firmware site.
I was using PNP, they showed right up in the phones section as soon as they were booted up.

@JohnS_3CX
Using a 3CX FQDN

The SBC was selected, however it had an X.X.X.112 address, instead of the X.X.X.5 that the device should be at. I double checked my DHCP Reservations and rebooted the PI confirmed it was at X.X.X.5 I deleted all the phones out of the "phones" section, and factory reset them.

The 22P came right up, I assigned the extension, and blink blink blink, it was provisioned!! The 42 and 46 did not show up under the Phones section (I wish when you deleted a phone, it would remove it from the "phones" list and from the users "phone provisioning" drop down. It only make sense to remove it from both places if deleting it.)

I have factory reset the 42, and 46, double checked the firmware, and rebooted them. They are not showing up under the Phones section now. (they were before). The 22p seems to be fine. ugh...

 

[JohnS_3CX]

Since the T22P worked, I would recommend you take a look at the following guide in order to troubleshoot the other two devices that don't appear under Phones

https://www.3cx.com/docs/plug-and-play-ip-phone/

 

[Saqqara]

What happens if you manually add the phones to 3CX , and paste the provisioning url into phone webfront end

 

[Chad Yost]

So after trying and rechecking ALL the suggestions, looking back at the tech sheets for set up. I decided it was time to beat them with a hammer!!

I downloaded Yealinks firmware (for 3cx) attempted to flash that, and try: No go
I tried the newer version of Yealinks firmware: No go (didn't expect it to, I was just getting an error trying to upload the same version of 3cx firmware from 3cx's site)
I redownloaded the 3cx firmware, (not just the patch!!) downgraded the phone to it. Still would not PNP show up in the Phones section.
I finally added the phones manually to 3cx, "Phones", "Add Phone", Put the MAC address in, and made sure to choose SBC, and manually put in the correct x.x.x.5 IP of the SBC, copied over the Provisioning link to the phone, and VOILA!!! They showed up!!!

To me it feels like 3CX was still holding on to the wrong SBC IP for those phones somewhere. Also in my haste, I assigned the wrong extension the the 46, the user had already been assigned to the 22p phone. I went in and deleted the phone from the user: Extensions, Phone Provisioning, drop down selected the 46 phone and clicked delete. (Opposite way of how I had deleted the phones starting this whole mess) But now if I go over to the phones section, it still shows the user as having that 46 phone assigned to them. If I drill in to the phone, and go back to the phone provisioning tab, the phone does not show up in the drop down menu. Feels like a bug there like that is maybe where it was holding on to the wrong SBC IP address.

Thanks to all who helped!
Chad

 

[YiannisH_3CX]

Glad to see you were able to provision the phones and everything is working now. Without looking at your configuration and logs however i cannot say what went wrong in your case but if a phone is deleted the PBX does not keep a record of PnP requests and the IP they came from.

What i should mention however is that deleting a device from the extensions provisioning tab will not delete or unregister the phone from the PBX. Since the phone has already been provisioned it knows the registrar address of the PBX and the credentials to register to the extension. So it will continue to register to the extension until the phone is factory reset. If by deleting the phone from the phone provisioning tab deleted the phone from the PBX entirely then manual registration of devices would not be possible. The provisioning tab is there to help you easily provision a device and pass it the correct information without the need of manually applying all changes. It does not control the registration of a device to the PBX.