Cisco Unified attendant console standard deployment with cucm

The Attendant console for the receptionist comes in two flavor for UC11.x onwards

The basic version is called the standard version : Limited feature suitable for small office and branches

Advance version: Have a dedicated server and suitable for large enterprise
It connect customers, employees, and business partners with the right person, the first time. Cisco^® Unified Attendant Console Standard (Figure 1) gives corporate operators and receptionists the tools they need to handle incoming calls efficiently and professionally. This desktop application communicates directly with Cisco Unified Communications Manager to control the operator’s phone. It makes it fast and easy to answer calls and transfer them to people across your organization.

This doesnt require a server to be maintained unlike its predecessors.

Its suitable for Branch and small enterprise but if call volume is large then advance version is recommended.

It can import max of 5000 contacts

For creating Bill of material looks for datasheet or ordering guide from cisco.com for the top level SKU
Total search capacity for the Client is 5000 contacts in case of standard version.
The client communicate with the CUCM using a CTI language
The Attendant require a presence enabled end user account

Here are the summary of steps required to implement the Attendant console in standard mode

Create a access group for CTI enable and Axl privilege

The group should contain the below role

Standard AXL API Access
Standard CTI Allow Calling Number Modification
Standard CTI Allow Call Park Monitoring
Standard CTI Allow Control of All Devices
Standard CTI Allow Reception of SRTP Key Material
Standard CTI Enabled

If you are using phone models 69xx, 7931, 7965, 89xx and 99xx, you must also select:

Standard CTI Allow Control of Phones supporting Connected Xfer and conf
Standard CTI Allow Control of Phones supporting Rollover Mode

Now create a Application user which should contain the device for attendant console login in the controlled device section and should have the above role.

Now Create a end user that is configured for Jabber ( So that can see the presence status of other users from attendant console)

next step is to start beginning the installation of the attendant console standard version:

Locate the installer
Doubleclick to run the installer .exe file
It will install the C++ library  as per below screenshot

Mention the  CUCM IP address and the application userid and password created in the above step

It will ask for presence server details provide the asked detail,The userid should be the end user id

After the installation finish, Configure the TSP

   

Mention the CTI manager ip address and user credentials

 

Once the installation is complete , Reboot the machine and login to the attendant console

In the login page for attendant console mention any extension that you have attached to the controlled devices.


Once you put the extesnion and click on sign In the user sign In to the application as follows



Here you need not to create any park and queue device for parking and queuing separately.

Cisco attendant console interact with the CUCM CTI manager using the TAPI (TSP) installed in the  attendant console client/server.

Follow the instruction in readme before doing the installation of the console as each version has some specific requirements.

In case of CUEAC standard 11.0 installation it install the TSP version 11.5 by default you need to unistall the TSP and install the TSP version 11.0

One more important point to keep in mind related to the parking of the call to attendant console is that you need to create park number in cucm to park the calls from attendant console.
 In the CUCM the park number can be created from Call routing > Call park



And once the park DN is configured in CUCM the Attendant console client can use the same to park the call.



Troubleshooting :

Check for TSP configuration
TSP logs
Make sure the DN for attendant is not shared line and should be unique
Log Location C:\Users\<Userid>\AppData\Roaming\CUACSLogging
Make sure that the telephone number field is populated in the end user page,This is required so that the attendant can dial using a directory search from the  attendant console window