Porting the Voice Environment and Applications

To provide voice functionality with non-Nuance VoiceXML platforms, the Portal Server 7.1 voice environment and voice applications must be ported.

The following issues are commonly encountered while porting:

• Each VoiceXML dialog file contains an XML DTD header, and the XML DTD header used by your voice application must be correct. To determine the correct XML DTD header, see the documentation for the voice browser you are using.

• Voice browser vendors sometimes use different grammar file formats. These could be proprietary, or based on evolving industry standards. Check to see if the grammar used by your voice browser is compatible with the Nuance format used by the Portal Server 7.1 software, and modify the grammars if necessary. Some grammars might be inline in VoiceXML dialogs, or in external grammar files.

• If you develop VoiceXML applications that use client-side scripting, such as ECMAScript or JavaScript, be aware of interpreter differences between voice platforms.

• Some voice browsers might not support the full set of VoiceXML tags. The voice browser documentation usually lists which tags the browser supports. You might need to modify VoiceXML code to remove unsupported tags.

• Some VoiceXML tags behave differently between voice browsers. Although the code might execute, the behavior could change subtly. Thoroughly test all dialog states in your application, even if the dialog states appear to execute correctly.

• If pre-recorded prompts are not played correctly, you might need to change the encoding from the default 8-bit, 8kHz, mulaw sphere encoded WAV audio file format.