Cisco Unity Connection

Introduction

This document describes how to identify the type of imported user with the use of command-line interface (CLI) commands in Cisco Unity Connection.

In Unity Connection, users can be imported from two sources - Cisco Unified Communications Manager (CUCM) and Active Directory (AD). Users imported from CUCM are known as Administrative XML (AXL) imported users. Users imported from Active Directory are known as Lightweight Directory Access Protocol (LDAP) imported users.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Cisco Unity Connection
• Cisco Unified Communications Manager
• Microsoft Active Directory

Components Used

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

• Cisco Unity Connection Release 7.X or later
• Cisco Unified Communications Manager Release 7.X or later

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.

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Import Users

If you are an AXL user, refer to Creating Multiple Cisco Unity Connection 8.x User Accounts from Cisco Unified Communications Manager Users.

If you are an LDAP user, refer to Creating User Accounts from LDAP User Data or Changing LDAP Integration Status for Existing Users in Cisco Unity Connection 8.x.

Identify the Type of Imported User

In order to identify the type of imported user, enter these commands in the CLI:

AXL Imported Users

run cuc dbquery unitydirdb select displayname, ccmid, ccmidtype from vw_subscriber
   where ccmid is not null

Non-AXL Imported Users

run cuc dbquery unitydirdb select displayname, ccmid, ccmidtype from vw_subscriber
 where ccmid is null

LDAP Imported Users

run cuc dbquery unitydirdb select displayname, ldapccmuserid, ldaptype, ldapccmpkid
 from vw_subscriber where ldapccmpkid is not null

Non-LDAP Imported Users

run cuc dbquery unitydirdb select displayname, ldapccmuserid, ldaptype, ldapccmpkid
 from vw_subscriber where ldapccmpkid is null

References

Ccmidtype

• 0 - CCM Enduser, also known as AXL Imported
• 3 - ldap user
• 4 - inactive ldap user; for example, marked inactive in ccm database

If Ldapccmpkid is not null, the user is LDAP Integrated.

• 0 - user is not LDAP enabled
• 1 - ldap synchronization enabled
• 2 - ldap authentication enabled
• 3 - ldap is enabled, but temporarily inactive for the user

Related Information

• Technical Support & Documentation - Cisco Systems