Cisco Cisco Customer Response Solution Downloads Leaflet
Diagnosing and Correcting Cisco CRA Problems
Cisco CallManager Automated Attendant Problems
6
Troubleshooting Cisco Customer Response Applications
OL-3051-01
Cisco CallManager Automated Attendant Problems
The following section describes common problems with the
Cisco CallManager Automated Attendant.
Cisco CallManager Automated Attendant.
Dial by name does not find the specified user
Symptom
The Cisco CallManager Automated Attendant cannot find a user that a
caller specifies when dialing by name.
Possible Cause
The extension of the requested user is not valid because the user
does not have a primary extension assigned in Cisco CallManager, or the
ccndir.ini file is missing information.
ccndir.ini file is missing information.
Recommended Action
1.
In the Cisco CallManager 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
an entry in the AutoAttendant Dialing field, that the User record has an
associated phone, and that the Primary Extension radio button is selected
2.
On the CRA server, verify that the ccndir.ini file contains the correct userbase
and profilebase information. For example:
and profilebase information. For example:
USERBASE “ou=Users, o=cisco.com”
PROFILEBASE “ou=profiles, ou=CCN, o=cisco.com”
Cisco CallManager Automated Attendant prompt is not played
Symptom
The Cisco CallManager Automated Attendant prompt is not played.
Possible Cause
An incorrect welcome prompt is specified in the welcomePrompt
field in the Cisco Script Application web page.
Recommended Action
From the CRA Administration web page, choose System >
System Parameters. Make sure that the following information appears in the
User Prompt Directory field:
User Prompt Directory field:
C:\program files\cisco\wfavvid\Prompts\User