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.
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.
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.
Firmware files are not associated with phone types.
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.
• 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 isrouter 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.
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.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...