Filter
Top Products
Contents
30 Avaya IR R2.0 Troubleshooting
BuiltinLocale A setting that indicates the language to be used for
built-in ASR grammars such as numbers or phone
numbers.
In Avaya IR release 1.2.1 and release 1.3, the IBM
WVS supports only one language at a time but
does offer several different languages. Refer to the
IBM WVS documentation for the full range of
language options.
Change this setting if the MRCP server supports a
language other than US English.
en-US
Erratic availability of MRCP speech resources
If speech resources are erratically available to your applications-sometimes they're available,
but sometimes they're not-there may be problems with port contention between applications.
Check the port ranges used by the MRCP feature and the other applications and utilities
running on your system.
If there is a port conflict, edit the MRCP configuration file (/vs/sproxy/cfg/mrcp.cfg) to reset
the RTPBasePort setting to prevent ongoing conflict.
MRCP servers are frequently out of service
When Avaya IR loses its connection with an MRCP server, it places the server into the Far
end Out Of Service (FOOS) state. (Avaya IR will not place the server into the BROKEN
state.)
This may be a temporary condition as connections between Avaya IR and the MRCP server
are dropped and reestablished during normal operations.
However, when links between the Avaya IR system and the MRCP servers regularly end up
out of service (FOOS), several things may contribute to the problem.
To investigate the problem:
1. Check to ensure the server has been properly administered.
In particular, check the server name and base port number. If the server is an IBM WVS,
the server name must be entered in the form name/media and the base port number
must be set to 554.
Use the table below to check the server name abd base port number entered.