Cisco 7960G Administrator's Manual page 37
Sip
Hide thumbs
Also See for 7960G:
- Administration manual (184 pages) ,
- User manual (122 pages) ,
- Phone manual (74 pages)
Table of Contents
Advertisement
Chapter 3
Initializing Cisco SIP IP Phones
2.
The phone learns its VLAN membership.
If the phone is connected to a Cisco Catalyst switch, the switch notifies the phone of the voice
VLAN defined on the switch. The phone needs to know its VLAN membership before it can send a
DHCP request for its IP settings (if using DHCP).
3.
The phone acquires its IP address.
If the phone uses DHCP to obtain IP settings, it queries the DHCP server. Otherwise, it uses IP
settings that are stored in flash memory.
The phone contacts the TFTP server and downloads the following files (or uses settings that are
4.
stored in its flash memory):
•
•
•
Note
•
•
•
•
Note
Refer to the
5.
The phone verifies the firmware version.
If the phone determines that the image defined in a configuration file differs from the image that it
has stored in flash memory, it performs a firmware upgrade. During upgrade, the phone downloads
the firmware image from the TFTP server, programs the image into flash memory, and reboots.
SEP<macaddress>.cnf.xml—Creates the filename SEP<macaddress>.cnf.xml on the TFTP
server into which you can place one of the following:
<device>
<loadInformation>P0S3-07-3-00</loadInformation>
</device>
The phone then checks the load information and either upgrades the phone firmware in FLASH
memory to the version stated in the <LoadInformation> tag using the TFTP loader in the
Universal Application Loader, or, if the version matches, exits the Universal Application Loader
and executes the firmware already loaded in FLASH memory.
<firmware-version>.loads—If the version matches, enables the phone to exit the Universal
Application Loader and executes the firmware already loaded in FLASH memory, as defined in
SEP<macaddress>.cnf.xml.
OS79XX.TXT—Enables the phone to initialize and automatically determine the network in
which it is being installed.
The use of dual boot file OS79XX.TXT is deprecated in favor of individual XML configuration
files for the phone using their SEP<macaddress>.cnf.xml style names. This allows
Cisco CallManager and SIP-based configurations to share a common TFTP server, as the XML
configuration is phone-specific and allows indivbidual phones to be switched between SIP,
SCCP, or MGCP images.
SIPDefault.cnf—Contains parameters intended for all phones. For information on customizing
the file, see the
"How to Customize the Default Configuration File" section on page
SIP<mac-addr>.cnf—Contains parameters specific to a phone. Use this file as a template from
which to create a file for each phone. Insert the MAC address of the phone in the filename.
RINGLIST.DAT—Lists audio files that are the custom-ring-type options for the phones. The
files must be in the root directory of the TFTP server.
dialplan.xml—Contains the North American sample dial plan. You can push the file down to the
phones with a notify (NTFY) message with a check-sync Event header.
Cisco 7940 and 7960 IP Phones Firmware Upgrade Matrix
Cisco SIP IP Phone Administrator Guide, Release 6.x and 7.x
Overview of the Initialization Process
3-5.
for additional information.
3-3
Advertisement
Table of Contents
