Basic CCME test environment and we have at least two 7941G-GE phones that are unresponsive. All they do is cycle green lights on the two line appearances and headset. Resets do nothing. Reprogramming does nothing. Reset to factory defaults is unresponsive.
Did you use the create cnf-files command under telephony-service? It is REQUIRED when installing the 7971 / 7912 / 7941 / 7961 Java-based IP phones:
Router(config-telephony)# create cnf-files
(Required for Cisco Unified IP Phones 7911G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE) Builds the XML configuration files that are required for Cisco Unified CME phones.
there are also MULTIPLE JAR files that need to be installed to flash on the router, as well as referenced in your config for these IP phones to register and work on a CME. Here is an excerpt:
Cisco Unified IP Phone 7911, 7941, 7941-GE, 7961, 7961-GE, 7970, and 7971 require multiple files to be shared using TFTP. The following configuration example adds support for these phones. Use the create cnf-files command after you add or change phone firmware.
! 7911 firmware
! 7941/41-GE, 7961/61-GE firmware
! 7970/71 firmware
load 7911 SCCP11.7-2-1-0S
load 7941 TERM41.7-0-3-0S
load 7961 TERM41.7-0-3-0S
load 7941GE TERM41.7-0-3-0S
load 7961GE TERM41.7-0-3-0S
load 7970 TERM70.7-0-1-0s
load 7971 TERM70.7-0-1-0s
create cnf-files version-stamp Jan 01 2002 00:00:00
I have also noticed this problem. It appears to be related to the Ver 8 firmware load. I have downgraded to the 7.0.3 version and phone reloads and starts responding again (after factory reset sequence). I am going to test a difference firmware load. The 7.0.3 version prevents me from connecting to our corporate directory with the url directories setting in CME 4.03.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...