The phone’s configuration files are loaded from a TFTP server at power-on. If DHCP is enabled on the handset the DHCP service option 66 must provide the IP address of the TFTP server. This is consistent with Polycom’s established provisioning process for the SoundPoint SIP desk phones. If DHCP is disabled, then all the network parameters, including the IP of the TFTP server, must be manually entered into the handset.
Once the TFTP server is contacted, the phone prompts for a username and password. Based on the username entered, the phone then downloads the associated configuration files. The configuration files are not stored locally on the phone. This is handy, as it allows the phone to be passed from user-to-user, assuming that individuals login when they switch phones so that the handset has the user’s proper extension number.
The core configuration is a two-part system with a file that is common to all handsets on the system (sip_allusers.cfg) and a user-specific file (ex. sip_1505.cfg).
The major benefit of this provisioning scheme is scalability and easy administration. With central provisioning it’s a simple matter to add or remove users, or push a new firmware release to an entire fleet of handsets.
The documentation provided with the phone gives comprehensive, notated examples of the config files. In my case the settings were very simple.
CODECS = g711u, g711a
PROXY1_ADDR = 192.168.1.200:5060
PROXY1_MAIL_ACCESS = 7999
PROXY1_KEYPRESS_2833 = disable
PROXY1_KEYPRESS_INFO = enable
PROXY1_HOLD_IP0 = disable
AUTH = 1505; 1505
LINE1 = 1505
LINE1_PROXY = 1
LINE1_CALLID = Sip Phone 1505
The phone supports up to five “lines” where each line is a separate SIP registration. A SIP registration may also be entered multiple times allowing for multiple simultaneous call appearances on that line. Each user profile can also contain a list of “favorites” that are effectively speed-dials for that user.