I have a newly installed 7941G that won't pull firmware updates. I had one remaining 7940G in my test lab, so I replaced it with a new 7941G. I Changed the ephone type and mac address to the new phone, reset and restarted the phones and the router numerous times. It just won?t pull the newer firmware. I have another 7941G that has been working fine all along.
does the phone pick the info from the DHCP ?? What is being displayed on the phone. Incase the phone is not picking up the IP Address, assign it IP Address Manually, point the TFTP Server to the CME. Also, if this does not work, please mention what is being seen on the phone and "debug ephone register mac-address " and "#debug tftp events"
Yes the phone does display correct DHCP, TFTP, and Default Router IP's. and subnet. However Load File, App Load ID, JVM load ID, OS Load ID, and Boot Load ID are all the older factory loads, and DPS Load ID is missing.
I compared debug tftp events and debug ephone register mac-address with a good 7941G and could only see the one interesting FAILED: line. What do you think?
Yes, the output of "more system...." does show the correct load (SCCP41.8-0-4ES4-0-1S)and this is what my other 7941G's are on. The bad one has a load of (TERM41.7-0-3-OS.
I agree with you that running 7.0(3) should work, but this was causing other issues in the field and in our lab. We had to upgrade to 8.0 loads because our 7941G/61G's would not display the correct time or the Local Speed Dial Directory that I created. This forum suggested upgrading to 8.0 and it worked. This newly installed 7941G is exibiting the same two problems.
Is ther a way to delete out the firmware on these phone so maybe then it would pull the correct one?
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.