Nuance ASR Property settings

In addition to the 'standard' w3c properties, the Prophecy platform with Nuance ASR (available on a per-request basis), also offers additional tuning properties for enhanced application parameter control via vendor-specific <property> settings. The properties listed below are not W3C compliant, and in no way should they be considered part of the VoiceXML 2.0/2.1 specifications.

Note: Any 'core' Nuance property used on the Prophecy platform must be prefixed by 'com'; to illustrate:

<property name="com.nuance.fieldHotwordTimeout" value="1s"/>

Property	Value
com.nuance.ttsResourceHint	`(TTS voice)`

Details: This property allows you to change the default text to speech voice in your application on a local, or global scope, depending on the placement of the property element.
--

Property	Value
com.nuance.ttsResourceHint	`(TTS voice)`

Details: This property allows you to change the default text to speech voice in your application on a local, or global scope, depending on the placement of the property element.

Property	Value
com.nuance.audio.sip.InstantConnect	`boolean`

Details: This will tell the VoiceXML browser to "connect" the call as soon as audio/media is heard on the line. This is useful for certain PSTN destinations that do not send an ISDN "answer" signal upon call pickup.

Most commonly used when postdialing parameters result in a noanswer event; note that a voice recognition prompt must reside within the <transfer> field in order for this setting to work:


<property name="com.nuance.audio.sip.InstantConnect" value="true"/>
   <transfer name="MyCall"  dest="tel:+18001112222;postd=333" bridge="true"
connecttimeout="20s">
   <prompt>Connecting your call</prompt>

Property	Value
maxinterpretations	`CDATA`

Details: Specifies the maximum number of ambiguous natural language interpretations that should be returned from the recognition. The default value for this property is '1'.

Property	Value
fetchaudiodelay	`CDATA`

Details: This property allows you to designate the amount of time to wait for the resource before playing the prompt specified as fetchaudio. The default value for this property is '0'.

ANNOTATIONS: EXISTING POSTS

safarishane

8/9/2005 1:19 PM (EDT)

Fetchaudiodelay is listed also as a W3C property in your docs, and on the spec itself. Is this something that only nuance supports at this time?

steve.sax

8/9/2005 1:32 PM (EDT)

Hello Shane,

This is simply an error in categorization; it is indeed a W3C property, and not Nuance-specific at all. I will alert our documentation team to this error, and see that they correct it immediately.

- Steve Sax

rostand

7/20/2006 7:24 AM (EDT)

Hi. I'm a frenchie and I have a problem using the nuance property
<property name="nuance.core.tts.ResourceName" value="fr-FR.default" />
It is said that this will make my voice turned to french but when I use it it keeps talking english !!! here is the code I execute :

<vxml version="2.0">
<property name="nuance.core.tts.ResourceName" value="fr-FR.default" />
<form>
<block>
<prompt> Bonjour le monde. </prompt>
</block>
</form>
</vxml>
I would really like to have a french voice. Please Help

Nota: I've just installed the prophecy voxeo server. Do I need to install nuance tts or something else ?

mikethompson

7/20/2006 12:08 PM (EDT)

Greetings Rostand,

The nuance property you are specifying is for use with our staging environment and is not integrated with our Prophecy platform.

Out of the box, Prophecy only supports English TTS. You'd have to obtain 3rd party TTS package to add support for other languages. People have successfully integrated with RealSpeak, for example. Any Rhetorical or Speechify package will work too.

Hope this helps,
Mike Thompson
Voxeo Corporation

rostand

7/20/2006 6:05 PM (EDT)

Thank you mike
I've just got the RealSpeak 4 and would you please let me know how to to integrate it in my prophecy ?

rostand

7/20/2006 7:58 PM (EDT)

I've read a post on the support forum ( really great by the way ) giving some explanation on how to initegrate realspeak. I tried but unsuccessfully. May be I'm doing something wrong. Could you please give me a clear step by step method and let me see an config.xml example for RealSpeak solo integration ? I'm still looking for the french language. Thank you

mikethompson

7/21/2006 2:51 PM (EDT)

Rostand,

I would be happy to help with Realspeak integration, but rather than proceed through a documentation posting, it would be most beneficial to you and other developers in our community, to start a thread in our Prophecy 2006 Forums. If you would be so kind, please start a thread there with the specifics of your troubles and we will be glad to help you out.

Regards,
Mike Thompson
Voxeo Corporation

jesusla

3/17/2007 6:38 PM (EDT)

Hi,

Assume the following grammar:
[ (oakland ?california) {<city 1>}
(oakland ?kentucky ) {<city 2>}
(upland ?california) {<city 3>} ]

I'm interested in retrieving ambiguous NL interpretations. E.g. if I say "oakland" I want to get:

lastresult$ = [{utterance: oakland, interpretation: { city: 1 } },
{utterance: oakland, interpretation: { city: 2 } }]

So, I set the following property.

<property name="maxinterpretations" value="2"/>

However, I only receive a single entry:

lastresult$ = [{utterance: oakland, interpretation: { city: 1 } }]

I can see in the Prophecy logs that the ASR did indeed return both interpretations, but Prophecy seems to be trimming the list down to 1. I believe Prophecy is taking this decision based on the value of the maxNBest property alone. To verify this, I changed maxNBest to 2, and now I got the NL ambiguous result.

Unfortunately, setting maxNBest to 2 has a side effect of sometimes yielding unwanted ambiguous acoustic results. E.g. if I say "oakland california", now I sometimes get:

lastresult$ = [
{utterance: oakland california, interpretation: { city: 1 } },
{utterance: upland california , interpretation: { city: 3 } } ]

So, ideally, I'd like to be able to set maxinterpretations > 1 while keeping maxNBest = 1.

Do you have any suggestions?

Thanks,
-jesus

MattHenry

3/19/2007 3:26 PM (EDT)

Hi there,

I suspect that what you are seeing may have something to do with the fact that the Prophecy version that you are using does not have full nbest support....I cannot say with any assurace, as I don't have any information on what version you are using to test, nor any debug data to work from. To be clear, full nbest support is available only in Build 7.0.3.11 and greater, which is not yet publicly available, (we have a rather strenuous QA program for releases in place).

I suggest that you hang tight for the moment, and wait until we have a release available for public consumption that addresses this topic more completely. If, after this time, you continue to have nbest issues, then send us some application logs from a test call, and we would be happy to assist.

Regards,

~Matthew Henry

sudhareddy

11/3/2008 4:59 AM (EST)

Hi
I am new to vxml and dot net...
i want to develop a IVR application in dot net using VXML2.1
which softwares i need to install..

sudhareddy

11/3/2008 5:05 AM (EST)

Hi
what is the software requirement for developing IVR application in dot net using VXML 2.1

voxeoJeffK

11/3/2008 5:21 AM (EST)

Hi,

All you need to develop applications in VoiceXML is a simple text editor. The XML code is executed by the voice browser much the same as HTML is executed by a web browser. If you are planning on dynamically generating the VXML you can use whatever server-side technology you wish, and just have the application output valid VXML.

regards,
Jeff K.

W3C Properties

| TOC

| Advanced Nuance ASR Property settings