Cisco 7945 Will Not Register With CUCM using Alternate TFTP

[is-opsnetwork1]

Trying to register a 7945 with an alternate call manager, if i set it via the DHCP scope Option 150 and point it to the alternate TFTP all works, however, when testing this is not what i want to happen, i would like to be able to set the alternate TFTP server and leave it at that, whats happening

1. Change the setting to use an alternate TFTP server

2. Set the new TFTP address

3. Save the settings

4. Delete the ITL file

5. Phone reboots yet when you brown to the phone it still has the old CUCM listed?

Anyone any idea's?

[is-opsnetwork1]

Should also mentions i have also tried factory defaulting the phone

[Ayodeji Okanlawon]

Take a packet capture from the phone ( use span to PC port) from the CUCM the phone is registered to currently. Attach the pcap file here. It is possible the phone is not able to connect to the alternate tftp server. A packet capture will tell us whats going on

[Maren Mahoney]

I'm pretty sure that with DHCP enabled, any locally set ip-related settings will be overridden by what is learned via DHCP. (Correct me if I'm wrong.)

If it is just one phone, can you create a manual entry for that MAC address in the DHCP server with the settings you want? I've done this in a router with the following:

ip dhcp pool main
 network 10.1.1.0 255.255.255.0
 default-router 10.1.1.1
 option 150 ip 10.1.1.100
 dns-server <whatever>
 domain <whatever>

ip dhcp pool special
 host 10.1.1.5 255.255.255.0
 client-identifier <mac.address.here>
 option 150 ip 10.1.1.200

The one phone with that mac address will get the IP and option 150 from the "special" dhcp pool and will pick up any remaining settings from the "main" pool.

You can do the same thing in a Windows DHCP server by creating a reservation and adding the Cisco Option 150 to the reservation after it is created.

HTH

[g.watt]

Found the issue, the phone was looking for a version of firmware we didn't have on the CCM