Appendix H: Voxeo Property Guide

Looking to tweak the default behavior of the VoiceXML platform? Then you will need to fine-tune the available properties within the application itself. Setting a property at the <vxml> level of a page will change the settings on a document scope, (or on the application scope if the document in question is the application root). You can also set a property for a specific input field or form in order to change a particular setting for a form/field scope. Be advised, that the default property settings are optimized for maximum performance, and changing any of them, (especially the Advanced Nuance Properties), should be undertaken with extreme caution.

Overview

W3C Properties: Detailing the standard tweaks available on any VoiceXML gateway, this guide covers all supported w3c properties for the available platforms

Nuance-Specific Properties: The Nuance engine carries with it another set of platform-specific properties that allow an even finer level of application tuning, and this section covers them all in minute detail.

Advanced Nuance Properties: If you want to really get down and dirty, then you can utilize some of the core Nuance properties to change default application behavior. The properties detailed in this section are intended for those advanced developers out there, to whom the word 'fear' is a foreign concept. Use carefully.

ANNOTATIONS: EXISTING POSTS

alexey.timofeev

12/15/2006 5:13 AM (EST)

Hi,
i have 2 questions:
1. is there any possibility to reduce amount of time after call answered and first
phrase pronounced?
2. is there any possibility to reduce amount of time after pressing button and
reaction on it?
I tried to reduce properties completetimeout, fetchaudiodelay, incompletetimeout
but saw no difference.

mikethompson

12/15/2006 2:15 PM (EST)

Hi Alexey,

Allow me to address your questions numerically:

1) There are a lot of things that influence how quickly the first phrase is pronounced. For example, large documents (especially involving server-side markup) will take longer to parse than a simple hello world application. Also, any audio files which are not cached can introduce delays. It all depends on how your application is built, as there are some nice things you can do to trim down the amount of delay. If you would like some more information specific to your scenario, please open a private account ticket with us.

2) So far you're on the right track. Compeltetimeout and incompletetimeout are certainly good properties to control. I would highly recommend checking out the spec on Appendix D ? Timing Properties:

http://www.w3.org/TR/2004/REC-voicexml20-20040316/#dmlATiming

This will cover all the properties you can modify to influence the timing of input for your application. I think you will find this section VERY helpful.

Best,
Mike Thompson
Voxeo Corporation

raghu.ram

2/27/2007 1:49 AM (EST)

hi,
comin straight to point
i hv a project, and i hv done it in cafe.bevocal.com
and i hv used some bevocal properties in my project..
and now im not fully OK with there services
so i want to try my code in ur site, and im havin a problem with the code in this ??
so plz guide me
what changes should me made to my current code, to work in this site..??

thanks
--raghu

mikethompson

2/27/2007 2:13 PM (EST)

Hi Raghu,

Our VoiceXML platform follows rather closely to the W3C spec:

http://www.w3.org/TR/2004/REC-voicexml20-20040316/

You will find most of your answers there, but our VoiceXML documentation will also prove to be extremely helpful. As it looks like you've already found our documentation, I would encourage you to check out our property guide:

http://docs.voxeo.com/voicexml/2.0/frame.jsp?page=mot_appendixh.htm

Of course, if you ever get stuck with your code conversions, feel free to ask us and we will gladly point you in the right direction.

Best,
Mike Thompson
Voxeo Corporation

yungwei

7/27/2007 6:00 PM (EDT)

Hi,

Is it correct to say that whatever is mentioned in Voxeo property guide is supported?

mikethompson

7/27/2007 6:24 PM (EDT)

Hi Yungwei,

The properties mentioned in the W3C property guide will work on our VoiceCenter 5.5 and Prophecy platforms. However, the Nuance specific properties will only work on VoiceCenter 5.5, as it uses a Nuance ASR. Prophecy uses its own in-house ASR, which does not support Nuance specific properties. However, you *can* integrate Nuance ASR with Prophecy if you would like to utilize these properties.

I hope this adresses your question, and do let me know if you have further questions.

Best,
Mike Thompson
Voxeo Corporation

jimijani1982

6/12/2008 8:14 AM (EDT)

My Question is How to read "Voxeo Logs" in Log Viewer. Which portion of logs we have to more concentrate.

My email:a.majid@ubl.com.pk

VoxeoDustin

6/12/2008 10:23 AM (EDT)

Hey,

Below are some links to our documentation on some of the information you'll find in the logger and how to decode it. Some of this is for our online debugger, but most of the information translates to the local Prophecy Log Viewer as well.

http://docs.voxeo.com/voicexml/2.0/loggerfeatures.htm
http://docs.voxeo.com/ccxml/1.0-final/loggerfeatures_ccxml.htm
http://docs.voxeo.com/callxml/3.0/loggerkey_cxml30.htm

Cheers,
Dustin

Transfer Hotwording

| TOC

| W3C Properties