I have a small customer with a 7750 (1 spe) running CM 3.3 sr2. They have 3 users who use Attendant Console (2 on the local LAN, 1 over a WAN) The customer tells me that callers get routed to AA every so often when they should be going to the online Attendant Console users.
All three are logging CTIManager Heartbeat timeouts in the event viewer of the call manager.
The LAN is all cisco-switched 100 Mb/s full duplex connections to the workstations and I have no interface errors or user complaints that would make me think there is an underlying infrastructure problem.
The PCs are Windows 2000 with 256MB Ram. I'm waiting for trace files from the Attendant Console PCs to see if they will tell me anything.
The call manager cti trace logs a "MYTCPERR_SOCKETBROKEN" error that corresponds (in time) to the event viewer entry.
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.