<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You can browse the tftp path via both CLI (file list tftp) and OS Admin. You cannot look into a cop file but all necessary info should be documented for the devpack.<div><br></div><div>I'm not sure about phone behavior, I'd confirm in the lab to be sure.</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>-Ryan</div></span>
</div>
<br><div><div>On Jun 16, 2010, at 11:14 AM, Brandon Bennett wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Is there a way to easily extract the phone loads off of either the CUCM tftp server or from the device-pack cop file?<br><br>I am thinking I can smell cooking a simple tftp file to check for new loads and download them to the local flash (and setup the necessary tftp-server commands on IOS). Quick and easy distributed load servers :)<br>
<br>So is there a file (or even AXL if required) where you can get a list of loads? What happens when a load is not found on the defined load server? Will it try another tftp server (ie: CUCM)?<br><br>-Brandon<br><br><div class="gmail_quote">
On Wed, Jun 16, 2010 at 8:00 AM, Ryan Ratliff <span dir="ltr"><<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Then you can use the load server setting on the phones to point them to a local tftp server for phone loads. This way you can put the loads on the router and not have to force phones into SRST to upgrade their loads.<br>
<font color="#888888"><br>
-Ryan<br>
</font><div><div></div><div class="h5"><br>
On Jun 16, 2010, at 9:52 AM, Nate VanMaren wrote:<br>
<br>
> Because TFTP is way to slow and un-relaible across some wan links.<br>
><br>
> ________________________________________<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ryan Ratliff [<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>]<br>
> Sent: Wednesday, June 16, 2010 7:20 AM<br>
> To: Gregory Wenzel<br>
> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: Re: [cisco-voip] Manually upload phone loads prior to upgrading<br>
><br>
> Why not just add the loads to the CUCM tftp server and let the phones upgrade from there?<br>
><br>
> -Ryan<br>
><br>
> On Jun 16, 2010, at 6:54 AM, Gregory Wenzel wrote:<br>
><br>
>> I've heard this thrown around the blogs but never thought about it. Now I find myself needing this so I ask the group -"Whats the best way to manually upload new phone loads"- prior to upgrading call manager to any version but most likely 5 to 7 or 8<br>
>><br>
>> Should I add the new load to the flash of each gateway and force phones into srst to upload the new load?<br>
>> Is this right or what other way is the best way?<br>
>><br>
>><br>
>><br>
>> TIA<br>
>><br>
>> ~greg<br>
>><br>
>><br>
>><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" target="_blank">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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
> NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.<br>
><br>
><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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br>
</blockquote></div><br></div></body></html>