Solved Yealink Phones won't AutoProvision from 3CX RPS link

[Kirsty - Fountain IT]

I have 2 Yealink phones I want to use remotely. A T46S and a T41S.
Both phones have been factory reset and are on the latest 3CX recommended firmware.

3CX is version 18 and fully up to date with all updates and patches.
All firewall tests have passed.

I have followed the Remote Provisioning instructions of putting the phones MAC addresses in against the appropriate extensions and the 3CX phone system has successfully published the provisioning address. I checked the event log and it says:-
RPS request for Yealink T41S IP Phone of xx xx (104) delivered successfully
RPS request for Yealink T46S IP Phone of xx xx (102) delivered successfully
I have also set allow extensions outside of the LAN option.

So as far as i'm concerned that is 3CX configured correctly.

I then factory reset both phones and waited for them to provision.
They come up with 'Config updating', then give up after a while with a 'No Service' message.

I have also tried manually putting the provisioning address in the phone's web interface and doing it that way.
Still no luck.

I have done both ways several times each but they just won't provision.

I have read in the forum that there was an issue with Let's Encrypt certificates causing an issue with provisioning, but the 3CX system is up to date with all updates and patches, so that shouldn't be an issue should it? How could I check if I have the right certificate?

How can I get the phones to provision?

 

[jcostlow]

Have you enabled use of the extension outside the LAN under the extensions options? I went to read the guide for those models and didn't see that mentioned but it is needed for phones using STUN or direct SIP.

 

[Kirsty - Fountain IT]

Yes, I wrote that in my original post:-

I have also set allow extensions outside of the LAN option.

 

[cobaltit]

Can you access the 3CX management console from the location where the remote phones are at??

 

[JohnS_3CX]

The phones will contact the Yealink RPS to get your PBX's config URL and then they will contact it.

At that point you should be able to see the phone asking you for credentials:

If this last part is not happening then we would have to check the following:

1. Can the phone access the internet?
2. Is your PBX HTTPS port open?
3. Have you installed the Let's Encrypt Hotfix that would have appeared in the 3CX Updates?
4. If you manually paste the config URL in one of the phones, will it provision itself?

 

[two]

1. Can the phone access the internet? Yes
2. Is your PBX HTTPS port open? Yes
3. Have you installed the Let's Encrypt Hotfix that would have appeared in the 3CX Updates? Yes
4. If you manually paste the config URL in one of the phones, will it provision itself? No

 

[JohnS_3CX]

@Nial ok in this case, please send me a private message with your FQDN so that I can check a couple of things from my end.

 

[two]

Hi All,

Please paste your stun provision link into the browser of the network you are putting phone on, followed by the 12 didgit mac address + .cfg. This will download the .cfg file. Please then import into the gui of the phone interface.

https://FQDN.3cx.co.uk/provisioning/0rand3bfcq5/000000000000.cfg

thank you

 

[JohnS_3CX]

Hi @Nial

is this for the same case that @fountain started or are you unrelated?

 

[two]

unrelated but same parameters.

 

[Kirsty - Fountain IT]

Can you access the 3CX management console from the location where the remote phones are at??

Hi cobaltit, no I cannot access the 3CX console from outside the 3CX server's LAN!!
You hit the nail right on the head.
Although I had opened all the ports for SIP and media etc (and the firewall tests pass). I had not done the port for the console.
I was thinking don't need that open to the Internet but of course you do for remote extensions.
Port open, factory reset phones again and both provisioned and working no problem.
Such a silly mistake overlooked on my part. THANK YOU cobaltit

 

[Kirsty - Fountain IT]

Hi JohnS_3CX,

1) Phones can access the Internet.
2) No the PBX HTTPS port was NOT open. Silly mistake on my part. All working now.
3) The Let's Encrypt hotfix was done.
4) Manually pasting the URL into the phone's interface did not work, because I hadn't opened the console port to the Internet. Firewall does not check for this.

Thanks for your help

 

[Kirsty - Fountain IT]

Oi Nial!, hijacking my thread, lol.
I do not know this man JohnS_3CX

 

[JohnS_3CX]

@Nial kindly read this and start a new thread so we don't confuse separate cases.

@Kirsty - Fountain IT glad it it was all sorted! we will mark this one as solved then