Solved Grandstream Phone Not Provision V16.0.1.273

[iSpark Solutions]

New 3CX setup v16.0.1.273 (Not upgrade), 3CX and IP Phones on same subnet.
I have two Granstream models GXP2170 and GXP2135, they all upgraded to firmware 1.0.9.132 which downloaded from 3CX
Phones show up in PNP, after assign extension to the phones, the new provision link updated in the Config Server Path settings correctly.
But then the phones won't reboot itself or manual reboot doesn't help, I also tried factory reset.
It happens on both Debian and Windows 10 installation.
Does anyone have a clue what would go wrong? Thanks.

 

[Evolute IT]

New 3CX setup v16.0.1.273 (Not upgrade), 3CX and IP Phones on same subnet.
I have two Granstream models GXP2170 and GXP2135, they all upgraded to firmware 1.0.9.132 which downloaded from 3CX
Phones show up in PNP, after assign extension to the phones, the new provision link updated in the Config Server Path settings correctly.
But then the phones won't reboot itself or manual reboot doesn't help, I also tried factory reset.
It happens on both Debian and Windows 10 installation.
Does anyone have a clue what would go wrong? Thanks.

Are you using a local 3CX?

Did you factory reset the phones?

Check for the "Validate server certificate" somewhere in the Provisioning settings. Uncheck it if your 3CX is local then try again.

 

[iSpark Solutions]

Are you using a local 3CX?

Did you factory reset the phones?

Check for the "Validate server certificate" somewhere in the Provisioning settings. Uncheck it if your 3CX is local then try again.

Yes the 3CX is local installation not cloud.
I did factory reset the phones.
Validate Server Certificates setting is No
Thanks.

 

[Evolute IT]

Yes the 3CX is local installation not cloud.
I did factory reset the phones.
Validate Server Certificates setting is No
Thanks.

Can you run a packet capture from both ends and see if the SIP NOTIFY gets to the phone.

Also, check that you don't have a DHCP Option 66. If so, it will interfere with the Provisioning.

 

[iSpark Solutions]

Can you run a packet capture from both ends and see if the SIP NOTIFY gets to the phone.

Also, check that you don't have a DHCP Option 66. If so, it will interfere with the Provisioning.

You rock Fredrick, the DHCP option cause the conflict, we are migrating to new phone system and not aware the old system has DHCP option 66 in place, the provision working fine now, you save my day, thanks