Grandstream Fails to load

[AS19]

When I tried adding some new Grandstream GXP1760Ws to my PBX today, none of the new phones would show up in the phones tab in 3cx.

So I copied and pasted the configuration url into phone, but kept getting a configuration failed message.

I eventually downloaded the XML config file directly from the 3cx server and tried loading to the phone via the phones web GUI, that didn't even slightly work.

The next thing I did was download the current config of the phone to get the command syntax and then convert the XML config file from 3cx to a plain text configuration file with the same syntax as the configuration file I downloaded form the phone. This kind of worked, some of settings were applied but the phone still doesn't register, the phone book doesn't work ect...

I can only assume that 3cx is generating an invalid configuration file.

I've also noticed that all my working phones suddenly have static IPs when they all should be DHCP.


Can anyone please help.


System Info

• 3CX Version, Standard Annual16.0.676
• Server OS, Debian 9
• Is the 3CX Server Hosted and where? Local VM, hypervisor VMware ESXi, 6.7.0, 14320388
• IP Phone Make/Model/Firmware: Various granstream handsets
• Provisioning Method: Local / VPN / STUN / SBC: Local
• Trunk Provider or Gateway Make/Model: Patton 4114 & Grandstream GXW4104
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

 

[cobaltit]

Since it wasn't mentioned, I have to ask. Did you follow this guide, especially the part about required 3CX firmware?

 

[AS19]

yes the phones were update to the latest firmware before I did anything else

 

[JohnS_3CX]

If your phones are local and they don't appear on the phones tab when you reset them, perhaps there is an issue in your network configuration.

The PBX listens on the 224.0.1.75 for phones announcing the presence. Run netstat -g and you should see your interface bound on sip.mcast.net which translates to 224.0.1.75, the IP that phones would announce to.

The phones will need to be on the same network which allows the multicast message to go out and reach the PBX.

If either the server is not listening there, or the phones are sending to a listening server but the message never arrives due to network misconfig, you would expect to not see the phones appear on the management console.

 

[AS19]

Yeah, I followed the instructions on the 3cx website for troubleshooting sip multi cast, the server is listening, and I seriously doubt the network suddenly got misconfigured after of working for months.

But I don't even care if the phones don't automatically show up at this point. What I do care about is that the 3cx XML config files that are being generated don't work.
The phones rejects them, when you try and load them to the phone by entering
"http://<IP of PBX>:5000/provisioning/hcqnzytaa6rj4/"into the config server path on the phones GUI and then hitting the reprovision button, you get a a config failed message on the phone.

I've even seen the configuration failed message when my working phones reboot. The PBX is trying to upload config files that the phones will not accept.

I even went so far as to run "wget http://<IP of PBX>:5000/provisioning/hcqnzytaa6rj4/cfg<MAC of Phone>.xml" download the XML config file and wrote a python script to convert the data in the XML file that 3cx creates to provision the phone to a text file that I could manually upload to the phone with the upload config button in the phones GUI. the data from the XML file gives the phone a non working configuration.

 

[Evolute IT]

Yeah, I followed the instructions on the 3cx website for troubleshooting sip multi cast, the server is listening, and I seriously doubt the network suddenly got misconfigured after of working for months.

But I don't even care if the phones don't automatically show up at this point. What I do care about is that the 3cx XML config files that are being generated don't work.
The phones rejects them, when you try and load them to the phone by entering them into the config server path into the phones GUI and then hitting the reprovision button, you get a a config failed message on the phone.

I've even seen the configuration failed message when my working phones reboot. The PBX is trying to upload config files that the phones will not accept.

I even went so far as to run "wget http://<IP of PBX>:5000/provisioning/hcqnzytaa6rj4/cfg<MAC of Phone>.xml" download the XML config file and wrote a python script to convert the data in the XML file that 3cx creates to provision the phone to a text file that I could manually upload to the phone with the upload config button in the phones GUI. the data from the XML file gives the phone a non working configuration.

What firmware are you using? Latest supported?

I've never had this issue and I use almost exclusively Grandstream devices. If you recently updated the firmware, make sure to clear your browser cache so the Javascript in the Web UI works correctly.

 

[AS19]

Firmware version 1.0.1.89 on the GXP1760

 

[Evolute IT]

Firmware version 1.0.1.89 on the GXP1760

If you just download the XML file generated and upload it (no need to convert it at all), is the phone getting the config?

There might be a special character somewhere (extension name or FQDN or even passwords) that cause the XML to be invalid.

 

[AS19]

If you try loading the XML file the phones do absolutely nothing, no error message, no settings on the phone get changed.

 

[Evolute IT]

If you try loading the XML file the phones do absolutely nothing, no error message, no settings on the phone get changed.

Press F12 to open the developer tools, go to Console when uploading and saving. See if an error occurs.

If so, try Ctrl + Shift + R to refresh and clear the cache, then try again.

By the way, have you tried simply factory resetting them?

 

[AS19]

Ok Will give that a shot.

Yes I've tried resetting the phones, no change after resetting.

 

[AS19]

Just tried loading the config.xml file again with the console open. the XML config file still doesn't work.

Screen shot of the console messages attached