cme load phone firmware and configs

michael murphy — Sun, 04 Jul 2021 07:35:27 GMT

what is the difference or purpose of the CME # LOAD command and the #create cnf-files? They both seem to create config files for the phone to download.

cme load phone firmware and configs

aqjaved — Tue, 20 Aug 2013 17:31:27 GMT

Load (telephony-service)

To associate a type of Cisco Unified IP phone with a phone firmware file, use the load command in telephony-service configuration mode. To disassociate a type of phone from a phone firmware file, use the no form of this command.

load phone-type firmware-file

no load phone-type

Syntax Description

phone-type

Type of phone. The following phone types are predefined in the system:

•6945—Cisco Unified IP Phone 6945.

•7902—Cisco Unified IP Phone 7902G.

•7905—Cisco Unified IP Phone 7905G.

•7910—Cisco Unified IP Phone 7910 and 7910G.

•7911—Cisco Unified IP Phone 7911G.

•7912—Cisco Unified IP Phone 7912G.

•7914—Cisco Unified IP Phone 7914 Expansion Module.

•7920—Cisco Unified Wireless IP Phone 7920.

•7921—Cisco Unified Wireless IP Phone 7921.

•7931—Cisco Unified IP Phone 7931G.

•7935—Cisco Unified IP Conference Station 7935.

•7936—Cisco Unified IP Conference Station 7936.

•Note You can also add a new phone type to your configuration by using the ephone-type command.

firmware-file

Filename of the IP phone firmware for a particular phone type.

•In Cisco Unified CME 7.0/4.3 and earlier versions, do not use the file suffix (.bin, .sbin, .loads) for any phone type except the Cisco ATA and Cisco Unified IP Phone 7905 and 7912.

•In Cisco Unified CME 7.0(1) and later versions, you must use the complete filename, including the file suffix, for phone firmware versions later than version 8-2-2 for all phone types.

•Filenames are case sensitive.

Command Default

Firmware files are not associated with phone types.

Command Modes

Telephony-service configuration (config-telephony)

Usage Guidelines

This command updates the Cisco Unified CME configuration file for the specified type of Cisco Unified IP phone to add the name of the firmware file to be loaded by a particular phone type. The firmware filename also provides the version number for the phone firmware that is in the file. When a phone is started up or rebooted, the phone reads the configuration file to determine which firmware file it must load and then looks for that firmware file on the TFTP server.

A separate load command is needed for each type of phone. The Cisco Unified IP Phones 7940 and 7940G and the Cisco Unified IP Phones 7960 and 7960G have the same phone firmware and share the 7960-7940 keyword.

Before Cisco Unified CME 7.0(1):

For example:

Router(config-telephony)# load 7941 SCCP41.8-2-2SR2S

Router(config-telephony)#

For example:

Router(config-telephony)# load 7941 SCCP41.8-3-3S.loads

Router(config-telephony)#

• The load command is enhanced to automatically create TFTP bindings for phone firmware files if the cnf-file location command is configured with the flash or slot0 keyword. You are no longer required to configure the tftp-server command to create TFTP bindings only if the location of the cnf files is router flash or slot 0 memory. If the cnf-file location command is configured for something other than flash or slot 0, such as a TFTP server (url) or system memory (system:its/), you must still configure the tftp-server command to create TFTP bindings for phone firmware files. Use the complete filename, including the file suffix, when you configure the tftp-server command for phone firmware versions later than version 8-2-2 for all phone types.

To verify TFTP bindings, including the dictionary, language, and tone configuration files that are associated with the ISO-3166 codes that have been selected, use the show telephony-service tftp-bindings command.

After associating a firmware file with a Cisco Unified IP phone, use the reset command to reboot the phone.

Create cnf-files

To build the eXtensible Markup Language (XML) configuration files that are required for IP phones in Cisco Unified CME, use the create cnf-files command in telephony-service configuration mode. To remove the configuration files and disable the automatic generation of configuration files, use the no form of this command.

create cnf-files

no create cnf-files

Syntax Description

This command has no arguments or keywords.

Command Default

Required XML configuration files are not built.

Command Modes

Telephony-service configuration (config-telephony)

Usage Guidelines

Use this command to generate the XML configuration files used for provisioning SCCP phones and write the files to the location specified with the cnf-file location command.

Examples

The following example builds the necessary XML configuration files on the Cisco Unified CME router:

Router (config)# telephony-service

Router(config-telephony)# create cnf-files

topic cme load phone firmware and configs in Wireless

cme load phone firmware and configs

cme load phone firmware and configs