Polycom 501 error updating bootrom
As of firmware 220.127.116.11, the Grandstreams are a decent phone, easy and quick to configure, but they have a horrible echo in the speakerphone for the remote party.A firmware fix for this was promised in October 2005, but I decided to not wait and get some Polycom 501 phones as well, as Polycom phones are legendary for being excellent speakerphones, and the 501 model was their lowest priced speakerphone model.There is good information on this site about setting up a Polycom phone to work with Asterisk, but it's rather spread out and unorganized, so I thought I'd take some time to get it all in one place.
Either way once the directory is setup then any device can be manually pointed to the directory and the phone will utilize HTTP to download and apply the firmware.
The Polycom SIP phones support a few different methods for software updates, most commonly utilizing a central FTP provisioning server so that all devices will check a single distribution point for configuration changes and new firmware images.
The previous article mentioned above contains links with more details on enterprise deployment and management practices.
At time of this writing, Grandstream GXP-2000's are around 5, and Polycom 501's are around 0.
The Polycom 501's do have more and easier-to-get-to functionality than the GXP-2000's, and have a more professional look and feel (and a great speakerphone), but the most notable downsides of the 501 are its awful, obtuse and slow configuration interfaces.
As of the writing of this article the Lync specific firmware release is not yet included on the Polycom Hosted Server, so primarily Open SIP only firmware releases will be available using this method.