Last Updated: March 26, 2007 This chapter describes how to generate configuration files for Cisco Unified IP phones that are connected to a Cisco Unified Communications Manager Express (Cisco Unified CME) router. Contents • • • • Information About Configuration Files To generate configuration files for phones in Cisco Unified CME, you should understand the following concepts: • • Configuration Files for Phones in Cisco Unified CME When a phone requests service from Cisco Unified CME, the registrar confirms the username, i.e. The phone number for the phone. The phone accesses its configuration profile on the TFTP server, typically the Cisco Unified CME router, and processes the information contained in the file, registers itself, and puts the phone number on the phone console display. Minimally, a configuration profile contains the MAC address, the type, and the number phone number that is permitted by the registrar to handle the Register message for a particular Cisco Unified IP phone.

Any time you create or modify parameters for either an individual phone or a directory number, generate a new phone configuration to properly propagate the parameters. By default, there is one shared XML configuration file located in system:/its/ for all Cisco Unified IP phones that are running SCCP. For SIP phones directly connected to Cisco Unified CME, an individual configuration profile is created for each phone and stored in system:/cme/sipphone/. When an IP phone comes online or is rebooted, it automatically gets information about itself from the appropriate configuration file.

Aug 20, 2010 However on the 7940 & 7960 when calling the. Are there any know firmwares for the 7940/7960 which has issues with phone xml. Text>The text to be. CME 10.5 and local directory problems IP Telephony Cisco Technical Support Forum. /pl_PL/7960-font.xml alias user_define_1/7960-font.xml.

The Cisco universal application loader for phone firmware files allows you to add additional phone features across all protocols. To do this, a hunt algorithm searches for multiple configuration files. After a phone is reset or restarted, the phone automatically selects protocol depending on which matching configuration file is found first. To ensure that Cisco Unified IP phones download the appropriate configuration for the desired protocol, SCCP or SIP, you must properly configure the IP phones before connecting or rebooting the phones.

The hunt algorithm searches for files in the following order: 1. CTLSEP file for a SCCP phone—For example, CTLSEP003094C25D2E.tlv 2. SEP file for a SCCP phone—For example, SEP003094C25D2E.cnf.xml 3. SIP file for a SIP phone—For example, SIP003094C25D2E.cnf or gk003069C25D2E 4. XML default file for SCCP phones—For example, SEPDefault.cnf. Software Ravel Complete Orchestral Works Rar. xmls 5. XML default file for SIP phones—For example, SIPDefault.cnf. In Cisco Unified CME 4.0 and later for SCCP and in Cisco CME 3.4 and later for SIP, you can designate one of the following locations in which to store configuration files: • System (Default)—For SCCP phones, one configuration file is created, stored, and used for all phones in the system.

For SIP phones, an individual configuration profile is created for each phone. • Flash or slot 0—When flash or slot 0 memory on the router is the storage location, you can create additional configuration files to be applied per phone type or per individual phone, such as user or network locales. • TFTP—When an external TFTP server is the storage location, you can create additional configuration files to be applied per phone type or per individual phone, which are required for multiple user and network locales. Per-Phone Configuration Files If configurations files for SCCP phones are to be stored somewhere other than in the default location, the following individual configuration files can be created for SCCP phones: • Per phone type—Creates separate configuration files for each phone type and all phones of the same type use the same configuration file.

This method is not supported if the configuration files are to stored in the system location. • Per phone—Creates a separate configuration file for each phone, by MAC address. This method is not supported if the configuration files are to be stored in the system location. For configuration information, see the.

How to Generate Configuration Files for Phones This section contains the following tasks: • • • • SCCP: Generating Configuration Files for SCCP Phones To generate the configuration profile files that are required by the SCCP phones in Cisco Unified CME and write them to either system memory or to the location specified by the cnf-file location command, follow the steps in this section. Restrictions • Externally stored and per-phone configuration files are not supported on the Cisco Unified IP Phone 7902G, 7910, 7910G, or 7920, or the Cisco Unified IP Conference Station 7935 and 7936. • TFTP does not support file deletion. When configuration files are updated, they overwrite any existing configuration files with the same name. If you change the configuration file location, files are not deleted from the TFTP server.