Guest

Cisco Unified Contact Center Enterprise

UCCE Integration with CM Configuration Example

Document ID: 117777

Updated: Jun 17, 2014

Contributed by William Ryan Bennett, Cisco TAC Engineer.

   Print

Introduction

This document describes to end users how to quickly walk through a Communications Manager (CM) server setup and verify that all the proper settings for a Unified Contact Center Enterprise (UCCE)/Cisco Unified Contact Center Express (UCCX) integration with CM are in place. If any of these settings are incorrect, then various different problems are expected to occur (such as you are not able to control the agent line, you receive a duplicate Distinguished Name (DN) error/Share Line error, and so on). The Technical Assistance Center (TAC) requests the modification of the parameters if any are incorrect. This document is also necessary for UCCX integrations.

Prerequisites

Requirements

Cisco recommends that you have agents configured with DNs already configured on CM and integrated within UCCE.

Components Used

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

  • CM 6.X Revision 11.x, installed
  • UCCE 7.x Revision 10.5, installed

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.

Configure

Network Diagram

UCCE and CM configured with a 'PGUser' type associated on both sides.

Configuration

  1. Check that the Application User, not an End User, is configured for the connection between the CM and UCCE/UCCX. The Application User configuration has been required since it was introduced back in CM Release 5.x.

    As shown in this example, there is a 'pguser' configured within the Application User and not End User. This is very important.

  2. Ensure that the Application User has the right associations in the Permissions Information section.

    The five Groups and Roles selected here are the only Groups/Roles that should be selected for the vast majority of integrations. If any else are needed, let the TAC make that recommendation.

    Do not choose the 'Standard CTI Allow Control of All Devices' selection because this causes other issues. The 'Standard CTI Allow Control of Phones supporting Connected Xfer and conf' selection is necessary for newer SIP phone models to work properly.

  3. Ensure the phones are selected in the 'Controlled Devices' location. However if the agent logs in via Extension Mobility, ensure that the Extension Mobility profile instead of the device is selected in this location. Do not include the device at all.

  4. Verify that the CM cluster only has the single agent DN and not any other form of that DN at all in the cluster. Choose Call Routing > Route Plan Report > Find (or search on the exact DN that the agent logs in with). The DN should appear only one time. Important restrictions are listed here:
    • Duplicate DNs are not supported
    • Duplicate DNs with different partitions are not supported
    • Call Park and call pickup is not supported
    • Hunt Groups are not supported
    • Computer Telephony Integration (CTI) Route Points and CTI ports should never be duplicated because that causes issues

  5. Check the DN configuration for 'Maximum Number of Calls' and 'Busy Trigger'. 'Maximum Number of Calls' should always be 2 and 'Busy Trigger' should always be 1 for any UCCE agent DN. If any other numbers are present, expect various different problems (Shared Line errors when you log in, agents receive multiple calls but cannot handle them, and so on).

    In order to verify these values, click the agent phone and choose Agent DN.

Verify

Use this section to confirm that your configuration works properly.

Follow the configuration and review any UCCE and CM traces as any issues arise.

Troubleshoot

This section provides information you can use to troubleshoot your configuration.

Follow the configuration and review any UCCE and CM traces as any issues arise.

Updated: Jun 17, 2014
Document ID: 117777