Filter
Top Products
6-5
Cisco CallManager Extended Services Administrator’s Guide
78-12959-01
Chapter6 Troubleshooting Cisco CallManager Extended Services
Clearing Problems with Cisco CallManager Extension Mobility
Clearing Problems with Cisco CallManager AutoAttendant
This section describes how to clear the following problems that may impact
Cisco CallManager AutoAttendant:
• No Matches for an Existing User, page 6-5
• Cisco CallManager AutoAttendant Prompt is Not Found, page 6-5
No Matches for an Existing User
Symptom A search fails for an existing user in the Cisco CallManager AA.
Possible Cause The user is not found because the ccndir.ini file is missing
information or the extension is not valid because the user does not have a primary
extension assigned in Cisco CallManager Administration.
Action
1. Verify that the user has an entry in the Cisco CallManager AA Name dialing
field and that the User record has an associated phone and that the primary
extension button is selected.
2. Verify that the ccndir.ini file contains the following lines:
USERBASE “ou=Users, o=cisco.com”
PROFILEBASE “ou=profiles, ou=CCN, o=cisco.com”
3. If you migrated the Cisco CallManager from version 2.4, a possible schema
issue exists. In the LDAP Directory Administration, verify that the user’s
Owner field is in Userid format, not full name format.
Cisco CallManager AutoAttendant Prompt is Not Found
Symptom The Cisco CallManager AA prompt is not found.
Possible Cause Media configuration was not initialized properly.
Select Media from the main Application Administration page and verify that the
prompt directory is listed as:
C:\program files\cisco\wffavvid\Prompts
and that the User Datagram Protocol (UDP) start port is 16384.