Call manager and dedicated TFTP server

[Stephen Keller]

We have call manager cluster off-site at a collocation

and we have an office with about 1500 phones.

is there a magic number as far as how many devices are at a site before a local TFTP server should be deployed in the cluster?

[Jonathan Schulenberg]

My answer is 'no' although others may disagree. At least for current model phones the Peer Firmware Sharing feature should negate the need for local TFTP as long as you are resetting devices together. The only time I look at local TFTP servers are for sites with extremely high latency (e.g. satellite links).

[David Hailey]

Well, let's make sure we're talking the same thing here.  The title of your query includes "dedicated TFTP server" but the actual body references a "local TFTP" server.

As per the SRND for CUCM (pick most any version), you need a dedicated TFTP server in a cluster with over 1250 phones.  By dedicated, this simply means a server whose primary role is serving TFTP.  This does not mean it has to be "local" - as in, it does not need to be local to a particular site.  In other words, there is a server that provides TFTP services and this is a dedicated TFTP server.  You do not need to plan on having "local" or same LAN-based TFTP services for sites but there is a standard, well-documented size at which you need to dedicate a server to providing TFTP to the cluster...this server would not be the Publisher nor would be a call processing Subscriber.

Hailey

Please rate helpful posts!