Secondary keywords

RecoService

Identifies the entry and is activated by the RecoService keyword in the NodeName entry for any node that wants to use the service. (If you have the same technology on different platforms, this keyword distinguishes between them.)

Enabled

Yes or No. Optional. Default is Yes.

InitTechnologyString

The initialization string of the plug-in technology. This is not required for all technologies. The value of the string is dependent on the speech technology being used. It is not required for MRCP V1.0 but can be used for MRCP V2 to override default settings for TCP and UDP.

Note: If you have multiple instances of a technology (for example, to configure engines for multiple languages), you must ensure that all the InitTechnologyStrings are identical to each other.

InitSessionString

The speech recognition session initialization string, which is not required for all technologies. The value of the string is dependent on the technology being used, but often includes a URI. URIs that include numeric IPv6 format addresses, must have the numeric part within [ ] brackets, for example:

rtsp://[2002:914:fc12:195:0000:8a2e:0370:7334]/media/recognizer

This applies to all protocols.

For an MRCP V1.0 configuration the value of InitSessionString should include the URI of the speech server’s recognition engine. You can also specify an additional URI for a back-up speech server’s recognition engine in an MRCP V1.0 configuration, for example:

RecoService=Reco_GB
  PlugInClass=com.ibm.telephony.directtalk.mrcp.MRCPReco
  InitSessionString=URI=rtsp://myasrserver.example.com:554/media/recognizer
  InitSessionString=URI=rtsp://mybackupasrserver.example.com:554/media/recognizer
  RecoType=Recoen_GB
;

The first InitSessionString entry must reference the primary server, and the second entry must reference the backup server.

To specify speech recognition using dynamic engine allocation, so that speech recognition engines are not assigned for the duration of call, but instead are allocated only for the duration of each period of speech recognition, append ,keepsessionforcall=no to the end of the InitSessionString URI value. The default setting is keepsessionforcall=yes. See Allocating speech recognition and TTS engines for more information. The vendor of your speech product may not support the use of dynamic engine allocation.

For an MRCP V2.0 configuration the value of InitSessionString should include the URI of the speech server’s recognition engine. For example

RecoService=RecoMRCPv2
  Enabled=yes
  RecoType=Reco_MRCPv2_Type
  PlugInClass=com.ibm.telephony.directtalk.mrcp.MRCPv2Reco
  InitTechnologyString=sip.listening_point[0].port=5070,sip.listening_point[0].protocol=udp,sip.listening_point[1].port=5070,sip.listening_point[1].protocol=TCP
  InitSessionString=URI=sip:mrcpv2@mrcpv2server.com
;

Note: This example shows the default settings in InitTechnologyString, those that would be used if it were not specified.

PlugInClass

Mandatory. The fully-qualified name of the plug-in Java class for the speech technology being used. For an MRCP V1.0 configuration the PlugInClass is com.ibm.telephony.directtalk.mrcp.MRCPReco. The fully-qualified name of the plug-in Java class for the speech technology being used. For an MRCP V2.0 configuration the PlugInClass is com.ibm.telephony.directtalk.mrcp.MRCPv2Reco

RecoType

Mandatory. Identifies the RecoService entry in the following contexts:

The Reco Definition specification in the application properties of the application (for applications run from the Java command or from a visual builder).
The RecoDefinition keyword in the AppName entry (if different applications running in the node require different engines or context profiles).
The RecoDefinition keyword in the NodeName entry (if all applications running in the node require the same engine and context profile).

The RecoType keyword is a platform-independent label for the RecoService entry. RecoService entries for the same technology on different platforms must therefore share the same RecoType.