Changes, additions, or deletions to MRCP ASR Providers, MRCP Servers, or Groups do not take effect
From DocWiki
(Difference between revisions)
m (1 revision) |
Docwikibot (Talk | contribs) m (Bot: Adding {{Template:Required Metadata}}) |
||
| Line 1: | Line 1: | ||
| + | {{Template:Required Metadata}} | ||
== Changes, additions, or deletions to MRCP ASR Providers, MRCP Servers, or Groups do not take effect == | == Changes, additions, or deletions to MRCP ASR Providers, MRCP Servers, or Groups do not take effect == | ||
Latest revision as of 18:20, 18 December 2009
Changes, additions, or deletions to MRCP ASR Providers, MRCP Servers, or Groups do not take effect
| Problem Summary | Changes made to either MRCP ASR Providers, MRCP Servers, or Groups through Cisco Unified CCX Administration do not seem to take effect. |
|---|---|
| Error Message | None. |
| Possible Cause | When you make any configuration changes (including additions or deletions) to either MRCP ASR Providers, MRCP Servers, or Groups including changes to locales through Cisco Unified CCX Administration, these changes are made in the Config datastore and do not affect the data that is already loaded by the engine. If you wish to make these changes effective immediately without having to restart the engine, the changes need to be explicitly reloaded by the MRCP ASR Subsystem. |
| Recommended Action |
If you want the changes to take effect immediately without having to restart the engine, do the following:
|
| Release | Release 7.0(1) |
| Associated CDETS # | None. |
