- Understanding the Theory of Voice VLANs
- Configuring Voice VLANs
- Power over Ethernet
- Essential Network Services: DHCP and NTP
- Understanding the Phone Bootup Process
- Installing Cisco IP Phone Firmware and XML Configuration Files
- Exam Prep Questions
- Answers to Exam Prep Questions
- Suggested Reading and Resources
Installing Cisco IP Phone Firmware and XML Configuration Files
Certain files are necessary for the proper operation of a Cisco IP phone or analog device so that it can register successfully with a Cisco Unified Communications call control device. These files are not installed on the Cisco router and must be installed from an external source. The file types are as follows:
- Firmware: The firmware is loaded into flash memory on the IP phone and can survive a reboot.
- SEPAAAABBBBCCCC.cnf.xml: This XML configuration file is specific to one device, and the AAAABBBBCCCC part of the name is the MAC address of the device.
- XMLDefault.cnf.xml: This XML configuration file specifies the proper firmware and the call agent's address and port, which the new phone needs to register.
The following sections describe each file type in greater detail.
Firmware
Install the firmware required by the Cisco IP phones in the flash memory of the Cisco Unified Communications Manager Express systems. There are two commands required to provide access to these firmware files:
- tftp-server flash:firmware-file-name: Use this global command to make the file available.
- load phone-type firmware-file: Use this telephony-service command to associate a type of phone with a firmware file.
All the necessary firmware files for Cisco IP phones are stored internally in the flash memory of the Cisco Unified Communications Manager Express router, so an external database or file server is not required. During registration, Cisco IP phones use TFTP to download firmware files from the router's flash memory. All Cisco Unified Communications Manager Express configuration and language files are located in the memory of the router in the system:/its/ directory.
To make the firmware file(s) available through a TFTP server, use the tftp-server flash:firmware-file-name(s) command on the Cisco Unified Communications Manager Express router. The load phone-type firmware-file command under telephony service is also required to associate the model of IP phone with the appropriate firmware file(s).
For Cisco Unified Communications Manager, the firmware files are installed on the server(s) in the cluster that run the TFTP service.
Device Configuration XML File
The XML file SEPAAAABBBBCCCC.cnf.xml (where AAAABBBBCCCC is the MAC address of the IP phone) contains the call agent IP address and port, firmware, locale, directory URL, and many other pieces of information. This file is present when the IP phone has been added to the configuration.
Listing 7.8 shows a configuration file that contains the phone model (7931), IP address (10.6.150.1), and port (2000) for registering; the firmware filename; the language (English United States); and additional information for proper IP phone operation.
Listing 7.8. SEPAAAABBBBCCCC.cnf.xml File (AAAABBBBCCCC = the MAC Address)
<device> <versionStamp>{7931 Aug 06 2008 14:23:48}</versionStamp> <devicePool> <dateTimeSetting> <dateTemplate>M/D/YA</dateTemplate> <timeZone>Eastern Standard/Daylight Time</timeZone> </dateTimeSetting> <callManagerGroup> <members> <member priority="0"> <callManager> <ports> <ethernetPhonePort>2000</ethernetPhonePort> </ports> <processNodeName>10.6.150.1</processNodeName> </callManager> </member> </members> </callManagerGroup> </devicePool> <commonProfile> <callLogBlfEnabled>3</callLogBlfEnabled> </commonProfile> <loadInformation>SCCP31.8-3-3S</loadInformation> <userLocale> <name>English_United_States</name> <langCode>en</langCode> </userLocale> <networkLocale>United_States</networkLocale> <networkLocaleInfo> <name>United_States</name> </networkLocaleInfo> <idleTimeout>0</idleTimeout> <authenticationURL>http://10.6.4.2/voiceview/authentication/authenticate.do </authenticationURL> <directoryURL>http://10.6.150.1:80/localdirectory</directoryURL> <idleURL></idleURL> <informationURL></informationURL> <messagesURL></messagesURL> <proxyServerURL></proxyServerURL> <servicesURL>http://10.6.150.1:80/CMEserverForPhone/serviceurl</servicesURL> <capfAuthMode>0</capfAuthMode> <capfList> <capf> <phonePort>3804</phonePort> <processNodeName></processNodeName> </capf> </capfList> <deviceSecurityMode>1</deviceSecurityMode> </device>
Default XML File
IP phones and devices that do not find the more specific SEPAAAABBBBCCCC.cnf.xml file can use the XMLDefault.cnf.xml file if they have never registered before and an autoregistration method has been enabled. IP phones that download this XML file through TFTP learn the IP address and port to send Skinny Client Control Protocol (SCCP) messages to when attempting to register. The IP phones also learn the version of firmware that is required to function properly with the Cisco Unified Communications call control product to which the phone is registering. Cisco IP phone models 7931 and 7961 are highlighted.
Listing 7.9 shows a default configuration file.
Listing 7.9. XMLDefault.cnf.xml File
<Default> <callManagerGroup> <members> <member priority="0"> <callManager> <ports> <ethernetPhonePort>2000</ethernetPhonePort> </ports> <processNodeName>10.6.150.1</processNodeName> </callManager> </member> </members> </callManagerGroup> <loadInformation124 model="Cisco IP Phone 7914 14-Button Line Expansion Module"></loadInformation124> <loadInformation227 model="Cisco IP Phone 7915 12-Button Line Expansion Module"></loadInformation227> <loadInformation228 model="Cisco IP Phone 7915 24-Button Line Expansion Module"></loadInformation228> <loadInformation229 model="Cisco IP Phone 7916 12-Button Line Expansion Module"></loadInformation229> <loadInformation230 model="Cisco IP Phone 7916 24-Button Line Expansion Module"></loadInformation230> <loadInformation30008 model="Cisco IP Phone 7902"></loadInformation30008> <loadInformation20000 model="Cisco IP Phone 7905"></loadInformation20000> <loadInformation369 model="Cisco IP Phone 7906"></loadInformation369> <loadInformation6 model="Cisco IP Phone 7910"></loadInformation6> <loadInformation307 model="Cisco IP Phone 7911"></loadInformation307> <loadInformation30007 model="Cisco IP Phone 7912"></loadInformation30007> <loadInformation30002 model="Cisco IP Phone 7920"></loadInformation30002> <loadInformation365 model="Cisco IP Phone 7921"></loadInformation365> <loadInformation348 model="Cisco IP Phone 7931">SCCP31.8-3-3S</loadInformation348> <loadInformation9 model="Cisco IP Conference Station 7935"></loadInformation9> <loadInformation30019 model="Cisco IP Phone 7936"></loadInformation30019> <loadInformation431 model="Cisco IP Conference Station 7937"></loadInformation431> <loadInformation8 model="Cisco IP Phone 7940"></loadInformation8> <loadInformation115 model="Cisco IP Phone 7941"></loadInformation115> <loadInformation309 model="Cisco IP Phone 7941GE"></loadInformation309> <loadInformation434 model="Cisco IP Phone 7942"></loadInformation434> <loadInformation435 model="Cisco IP Phone 7945"></loadInformation435> <loadInformation7 model="Cisco IP Phone 7960"></loadInformation7> <loadInformation30018 model="Cisco IP Phone 7961">SCCP41.8-3-3S</loadInformation30018> <loadInformation308 model="Cisco IP Phone 7961GE"></loadInformation308> <loadInformation404 model="Cisco IP Phone 7962"></loadInformation404> <loadInformation436 model="Cisco IP Phone 7965"></loadInformation436> <loadInformation30006 model="Cisco IP Phone 7970"></loadInformation30006> <loadInformation119 model="Cisco IP Phone 7971"></loadInformation119> <loadInformation437 model="Cisco IP Phone 7975"></loadInformation437> <loadInformation302 model="Cisco IP Phone 7985"></loadInformation302> </Default>