Cisco Cisco Customer Response Solution Downloads Troubleshooting Guide
8-43
Cisco Unified Contact Center Express Servicing and Troubleshooting Guide, Release 7.0(1)
Chapter 8 Troubleshooting Tips
Cisco Unified CCX Engine Problems
Unable to connect to JTAPI provider
Symptom
The JTAPI provider is unavailable.
Error Message
None
.
Possible Cause
The problem might be caused by one of the following:
•
Cisco Unified CM is not running.
•
Incorrect JTAPI client version is installed on the Cisco Unified CCX server.
•
JTAPI user is not configured correctly.
•
JTAPI client cannot communicate with the Cisco Unified CM.
Recommended Action
Depending upon the cause, do one of the following:
•
Troubleshoot the Cisco Unified CM (refer to Cisco Unified Communications Manager
Administration Guide).
Administration Guide).
•
Check the JTAPI version on the Cisco Unified CCX server by selecting Start > Programs > Cisco
JTAPI > Readme.
JTAPI > Readme.
•
From the Cisco Unified CCX Administration web page, choose Subsystems > JTAPI, click the
JTAPI Provider hyperlink, and then verify that information in the User ID field matches the name
of a valid user in Cisco Unified CM. Verify that information in the Password field is correct.
JTAPI Provider hyperlink, and then verify that information in the User ID field matches the name
of a valid user in Cisco Unified CM. Verify that information in the Password field is correct.
•
Verify that Cisco Unified CM is running. Configure Cisco Unified CM using the IP address instead
of the DNS name.
of the DNS name.
The Simple Recognition step takes the unsuccessful branch
Symptom
The Simple Recognition step in a script takes the unsuccessful branch even when the word
spoken or DTMF key pressed is defined in the grammar.
Error Message
None
.
Possible Cause
The Simple Recognition step is configured with a set of tags and output points. Most
likely, the tag names defined in the step do not exactly match the tag names defined in the grammar used
by the step. Such a mismatch can occur when a tag name is defined in the grammar
by the step. Such a mismatch can occur when a tag name is defined in the grammar
Recommended Action
Complete the following steps:
Step 1
Verify that all tag names defined in the grammar are configured in the Simple Recognition step with
matching spelling and case.
matching spelling and case.
Step 2
If the grammar contains tag names that are not configured in the Simple Recognition step, either
configure the same tag name in the Simple Recognition step or remove the tag names from the grammar.
configure the same tag name in the Simple Recognition step or remove the tag names from the grammar.