grandstream phones constantly ringing after update

[Noob]

Sorry, for my English

I solved the problem on my grandstream 1620 and 2130 phones​

but most of my phones are 1450, and I can not find a fix for them, so far they have not caused any problems.

I invested a lot in this 3cx solution, and when I implemented everything it was compatible

 

[accentlogic]

Good Morning,

I had the same problem, and it is very embarrassing, especially as IT manager and 3cx opologist as implementer, explain the management of a company, where the business lives on the phones, it will have to stop one day to solve the problem .

How to explain to the company that made a recent investment, that after all the phones are no longer supported on some models, and what's going to have to change everything?

Solution to phones constantly ringing after update:

The phones when they are playing do not let you make the changes.

1. download the firmware on the page of 3cx
https://www.3cx.com/support/phone-firmwares/
2. change the account ext. password in 3cx so that the phone does not register
3.create a TFTP, and put the files made available by 3CX
https://www.grandstream.com/sites/default/files/Resources/Firmware_Upgrade_Guide.pdf
4. on the machine that will have TFTP, turn off the firewall and antivirus
5. on the phones, restart and log in, change the settings to update via FTP
and restart.

Good luck.

Exactly what we did and all phones are working. For step 5 we did use SSH to change the phones to use TFTP and set the server URL, then upgrade the firmware. Good post, and short process to get things working AND supported!

 

[microsystems]

We are currently seeing this problem with a customer using gxp 2140 phones they currently are running 1.07.15 phone firmware, which worked well for us until sp3. i tried to upgrade to 1.09.58 using the 3cx facility, the never seemed to upgrade. i then set up a local tftp, set the phones to tftp firmware upgrade, and rebooted. the phones are requesting the gxp2140fw.bin from the tftp server, but when it serves the file to the phone, the phone comes back with an tftp error 6, duplicate file, and cancels the request.

we did blank the phones via factory reset, and also tried ssh to the phones interface and ran the upgrade commands. same thing.

i now have an entire company down , and we had to forward the trunks to their cell phones.

anyone have a solution to force the gxp 2140's to upgrade the firmware? not sure why they are rejecting the file. I also opened a ticket with GS, but have not heard back. We cannot charge off this time to the client, and if we cant solve today will most likely have to buy them new phones and send out installers to place and provision them. Not a big fan of automatic updates at this point.

jeff corey
3cx partner
microsystems development

 

[accentlogic]

If the phones are

We are currently seeing this problem with a customer using gxp 2140 phones they currently are running 1.07.15 phone firmware, which worked well for us until sp3. i tried to upgrade to 1.09.58 using the 3cx facility, the never seemed to upgrade. i then set up a local tftp, set the phones to tftp firmware upgrade, and rebooted. the phones are requesting the gxp2140fw.bin from the tftp server, but when it serves the file to the phone, the phone comes back with an tftp error 6, duplicate file, and cancels the request.

we did blank the phones via factory reset, and also tried ssh to the phones interface and ran the upgrade commands. same thing.

i now have an entire company down , and we had to forward the trunks to their cell phones.

anyone have a solution to force the gxp 2140's to upgrade the firmware? not sure why they are rejecting the file. I also opened a ticket with GS, but have not heard back. We cannot charge off this time to the client, and if we cant solve today will most likely have to buy them new phones and send out installers to place and provision them. Not a big fan of automatic updates at this point.

jeff corey
3cx partner
microsystems development

According to Grandstream, if the phones are on firmware 1.0.7.x and can't upgrade to 1.0.9.x directly, you will need to upgrade to 1.0.8.x first, and then upgrade to 1.0.9.x. We had this issue on several phones.

See http://www.grandstream.com/support/firmware for access to the prior version firmware.

 

[microsystems]

If the phones are


According to Grandstream, if the phones are on firmware 1.0.7.x and can't upgrade to 1.0.9.x directly, you will need to upgrade to 1.0.8.x first, and then upgrade to 1.0.9.x. We had this issue on several phones.

See http://www.grandstream.com/support/firmware for access to the prior version firmware.

Thanks, trying now....will advise......

great that 3cx engineers can help one another.

 

[Noob]

If the phones are


