Secondary keywords

TTSService

Identifies the entry, and is activated by the TTSService 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 some speech technologies. The value of the string is entirely dependent on the technology being used. It is not required for MRCP V1 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 text-to-speech session initialization string, which is not required for some speech technologies. The value of the string is entirely 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/speechsynthesizer

This applies to all protocols.

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

TTSService=Tts_GB
  PlugInClass=com.ibm.telephony.directtalk.mrcp.MRCPTTS
  InitSessionString=URI=rtsp://myasrserver.example.com:554/media/speechsynthesizer
  InitSessionString=URI=rtsp://mybackupasrserver.example.com:554/media/speechsynthesizer
  TTSType=Ttsen_GB
;

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

To specify text-to-speech using dynamic engine allocation, so that TTS engines are not assigned for the duration of call, but instead are allocated only for the duration of each period of text-to-speech, 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 text-to-speech engine, for example:

TTSService=TTSMRCPv2
  Enabled=yes
  TTSType=TTS_MRCPv2_type
  PlugInClass=com.ibm.telephony.directtalk.mrcp.MRCPv2TTS
  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 technology being used. For an MRCP V1 configuration the PlugInClass is com.ibm.telephony.directtalk.mrcp.MRCPTTS. For an MRCP V2 configuration the PlugInClass is com.ibm.telephony.directtalk.mrcp.MRCPv2TTS

TTSType

Mandatory. The TTSType keyword identifies the TTSService entry in the following:

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

(The TTSType keyword is a platform-independent label for the TTSService entry. TTSService entries for the same technology on different platforms must therefore share the same TTSType.)