How to configure a Polycom SoundPoint IP phone for Asterisk on Fedora 10

In my opinion the best IP business phones on the market are made by Polycom. Anyone that knows anything about the VoIP Industry knows that!  High quality Polycom desk phones combined with Asterisk are a great combination of quality/price. So to that end we’re doing this lab.

Polycom employs several methods of provisioning the SIP phones.  For general configuration Sound Point IP have an excellent built web GUI,  but for multiple phones Polycom has an XML based system as well.  Every Sound Point IP can be provisioned based on MAC address.  Polycom’s provisioning method makes use of TFTP, FTP, or HTTP to deliver firmware updates and individual phone settings.

The goals of this post:

– Configure FTP server for Polycom firmware and configuration

– Configure Asterisk SIP extension

– deploy firmware and XML configuration files to Polycom SoundPoint IP 501 SIP phone



Fedora, Asterisk, Polycom and making dhcp option 66

My main job at work is to build, configure, maintain, etc… Asterisk phone systems.  Every phone system needs phones and the most popular VoIP phones for Asterisk are the Polycom Soundpoint IP SIP phones.  One of the great features of the SoundPoint IP series is the ability to easily manage a large number of phones by storing their configuration files on a central FTP server.  In this article:

1) I briefly explain the Polycom Soundpoint IP series FTP boot process(not a tutorial).

2) provide a basic example of a dhcpd.conf that supplies FTP credentials for the Polycom phones via DHCP.

The Polycom phone boots up and attempts to retrieve it’s configuration file and check for firmware updates.  The ftp username and password are entered during the first boot of the phone.  For a small number of phones this is fine, but Polycom Soundpoint IP phones have the built-in ‘option 66’ for easily deploying an unlimited number of phones.

Option 66 is a term used by some DHCP vendors to describe DHCP code 66.  This option code(when set) supplies a TFTP boot server address to the DHCP client to boot from.  In our case we’re talking about VoIP phones, but option 66 is probably most commonly used by citrix thin clients.

There isn’t much out there on how to configure option 66 with standard Linux DHCP server.  After googling for a while, I decided to install gdhcpd.  It’s a simple DHCP configuration tool that is easy to use.  I generated a simple configuration using the tool then added options I read about in the man file.  Trust me… read man files.  A wealth of info without the need to forum hop.

[matt@mattcom1 Desktop]$ man dhcpd.conf

[matt@mattcom1 Desktop]$ man dhcp-options


ddns-update-style none;
ddns-updates off;
option T150 code 150 = string;
deny client-updates;
one-lease-per-client false;
allow bootp;

# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#   see ‘man 5 dhcpd.conf’

subnet netmask {
interface eth0;
default-lease-time 6000;
max-lease-time 7200;
option subnet-mask;
option time-offset -28800;
option tftp-server-name “ftp://polycom:password@”;
option ntp-servers pool.ntp.org;
option domain-name-servers;


Change the subnet,range, and netmask to your taste!  Then restart the dhcp daemon.

[matt@mattcom1 Desktop]$ service dhcpd restart