Target Platform

Platform

Specifies the platform for the run-time version of the loaded resource files. Options are:

• IR - Application is to run on an Avaya IR system.

• Voice Portal - Application is to run on an Avaya Voice Portal system.

• Desktop - (Default) Use this option while you or another developer is doing development work on the project, using another computer

• Other - Application is to run on another VoiceXML 2.0-compliant IVR system.

Servlet container

Servlet container options for the IVR system. Options are:

• Apache Tomcat - (Default) IVR system uses Apache Tomcat application server software.

• IBM WebSphere - IVR system uses IBM WebSphere or WebSphere Express application server software.

• BEA WebLogic - IVR system uses BEA WebLogic application server software.

Speech

Note: The following parameters apply to exports of speech application projects only, not call control application projects.

Grammar compatibility

Type of ASR server engine to target ASR grammars. Options are:

• Loquendo

• IBM - Grammars are optimized to work with IBM WebSphere or WebSphere Express ASR engines.

• Nuance 9.0 (Quantum) - Grammars are optimized to work with Nuance 9.0.

• Nuance OSR - Grammars are optimized to work with Nuance OpenSpeech Recognition products (including Quantum).

• SRGS-Literals - (Default) Grammars conform to the SRGS Version 1.0 standard.

• SRGS-SISR - Grammars are generated in the SRGS format with SISR per the standards and do not take into account any vendor specific nuances.

Dialog Designer, by default, creates grammars to support all ASR engines. The grammars used at run-time are based on what is selected in this field, and ultimately the value of the following variable in the web.xml file: runtime-asr.

Grammar Caching

Grammar caching option to use. Options are:

• none - No grammar caching is permitted for this application.

• default - The application uses the IVR system default setting for grammar caching.

DTMF Compatibility

DTMF grammar option to use. Options are:

• native - Generates the DTMF grammars in the ASR engine's Native format as specified in the Grammar Compatibility. This also requires that on the Voice Portal platform you enable the application for remote DTMF processing (under advanced options). The ASR engine then handles DTMF grammar processing. This option is for Voice Portal only.

• local SRGS-Literals - This is the default option. Grammars are generated in SRGS literal format and are processed by the Voice Browser. You can use this option for Desktop, IR, and Voice Portal 4.1 and earlier.

• local SRGS-SISR - If you select this option, grammars are generated with SISR tags and processed locally by the Voice Browser. You can use this option for Voice Portal 5.0 and later.

Enable Speech Synthesis Markup Language (SSML) generation in project prompts

To enable SSML markers to work in prompts, select this check box. To disable SSML markers, clear this check box.

If you select this check box, when the voice browser is generating the TTS content, it also generates the SSML data to help with the rendering of that content.

Note: If you select this check box, the AAS generates the SSML data, even in simulation mode during testing. The Microsoft TTS engine that Dialog Designer uses, however, is not capable of generating or using SSML data, so it is not apparent during testing that it is being generated.

Generate DTMF in ASR native format. For Platform Remote DTMF Processing

Select this option to enable DTMF to be generated in the ASR native formatting.

When this is selected, the generated web.xml file will have the attribute runtime-DTMF-Native set as true. The value in the web.xml file only holds the current state of the generated DTMF grammars. To change the value, you must use the project properties speech tab in the development environment. Once you change the value, you must regenerate the DTMF grammars and then redeploy the application.

Note: In conjunction with this setting, configure the application for remote DTMF processing. (Effectively, DTMF grammars are sent to the ASR engine instead of being processed locally by the Avaya Voice Browser).