We have a centralized CallManager Cluster (4.1.3 upgrading to 5.1.2 soon)
Is it technically possible (albeit not likely supported )to have the phone load hosted by the TFTP services of an SRST router. The phone config files would still reside on the servers. The goal is simply allow the phone to receive it?s upgrade from a distributed (local to the phone) source.
My understanding of the TFTP process is that when the phone boots it looks to the configured primary TFTP source for it?s configuration file and if it is not found will go to the secondary.
One con of this is that with only two tftp servers there would be no redundant (tertiary) tftp source for the phone config files.
I am very interested in a procedure to upgrade phone located on remotes sites with few bandwidth by serving loads directly from the local SRST router flash. Could you please detail your proposed strategy a little more?
Not sure why I missed your reply and expressing my thanks. So Thank you.
I would however like to leave the phone .cnf file on the call manager. So here is my concept.
Via DHCP option 150 point the first tftp server to the local router and the secondary/tertiary to the call manager servers. The phone boots and looks to the srst for its config file, fails and looks to the callmanager servers. Once it downloads the config file and know that it need to update, reboots, looks again to the srst router and finds the phone image to proceed with the upgrade. The phone reboots after the upgrade and goes though the process skipping the upgrade until I change the phone config again.
This should provide me the central management of the phone configs and only have the phone image local. We have some offices with 100+ phones and during an upgrade would off load the image update process.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.