<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
TFTP clients retrieve files from CM's TFTP server without any issue.
Just GET the file names you need.<br>
<br>
/Wes<br>
<br>
<br>
<br>
On Wednesday, June 16, 2010 11:14:51 AM, Brandon Bennett
<a class="moz-txt-link-rfc2396E" href="mailto:bennetb@gmail.com"><bennetb@gmail.com></a> wrote:<br>
<blockquote
cite="mid:AANLkTil4naadn04rw1MIDc0_EDoaGbKOXu8vg_I7C14z@mail.gmail.com"
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 moz-do-not-send="true"
href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; 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 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 moz-do-not-send="true"
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a moz-do-not-send="true"
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Ryan Ratliff [<a moz-do-not-send="true"
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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> <a moz-do-not-send="true"
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 moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a moz-do-not-send="true"
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 moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a moz-do-not-send="true"
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>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>