My IP601 keeps booting - it loads the application, asks me to wait a few seconds while it reads the configuration, then says "Configuration error, error is 0x4020". I tried clean, new config files, booting offline (same error), and everything else I could think of - including updating to the latest bootRom and application using the firmware-polycom package.
Any help would be greatly appreciated!
It's defintely a config error, but having it continuously reboot is the challenge. I've found connecting the SoundPoint to a standalone switch with a static IP sometimes stabilizes it enough to get to an idle screen. If you can get there, you may have some hope. The next step would be to try the Reset to Defaults menu (Menu, 3, 2, admin pswd enter, 4) and Format File System. If you are able to complete this, change your Network Config parameters back to your provisioning server and attempt to load the bootrom.ld, default master config file (all-zeros.cfg, don't forget to rename your
Mitch
Mitchell,
thank you for your hint. I think it's great that somebody from Polycom actually participates in the trixbox forum and tries to resolve issues with Polycom phones. Unfortunately, it didn't work.
Judging by what other people with the same problem write on the internet, this behaviour occurs if some unfortunate glitch happens once during configuration loading, and, at least in some cases, this cannot be fixed without sending the phone to somebody who probably either knows which pins to short inside the phone to cause a complete hardware reset including flash memory or who simply attaches a device to flash the memory without the phone's cooperation.
Either way - I don't care. I thoroughly regret to have bought a Polycom phone, and I believe that either software or hardware engineering at Polycom must have missed at least one rather obvious point. I hate to imagine a company with 1000 Polycom phones, a glitch in the networking setup of this company, followed by an inoperational company because of error 0x4020.
I for one have just openend my IP601, tried to short about all jumper pins I could find, which had no effect on the phone's behaviour whatsoever. I then proceded to forcefully throw the phone into the rubbish bin at high speed, an admittedly uneconomic, but nonetheless highly satisfying action.
To those responsible for this problem: I hope your car will breakdown in the middle of the night in a remote part of a country you don't know very well, phone your car's manufacturer and be told "This is because you touched the indicator while accelerating. You car will have to go back to us to be reset - and then, make sure you don't do it again.".
Sorry for being cynic, and I am sure the problem is not Mitchell's fault. However, I have just spent the better part of two days on trying to get this phone to work.
Time to purchase another phone, I think. And no, it most definitely will not be a Polycom.
Christian
I know the Poly's can be frustrating, but your problem is almost certainly curable. I'd fish the thing out of the trash and set it aside for a little while, until you're less pissed off about it. I'm fairly sure I've seen that error code before, and still got the phone working after some struggling with it.
One thing I get a lot is that when I go in to edit a config file, nano will often insert erroneous line breaks, which will make the phone choke. (Although I think I usually get a different error.)
Read over your config files looking not for bad settings, but rather bad syntax [eg missing brackets, slashes, bad line breaks, etc.]
Unplug the phone from the network and boot it, you should be presented with a menu that will let you format the phone. You can then reattempt upload and provisioning.
IIRC, this error might have to do w/FTP problems. Make sure that you've set the correct FTP/TFTP server address, selected the correct protocol, created the neccessary accounts/directories on your server, that the MAC.cfg file uses all lower case letters in the file name, that you're not specifying any additional files that are missing, etc.
Check and see if the phone managed to upload a bootlog upon fail. That often helps.
Your FTP/TFTP logs should have useful information too.
Consider connecting the phone to the trixbox with a crossover cable, run tethereal or wireshark, and watch the conversation over the wire to see what's happening.
-DAF
InnateTech
I setup a ftp site with the configs I use you can try booting off it, if you would like.
ftp.xcsar.com
un: polycom@xcsar.com (use the * key to get the @ sign)
pw: polycom
This will change the default phone password to 1234
These files were created with the trixbox end-point manager and had a little mods done.
This will connect to my pbxes.com account where you can do a *43 echo test and also you should get a images on you screen. you can also dial any 800#'s I like to use 1800-555-tell (8355)
If you have any questions let me know.
Also If you would like to view the files or download them go to http://www.xcsar.com/polycom/
rperkins,
I don't know what magics you did (I hope I'll find out when I look at your config files in a minute though), but it certainly revived my Polycom.
I apologize for probably having done Polycom an injustice - apparently, in the boot of that car, there is a spanner which one has to through somewhere in the engine to make it come back to life.
Usually, I would assume that I made a stupid mistake in my config files - but actually, they were utterly unmodified by me and came straight out of the polycom distribution and the trixbox polycom module.
Well, it's time to find the other bits of my phone in the rubbish bin, screw the back on again, remove the odd onion skin from the receiver and try with my setup again.
Thanks a bunch - you just made a desperate guy very happy.
Christian
No problems I started out about a year ago and trial & error and 5 RMAs later I finally figured out how to fix it. If you need any more help let me know.
If anyone is interested I am wanting to start a how to config site with config add-ons and other polycom information to help all us polycom-trixbox users.
I have to give a shout out to the guys at polycom who help us out here and to the guys at the voip connection who have help threw the early day when I was a big pain in the a$$ and to Andrew $ Kerry and the rest of the trixbox team for bring us so far.
Thanks again for providing a fix for flyingcat and salvaging the SoundPoint. I've worked with many VoIP phones and prefer the SoundPoints even before working here. Like everyone else, I have those days when I encounter some strange behavior / problem, but they're far fewer headaches than before. Thanks again!
Mitch
This worked for my 430 with the same 4020 error, but how do I then added it to my system? I logged on to your site, the phone up dated and boom all was right with thte world. Now I want to add it back to my Trixbox. When I tried this I went right back to error 4020. From what I can tell from the log files the phone doesn't seem to be able to connect to the server using Tftp, which might be why it has no problem connecting to your site. The version on my server is the latest 212.0078, and I assume all is right with it. I am still new to all this, but any help would be greatly appreciated.
Thanks,
Shawn
shawnesc,
Did you solve this problem. I'm having the same issue.
After having tftp problems so many times and getting 0X0 and 0X420 errors from my polycom 301/501 phones, I decided to use solarwinds TFTP utility. This free utility is very easy to use and works on windows environment. You can download it from this link http://support.solarwinds.net/updates/MoreSoftware.cfm?Program=52
This is for people that are having problems for trixbox’s tftp and like to try alternatives.
What I did is I downloaded the above file and run/configure it. It is very easy to configure and setup.
After installation it will create tftp folder in C drive.
Then I run setup-polycom on my trixbox machine. Doing this creates some files in tftp folder.
Then moved those files from trixbox machine to my XP machine (C:\tftp) using WinCP3.
Then, I pointed my polycom phones to XP machine’s IP address. Now, Polycom phones are working since with no problem at all.
I have found that in my case the sip.cfg file was missing. I rebooted trixbox. then re-ran setup-polycom from the command line and the file was regenerated.
I got myself into this problem by upgrading the polycom firmware from the packager in the trixbox UI
Eric Plummer
Please check out my blog posting regarding a similar issue I was having, it might help, it might not.
http://dwclarknu.blogspot.com/2008/05/polycom-ip330-and-0x4020.ht...
I had the same issue with the new conference phone. I couldn't get the dang thing to flash back to original setting so I had to request a new phone. I am going to reinstall tomorrow.
So is the problem in the tftp?
I wouldn't mind switching from tftp to ftp if its going to solve the problem.
I been having some problems with this polycom soundpoint ip 601 and after seeing this post it helped me a lot in digging out some things.
I don´t know if anyone has still this problem but i share the information that i gathered:
Until the bootprom 3.00 the available protocols for provisioning in this model are TFTP and FTP, and from 3.00 and up FTP and SFTP. I used Xlight ftp server and created a virtual server, added account polycom in order to boot from the ftp server. In the phone i configured the ftp settings. The boot server the settings can be both ways either in the dhcp server ( http://www.sureteq.com/asterisk/polycom.htm ) or by the custom address in the settings on the settings pannel on the phone.
I found something interesting when using bootprom 4.00 the phone when using custom+ option 66 the phone if does not achieve to download something from the dhcp server settings should return to the custom settings or vice versa and it didn´t did that.
The directory needs to have the the .cfg file either the all zeros.cfg or the mac address .cfg .
If someone wants to use tftp of sftp bootprom one can download boot prom :version :http://www.polycom.com/usa/en/support/voice/soundpoint_ip/soundpoint_ip601.html
for the tftp testing i used plain ftp from CentOs.
Hope that this information helps someone.
Cheers,
FCosta
Trixbox 2.4CE and Polycom IP330 has been an interesting install. Here is how I got it to work. First, I installed the latest firmware and sip software from Polycom into my tftpboot directory on trixbox. However, the phone would never connect to that server via tftp during the initial install. I would always get a "cannot connect to boot server" message. So, I installed tftp32d on my windows laptop and copied all of the files in the tftpboot directory to the root directory of tftp32d and the subdirectory named tftpboot under the tftp32d directory (I was not sure which directory the phone would search for, so I put the files at boot the root and tftpboot subdir on my PC. I copied the files after I had used Endpoint Manager to create the phone cfg files.
Then I set the phone to use my local PC as the tftp server and it downloaded the files and did the initial config. And when I set the tftp server back to the trixbox server, it no longer complained about finding the boot server. As for the 0x4020, I found that I would get the error after doing all of the above while using a fixed IP address, not a dhcp assigned address. As soon as I changed the phone back to dhcp assigned, then I stopped receiving the 0x4020 message. Really whacky, but that is what I experienced while setting up the Polycom IP330 phones.
Then I set the phone to use my local PC as the tftp server and it downloaded the files
Sounds like an awful lot of trouble. For those reading this thread if you enable the DHCP server on the trixbox the phones will automatically load the software from the trixbox server.
Proper procedure:
Scott
aka "Skyking"
So the main reasons you get these two errors are
1. You are missing a file in the
2. You are missing a comma to separate the files
3. You have a typo in the file names
What happens in TB in these failed scenarios is beyond me as the TB is supposed to build a set of files when you use endpoint manager. Putting the files on a separate computer or switching from TFTP to FTP or vice versa is not going to solve the fact the phone is missing files.
Although if you manually manage files you will probably see the error before the phone does and you will have a chance to fix it.
Even if you think the files are there or correct, double check them.
I encountered this error today (it happened with 601s in a mixed network of several Polycom models) and I'd like to thank everyone for posting the troubleshooting advice. I'm using a different Asterisk-based system, so it looks like this problem doesn't just affect trixbox users.
Using the SolarWinds TFTP server on my laptop as suggested, I could see that the 601 was downloading the [MAC].cfg file and sip.ld, but it would generate the 0x4020 error before requesting any of the files in the CONFIG_FILES parameter from the TFTP server. Wiping the file system, checking the .cfg files for syntax, etc., had no effect.
In my case, the solution to the problem was to change the phone from a static IP back to DHCP - for some reason, that one change allowed the 601 to avoid the 0x4020 error and continue loading. (Our 430s are all on static IPs and did not exhibit this problem; the 601s and an IP4000 did.) Is it known whether this might be a weakness in the phones' TFTP implementation?
I'm going to play around a little bit and see if I can narrow the problem down further, now that I know how to fix this flavor; if I find anything interesting I'll post it here. Thanks again, everyone.
Member Since:
2007-07-29