<br><font size=2 face="sans-serif">Router is definatly an option as I am
part of the network group. However again this would mean that I or
someone from my team would need to manage 350 different TFTP servers. One
across each site. So not real scalable.</font>
<br>
<br><font size=2 face="sans-serif">Wes maybe you know did cisco monkey
with the TFTP times on the phones. The default for TFTP timeout
is 1000ms however I have seen some people change this down to 200 or 300ms.</font>
<br>
<br><font size=2 face="sans-serif">Craig<br>
<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Robert Kulagowski <bob@smalltime.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: cisco-voip-bounces@puck.nether.net</font>
<p><font size=1 face="sans-serif">08/14/2006 09:56 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">cisco-voip@puck.nether.net</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [cisco-voip] Upgrading firmware
on 7961 remotly</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>> Would love to however by the time we are done
with our rollout we will <br>
> have about 350 sites across the globe so if we have to setup seperate
<br>
> TFTP servers at each location that is HUGE administration nightmare.<br>
<br>
Well, you can always use the router as a tftp server; is that an option?<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</font></tt>
<br>