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.)
rtsp://[2002:914:fc12:195:0000:8a2e:0370:7334]/media/speechsynthesizerThis applies to all protocols.
For an MRCP 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 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.
(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.)