Ok, can you please help me understand how the phone sees the file if I can't see it on the disk? I don't quite understand the caching feature. <br>Also where do you access the TFTP service parameters, the Windows MMC services snap-in or in CM somewhere?
<br><br>thanks<br><br><div><span class="gmail_quote">On 10/6/06, <b class="gmail_sendername">Ryan Ratliff</b> <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The Cisco TFTP server caches config files in memory to reduce disk<br>access and speed up tftp requests. Unless you go into advanced TFTP<br>service parameters and disable caching you will never see the config<br>files on the hard disk.
<br><br>-Ryan<br><br>On Oct 6, 2006, at 1:54 PM, Candese Perez wrote:<br><br>ok, i do see a read request for an xmldefault.cnf.xml from the phone<br>to the cm server but i don't see that file in my tftp directory. Any<br>
ideas as to why that is?<br><br><br><br>On 10/6/06, Wes Sisk <<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>> wrote:<br>default.cnf was only used by old phone loads (in CM3.1 we changed<br>to .cnf.xml files). that file will probably not be built unless you
<br>change the TFTP service parameter from 'build selective' to 'build all'.<br><br>only VERY old phone loads should need that file.<br><br>/Wes<br><br>Candese Perez wrote:<br>> Manually adding the phone works. (Thank you)
<br>> Any ideas on why I don't have a default.cnf file in my tftp<br>> directory if auto-registration is enabled?<br>><br>> On 10/6/06, Ryan Ratliff <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>
> wrote: Under System-<br>> >CallManager there is a check box to disable auto-<br>> registration on a server.<br>><br>> There will not be a config file on the TFTP server unless the phone<br>> is in the database. I'd recommend you add the phone manually and it
<br>> will then register.<br>><br>> -Ryan<br>><br>> On Oct 6, 2006, at 12:48 PM, Candese Perez wrote:<br>><br>> I don't believe the phone is in the database because i can't find it<br>> when searching by it's MAC address. When I look at my CM server
<br>> configuration I don't see that auto-registration is disabled. Is<br>> there some place else I should be looking to check for auto-<br>> registration?<br>><br>><br>><br>> On 10/6/06, Ryan Ratliff <
<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote: Is the phone in<br>> the database? If not and autoregistration is<br>> disabled then the config file won't exist and it won't register.<br>><br>
> If the phone is in the database try bouncing TFTP and then doing a<br>> TFTP GET on the macaddr.cnf.xml from a windows cmd prompt to see if<br>> you can get the file.<br>><br>> -Ryan<br>><br>> On Oct 6, 2006, at 12:26 PM, Candese Perez wrote:
<br>><br>> When I do a factory reset it looks for a file SEP+MAC address and<br>> then says file not found and returns to registration rejected. In my<br>> trace file I can see several TFTP error codes referencing the same
<br>> message that the tftp server doesn't have the SEP+MAC.cnf.xml file<br>> nor does it have XMLDefault.cnf.xml.<br>><br>> On 10/6/06, Brian Henry <<a href="mailto:Brian.Henry@apptis.com">Brian.Henry@apptis.com
</a>> wrote:<br>> I assume that you are not running in secure mode.<br>><br>> 1. Did you do a factory reset of the phone?<br>><br>> Have you looked at the debugs on the phone web page to see what error<br>
> code it is giving you? or you can attach the cable in the docs to the<br>> aux port to look at the phones boot up process and a more detailed<br>> view.<br>><br>> Brian<br>><br>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">
cisco-voip-bounces@puck.nether.net</a> on behalf of Candese Perez<br>> Sent: Fri 10/6/2006 11:58 AM<br>> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Subject: [cisco-voip] Phone Registration Rejected
<br>><br>> I have a 7960 that will nto register with my CM 4.0 server, and I<br>> believe it is because the .cnf file is out of date or has changed as<br>> this phone has been in storage for several months.<br>
><br>> How can i get the phone to use the new file on CM if it won't<br>> register in CM. Is there a way to push the new file to the phone?<br>><br>> Candese<br>><br>> _______________________________________________
<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br></blockquote></div><br>