Page 120 - Asterisk™: The Future of Telephony
P. 120

The application image.  Since Polycom sets are capable of supporting other VoIP protocols
               (MGCP is supported, for example), the protocol that this set will employ forms part of
               the application image that the phone will download and run. If the image on the set is
               already correct, this file is not actually needed on the FTP server; however, it is common
               to have this file available to ensure that the most recent version of the protocol is avail-
               able for the sets to download. You will sometimes receive phones that are not running
               the latest version, so having the most current image will ensure that all sets are up-to-
               date.
               The sip.cfg file.  There is normally only one version of this file on a system, but it can be
               named anything you want, and there can be as many different versions of this file as
               are needed. For example, if you had an office where there were two different languages
               in use, some users might prefer French on their set, and others English. In that case,
               you’d create a french.sip.conf file and an english.sip.conf file to handle each case. Name
               this file as you see fit, but pick a name that makes sense so that future administrators
               have a chance to make sense of your design choices.
               The master config file for each phone.  This file is very simple and small. It is named to match
               the MAC address of each phone (so each set will need its own copy of this file) and tells
               the set what other files it needs to download in order to configure itself. This is the first
               config file each set will read. In this file will be a reference to the application image this
               set will use (currently named sip.ld), as well as the names of the XML files that have the
               parameters for this phone (the .cfg files). A master config file for a set might look some-
               thing like this:
                   '<?xml version="1.0" standalone="yes"?>'
                   '<!-- Default Master SIP Configuration File-->'
                   '<!-- Edit and rename this file to <Ethernet-address>.cfg for each phone.-->'
                   '<!-- $Revision: 1.14 $  $Date: 2005/07/27 18:43:30 $ -->'
                   '<APPLICATION APP_FILE_PATH="sip.ld"
                     CONFIG_FILES="phone1.cfg, sip.cfg"
                     MISC_FILES=""
                     LOG_FILE_DIRECTORY=""
                     OVERRIDES_DIRECTORY=""
                     CONTACTS_DIRECTORY=""
                   />'
               Note the name of the application file that we want this set to use, and the config files
               that it will be trying to find and apply.
               The set-specific config file.  We  recommend  giving  the  phone1.cfg  files  names  that  make
               sense. For example, SET<xxx>.cfg (such as SET201.cfg) to match the extension num-
               ber of the phone, or FLOOR4CUBE23.cfg, or maybe BOB_SMITHS_IP430_SET.cfg,
               or whatever seems best to you. What’s the best way to name them? We’re going to
               answer that question by asking a question. Let’s say you have 100 of these phones.
               When you list the contents of the /home/PlcmSpIp folder, how do you want the 100
               config files for the sets to appear?





               92 | Chapter 4: Initial Configuration of Asterisk
   115   116   117   118   119   120   121   122   123   124   125