Sorry, I’m not a super-frequent poster. I used to be a developer, but now I’m a lawyer.
As for the use of FTP, my post above shows how to do that. See the dhcp.conf line that starts with “tftp”.
As for allocating IP addresses out of a pool, I really meant what I said. Have a look at the dhcp.conf I posted. Then add the “range” directive exactly as I indicated in my later post.
I don’t use .cfg. Instead, I used 000000000000.cfg, which is used by all phones. I’m posting mine here. There is documentation on the polycom website about how this works. It’s pretty involved.
<?xml version="1.0" standalone="yes"?>
<!-- Default Master SIP Configuration File-->
<!-- For information on configuring Polycom VoIP phones please refer to the -->
<!-- Configuration File Management white paper available from: -->
<!-- http://www.polycom.com/common/documents/whitepapers/configuration_file_management_on_soundpoint_ip_phones.pdf -->
<!-- $RCSfile: 000000000000.cfg,v $ $Revision: 1.19.2.1 $ -->
<APPLICATION APP_FILE_PATH="sip.ld" CONFIG_FILES="phone-[PHONE_MAC_ADDRESS].cfg, local.phone.cfg, local.sip_330.cfg, local.sip.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="logs" OVERRIDES_DIRECTORY="overrides" CONTACTS_DIRECTORY="contacts" LICENSE_DIRECTORY="">
<!-- Not using these
<APPLICATION_SPIP300 APP_FILE_PATH_SPIP300="sip_213.ld" CONFIG_FILES_SPIP300="phone1_213.cfg, sip_213.cfg"/>
<APPLICATION_SPIP301 APP_FILE_PATH_SPIP301="sip_316.ld" CONFIG_FILES_SPIP301="phone1_316.cfg, sip_316.cfg"/>
<APPLICATION_SPIP430 APP_FILE_PATH_SPIP430="sip_323.ld" CONFIG_FILES_SPIP430="phone1_323.cfg, sip_323.cfg"/>
<APPLICATION_SPIP500 APP_FILE_PATH_SPIP500="sip_213.ld" CONFIG_FILES_SPIP500="phone1_213.cfg, sip_213.cfg"/>
-->
<APPLICATION_SPIP501 APP_FILE_PATH_SPIP501="sip_316.ld" CONFIG_FILES_SPIP501="phone-[PHONE_MAC_ADDRESS].cfg, local.phone501.cfg, local.phone.cfg, phone1_316.cfg, local.sip_316.cfg, local.sip.cfg, sip_316.cfg" />
<!-- Not using these
<APPLICATION_SPIP600 APP_FILE_PATH_SPIP600="sip_316.ld" CONFIG_FILES_SPIP600="phone1_316.cfg, sip_316.cfg" />
<APPLICATION_SPIP601 APP_FILE_PATH_SPIP601="sip_316.ld" CONFIG_FILES_SPIP601="phone1_316.cfg, sip_316.cfg" />
<APPLICATION_SSIP4000 APP_FILE_PATH_SSIP4000="sip_316.ld" CONFIG_FILES_SSIP4000="phone1_316.cfg, sip_316.cfg" />
-->
</APPLICATION>
You’ll notice that different phones use different configuration files. I have commented out those phones that I do not use, leaving two generations of phones that I current use: the 501’s and everything else. The 501’s cannot use the latest software, hence the use of sip_316.ld instead of sip.ld, which is the latest stuff. Also, the 501’s must have all configuration included in at least one of the .cfg files, whereas the newer phones only need the exceptions from the default. This is why the configuration for the newer phones only uses the “local” config files (which I created) whereas the 501’s need the polycom-supplied config files with everything in them. The hierarchy of config files is my own design. It could certainly be simplified in some environments.
This isn’t simple stuff. It requires time-consuming, careful study of the documentation and a bunch of trial and error. It’s worth starting very simple and slowly adding functionality.