Solved Unable to provision phones through SBC

Status
Not open for further replies.

Gwish

Gold Partner
Advanced Certified
Joined
Oct 12, 2021
Messages
10
Reaction score
6
PBX: 18.0.7.312
SBC: Windows 18.1.36

We have a client that is unable to provision phones through the SBC on the current production (non-alpha) version. I tested this on our Lab environment with the exact same results.

I then fully updated our lab to the newest "Alpha" version and the phones we able to be provisioned.

What is broken in the current release that is not provisioning phones properly?
How are clients able to provision phones without updating to an alpha version?
 
Hi there.
The phones on the mentioned version of the PBX should be able to get the provisioning link directly from the RPS server once they are on the latest, supported firmware, as well as factory reset.
Once the config file is loaded on the phone (it might take some minutes as some phones will reboot too), then the phone will use the SBC to register on the PBX.

Not sure what was the issue in your case, and we could have a look if you open a ticket with us.
 
The phones are Yealink T43U, on the latest, supported firmware. I agree with everything you said, however, it is not so. I spent all of the previous day factory resetting the phones, trying to get them to provision. I also provisioned them with our internal PBX to make sure I wasn't going crazy, or that I had dead phones.

They show up in the "Phones" page as "New" then I assign them to an extension, and nothing ever happens. I've waited plenty long (15-20 minutes) but the phones are not getting provisioned.

I will open a ticket to have support take a look.
 
Great, we will take it from there.
It seems that your FQDN is not a 3CX one as well as you are using your own SSL, which can be the source of the issue.
You could try and disable the phone TLS SSL check to verify if it's getting provisioned after.
 
  • Like
Reactions: JohnS_3CX and Gwish
Thank you Oleg. It was in fact the custom SSL certificate we are using was not trusted by the Yealink phones. A temporary workaround is to disable the "Only Accept Trusted Certificates" in the phone security menu.

I will load the certificate into the trusted repository on the phones to prevent further provisioning issues.
 
Perfect. Thank you for your feedback provided here, it can be useful for the other colleagues too
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet