Chapter 2 Preparing to Install the Cisco Unified IP Phone on Your Network
Understanding the Phone Startup Process
Table | Cisco Unified IP Phone Startup Process (continued) |
|
| |
|
|
|
| |
Step |
| Description | Related Topics | |
|
|
|
| |
7. Requesting the | The TFTP server has configuration files, which | • | Adding Phones to | |
Configuration File | define parameters for connecting to Cisco |
| the Cisco | |
|
| Unified Communications Manager and other |
| Unified Communic |
|
| information for the phone. |
| ations Manager |
|
|
|
| Database, |
|
|
|
| page |
|
|
| • | Resolving Startup |
|
|
|
| Problems, |
|
|
|
| page |
|
|
|
| |
8. Contacting Cisco | The configuration file defines how the Cisco | • | Resolving Startup | |
Unified Communicatio | Unified IP Phone communicates with Cisco |
| Problems, | |
ns Manager |
| Unified Communications Manager and provides a |
| page |
|
| phone with its load ID. After obtaining the file |
|
|
|
| from the TFTP server, the phone attempts to make |
|
|
|
| a connection to the highest priority Cisco |
|
|
|
| Unified Communications Manager on the list. If |
|
|
|
| security is implemented, the phone makes a TLS |
|
|
|
| connection. Otherwise, it makes a |
|
|
|
| connection. |
|
|
|
| If the phone was manually added to the database, |
|
|
|
| Cisco Unified Communications Manager |
|
|
|
| identifies the phone. If the phone was not |
|
|
|
| manually added to the database and |
|
|
|
|
|
| |
|
| Unified Communications Manager, the phone |
|
|
|
| attempts to |
|
|
|
| Unified Communications Manager database. |
|
|
|
| Note |
|
|
|
| security is enabled on Cisco Unified |
|
|
|
| Communications Manager. In this case, |
|
|
|
| the phone must be manually added to the |
|
|
|
| Cisco Unified Communications Manager |
|
|
|
| database. |
|
|
|
|
|
|
|
|
| Cisco Unified IP Phone | |
|
| ||
|
| ||
|
|