Deploying VoiceXML applications

You can deploy your VoiceXML documents onto any HTTP compliant Web server when you want to put them into production, but the speech browsers that request them and download their associated audio must know where to find them. To ensure this happens, the Web address (URI) of every VoiceXML document you want the speech browsers to access must be specified in the default.cff configuration file. To do this, you can use the dtjit configuration tool as described in Updating the configuration database or manually edit default.cff.

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.
You may want to configure your web server to support the following MIME types:
You can use the file system on your local machine to hold VoiceXML documents. In this case you specify the URI using file:// before the filename using the full path. For example, on AIX this could be: 
file:///var/dirTalk/DTBE/samples/en_US/Weather.vxml
In this case, as with Web servers, the VoiceXML document will reference associated resources (for example, audio files) using a path relative to the originating document.
Note: File names containing illegal or non-ascii characters must be escaped and encoded in UTF-8 encoding. For example, a space character in the file name is specified as %20 in the URI.

MIME type

MIME type is a unique identifier used when files are transferred across a MIME-based protocol such as HTTP. The VoiceXML browser supports the following MIME types:

File Type

MIME type
VoiceXML documents
  • text/vxml
  • text/x-vxml
  • application/vxml
  • application/x-vxml
audio files
  • audio/basic = headerless and .au files with μ-law encoding (audio/basic .au is the default when recording)
  • audio/x-alaw-basic = headerless and .au files with a-law encoding
  • audio/wav = Microsoft wav file
ABNF grammar files
  • application/srgs
XML grammar files
  • application/srgs+xml
precompiled grammar files
  • application/x-ibmfsg
natural language understanding (NLU)
  • application/x-ibm-ngram
Parent topic: Putting your application into production