[cisco-voip] Manually upload phone loads prior to upgrading

[Ryan Ratliff]

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.

-Ryan

On Jun 16, 2010, at 9:52 AM, Nate VanMaren wrote:

> Because TFTP is way to slow and un-relaible across some wan links.
> 
> ________________________________________
> From: cisco-voip-bounces at puck.nether.net [cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff [rratliff at cisco.com]
> Sent: Wednesday, June 16, 2010 7:20 AM
> To: Gregory Wenzel
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Manually upload phone loads prior to upgrading
> 
> Why not just add the loads to the CUCM tftp server and let the phones upgrade from there?
> 
> -Ryan
> 
> On Jun 16, 2010, at 6:54 AM, Gregory Wenzel wrote:
> 
>> 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
>> 
>> Should I add the new load to the flash of each gateway and force phones into srst to upload the new load?
>> Is this right or what other way is the best way?
>> 
>> 
>> 
>> TIA
>> 
>> ~greg
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> 
> 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.
> 
>