Avaya Logo

Previous Topic

Next Topic

Book Contents

Book Index

The MRCP configuration file

Installing the MRCP feature on Avaya IR creates a configuration file (/vs/sproxy/cfg/mrcp.cfg) and the default settings shown in the following table.

The configuration file sets parameters for the ports used for signaling and the timing intervals that Avaya IR uses to determine if it has lost touch with speech resource servers. Under most circumstances, there is no need to change these default settings.

Parameter

Description

Default Setting

RTPNumberofPorts

The number of ports on Avaya IR available for RTP connections to MRCP servers.

Note:
The default setting is higher than the number of ports that Avaya IR can support for ARS and TTS combined. This helps prevent port conflict.

1000

RTPBasePort

The base port number on Avaya IR for the range of ports used for RTP connections to MRCP servers.

This value, combined with the RTPNumberofPorts value, defines the range of ports reserved for connections to MRCP servers.

ASR requests use the lower half of the range, while TTS requests use the upper half of the range.

The default setting has been set to prevent conflicts with the RTP ports needed for Voice Over IP.

Change this value only if you experience port conflicts.

10000

RTPPacketRate

The rate, measured in milliseconds, at which data is transmitted over each RTP connection.

Change this value to match the packet rate of the MRCP server at the other end of the connection.

20

RTSPNoActivityTimeout

The number of seconds Avaya IR will wait for a response from an MRCP server before sending a DESCRIBE message as a test of the connection.

If a second timeout interval elapses with no response, Avaya IR decides that the server or the connection is out of service. It then places the server into the maintenance state called FOOS (facility out-of-service), logs the event, and raises an alarm.

Reducing this interval will improve the speed at which lost connections are detected, but it will also increase the messaging overhead between Avaya IR and the servers.

MRCP servers may use a similar approach to monitoring connectivity. If so, make sure that the interval set on Avaya IR s not higher than what is set on the server. If the interval on Avaya IR is inadvertently set higher than on the server, the server may erroneously assume that its connection to Avaya IR has failed when, in fact, it has not.

15

ResponseTimer

The number of seconds that an Avaya IR application will wait for a response from an MRCP server providing ASR or TTS support.

Example:
When applications attempt to allocate a speech processing resource, a SETUP message is sent to the server that provides that support and this timer starts. If Avaya IR receives no response to the SETUP request within the specified interval, the application is told that the allocation failed.

5

PerPortConnection

A setting that indicates whether the MRCP implementation uses port 554 for a single connection for signaling or for multiple, per-port connections.

If TRUE, multiple, per-port connections are used for signaling. (This is required in Avaya IR release 1.2.1 and release 1.3? if the MRCP server is an IBM WVS.)

If FALSE, a single connection is used for signaling.

TRUE

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

© 2006 Avaya Inc. All Rights Reserved.