#Cisco ip phone ip address menu upgrade#

The SIP phone requests a firmware upgrade (Load ID file), if one was specified in the configuration file.If the SIP Phone registration process has not been provisioned before boot time, the SIP Phone downloads the default configuration file from the TFTP server.The phone contacts the TFTP server and requests its configuration file.The phone contacts the TFTP server and requests the Certificate Trust List file (only if the cluster is secured).Steps 1 to 4 are the same as SCCP Phones, refer the steps as illustrated in the figure: SCCP Phone Boot Process. SIP Phones use a different set of steps to achieve the same goal. The CUCM server sends other configurations such as DNs, softkeys and speed dials via the SCCP messages in the last phase of the registration process. It also lists the firmware version for each device model and the service URLs that each device should be using. It lists the TCP ports it should use for SCCP communication. This file contains a list of CUCM server, in order, that the phone should register with. Lets understand what is in file and what is in it ? CUCM then sends the soft-key template to the phone using SCCP messages. The phone registers with the primary CUCM server listed in its configuration file.Each phone has a customised configuration file named created by CUCM and uploaded to TFTP when the administrator creates or modifies the phone. The phone uses DHCP to learn its IP address, subnet mask, default gateway and TFTP server address.The phone learns the Voice VLAN ID via CDP from the switch.The phone loads its locally stored firmware image.SCCP phone obtains the Power (PoE or AC adaptor).This document is related to Cisco IP Phone registration process with Cisco Unified Communication Manager (CUCM). Voice implementers and operation engineers need to understand the basics of IP Phone Boot and registration process to address day to day troubleshooting and configuration issues.

#Cisco ip phone ip address menu upgrade#