Polycom SIP 3.1 manual For example, replace the reference to sip.cfg with sip650.cfg

Setting up Your System

cEdit the CONFIG_FILES attribute of the <Ethernet address>.cfg files so that it references the appropriate sipXXXX.cfg file.

For example, replace the reference to sip.cfg with sip650.cfg.

dEdit the LOG_FILE_DIRECTORY attribute of the <Ethernet address>.cfg files so that it points to the log file directory.

eEdit the CONTACT_DIRECTORY attribute of the <Ethernet address>.cfg files so that it points to the organization’s contact directory.

4.Reboot the phones by pressing the reboot multiple key combination. For more information, refer to Multiple Key Combinations on page C-10.

The bootROM and SIP application modify the APPLICATION

APP_FILE_PATH attribute of the <Ethernet address>.cfg files so that it references the appropriate sip.ld files.

For example, the reference to sip.ld is changed to 2345-11605-001.sip.ldto boot the SoundPoint IP 601 image.

Note	At this point, the phone sends a DHCP Discover packet to the DHCP server. This is
	found in the Bootstrap Protocol/option "Vendor Class Identifier" section of the
	packet and includes the phone’s part number and the bootROM version.
	For example, a SoundPoint IP 650 might send the following information:
	5EL@
	DC?5cSc52*46*(9N7*<u6=pPolycomSoundPointIP-SPIP_6502345-12600-001,1B
	R/4.0.0.0155/23-May-07 13:35BR/4.0.0.0155/23-May-07 13:35
	For more information, refer to Parsing Vendor ID Information on page C-24.

5.Monitor the boot server event log and the uploaded event log files (if permitted).

Ensure that the configuration process completed correctly. All configuration files used by the boot server are logged.

You can now instruct your users to start making calls.

3 - 17