Calling A Route Point With An Mrcp Asr Dialog Group Results In Default Treatment; Outbound Problems; Agent Does Skip Or Skip-Close But Does Not Stay Reserved - Cisco Unified Contact Center Express Servicing And Troubleshooting Manual

Outbound Problems

If you want to reload the data associated with a single MRCP Provider, Server, or Group, go to
Step 1
Subsystems > MRCP ASR to access the MRCP ASR Configuration page and click the refresh icon for
the corresponding provider. You can also use this step to load a newly created MRCP ASR Provider.
Step 2 If you want to reload all providers, go to Subsystems > MRCP ASR to access the MRCP ASR
Configuration page and click Refresh All.
Calling a route point with an MRCP ASR Dialog Group results in default
treatment
Symptom
Group.
Error Message None.
The cause might be one of the following:
•
•
Recommended Action
•
•
•
•
Outbound Problems
This section contains the following troubleshooting tips on Outbound problems:
•
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
8-56
The customer gets the default treatment when calling a route point with an MRCP ASR Dialog
No server is configured for this dialog group. The MRCP ASR Dialog Group refers to a specific
MRCP ASR Provider. Each MRCP ASR Provider must have at least one reachable server configured
in order to be IN_SERVICE.
None of the servers for the MRCP ASR Provider can provide all the languages required by the
MRCP Dialog Group.
Depending upon the cause, do one of the following:
Ensure that a server is configured and reachable for the MRCP ASR Provider being used by the
MRCP ASR Dialog Group.
When configuring an MRCP ASR Provider, more than one MRCP ASR Server can be associated
with that Provider. Each server can support a different set of languages. For example, server A
supports en_US and server B supports es_ES. When configuring an MRCP Dialog Group in the
Provider that contains these two servers, you are provided with a list of Enabled Languages. For this
example, the list contains both en_US and es_US because there are servers for the specified provider
that support these languages.
Normally the user interface will prevent you from selecting both en_US and es_ES for the group
because neither server supports both languages; however, it is possible to create an illegal situation
if at least one of the servers starts out supporting all the languages installed. The UI will allow you
to select all languages for the group as well because there is at least one server in the Provider that
supports all languages. It is possible to go back to that server and remove support for one of the
languages. If you do this, the group is not changed and now needs a language combination that
neither server can provide.
To check for this, access the CRS Administration page for the group in question. Click Update. If
you see the message, There are no servers to satisfy this selection of languages, then you need to
change the languages selected to a set that is supported by at least one of the servers in the Provider.
Agent does skip or skip-close but does not stay reserved, page 8-57
Chapter 8 Troubleshooting Tips