Guest

Cisco Unified Contact Center Management Portal

CCMP Version 9.x Unified Config Web Service Connection Fails with Error "HTTP Status 403"

Document ID: 117363

Updated: May 05, 2014

Contributed by Nebojsa Zdravkovic, Cisco TAC Engineer.

   Print

Introduction

This document describes the problem when the Contact Center Management Portal (CCMP) Unified Config Web Service connection might fail with the correct Unified Config URL on the Administration Workstation (AW). When tested in a browser directly on the AW, the https://<aw_ip_addr>/unifiedconfig/config/agent/ URL might also fail with any domain account. This includes domain administration accounts. Even though all possible permissions and group membership to all Unified Contact Center Enterprise (UCCE) groups might be given to domain administrators, the issue might still persist.

Problem

CCMP Version 9.x uses the Unified Config Web Service connection Tomcat URL (https://<aw_ip_addr>/unifiedconfig/config/agent/) for configuration retrieval. In the Add CCE Server wizard, CCMP identifies this URL correctly and it also passes the initial checks. However, the actual connection might fail. When this URL is tested in a browser located on the AW directly, the error returned might be:

Solution

The reason for this problem might be an incorrect deployment type set in the UCCE administrator page, which is the setting applicable for Version 9 and later. If there is not a type or an incorrect type set, access permission to the Unified Config URL is restricted, which causes it to return the error 403 - access forbidden. After the deployment type is changed to UCCE it should work right away, without the need for a restart. The correct response from the URL above, when all is configured correctly, is similar to this:

In order to configure UCCE deployment types on the AW, complete these steps:

  1. Go to https://<aw_ip_addr>/cceadmin.

  2. Click the Settings tab.

  3. From the Deployment Type drop-down list, choose the correct deployment type.

This should fix the issue with the Unified Config URL in Tomcat.

Updated: May 05, 2014
Document ID: 117363