Chapter 2 Preparing to Install the Cisco Unified IP Phone on Your Network

Understanding the Phone Startup Process

For more information about how the phone interacts with the TFTP server, refer to the Cisco Unified CallManager System Guide, “Cisco TFTP” chapter.

The TFTP server generates these SIP configuration files:

SIP IP Phone:

For unsigned and unencrypted files—SEP<mac>.cnf.xml

For signed files—SEP<mac>.cnf.xml.sgn

For signed and encrypted files—SEP<mac>.cnf.xml.enc.sgn

Dial Plan—<dialplan>.xml

Softkey Template—<softkey_template>.xml

The filenames are derived from the MAC Address and Description fields in the Phone Configuration window of Cisco Unified CallManager Administration and the devicename field in the Cisco Unified CallManager database. The MAC address uniquely identifies the phone. For more information refer to the Cisco Unified CallManager Administration Guide.

SIP Dial Rules

For Cisco SIP Unified IP phones, the administrator uses dial rules to configure SIP phone dial plans. These dial plans must be associated with a SIP phone device to enable dial plans to be sent to the configuration file. If the administrator does not configure a SIP phone dial plan, the phone does not display any indication of a dial plan.

For more information on configuring SIP dial rules, refer to the Cisco Unified CallManager Administration Guide.

Understanding the Phone Startup Process

When connecting to the VoIP network, the Cisco Unified IP Phone goes through a standard startup process, as described in Table 2-4. Depending on your specific network configuration, not all of these steps may occur on your

Cisco Unified IP Phone.

Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager 5.1 (SIP), Cisco Unified IP Phones

 

OL-11524-01

2-9

 

Page 73
Image 73
Cisco Systems 7970G manual Understanding the Phone Startup Process, SIP Dial Rules