<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">auto reg isn't going to work so well with centralized TFTP.<div><br></div><div>centralized TFTP very basically does this:</div><div>If file is not found locally then request it from the defined peer TFTP servers</div><div><br></div><div>In this case autoreg uses information in xmldefault.cnf.xml which will always be found on the centralized server. *if* it works your phones would all register in the cluster that performs as the centralized TFTP server.</div><div><br></div><div>/wes</div><div><br><div><div>On Nov 4, 2011, at 1:12 PM, Anthony Holloway wrote:</div><br class="Apple-interchange-newline"><div>Cisco VoIP Group,</div>
<div> </div>
<div>I am reading the following section of the UC SRND:</div>
<div><a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/netstruc.html#Centralized_TFTP_Services" target="_blank"><font color="#1155cc">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/netstruc.html#Centralized_TFTP_Services</font></a></div>
<div> </div>
<div>And I am wondering how phone auto registration is affected by the Centralized TFTP model? Or if it's even supported? If so, what are the limitations?</div>
<div> </div>
<div>I don't see this referenced in the SRND, and would be open to reading any supporting documentation I am pointed to.</div>
<div> </div>
<div>Thank you,</div>
<div><br clear="all">Anthony</div>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div><br></div></body></html>