Firmware upgrade problem.
Submitted by ah_clem on Sat, 04/19/2008 - 1:14am.
Maybe it's a lack of knowledge on my part, but I can't seem to get firmware to upgrade on my GSX2000. Right now it's behavior is such that every few minutes it shows the "TFTP Provisioning" screen that shows it's trying to download boot55d.bin. This began when I entered the PBX's IP address in the Firmware and Config Server Path on the phone. The screen displays the download message for 30 seconds or so then nothing else happens until the regular screen appears. I check the status page and it shows no change in the boot (1.1.4.6) or firmware (1.1.4.18) versions. I've tried installing the firmware using both a local tftp server implementation on the PBX machine, and via the Grandstream update IP of 168.75.215.189. Both behave the same way... This is my first time through the firmware upgrade process, so I don't even know what to expect as far as the progression on the display that would indicate something "good' has happened.
I guess my first question is which version is recommended at this point?
Also, do these firmware updates need to be done "in baby steps", in other words do you have to do each and every released version, or can you load the latest and be up to date? Say in my case going from 1.1.4.18 to 1.1.6.16, what if any intermediate versions do I need to load?
I've noticed that my download of 1.1.6.16 doesn't seem to have all the boot55x.bin files, with the boot55.bin - boot55c.bin not being included in the zip from Grandstream's site. This leaves me wondering how this upgrade process works...
Any clues appreciated...
Thanx in advance...
This can't be good...
Sat, 04/19/2008 - 12:34pm
Well I think I'm now the proud owner of a Grandstream GSX2000 paperweight. After working with the tftp server I was able to get part of the upgrade done, my boot firmware seemed to change versions, but I was till getting the same problem above. After trying a number of things I'm now at a place where when the phone is power-cycled I see "tftp recovery started" then "downloading application" and after several seconds I get "application image checksum fail". That's about all she wrote...
If you are getting that
Sat, 04/19/2008 - 1:00pm
If you are getting that information on the LCD then I doubt you have bricked your phone.
tail the tftp log on the server (tail /var/log/atftpd.log -f) and watch and see what image it is trying to get.
Then make sure letter for letter, case counts that file exists in /tftpboot
Nothing new in tftp log file.
Sat, 04/19/2008 - 11:03pm
As suggested I checked the tftp log file and though there are a couple of older entries there's nothing current. xinetd is running, and given it worked several hours ago I'd assume it work now...
I looked in the end point manager and I do see the phone listed there. I've checked the Grandstream_GSX2000_default.txt file and the firmware and config servers IP addresses are correct.
Any other suggestions on how to proceed? I could sure use some good news right now...
Thanx.
Here's what I'd look at.
Mon, 04/21/2008 - 2:21pm
1. Is the tftp server set up correctly? If you've changed the IP address of the TRIXBOX server since you set it up, the tftp server will be confused. If it didn't install correctly, it will be confused.
Log into the command line of the trixbox (either locally, or SSH) and type
setup-grandstream
and then reboot, for good measure.
2. Is the phone pointing at that server? Use your web browser and log into the phone using admin rights. The IP address of the tftp server should be loaded as below: This is what my phones are set up as...
Firmware Upgrade and
Provisioning: Upgrade Via x TFTP HTTP
Firmware Server Path: 192.168.1.3
Config Server Path:
Firmware File Prefix:
Firmware File Postfix:
Config File Prefix:
Config File Postfix:
Allow DHCP Option 66 to override server:
x No Yes
Automatic Upgrade:
No x Yes, check for upgrade every 1440 minutes (default 7 days)
x Always Check for New Firmware
Check New Firmware only when F/W pre/suffix changes
Always Skip the Firmware Check
Authenticate Conf File:
x No Yes (cfg file would be authenticated before acceptance if set to Yes)
reboot the phone and you should be in business.
FWIW, the 1.1.6.16 software is GREAT, and has been VERY stable.
Enjoy,
Mark
Thanks but...
Thu, 04/24/2008 - 9:04am
Though the IP of the pbx has not changed, I had run setup-grandstream prior just in case.
I cannot log into the phone from a web browser because it does not appear on the network, I think it's to early in the boot sequence to allow that to happen. I do see the MAC address under the End Point Manager, and if I click on that and submit the changes I see the cfg
I've also tried deleting the cfg file, changing the Grandstream_GXP2000_Default.txt file so that it points to either the local PBX, or any number of alleged Grandstream IP addresses or domain names/paths. So far I've seen 168.75.215.188 and 189, and fm.grandstream.com/gs. After making changes to the default text file, I move the existing cfg file and go back into the End Point Manager and have it recreate the cfg file, thinking that it should use the default.txt file as a starting point. Though at times it seems that it takes longer to get the "application image checksum fail" message, it still appears each time.
One of my questions relates to tftpboot functionality. Does the tftpboot process use port 21 as per standard ftp, or does it use a different port? I'm wondering if my firewall is getting in the way and blocking outside communications when I try to upgrade from Grandstream.
Also I have not been able to find any discussions on what all the firmware files are for, whether they're all needed, or anything about how the heck this process works at a lower level. As a for instance, I see there are files named "boot55.bin boot55a.bin boot55b.bin" etc. but I also see that the 1.1.6.16 load of firmware only contains "boot55c, d, and e." files. So does that mean that the prior files (boot55.bin through boot55b.bin) are not needed?
Thanks for any and all help on this...
ah_clem: a/b/c/d represent
Mon, 04/28/2008 - 2:44pm
ah_clem: a/b/c/d represent different stage of firmware version, if you use earlier firmware such as 1.1.1.14, you need all of them to be in, which are already in the firmware release 1.1.6.16. You need to unzip it and put ALL of them into the firmware server TFTP root path in order to upgrade them. It might take a little while for it to upgrade the unit.
Member Since:
2007-09-16