<div>personally, I go into the phones. Select 50 phone and click reset. when those 50 come up then I go onto the next 50. Kind of painful but I *usually* don't have phone locked up in the morning when I come in.</div>
<div> </div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Jan 30, 2008 1:06 PM, Matthew Melbourne <<a href="mailto:matt@melbourne.org.uk">matt@melbourne.org.uk</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I'm considering an upgrade to CCM 4.1(3)SR6. However, this has not yet<br>appeared on the compatibility matrix with CRS 4.0(5).<br>
<br>In order to add device support for the 7921s, it is necessary to apply a<br>DevPack. I was hoping to do this with the application of SR6 which itself<br>includes DevPack 64.<br><br>If I apply the standalone DevPack 65 (which is compatible with the<br>
existing CCM 4.1(3)SR2, will the later application of SR6 overwrite the<br>device loads set by DevPack 65?<br><br>Obviously, when device loads get updated there is the possibility that a<br>large number of phones will attempt to update at the same time. What is<br>
the robustness of this procedure (assuming one TFTP server on the<br>Publisher)? Is it advisable to reload phones in a controlled manner,<br>perhaps on a site-by-site basis by bouncing switch ports?<br><br>Cheers,<br><br>
Matt<br><font color="#888888"><br>--<br>Matthew Melbourne<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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></font></blockquote></div><br>