Upgraded to 4.3 from 4.1 on new servers. All went well except for the Attendant. All speed dials and user lists have the "?" unkown status. It was working great with 4.1. Have done all posted documentation and have done it all again with a Cisco tech via TAC.
No firewalls, deleteted text files, restarted services.... Even unloaded and reloaded the latest version of attendant and did all the documentation again.
Re: Unknown status in Attendant Speed dials and Lists
Very whetherTCD and CTI Manager service are running. The CcmLineLinkState performance monitor for the attendant console provides a quick way to check whether the attendant console is functioning correctly: If the CcmLineLinkState counter is 11, this state indicates that Cisco TCD is functioning normally. The left-most digit of CcmLineLinkState indicates whether Cisco TCD is connected to and registered with the Cisco CallManager CTI. If this digit is 0, a problem may exist with the CTI or the directory. The right-most digit of CcmLineLinkState indicates whether Cisco TCD can perceive line state information through Cisco CallManager. If this digit is 0, a problem probably exists with Cisco CallManager.
Note When an attendant console user cannot log in to the attendant console and no line state information is available, view the CcmLineLinkState performance monitor to verify that all components of attendant console are functioning properly. Make sure you have the Cisco Telephony Call Dispatcher started on the pub and all subs.
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.