According to Grandstream, if the phones are on firmware 1.0.7.x and can't upgrade to 1.0.9.x directly, you will need to upgrade to 1.0.8.x first, and then upgrade to 1.0.9.x. We had this issue on several phones.

See http://www.grandstream.com/support/firmware for access to the prior version firmware.

Yes it's true, sorry, I forgot to mention this part, I had to do the same, but I thought it was written in the attachment

 

[Noob]

Once you have the re-routing done for the cell phones, instead of going to change the pass the extensions. just keep the 3CX off, when you have all the phones updated, just turn on 3cx

 

[fahillion]

I have also experienced the same issues with the GXP2130 and GXP2135 phones. However, updating them to the supported 3CX firmware did solve the issue.

I have not tried this, but I wanted to throw it out there as a possible solution for those who have hundreds of endpoints that need updating. In the 3CX Parameter Settings, there is a setting labeled: CSTA_USER_AGENTS. In this setting it lists all of the phones in this post that are having issues. I am wondering if removing those affected phone models from the list will stop the PBX from sending the CSTA messages?


I am not saying this is the supported way of getting the problem to go away, but it may be a stop-gap to allow those with a large number of phones to update their phones and then re-enable the feature once they are updated.

 

[microsystems]

Yes it's true, sorry, I forgot to mention this part, I had to do the same, but I thought it was written in the attachment

Thanks, and also my attempt to use tftp / pumpkin failed miserably on the 2140 phones, the best way to upgrade them is to put the file in the provisioniong directory and point the template / phone to upgrade from there. once all are upgraded to the 1.08xx, you can use the 3cx firmware update button to complete the upgrade to 1.09xx

 

[Noob]

I tried in many ways to update the phones by provisioning 3CX but without success, even after updating to see. 1.08xx.
Remotely by TFTP also failed, only after putting a machine on the same network with TFTP installed and shut down the machine firewall and the antivirus is that the phones were able to detect and update.
Surely now there are other ways to solve, but this way I solved my problem.
In my case there are 3 sites with about 30 phones each, it costs to start at all but it is only once.
But now that you have to update, just upload the file to the TFTP server and it will automatically update itself.

 

[microsystems]

I tried in many ways to update the phones by provisioning 3CX but without success, even after updating to see. 1.08xx.
Remotely by TFTP also failed, only after putting a machine on the same network with TFTP installed and shut down the machine firewall and the antivirus is that the phones were able to detect and update.
Surely now there are other ways to solve, but this way I solved my problem.
In my case there are 3 sites with about 30 phones each, it costs to start at all but it is only once.
But now that you have to update, just upload the file to the TFTP server and it will automatically update itself.

I feel your pain, i have lost 2 days of billable time fighting this. customer will not pay, they just want their phones working like they did last week.........

no more automatic updates for me, ever. thats why i went to ubuntu, the windows 10 pbx constantly reboots for updates in the middle of the day. not fun explaining why we ripped a perfectly good pbx off the wall to install these new phones.....

 

[fahillion]

This evening I wanted to test a temporary solution. Below are the details of what I tested. Essentially I wanted to find a way to temporarily shut off the CSTA from the 3CX to allow the phones to calm down so we could save settings, update firmware, etc... without having to shut down services or disable the extensions. Below is what we used for testing.

- GXP2135 running 1.0.9.58 3cx supported firmware with 3CX running 15.5.8801.3 (newest version).
- Phone was operating normally.
- Factory defaulted phone and downgraded to firmware 1.0.9.26.
- Manually added phone to PBX.
- Phantom ringing started almost immediately after we lowered the firmware version.
***Note: I did the above to get my phone to a state where it could be tested. You should not have to do the above if your phones are having the ringing issue. We did this to isolate and test.

What we did to temporarily resolve the issue:
1. Removed the following from the "CSTA_USER_AGENTS" parameter setting:
"GrandStream GXP2170,GrandStream GXP2160,GrandStream GXP2140,GrandStream GXP2135,GrandStream GXP2130,GrandStream GXP1760,GrandStream GXP1760W,GrandStream GXP1780,GrandStream GXP1782,GrandStream GXP1610,GrandStream GXP1615,GrandStream GXP1620,GrandStream GXP1625,GrandStream GXP1628,GrandStream GXP1630"
2. Saved the parameter.
3. Ringing stopped almost immediately.
4. Waited a very long time to see if ringing returned. It has not.

