[cisco-voip] CUCM Remote TFTP options

[Wes Sisk]

Fully agreed.

There is 1 optimization available that has not yet been leveraged.  For 
the "centralized TFTP" feature (see SRND) CM TFTP servers will serve up 
files via HTTP.  For an example see CSCsq48448.

An ambitious individual could leverage this feature to setup something 
similar to a TFTP proxy server:
remote_site_phone<--tftp-->local_tftp_proxy<---http---->central_site_CM_TFTP_server

The proxy would take a TFTP request, retrieve the requested file from 
central via http, then serve it up locally via TFTP.
This would use HTTP over the WAN for better efficiency.  I am not aware 
of anyone productizing this yet.

/Wes

On Monday, January 25, 2010 10:29:51 AM, Ted Nugent 
<tednugent73 at gmail.com> wrote:
> We had a client that attempted this in the past and 
> quickly abandoned the idea. You have to remember that its not just the 
> phone loads that you're pulling from the tftp but also anytime you 
> make a change to a phone the phone needs to pull a new config file off 
> the tftp and that tftp server needs to be part of the cluster. You'd 
> be stuck manually or scripting the config files off the cluster tftp 
> which is an admin challenge to say the least.
>
>
> On Mon, Jan 25, 2010 at 10:20 AM, <george.hendrix at l-3com.com 
> <mailto:george.hendrix at l-3com.com>> wrote:
>
>     Hi everyone,
>
>      
>
>       I am looking at having multiple remote sites on a single
>     cluster.  I would prefer the remote sites have local TFTP servers,
>     but it’s my understanding the TFTP servers for the phones must
>     also be part of the CUCM cluster.  Is this correct or is there any
>     documentation on how to standup a separate TFTP server which isn’t
>     part of the CUCM cluster?
>
>      
>
>     Thanks,
>
>      
>
>     Bill Hendrix
>
>     george.hendrix at l-3com.com <mailto:george.hendrix at l-3com.com>
>
>      
>
>
>     _______________________________________________
>     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
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

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