Issues with registration since upgrading to v20

[Alphabetic]

Hi support

I took an on premise installation to v20 yesterday and had issues with phone provisioning.

PBX and phones are on the LAN.

Split DNS is set up.

I've got floods of entries in the event log 12291 - Block WAN requests is ON - Why does this apply when they're all local?

WAN IP and LAN Subnet are whitelisted.

When I use the FQDN under account / SIP the phone doesnt register.

Changing it to the LAN IP and it works but it reprovisioned with the FQDN and it gets kicked off again.

Phone is a Yealink T46S 66.86.0.15

 

[JohnS_3CX]

Sounds very much like the split DNS entries are not working, and the phones probably resolve the FQDN to the public IP instead of the local IP of the machine.

 

[Alphabetic]

Hi John,

this is from the phone that I just factory reset.




It doesnt appear to be then pulling the config and setting itself up.

Its showing up in the PNP tab



Cant do much else - in v18 I could assign it again and it would pull, but it wont.

Am I supposed to do something? Do I need opt 66?

 

[JohnS_3CX]

I notice this is a Yealink phone. Are you using our FQDN and certs?

Yealink phones do not support all 3rd party certs and they will fail to provision over HTTPS

 

[Alphabetic]

Yes, all 3CX FQDN and certs nothing out the ordinary.

 

[OlegR_3CX]

@Alphabetic
Did you modify any parameter in the 3CX system?
When you mentioned the phones got blacklisted, did you notice all different local IPs in the Blacklist there?

 

[Alphabetic]

No, phones initially would have been set up with :5001 so we factory reset them.

 

[JohnS_3CX]

I've just assigned a T46S 66.86.0.15 to a Local V20 update 1 over split DNS FQDN provisioning just now, so I can confirm it should work in principle.

Check the phones have not been blacklisted, check the 3CX Network settings and ensure the correct machine IP is defined (in case it has changed), and ensure the "Block WAN requests is ON" was coming specifically from a phone local IP and not something else.

 

[Alphabetic]

Hi John,

yes - If i delete the phone and then use PNP to assign again it works.



The scenario is the the phone is already assigned to the extension so the phone doesnt appear to be going to ask for its config. In v18 I could assign the phone to the extension again and it would send the config but cannot do that in v20. So do I need opt 66?

 

[OlegR_3CX]

No, phones initially would have been set up with :5001 so we factory reset them.

This is not clear, can you please elaborate in more details?
Does it mean your system was on 5001, and you manually change the port it in the parameters?

 

[Alphabetic]

This is not clear, can you please elaborate in more details?
Does it mean your system was on 5001, and you manually change the port it in the parameters?

v18 we were on :5001

Reinstalled with the ISO, restored from backup and the default was 443.

 

[OlegR_3CX]

We need some more clarifications here.
So all your phones had port 5001 in their settings and only after reinstall they got blacklisted, right? If you factory reset the phone and provision it again it works fine, correct?

 

[Alphabetic]

Yes, phones were getting blacklisted after going to v20.

Factory reset the phones and whilst some appeared to come back and reprovision, some did not.

initially I did not have split DNS configured so this is probably why the WAN block request was coming.

However, i'm finding that when It comes to set the phones back up again, they're not looking to the PBX for config unless I delete the phone from ext and set it back up.

How do I get it so the phones go looking? its like the RPS request hasnt been sent

 

[OlegR_3CX]

So initially, your phones had IP URL in their settings, right?

 

[Alphabetic]

Yes

 

[OlegR_3CX]

It's now it's clear, and actually you had no way around that in this way.
The phones were getting blacklisted, as they were contacting a wrong port, as the 3CX system could not generate a config file based on that request.
So if you choose Split-DNS, the phones need to get a NEW provisioning link which is your FQDN URL, and they can only get it once they are factory reset. In your case, there is no way around that, unless you would manually delete the port from the phones so the phone make a correct request and get a config file in return.

 

[Alphabetic]

Yes Oleg, thats what i'm saying we're doing.

The phones are factory resetting and then they're staying factory reset.

phone says config skipped.

Its only when I delete phone and add it back again to ext do I get the notification about RPS being sent then the phone provisions.

I cannot do anything from the PNP phone tab, cannot reassign, cannot push config.

v18 I could just assign and press OK and the RPS would go off. There seems to be no way I can go to the IP Phone tab, change a setting then hit OK to send that RPS request.

 

[SweetAction]

I would recommend you set opt66 unless you have access to Yealink RPS and can manually add the entries. I understand you want the 3CX system to send the RPS request, but it won't do so by just hitting OK in the web admin - you need to delete and readd - so these other 2 options will avoid that issue.

 

[OlegR_3CX]

@Alphabetic
In V20, you cannot reassign the phone like you could on V18. You have to delete it first before you can send PnP Notify message to the phone.

 

[HighTechIT]

@Alphabetic I've just upgraded to V20 and had the same problem, and I believe I've found the issue.
The auto provisioning URL that is stored in the Yealink phones is now wrong after the V20 upgrade.
I've changed my URL's below for security.
V18 http://1.1.1.1(3CXServerIP):5000/provisioning/....(UniqueProvisioningID)
V20 http://1.1.1.1(3CXServerIP)/provisioning/....(UniqueProvisioningID)
Notice the port 5000 is not in the V20 provisioning URL.

I found that I can't update firmware on phones, or make changes.

If I login to a Yealink phone and fix the URL (delete :5000) I can then push firmware as expected.