Please, note, if this works for you, it is not a recommended permanent solution. It would be meant as a stop-gap measure to get phones updated and to a supported 3CX level. The phone is working normal at this point and I imagine that it will continue working while we update, etc...

 

[Noob]

This evening I wanted to test a temporary solution. Below are the details of what I tested. Essentially I wanted to find a way to temporarily shut off the CSTA from the 3CX to allow the phones to calm down so we could save settings, update firmware, etc... without having to shut down services or disable the extensions. Below is what we used for testing.

1. GXP2135 running 1.0.9.58 3cx supported firmware with 3CX running 15.5.8801.3 (newest version).
2. Phone was operating normally.
3. Factory defaulted phone and downgraded to firmware 1.0.9.26.
4. Manually added phone to PBX.
5. Phantom ringing started almost immediately.
6. Removed the following from the "CSTA_USER_AGENTS" parameter setting:
"GrandStream GXP2170,GrandStream GXP2160,GrandStream GXP2140,GrandStream GXP2135,GrandStream GXP2130,GrandStream GXP1760,GrandStream GXP1760W,GrandStream GXP1780,GrandStream GXP1782,GrandStream GXP1610,GrandStream GXP1615,GrandStream GXP1620,GrandStream GXP1625,GrandStream GXP1628,GrandStream GXP1630"
7. Saved the parameter.
8. Ringing stopped almost immediately.
9. Waited a very long time to see if ringing returned. It has not.

Please, note, if this works for you, it is not a recommended permanent solution. It would be meant as a stop-gap measure to get phones updated and to a supported 3CX level. The phone is working normal at this point and I imagine that it will continue working while we update, etc...

The idea of disabling extensions or stopping services is not having to do a factory reset to phones so you do not have to manually set up one by one. if you can skip these steps I think you'll have less work.

3. Factory defaulted phone and downgraded to firmware 1.0.9.26.
4. Manually added phone to PBX

 

[fahillion]

Sorry about that. It was part of our testing and not part of the recommended temporary solution. I made an edit to the post. Thanks for pointing that out.

 

[microsystems]

Sorry about that. It was part of our testing and not part of the recommended temporary solution. I made an edit to the post. Thanks for pointing that out.

By the way, this is Grandstreams late response to my ticket i put in on the 14th - ( totally useless )

Hi,

Please the ticket was created on the 2/15/2018. You could have created ticket one week ago. There is no known issue for an upgrade to lockup the ip phone as you mentioned in the ticket.

Regards

Made by: ********* on February 16, 2018 10:41

We will NOT be installing any more Grandstream product. Fanvil is a better alternative with faster tech support response.

I see why 3cx dropped them initially.

 

[GS_GS_GS]

To microsystems;

What you wrote previously is misleading, it seems you name is "******" , you need to have the courage to put your own name before revealing other's personal name.

Could you put all you r comments from the ticket.

 

[microsystems]

To microsystems;

What you wrote previously is misleading, it seems you name is "******" , you need to have the courage to put your own name before revealing other's personal name.

Could you put all you r comments from the ticket.

No problem, I am Jeff Corey, the owner of Microsystems Development, a 3cx partner and GS reseller.

I sent GS support a ticket with a tftp window clearly showing the phone rejecting the 1.09xx firmware.

it was not until i reached out on this forum that it seems the phones at 1.07xx need to go to 1.08xx firmware before they will accept 1.09

THIS WAS NEVER DOCUMENTED. Take the view of our end users, hundreds of gxp 2140 endpoints, that could not use their phones for days. some are threatening legal action for loss of business.

I stand by my post and do not know how GS support can take well over a day and a half to respond, and when they do respond it bears nothing towards a solution to the problem.

please feel free to have a member of Grandstream management contact me.

regards,

jeff

 

[manfer]

