Attendant Console Call Control Failure

-
A lot of people get confused with AC plugin as AC business edition server. Let me define what stands for what.
AC server is the server which is running Attendant console service, for example CM server and CUEAC server.
AC plugin comes under application plugin in Call manager.
CUxAC is the cisco unified business/department/enterprise attendant console, which Cisco has manufactured as a separate server.

AC plugin used to come till CM version 6.1 installation DVD. Now, you can only get it when you are upgrading the server till CM version 7.1. Please note that AC plugin will not be there anymore in case you are upgrading the server to CM version 8.X.

Coming back to the issue we are discussing. When we launch AC console, we get the following error message-
"Initialization of call control failed"

These are my recommendations, which should resolve our issue swiftly:
  1. Make sure there is no firewall or ports block between your AC client (workstation) and call manager. Have a look at this document.
  2. Make sure that Pilot point and hunt group members are added in Acdeviceauthenticationuser and AC application user.
  3. Delete the password and re-add it as 12345 on both application users. The password has to be same on both on them and has to be 12345, it's a mandate.
  4. Restart Cisco unified attendant console server under Cisco Unified serviceability > tools > control center- feature service.
  5. Restart CTI Manager under Cisco Unified serviceability > tools > control center- feature service.

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more