Cisco Unified Attendant Consoles

CUAC User Entry Maximum Limit Determination

Document ID: 116323

Updated: Aug 12, 2013

Contributed by Tray Stoutmeyer, Cisco TAC Engineer.



This document describes how to determine if the maximum limit of user entries on the Cisco Unified Attendant Console (CUAC) Directory is reached and which users are present in the Directory once that limit is reached.



Cisco recommends that you have knowledge of these topics:

  • CUAC
  • Cisco Unified Communicaiton Manager (CUCM)

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco Unified Business Attendant Console (CUBAC) Versions 8.x and 9.x
  • Cisco Unified Department Attendant Console (CUDAC) Versions 8.x and 9.x
  • Cisco Unified Enterprise Attendant Console (CUEAC) Versions 8.x and 9.x
  • Cisco Unified Premium Attendant Console (CUPAC) Versions 8.x and 9.x
  • CUCM Versions 8.x and 9.x

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Determine if the Maximum Limit of User Entries in the CUCM Directory is Reached

In order to determine if the maximum limit of user entries has been reached, complete these steps:

Note: Before you complete these steps, make sure that Directory Sync is enabled (System Configuration > Directory Synchronization >  Enable), that you restarted the Lightweight Directory Access Protocol (LDAP) plugin service, and that you closed the client console and logged back in.

  1. Navigate to Start > All Programs > Microsoft SQL Server 2008 and click the Connect button. Expand the tree structure until you reach the Tables level:


  2. Highlight the dbo.Contact_Numbers table and right-click on it. Choose Select Top 1000 rows. You can now see the number of users imported into the Directory in the lower-right corner:


Determine Which Users are Present Inside the Directory Once the Maximum Limit is Reached

The Attendant Console filters the user directory from CallManager and sorts the entries based their pkid value. Basically, it is first come, first served. However, the pkids are out of your control, and are also random. For example, this output displays a Secure Shell (SSH) connection to a Publisher:

admin:run sql select telephonenumber,userid,pkid from enduser order by pkid

telephonenumber   userid        pkid

============= ============ ====================================

7005          luzuniga     072db6cd-4968-664f-07c6-e3b284c03682

7003          aformosa     ae5e7d41-a66a-5f0d-b10c-50a8f445638c

1234          1234tome     b517f6c5-ec3c-3e15-56d4-226bf4156b79

7005          cbucket      c8f7be03-9028-0ad3-a871-3f35337e5c25

7335          willy        dddd2b45-aad9-7218-a5e5-ff332e3ecb0

The output shows the order that the Attendant Console reads the user list from the CallManager, and inserts them into the database. Notice how the username with extension 7005 is not the first one alphabetically, nor is it the lowest directory number. Although it is not the first user inserted chronologically, its pkid starts with 0.

If your Attendant Console is able to display a maximum of three users on a client Console, then Charlie Bucket (cbucket) and Willy (willy) are not displayed at all. CUBAC has a maximum of 500 users, CUDAC a maximum of 750 users, and CUEAC a maximum of 100, 000 users.

The Structured Query Language (SQL) Query shown is used in order to determine the entries that are not inserted into the CUAC LDAP database.

Related Information

Updated: Aug 12, 2013
Document ID: 116323