Solved Grandstream GXP2160 phones won't provision

[sdrummond]

Attempting to set up a new system (3CX Professional 16.0.8.9), GXP2160 phones won't provision.

The phones are on the same subnet as 3CX and are showing up in the phones tab, but aren't actually pulling any configuration.

I've factory defaulted the phones several times with no change. The phones are pulling the correct configuration URL from the PBX, but just aren't pulling the actual configuration. If I go to the provisioning URL (with cfgMAC.xml), I get a valid .xml file.

I plugged in a snom D735 phone, it provisioned with no problems.

I've also connected a known-working GXP2160 phone from another system in, it is also failing to provision.

Any thoughts/suggestions/ideas?

 

[Evolute IT]

Attempting to set up a new system (3CX Professional 16.0.8.9), GXP2160 phones won't provision.

The phones are on the same subnet as 3CX and are showing up in the phones tab, but aren't actually pulling any configuration.

I've factory defaulted the phones several times with no change. The phones are pulling the correct configuration URL from the PBX, but just aren't pulling the actual configuration. If I go to the provisioning URL (with cfgMAC.xml), I get a valid .xml file.

I plugged in a snom D735 phone, it provisioned with no problems.

I've also connected a known-working GXP2160 phone from another system in, it is also failing to provision.

Any thoughts/suggestions/ideas?

Firmware of the phone?

 

[Saqqara]

Running the correct firmware ?

https://www.3cx.com/sip-phones/grandstream-gxp21-series/

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

 

[sdrummond]

Firmware of the phone?

Currently on 1.0.11.35. I've attempted to provision 3 separate GXP2160's, several were originally on 1.0.9.35.

 

[Evolute IT]

Currently on 1.0.11.35. I've attempted to provision 3 separate GXP2160's, several were originally on 1.0.9.35.

Try downloading the XML file and uploading it manually to the phone Config File XML.

 

[sdrummond]

Try downloading the XML file and uploading it manually to the phone Config File XML.

That works - the test phone registered successfully. I'm still trying to figure out why it isn't pulling automatically as I have over 20 phones to set up for this system.

 

[Evolute IT]

That works - the test phone registered successfully. I'm still trying to figure out why it isn't pulling automatically as I have over 20 phones to set up for this system.

It is odd. Could it be a local firewall policy or any kind of routing?

Also, is it on Windows or Linux? You need to disable the Windows firewall if it's Windows.

 

[sdrummond]

It is odd. Could it be a local firewall policy or any kind of routing?

Also, is it on Windows or Linux? You need to disable the Windows firewall if it's Windows.

They're on the same subnet and switch behind a Sonicwall TZ350 firewall. I've looked at the routing and couldn't find anything blocking traffic on the subnet, but will double-check.

It's a fresh install from the 3CX Debian ISO (downloaded yesterday).

As a test, I added BLF keys to the phone and then told the system to re-provision - it successfully pushed the updated configuration.

 

[Evolute IT]

They're on the same subnet and switch behind a Sonicwall TZ350 firewall. I've looked at the routing and couldn't find anything blocking traffic on the subnet, but will double-check.

It's a fresh install from the 3CX Debian ISO (downloaded yesterday).

As a test, I added BLF keys to the phone and then told the system to re-provision - it successfully pushed the updated configuration.

Do you have SIP ALG disabled?

If the phones did show up, you don't have a multicast issue. And if they reprovisioned once initially provisioned, then the file is valid.

Therefore, the issue comes when the PBX tries to send the SIP NOTIFY to the phone for it to provision.

 

[sdrummond]

Do you have SIP ALG disabled?

If the phones did show up, you don't have a multicast issue. And if they reprovisioned once initially provisioned, then the file is valid.

Therefore, the issue comes when the PBX tries to send the SIP NOTIFY to the phone for it to provision.

Sonicwall doesn't have SIP ALG as a specific setting, but I had already used the steps listed by Sonicwall to disable SIP ALG: https://www.sonicwall.com/support/knowledge-base/how-to-disable-sip-alg/210615065648977/.

I'm still digging in the firewall - I wasn't seeing any traffic between the PBX and the phone when I tried to monitor through the firewall earlier.

 

[sdrummond]

Thank you for your help - I also opened a ticket with 3CX support and think we may have resolved the issue. They stated that DHCP options can interfere with the provisioning process. After disabling DHCP option 66, I was able to successfully provision a phone. I'll update shortly to confirm if this is resolved.

 

[sdrummond]

Thank you for your help - I also opened a ticket with 3CX support and think we may have resolved the issue. They stated that DHCP options can interfere with the provisioning process. After disabling DHCP option 66, I was able to successfully provision a phone. I'll update shortly to confirm if this is resolved.

I apologize for the delay - I have confirmed disabling the DHCP option has resolved the issue. I was able to add a new phone to the network and provision it with no issues.

Thank you all for your help, especially @Frederick Marcoux!