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.

   ASR Servers	Server Name	Base Port Number
   IBM WVS	<hostname>/media/recognizer	554
   Scansoft SWMS	<hostname>/media/speechrecognizer	4900
   Nuance MRCP Server	<hostname>/recognizer	554

   TTS Servers	Server Name	Base Port Number
   IBM WVS	<hostname>/media/synthesizer	554
   Scansoft SWMS	<hostname>/media/speechsynthesizer	4900
   Nuance MRCP Server	<hostname>/synthesizer	554

   Note: The suffixes above are automatically appended when the above media servers are configured through Web Administration.

2. Check the performance of your LAN.

   Slow or interrupted LAN communications can result in failed processes for speech recognition, Text-to-Speech, or database operations. The cause is generally overloading of the Avaya IR system or the LAN.

   For more information, see Checking LAN communications.

3. Check for speech server disconnect problems.

   For more information, see Troubleshooting speech server disconnections.

4. Run a trace using debug level 5 and examine the MRCP message exchange.

   Use the command sproxyadm -r OPSRx -D 5

© 2006 Avaya Inc. All Rights Reserved.