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

Nate VanMaren VanMarenNP at ldschurch.org
Wed Jun 16 11:21:42 EDT 2010


What you really need is a caching TFTP proxy server, kind of like super cluster TFTP, that runs on the ISR.

So you'd just point option 150 to the local router and it would go get the file that the phones need and cache the loads for the next time.

If the load is not on the load server, it says file not found on the phone and continues to boot

-Nate

From: Brandon Bennett [mailto:bennetb at gmail.com]
Sent: Wednesday, June 16, 2010 9:15 AM
To: Ryan Ratliff
Cc: Nate VanMaren; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Manually upload phone loads prior to upgrading

Is there a way to easily extract the phone loads off of either the CUCM tftp server or from the device-pack cop file?

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 :)

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)?

-Brandon
On Wed, Jun 16, 2010 at 8:00 AM, Ryan Ratliff <rratliff at cisco.com<mailto:rratliff at cisco.com>> wrote:
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<mailto:cisco-voip-bounces at puck.nether.net> [cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Ryan Ratliff [rratliff at cisco.com<mailto:rratliff at cisco.com>]
> Sent: Wednesday, June 16, 2010 7:20 AM
> To: Gregory Wenzel
> Cc: cisco-voip at puck.nether.net<mailto: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<mailto:cisco-voip at puck.nether.net>
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<mailto: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.
>
>


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100616/c97f3f04/attachment.html>


More information about the cisco-voip mailing list