8-9
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
Chapter 8 Troubleshooting Tips
Cisco Unified Communications Manager Automated Attendant problems
Cisco Unified Communications Manager Automated Attendant problems
This section contains the following troubleshooting tips on Cisco Unified Communications Manager
(Unified CM) Automated Attendant (AA) problems:
Dial by name does not find the specified server, page 8-9
Automated Attendant prompt is not played, page 8-9

Dial by name does not find the specified server

Symptom The Cisco Unified Communications Manager Automated Attendant cannot find a user that a
caller specifies when dialing by name.
Error Message None.
Possible Cause The extension of the requested user is not valid because the user does not have a primary
extension assigned in Cisco Unified Communications Manager, or the ccndir.ini file is missing
information.
Recommended Action Complete the following steps:
Step 1 In the Cisco Unified Communications Manager User Information web page, verify that the user has an
entry in the AutoAttendant Dialing field, that the User record has an associated phone, and that the
Primary Extension radio button is selected.
Step 2 On the CRS server, verify that the ccndir.ini file contains the correct userbase and profilebase
information. For example:
# Base DN for CCN APPS
CCNAPPSBASE "ou=CCN Apps, o=cisco.com"
# CCN Cluster Profile name
CCNCLUSTERPROFILE "johndoe_test"
# Base DN for Users
USERBASE "ou=Users, o=cisco.com"

Automated Attendant prompt is not played

Symptom The Cisco Unified Communications Manager Automated Attendant prompt is not played.
Error Message None.
Possible Cause An incorrect welcome prompt is specified in the welcomePrompt field in the Cisco Script
Application web page.
Recommended Action From the CRS Administration web page, choose Applications > Prompt
Management. Click the Upload New Prompts link to upload the Welcome prompt.