legacy:text-to-speech_guide:tts_http_protocol:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
text-to-speech_guide:tts_http_protocol:start [2015/03/03 21:00] – [VoiceXML Browser configuration] borjalegacy:text-to-speech_guide:tts_http_protocol:start [2017/07/31 16:17] (current) – ↷ Links adapted because of a move operation javier
Line 1: Line 1:
 ====== HTTP/TTS Protocol ====== ====== HTTP/TTS Protocol ======
  
-[[:vxi_installation_guide:start|Home]] >+[[vxi_installation_guide:start|Home]] >
  
 ===== Description ===== ===== Description =====
  
-Our VoiceXML browser can connect to a TTS engine using HTTP.+The VoiceXML browser can connect to a TTS engine using HTTP.
 The HTTP protocol is used to transform the prompt text to an audio file. The HTTP protocol is used to transform the prompt text to an audio file.
 The audio file can be store in a cache directory in order to optimize the TTS ressources using. The audio file can be store in a cache directory in order to optimize the TTS ressources using.
Line 12: Line 12:
 This protocol is simple : This protocol is simple :
   * From the VoiceXML browser, you configure to use HTTP, a (POST recommended) request containing mainly the text content and additional parameters (like language, voice...).   * From the VoiceXML browser, you configure to use HTTP, a (POST recommended) request containing mainly the text content and additional parameters (like language, voice...).
-  * The server treats your request. +  * The web server with the TTS engine treats your request. 
-  * The VoiceXML browser receives an audio file (cpataible with Asterisk) : it store its in cache and play it. +  * The VoiceXML browser receives an audio file (compatible with the Asterisk audio formats) : it stores the file in cache and plays it. 
-  * If you try to use the same content, the VoiceXML will check and use the cache content instead of requesting the TTS engine.+  * If you try to use the same content after, the VoiceXML will check and use the cache content instead of requesting the TTS engine.
  
  
Line 52: Line 52:
 #client.prompt.resource.0.password           VXIString   demo #client.prompt.resource.0.password           VXIString   demo
 client.prompt.resource.0.ssml               VXIInteger  0 client.prompt.resource.0.ssml               VXIInteger  0
 +</code>
 +
 +Most of this parameters can be change from the VoiceXML syntax using properties. Use the property name 'prompt' added with the parameter name.
 +
 +VoiceXML example :
 +
 +<code>
 +<property name="promptvoice" value="Poala"/>
 </code> </code>
 ===== HTTP Parameters ==== ===== HTTP Parameters ====
Line 58: Line 66:
   * **language** : the language used (en-GB, fr-FR...) : from the xml:lang attribut.   * **language** : the language used (en-GB, fr-FR...) : from the xml:lang attribut.
   * **format** : the audio format to return (wav, gsm, mp4... formats supported by Asterisk) : from the configuration.   * **format** : the audio format to return (wav, gsm, mp4... formats supported by Asterisk) : from the configuration.
-  * **voice** : the voice (Carla, Marcos... depends on the TTS provider) : from the xml:lang attribut.+  * **voice** : the voice (Carla, Marcos... depends on the TTS provider) : from the xml:lang attribut (3th parameter ex: "it-IT-Paola").
   * **size*** : the size of the image : from the property promptsize.   * **size*** : the size of the image : from the property promptsize.
   * **backgroud*** : the image reference or color used for the background : from the property promptbackground.   * **backgroud*** : the image reference or color used for the background : from the property promptbackground.
  • legacy/text-to-speech_guide/tts_http_protocol/start.1425416457.txt.gz
  • Last modified: 2017/07/28 22:29
  • (external edit)