Removed the following from the "CSTA_USER_AGENTS" parameter setting:
"GrandStream GXP2170,GrandStream GXP2160,GrandStream GXP2140,GrandStream GXP2135,GrandStream GXP2130,GrandStream GXP1760,GrandStream GXP1760W,GrandStream GXP1780,GrandStream GXP1782,GrandStream GXP1610,GrandStream GXP1615,GrandStream GXP1620,GrandStream GXP1625,GrandStream GXP1628,GrandStream GXP1630"

Very interesting catch in the parameters.

I'm tempted to test CSTA even with that change on the parameters. I have the impression I tested CSTA on an updated grandstream phone before upgrading to v15.5 SP3 and worked. But I can't be sure. Too many things happening to be sure I didn't upgrade the PBX before testing.

The best way I found to update the phones was just stopping SIP Service from 3CX management console. Only 2 or 3 services more are stopped but the rest of them still stay running and you can start upgrading the phones after they lost registration.

This has been a really unfortunate issue.

I'm not sure but it all indicates that grandstream phones even on firmware bellow 1.0.9.58 should had rejected those CSTA request instead of starting ringing non stop.

Unfortunaly 3CX added CSTA support without taking into account this could happen and there were not enough warning for us.

The good news in my opinion is that I'm sure grandstream phones are going to work a lot better with 3CX now that 3CX engineers test and certificate the firmwares. And when using grandstream phones with 3CX I will use those firmwares for sure. No upgrade till there is a new version in 3CX website.

 

[fahillion]

Very interesting catch in the parameters.

I'm tempted to test CSTA even with that change on the parameters. I have the impression I tested CSTA on an updated grandstream phone before upgrading to v15.5 SP3 and worked. But I can't be sure. Too many things happening to be sure I didn't upgrade the PBX before testing.

FYI, I did some further testing. I spun up a brand new 3CX machine and added a GXP2135 on 1.0.9.26 firmware. As soon as we setup the phone's account to the 3CX it started ringing. As soon as removed the parameter setting for the Grandstream phones, it stopped.

 

[accentlogic]

To reliably get all the phones updated to 1.0.9.58 you can set a TFTP server and use Putty to set the new URL and start the update.

• If the phones are on 1.0.4.x or lower, upgrade to 1.0.7.97 first.
• If phones are below 1.0.8.x then upgrade to that first, then upgrade to 1.0.9.58.
• See http://www.grandstream.com/support/firmware for details

1. Install SolarWinds free TFTP server on a local Windows machine (or your preferred TFTP solution) https://www.solarwinds.com/free-tools/free-tftp-server. Make sure TCP port 8099 and UDP port 69 are open for inbound traffic.
2. Download the needed Grandstream Firmware(s) from http://www.grandstream.com/support/firmware
3. Download the needed 3CX Grandstream firmware(s) from https://www.3cx.com/support/phone-firmwares/
4. Place the firmware bin file(s) for 1.0.7.97 in C:\TFTP-Root (or whatever your server's TFTP folder is set to)
5. Use Putty to set the protocol, URL and start the upgrade. Use the 3CX console phones tab to reveal the phone password and connect to the IP address for the phone. Then issue the following commands and press Enter after each:
   1. upgrade
   2. set TFTP
   3. set URL "ip address of TFTP server" (without the quotes)
   4. commit
   5. upgrade
   6. yes
6. After all phones are on at least 1.0.7.97 then you can replace the firmware file in C:\TFTP-Root with version 1.0.8.56. To force another update, you can reboot the phones or use Putty again with just the commands upgrade, commit, upgrade, yes.
7. After all the phones are at least on 1.0.8.56, then you can replace the firmware file in C:\TFTP-Root with the 3CX version 1.0.9.58. To force another update, you can reboot the phones or use Putty again with just the commands upgrade, commit, upgrade, yes.
8. After all the phones are on the supported 3CX firmware, you should connect again with Putty and set the phones back to the HTTP protocol and the default 3CX Provisioning URL so that future 3CX firmware updates can be installed properly from the console.
   1. upgrade
   2. set HTTP
   3. set URL "3CX provisioning URL" (without the quotes)
   4. commit
   5. exit
   6. exit

That should get you into a supported configuration with current firmware if you also switch to the default templates.

I suppose it might work if you place the older firmware files onto the 3CX server and use that instead of TFTP, but we did not test that.

If someone has a lot of phones I suppose this can even be scripted.