Hello all, We ran into a problem where it seems the.cnf.xml file of the phones is corrupted so the phone does not registers. If you change any detail on the device configuration (i.e.
Add a '-' on description) the phone registers back. I assume it works because a new file is generated and the phone gets this new, non-corrupted file from TFTP and is able to register.
What I wanted to do is to get the.cnf.xml file from a phone that is not working, then 'fix' it and get the new file again to compare and see if something can be found to indicate why this happened. Does anyone knows how can I get the.cnf file or knows any additional details on this issue?
Bruno, The config files should be in the default directory of the TFTP server. However, I recall there was a configuration in v4 which controlled whether the config files were stored in memory or on disk. By default they were stored in memory so you would never see them on disk or have access to them. I checked v7 TFTP Service Parameters and there's no setting which I can tell which controls this.
Cisco 7960G IP Phone on Asterisk. I spotted on a number of sites that the SIP firmware is/was available from Cisco to download. Touch xmlDefault.CNF.XML ln.
I'm not sure they build them to disk anymore. You could probably setup a TFTP client (Klever/Pumpkin) and simply try to retrieve the file as if the phone would. HTH Lelio --- Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Cooking with unix is easy. You just sed it and forget it. - LFJ (with apologies to Mr.
Popeil) ----- Original Message ----- From: 'Bruno Takahashi' To: cisco-voip@puck.nether.net Sent: Monday, October 10, 2011 7:29:44 PM Subject: [cisco-voip] How to get a Phone's.cnf.xml file from CUCM Hello all, We ran into a problem where it seems the.cnf.xml file of the phones is corrupted so the phone does not registers. If you change any detail on the device configuration (i.e. Add a '-' on description) the phone registers back. I assume it works because a new file is generated and the phone gets this new, non-corrupted file from TFTP and is able to register. What I wanted to do is to get the.cnf.xml file from a phone that is not working, then 'fix' it and get the new file again to compare and see if something can be found to indicate why this happened. Does anyone knows how can I get the.cnf file or knows any additional details on this issue? -- Bruno _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net.
On Windows you can just pop open a command prompt window and type: C: >tftp get SEP.cnf.xml Example: C: >tftp 10.1.1.1 get SEP0000DEADBEEF.cnf.xml Source: NOTE: Win7 users may need to turn on TFTP command line client from within Add/Remove programs first. On *nix systems: 'man tftp' should tell you what you need to know. You may also want to SPAN the switch port the phone is on, and look at the traffic. Perhaps the.cnk.xml file is not even making it to the phone, or perhaps there are missing packets.
TFTP is UDP after all, and therefore has no re-transmits. -Anthony On Mon, Oct 10, 2011 at 6:29 PM, Bruno Takahashi wrote: >Hello all, >>We ran into a problem where it seems the.cnf.xml file of the phones is >corrupted so the phone does not registers. >If you change any detail on the device configuration (i.e. Add a '-' on >description) the phone registers back. >I assume it works because a new file is generated and the phone gets this >new, non-corrupted file from TFTP and is able to register. >>What I wanted to do is to get the.cnf. Free Download Program Contoh Soal Tpa Bappenas S2 Pdf. xml file from a phone that is not >working, then 'fix' it and get the new file again to compare and see if >something can be found to indicate why this happened. >>Does anyone knows how can I get the.cnf file or knows any additional >details on this issue?
>>-- >*Bruno* >>_______________________________________________ >cisco-voip mailing list >cisco-voip@puck.nether.net >>.
After a Cisco CallManager upgrade, some IP phones do not download the new IP phone load from TFTP and do not register with the Cisco CallManager. This document discusses and provides a resolution for this issue. Cisco recommends that you have knowledge of these topics: • Cisco CallManager Administration • The information in this document is based on these software and hardware versions: • Cisco CallManager 3.x and later • Cisco 7900 IP phones The information in this document was created from the devices in a specific lab environment.
All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Refer to for more information on document conventions. After a Cisco CallManager upgrade, some of the IP phones do not boot up completely. They are stuck in various states of the boot process that include 'Configuring CM List' and 'Upgrading Software'.
The IP phones also do not register with the Cisco CallManager and display the.cnf.xml files cannot be located error message. Complete these steps to resolve this problem: • Open the Cisco CallManager Administration page.
• Select Service >Service Parameters. • Select the CallManager server and choose Cisco Tftp for the service. • Click Advanced. • Set these parameters under Clusterwide Parameters (parameters that apply to all servers): • Set the value for Build CNF Files* to Build All. Note: When you set the Build CNF Files service parameter to Build All, the TFTP server builds both.cnf.xml and.cnf format configuration files for all devices. When you set this service parameter to Build None, the TFTP server builds only.cnf.xml files for all devices.
When this parameter is set to Build Selective, which is the default value, the TFTP server builds.cnf.xml files for all devices. It also builds.cnf files only for a select list of devices that do not support.cnf.xml. • Set the Enable Caching of Constant and Bin Files at Startup parameter to False. • Set the Enable Caching of Configuration Files parameter to False. Note: By default, Enable Caching of Configuration Files is set to True. When this parameter is set to True, all the CNF and XML files are built and kept only in memory. When this parameter is set to False, TFTP writes all the CNF and XML files to the disk under the TFTP path C: Program Files Cisco TFTPPath.
It can take a long time to write these files to the disk if a large number of devices exist in the network. Therefore, set the Enable Caching of Configuration Files parameter to False to reduce the performance of the TFTP server. • Restart the Cisco TFTP service. Complete these steps: • Select Application >Cisco CallManager Serviceability >Tools >Control Center. • Click on the Cisco CallManager server, choose Cisco TFTP and click Restart.
Note: You are now able to see the configuration files for the devices in C: Program Files Cisco TFTPPath. • Restart the affected Cisco IP phones. Broadcom Usb Serial Adapter Driver.
• Set the values of the Enable Caching of Constant and Bin Files at Startup parameter and the Enable Caching of Configuration Files parameter back to True. Note: There are several problems that can cause a Cisco IP phone not to register. Refer to for more information on those problems.