Polycom 501 error updating bootrom

These SIP extension setup instructions are pretty standard: In extensions.conf, add a SIP extension as normal.

I use the built-in Asterisk macros for mine: [internal] ; Use your applicable context name (default, internal, etc.)exten = 510,1, Macro(extensions, Sip/510,510); The above creates SIP extension 510 with the usual voicemail features In sip.conf, I use a standard SIP phone setup: [510] ; Extension 510type=friendsecret=polycom ; Password for the extensioncontext=internal ; Use the applicable context from extensions.confhost=dynamicmailbox=510callerid=Firstname Lastname 1234, Firstname Lastname,[email protected], get the latest firmware available and flash it via TFTP or FTP (FTP is strongly suggested, TFTP can be a royal pain).

In the instructions below, TFTP is only really used to push out the firmware updates.

About the Polycom 501 If you’re reading this to see how good certain phones are with Asterisk, let me tell you that the Polycom 501 has excellent features, but is a pain to configure and very tempermental.

As you probably already know, Polycom is very protective when it comes down to getting their SIP updates and BOOTROM updates.

They will only allow CERTIFIED resellers to download their updates and they’re supposed to provide you with those updates.

Instead of setting these phones up by hand they should ALL be setup via files on the the FTP server.These instructions apply to the 501 models, but I believe they would adapt well to other Polycom models.I also don’t go into pushing out configurations from XML files on a TFTP server, but it may be the way to go if you’re doing more than one phone.Proceeding to the configuration: these instructions were made with Asterisk 1.0.9, Polycom Boot ROM 2.6.2 and SIP software version 1.5.2.For starters, might as well get the extension configured in Asterisk.

Leave a Reply