I got a call while I was sleeping early about 6AM. The IT Director was calling to tell me that the operators at the hospital could not log in to the Cisco Attendant. First thing I thought of was the user name and passwords were wrong that is the most common issue when they can not log in. The Cisco Call Attendant reflects off the users Active Directory account - they use their regular domain account to log in but this time that was NOT the issue... The user names and passwords were correct. Turns out the Attendant service needed to be restarted on the Call Manager server, this time it was not just a password problem...
The Problem:
Users can not log in to the Attendant.
Example: PBX (operators) the users there log in to the Attendant to call and organize calls. If they get errors and can NOT login
The Solution:
1) Account Problem :
Reset password. The logins are based off the AD accounts. Sometimes users might have the wrong password, the account could be locked in Active Directory or they might just be trying the wrong user name.
2) The service has failed:
There is a “Cisco Call Manager Attendant Console Server” service inside the call manager. Sometimes this service can fail and will need to be restarted. Here is how to restart it.
Login to call manager http://XXXXXXXXX
Navigate to “Cisco Unified Serviceability” and click GO (top right of the screen)
From the menu go to Tools and “Control Center –Feature Services”
Select server “192.X.X.X” from the drop down menu and click GO
Under “CTI Services” Select the –Cisco CallManager Attendant Console Server- button, scroll down to the bottom of the left screen and click “RESTART”.
This is a good thing to note because you can also restart other critical services from here as well.. Also when I spoke to cisco they told me secretly it is good practice to restart any services that have been running for over 60 Days. Of course they would not advertise that with their products but thats what they honestly do recommend.
No comments:
Post a Comment