Polycom stuck on updating initial configuration
The GXP-2000’s are much more resilient and much faster to boot.
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.
The relevant options for Asterisk configuration are buried fairly deep on the console, and the big problem with the web interface is that it takes at least an extra minute to become available even AFTER the phone is up and running.
And, of course, every time you make ANY change in ANY section of the web interface and click “Submit,” it has to do a soft boot….. It makes the XML/TFTP configuration option look pretty good, even for just a few phones.
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:  ; 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).
As you probably already know, Polycom is very protective when it comes down to getting their SIP updates and BOOTROM updates.