Users Receive Fast Busy When Dialing Cisco IP AutoAttendant Number [Cisco Unified Communications Manager (CallManager)]

Document ID: 5247

Introduction
Before You Begin
      Conventions
      Prerequisites
      Components Used
Checking the Cisco IP AutoAttendant Configuration in the Application Administrator
Related Information

Introduction

This document outlines some quick steps for checking the configuration of Cisco IP AutoAttendant within the Application Administrator.

Before You Begin

Conventions

For more information on document conventions, see the Cisco Technical Tips Conventions.

General familiarity with the Cisco CallManager web administration interface is assumed. It would be a good idea to review and follow the instructions in Configuring the Cisco Four Port IP Auto-Attendant Application on a CallManager Server before reviewing this document.

Components Used

The screenshots in this document are based on Cisco CallManager 3.0.9 and Extended Services 2.1 and apply to later CallManager and Extended Services versions. As an example, this document can also be used to troubleshoot a Cisco CallManager 3.2 installation with Customer Response Application (CRA) 2.2.5.

This document does not apply to Customer Response Solutions (CRS) 3.X (IP Contact Center (IPCC) Express) .

The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.

Checking the Cisco IP AutoAttendant Configuration in the Application Administrator

Follow the instructions provided below:

Ensure that the Cisco Telephony Integration (CTI) route points, CTI ports and the Java Telephony API (JTAPI) user have been properly configured and specified as per the installation document.
Verify that the Application engine is running and the JTAPI subsystem is in service. Point your browser to http://ip address of Appserver/appadmin.
Click Engine and make sure that it is running and the JTAPI subsystem is IN_SERVICE.
The next thing to check is the Application setup. Go back to the main menu and click Application.
Click the link for the application you created (Autoattendant in this example) and then click Next. This should take you to the Application Administration parameters page.
Ensure that the Enabled button has been set to Yes. If it is set to No, change it to Yes, and stop and start the Engine. These steps should allow you to dial the AutoAttendant pilot number successfully.