Unlock Settings on 7960 phone

[pmenico]

I need to change the TFTP address on the phone but the settings are locked. I tried **# before the settings menu but it does not work. I plugged in the phone it found the DHCP server OK but it is stuck on Configuring IP message.

Are there any other codes like **# and **#** that I might try?

[aaronw.ca]

You have the correct key sequences:

**# to unlock the settings

**#** to reset the phone

However, you cannot change the TFTP server until you disable DHCP, since the phone gets this setting from DHCP. First, unlock the settings with **#, then go into the configuration, and set DHCP to "No" (ie disable DHCP), then go up and change the TFTP server.

Note that disabling the DHCP server means that while the phone may retain the IP address it has been assigned, it will not be renewing the lease with the DHCP server, so are potential problems later when another device may be assigned the IP address being used by the phone without the DHCP server's knowledge. I would suggest using this for short term only, or even better, use a static IP for the phone in these circumstances.

You could also get away with modifying the config file for that phone on the tftp server, depending on what you're after. For that you might have to modify the CallManager service parameter to disable caching of config files so that they are actually placed in the tftp server rather than cached in memory (defaults to the latter).

[pmenico]

Thanks for your response. My problem is that for some reason in the settings it thinks that there is a CM at 169.254.173.1 and it gets stuck at "Connecting 169.254.173.1" message. "**#" has no affect at this point. When I press "settings" and then "Network Conf." it remains locked. All info looks correct (DHCP, domain, IP Address,subnet mask, TFTP, default router1, DNS1, DNS2) except "Call Manager 1" which has the above address which is not correct and I have no idea how it got there. I am stuck in a catch 22. I cannot get passed this state and be allowed to "**#" unlock and change the settings so I can remove this address.

Any ideas?

[ngss]

Try pressing * 6 at the same time.

Thanks

SSng

[aaronw.ca]

Is the CallManager configured correctly? Are other phones able to connect? Is this phone configured as a device in the CallManager, or is CallManager configured to allow autoregistration?

It looks like the phone is trying to register with the default CallManager, so perhaps it either cannot find the TFTP server or what it finds on the TFTP server it doesn't like.

[stephan.steiner]

my two development CCMs are not in the DNS, and neither is the option 150 set in DHCP. Yet, that's no problem thanks to the alternative TFTP setting. You can easily leave your phone configured in DHCP mode, then activate "enable alternative tftp" and enter the IP address of your call manager. So if the call manager in the list cannot be contacted, the phone will default to your alternative TFTP address. In my case, the first call manager in the list is the hostname of my CCM machine, but since the CCM is not in the DNS, the phones never find it and thus default to the TFTP server I have configured.

[pmenico]

Thank you all, I resolved this. The issue was not only to press **# at the settings menu but also on the individual settings. Strange but worked.

Option 150 is picked up from my DHCP now and the CM defualts to the TFTP address.

Thanks again all.