We have a cluster with cetralised deployement model.
The remote sites are connected to the cluster over the WAN. We have about 3000 phones that need to register for the first time. we assume that getting 3000 phones registered over the WAN would take a long time.
Is there a way we can get the phones to fetch the configuration file from a local gateway (by editing DHCP option 150 in the scope to point to the gateway) and once phones have loaded the files we change the tftp address again to point to the TFTP server in the cluster.
Centralized model need more bandwidth.
But, i want to know how many remote site, and how many remote phones.
The quickest way is to do it site by site.
I don't know if what you ask is possible, but copy all .cnf.xml file from the CUCM tftp server to another tftp server looks technicaly fine to be (you would then need to configure your dhcp server to point to your temporary tftp server) But don't forget about the phone firmware that could be different from the default one on CUCM =>should also be present on tftp.
One question : how do you know those 3000 (new ?) phones will register at the same time ?
Thank u for ur reply.
@ iantra: We have enough bandwidth for the WAN link but the point is that the phones will be registering to the UCAAS (cisco hosted cluster) from UK. Thus it would take longer than usual time to register the phones.
@ James: The firmware is not an issue we can use the same at both places. Also the DHCP option for TFTP can be easily changed.
The issue is that i am not aware if we can use a default cnf file for all the phones or we would need a seperate file for all the phones.
We know that the 3000 phones would register at the same time b coz the site is being migrated from an Avaya PBX to Cisco IPT.
I'm 99% sure that each phone has its own cnf file, because each phone is looking for its SEPxx.cnf.xml during boot process. So I don't think you will be able to do it with a commong cnf file.
So lets take it other way round now. It seems that the actual time that a phone takes to load is the firmware file and not the configuration file. So i think if we use a local tftp to host the firmware files and then get the phones to register to the original CUCM to dowload the cnf file would it resolve the issue??