04-02-2008 03:17 PM - edited 03-15-2019 09:49 AM
The Attendant Console client used to work. I have made no changes to the setting but says unable to connect to server. I can ping the server.
What would the problem be?
04-02-2008 03:27 PM
It may be that your TCD service has quit responding. Restart TCD. I have seen TCD just lock up many times.
Its under your control panel in call manager.
This is from memory so it may not be 100% accurate.
Call Manager Servicability----tools---control center
Restart Telephony Call Dispatch on both servers.
03-26-2009 09:46 AM
Same issue and works.
03-22-2016 12:42 PM
I restart Cisco IP Manager Assistant Service and It works.
CUCM Version 11
04-02-2008 03:32 PM
Problem solved I restarted the Attendant Console Service in Call Manager and it works now
04-16-2008 07:46 AM
I had the same issue and a Heartbeat error. Restarting the service was the trick.
07-21-2009 04:47 AM
i have three computers in the office that use attendant console. two of the computers can connect fine to the AC server and answer calls. One of the pcs states that it cannot connect to the server and we cannot make any changes to the ac settings.
i have restarted the services in CCM and added the ip address and host name to the
lmhosts and host files in c:\windows\system32\drivers\etc
07-31-2018 01:06 PM
I have the same issue where 5 computers can connect, but one says cannot find server after reloading the software twice. All PC's are on the same Vlan. Any idea's what the issue is here? We are on CUCM version 11.5, CUAC 11.0.1 and working with Windows 10 machine.
09-28-2018 11:46 AM - edited 09-28-2018 11:48 AM
I Have the same issue, any ideas?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: