09-05-2008 02:56 AM - edited 03-15-2019 01:04 PM
I am unable to connect to the attendant console. I get the message ("unable to connect to server")I enable trace to see the logs and I get the following
20[Thread-7]09/05 12:52:06.034 WARN Thread-7 >>> No RMI connection bound.
21[Thread-7]09/05 12:52:23.456 WARN Thread-7 >>> No RMI connection bound.
22[Thread-7]09/05 12:52:44.284 WARN Thread-7 >>> No RMI connection bound.
23[Thread-7]09/05 12:53:05.299 WARN Thread-7 >>> No RMI connection bound.
24[Thread-7]09/05 12:53:26.127 WARN Thread-7 >>> No RMI connection bound.
25[Thread-7]09/05 12:53:47.159 WARN Thread-7 >>> No RMI connection bound.
26[Thread-7]09/05 12:54:07.987 WARN Thread-7 >>> No RMI connection bound.
However, I can ping the server and the IP phones are working fine.
Any help will be appreciated
09-05-2008 03:54 AM
Hi,
Have you made sure the phone is associated to the AC account in CallManager?
Make sure the AC account has all the proper associations. More information can be found here:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_1_3/ccmfeat/fsccmac.html#wpxref29392
Please rate useful posts....
09-05-2008 04:02 AM
Also, is this a new intallation of attendant console (from the plug page) or has it worked before. If it's new, make sure you are using the correct version of AC for the version of CCM you are using..
09-05-2008 04:40 AM
it is a new installation. I just did the ac installation from the plugin. I also did device associations but still doesn't work.
09-05-2008 04:54 AM
Please ensure that the windows firewall on the XP/Vista PC is disabled or you have an exception rule to allow AC.EXE.
09-05-2008 08:01 AM
Ok, is there another instance of AC running anywhere successfully? If so, was this version installed from the same callmanager?
Have you tried re-starting the TCD service to see if it helps anything?
Attendant console problems are usually related to the following issues:
1) Devices aren't associated with AC account
2) host name doesn't resolve when lauching app - if so, use an IP address
3) CallManager service issue - if so, re-start the TCD service
What version of CallManager are you using?
Please rate useful posts.....
09-05-2008 08:18 AM
Ok, is there another instance of AC running anywhere successfully? If so, was this version installed from the same callmanager?
Have you tried re-starting the TCD service to see if it helps anything?
Attendant console problems are usually related to the following issues:
1) Devices aren't associated with AC account
2) host name doesn't resolve when lauching app - if so, use an IP address
3) CallManager service issue - if so, re-start the TCD service
What version of CallManager are you using?
Please rate useful posts.....
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide