| VoiceXML 2.1 Development Guide | Home | Frameset Home |
| dtmf | Data Type: (true|false) | Default: False |
| The dtmf attribute, when set to 'true', will assign the first 9 menu choices implicit dtmf grammar values, unless the choices already have them explicitly assigned. Unless specified, the default value for the dtmf attribute is false, thus disallowing implicit dtmf grammar assignation. | ||
| id | Data Type: ID | Default: Optional |
| The id attribute specifies the navigational identifier of the form element. Once specified, the developer can assign the id as a destination of any goto statement. | ||
| scope | Data Type: (dialog|document) | Default: Dialog |
| The scope attribute denotes the scope of any grammars contained within the menu. If set to ‘dialog’, (default), then all grammars contained will only be active within the current form. If set to ‘document’, then the grammars will be considered active throughout the current page of Voicexml code. If, however, the scope is set to ‘document’ in the application root document, then the menu grammar will be active throughout the entire application. | ||
| <?xml version="1.0" encoding="UTF-8"?>
<vxml version = "2.1"> <meta name="author" content="Matthew Henry"/> <meta name="copyright" content="2005 voxeo corporation"/> <meta name="maintainer" content="YOUR_EMAIL@HERE.COM"/> <!-- document scoped match --> <catch event="batboy_event"> <prompt> bat boy is always the life of the party.</prompt> </catch> <!-- document scoped match --> <catch event="elvis_event"> <prompt> the two headed elvis clone is indeed popular.</prompt> </catch> <!-- dialog scoped match --> <catch event="bigfoot_event"> <prompt> lie za minell e, while being both the bride of bigfoot, and immensely popular to those with no taste or sense of artistic merit, is not nearly the most popular tabloid celebrity. </prompt> <!-- fans of liza minelli should always be disconnected immediately --> <disconnect/> </catch> <menu id="M1" scope="dialog" dtmf="true"> <prompt> Who is the most infamous celebrity in the weekly world news tabloid? </prompt> <prompt> <enumerate> For <value expr="_prompt"/>, press <value expr="_dtmf"/> </enumerate> </prompt> <choice event="bigfoot_event"> lie za manelly </choice> <choice event="bigfoot_event"> bride of bigfoot </choice> </menu> <menu id="M2" scope="document" dtmf="false"> <prompt>.</prompt> <!-- note that an empty prompt within this menu is neccessary to avoid a badfetch--> <choice event="batboy_event"> bat boy </choice> <choice event="elvis_event"> elvis clone <grammar xml:lang="en-us" root="TOPLEVEL"> <rule id="TOPLEVEL"> <item> <item repeat="0-1"> the </item> two headed elvis clone </item> </rule> </grammar> </choice> </menu> </vxml> |
| ANNOTATIONS: EXISTING POSTS |
pjamestx
|
|
| The description of the menu's id attribute leads one to believe that you can use a goto to navigate to a menu. However, the information on the goto tag seems to indicate that it can only target a URI or a form. Is it possible to goto a menu? | |
MattHenry
|
|
| Hiyas,
You can indeed use the <goto> to navigate to a <menu>, as long as it is properly formatted: <goto next="#MyMenuName"/> Let me know if you run into any problems. ~Matt |
|
shinde_pallavi
|
|
| In the above example, if the dtmf property of menu M2 were set to true, then which event would be thrown when the caller pressed dtmf-1? Would it be bigfoot_event or elvis_event? | |
MattHenry
|
|
| Note that in the event that M2 had it's dtmf property set to true, then our mappings would be as follows:
dtmf-1 = batboy_event dtmf-2 = elvis_event <menu id="M2" scope="document" dtmf="true"> <prompt> choose an event by pressing 1 or 2</prompt> <!-- note that an empty prompt within this menu is neccessary to avoid a badfetch--> <choice event="batboy_event"> bat boy </choice> <choice event="elvis_event"> elvis clone <grammar type="text/gsl">[(?the two headed elvis clone)]</grammar> </choice> </menu> ~Matt |
|
john.ament
|
|
| Just wondering if I could get a comment on how to get a timeout catch or invalid number catch? We use DTMF input only. For invalid numbers, I just assigned the extra numbers to the same event. Is there another way? | |
MattHenry
|
|
|
Hiya John, To catch either of these events, then you'd probably want to define a catch handler. As such, you'd be looking at something like this, for the sample code above: <menu id="M1" scope="dialog" dtmf="true"> <!-- 'wrong' keypress --> <nomatch> <audio src="InvalidInput.wav"/> <goto next="#M1"/> </nomatch> <!-- no keypress at all --> <noinput> <audio src="DidnthearAnything.wav"/> <goto next="#M1"/> </noinput> I should also mention that if you are looking to use DTMF input only, then you might want to turn off the voice reco altogether, by way of the 'inputmodes' property setting....check out 'Appendix H: Property Guide' for details. ~Matthew Henry |
|
john.ament
|
|
| Matt-
Thanks for the info. I had asked another question but dropped it after rereading the specifications. Thanks. |
|
mikethompson
|
|
| Hey John,
Glad we could help you out =^) Regards, Mike Thompson Voxeo Extreme Support |
|
bpcamac
|
|
| Subject : DTMF="#"
The voxeo test platform correctly announces the dtmf key # as the pound sign when enumerating the choices, but never recognizes it as a valid response eventhough it does recognize "1" and "*" in the example below. Any ideas why it doesn't work? Does the pound sign need to be escaped? Enclosing the key in single quotes produces parsing errors. <menu> <prompt> <enumerate> <value expr="_prompt"/> press <value expr="_dtmf"/>. </enumerate> </prompt> <choice next="#Menu1" dtmf="1"> To select the first choice </choice> <choice next="#Menu1" dtmf="*"> To select the second choice </choice> <choice next="#MainMenu" dtmf="#"> To return to the main menu </choice> </menu> |
|
MattHenry
|
|
|
Hi there, The '#' key isusually reserved as the default terminating character; you will need to change this default termchar if you want to use this as an option within your application. Check out "appendix H:property guide", and do a quick serach for the 'termchar' property to learn how you can get around this. ~Matt |
|
PUNUKA
|
|
| hi .. In w3c voicexml 2.0 and 2.1 how many max numbers of choices are allowed in the menu tag? in case of inputmode set as speech and not dtmf and suppose I specify a grammar tag inside the menu and the choices have their prompts(text) which one will be used as recognition grammar for use input? which takes precedence? is it the grammar or the choice prompts? I am currently testing a voicexml 2.1 compliant and I need to be exact about this? kindly help | |
MattHenry
|
|
|
Hi there, Let's try and address these questions one by one: Q:how many max numbers of choices are allowed in the menu tag? A: I haven't tested for any specific upper limit, but I would think that as along as your VXML document doesn't get to be above 1/2 MB, then you should be okay. In all honesty, for grmmars this complex, then you might want to think about simply writing an external grammar, and referencing it via the <field> element for easier management of your code. Q:in case of inputmode set as speech and not dtmf and suppose I specify a grammar tag inside the menu and the choices have their prompts(text) which one will be used as recognition grammar for use input? A: If inputmodes is set to "speech" then all DTMF reco will be ignored, of course. I haven't tested a menu with a choice grammar and a inline or external grammar, but I would assume that both would be active. However, this makes for ugly code. I would suggest sticking with one method or the other. Q: which takes precedence? is it the grammar or the choice prompts? A: Again, this isn't something that I have specifically tested for, but you can try setting different interpretation values for each, and confirming which of the two will take priority. ~Matt |
|
VXMLDud
|
|
| Is it possible to use the grammar element as a child of the choice element in a menu, while the menu attribute for DTMF is set to TRUE? The VoiceXML specification states that when an explicit DTMF sequence is given in the choice under such a scenario an error is thrown, and the grammar element may specify a DTMF sequence to be matched. E.g.
Also is there anything to stop us from specifying a grammar for some of the choices in a menu? See e.g. <menu> <choice next="http://www.sports.example.com/vxml/start.vxml"> <grammar src="sports.grxml" type="application/srgs+xml"/> Sports </choice> <choice next="http://www.weather.example.com/intro.vxml"> Weather </choice> <choice next="http://www.stargazer.example.com/voice/astronews.vxml"> Stargazer astrophysics news </choice> </menu> |
|
mikethompson
|
|
| Hello VXMLDud,
I did some testing around your questions and I have some information for you... I could not cause an error badfetch, per the documentation, when explicitly defining a DTMF value (for <choice), in conjunction with the DTMF attribute in <menu>. In the below code sample, I was able to get a successful match when using both dtmf="value" within <choice> and by using an inline grammar within choice. Of course, during both tests I had dtmf="true" within <menu>. <vxml version="2.0"> <!-- document scoped match --> <catch event="batboy_event"> <prompt> bat boy is always the life of the party.</prompt> </catch> <!-- document scoped match --> <catch event="elvis_event"> <prompt> You said the elvis clone. </prompt> </catch> <menu id="M2" scope="document" dtmf="true"> <prompt> choose an event by pressing 1 or 2</prompt> <choice event="batboy_event"> bat boy </choice> <choice event="elvis_event" dtmf="4"> elvis clone <!-- <grammar type="text/gsl">[dtmf-4]</grammar> --> </choice> </menu> </vxml> I'm going to discuss this with Engineering and see if we can make this behave more in line with the spec. Stay tuned, Mike Thompson Voxeo Corporation |
|
mikethompson
|
|
| Hello,
As an update, I wanted to let you know our Engineers are tracking the issue in internal bug ticket #490342. Once Voxeo Engineering has had a moment to diagnose the bug and make a fix, I will post back to this ticket with the information. Best, Mike Thompson Voxeo Corporation |
|
mikethompson
|
|
| Hello,
I spent some more time reviewing this issue with our Platform Engineers, and I have some information for you. After looking closer at the spec, it only defines the use of the DTMF attribute, not external grammars. As such, the example I used a while back is working as intended. However, *this* example should throw a error.badfetch: <vxml version="2.0"> <!-- document scoped match --> <catch event="big_boy"> <prompt> who's a big boy? You are.</prompt> </catch> <!-- document scoped match --> <catch event="pork"> <prompt> You chose pork chops.</prompt> </catch> <menu id="M2" scope="document" dtmf="true"> <prompt> choose an event by pressing 4</prompt> <!-- note that an empty prompt within this menu is neccessary to avoid a badfetch --> <choice event="big_boy" dtmf="5"> big boy </choice> <choice event="pork"> <!-- Pork chops --> <grammar type="text/gsl">[dtmf-4]</grammar> </choice> </menu> </vxml> However, the above example is *not* throwing an error.badfetch either. This is because our VXML Platform Engineers do not agree with the spec behavior in this scenario. It tends to put unnecessary constraints on the contents of the VXML document. In short, we've given the developer more control (and options) with the menu/choice combination. As such, the above snippet will allow the user to use "5" instead of cause the application to get a bad fetch. :) Please let me know if you have additional questions. Best, Mike Thompson Voxeo Corporation |
|
DeKey
|
|
| I have a question:
how do you retrieve the value of a menu that has been filled? I tried the following but it doesnt work... <menu id="mymenu" scope="document" dtmf="false"> <prompt> Please say one of the following choises: <enumerate/> </prompt> <choice next="#c1"accept="approximate">choice 1</choice> <choice next="#c2" accept="approximate">choice 2</choice> <choice next="#c3" accept="approximate">choice 3</choice> <choice next="#c" accept="approximate">choice 4</choice> </menu> <form id="c1" scope="dialog"> <block> <prompt> Did you say <value expr="document.mymenu"/>? </prompt> <exit/> </block> </form> |
|
voxeojeremyr
|
|
| Hi DeKey,
Because we have have left the menu form, the variable "menuchoice" is out of scope and no longer available. To get the last speech interpretation you can use this in your "c1" form: <value expr="application.lastresult$[0].interpretation"/> If you have any questions, please let us know. Thanks, Jeremy Richmond Voxeo Support |
|
DeKey
|
|
| This is an interesting approach (and it's working alright). But it raises two questions:
I) how do I submit the value of the menu (with submit tag) II) is there a way to ask for user confirmation (e.g. was your choice ??) while menu is on scope? |
|
VoxeoDustin
|
|
| Hey,
1) You can find some pretty good examples of using submit to send data off in our docs. You'll simply want to use the variable name you'd like to submit in the namelist attribute of submit. http://docs.voxeo.com/voicexml/2.0/submit.htm 2) Once you've stored the value of the response in a variable, you can then use a subsequent field with type="boolean" to get a yes/no response from the caller: <form id="Form_2"> <field name="Verify" type="boolean"> <prompt>You said <value expr="application.lastresult$.interpretation"/>. Is that correct? </prompt> <filled> <if cond="Verify"> <goto next="#Form_3"/> <else/> <goto next="#Menu_1"/> </filled> </field> </form> Cheers, Dustin |
|
chuchoomar
|
|
| 1. the element filled is a menu child?......or no it is possible?
2. is possible and how is possible that i have in a one menu with dtmf and voice recognition? |
|
VoxeoDustin
|
|
| Hey,
The filled element is only a valid child of field, which may be better suited for your purposes. http://docs.voxeo.com/voicexml/2.0/field.htm You can certainly look for both DTMF and voice input in the same field: <field name="F_1"> <grammar type="application/grammar+xml" mode="voice" xml:lang="en-us" root="VOICE"> <rule id="VOICE"> <one-of> <item> apples </item> <item> oranges </item> </one-of> </rule> </grammar> <grammar type="application/grammar+xml" mode="dtmf" xml:lang="en-us" root="DTMF"> <rule id="DTMF"> <one-of> <item> 1 </item> <item> 2 </item> </one-of> </rule> </grammar> <prompt> Press 1 or say apples for apples, press 2 or say oranges for oranges </prompt> <filled> <prompt> You selected <value expr="F_1"/> </prompt> </filled> </field> Thanks, Dustin |
|
crishvi
|
|
| hi,
According to the what you said the dtmf values are automatically assigned to the choice elements but what will happen if the number of choice elements exceed 10 ???.I mean will it recognise if i enter 11 through dtmf or try to take 1 for the current menu and take 1 for the next dialog like it does in the case of field . Thanks, Rishvi |
|
voxeojeff
|
|
| Hi Rishvi,
When you have dtmf set to 'true' in your <menu> element, it automatically assigns the first 9 choices to implicit dtmf values (assuming you have 9). If you wish to go beyond 9, I'd recommend setting them in the <choice> elements, as they will allow for DTMF sequences. For example: <?xml version="1.0" encoding="UTF-8"?> <vxml version = "2.1"> <catch event="Event_1 Event_2"> <prompt> <value expr="_message"/> </prompt> </catch> <menu id="menu"> <prompt> Would you like selection one or twelve? </prompt> <choice event="Event_1" dtmf="1" message="'you selected one'"> </choice> <choice event="Event_2" dtmf="12" message="'you selected twelve'"> </choice> </menu> </vxml> Pressing a dtmf-1 dtmf-2 sequence triggers Event_2's message. On the other hand, pressing dtmf-1 alone or followed by the pound sign (#) will trigger Event_1's message. The pound key is the default termchar, and can be used when you don't want to wait for your selection to register. Hope this helps, Jeff |
|
crishvi
|
|
| Thanks for the quick reply.You guys are doing a great job. | |
annuvinayak
|
|
| Hi,
I want to specify a similar action to take place for more then one DTMF choices. Can anyone suggest how I could do that. This is what I want to do: <menu id="M1" dtmf="true"> <prompt> Press one for sports or two for weather </prompt> <choice dtmf="1" next="#x" /> <choice dtmf="2" next="#y" /> <choice dtmf="3 4 5 6 7 8 9 0" next="#z" /> </menu> Thanks in advance! |
|
VoxeoDustin
|
|
| Hey,
The dtmf attribute of choice specifies a sequence of key presses necessary to match, so to enable the same target for multiple DTMF key presses, we'll have to specify a choice for each possible entry: <choice dtmf="3" next="#z" /> <choice dtmf="4" next="#z" /> <choice dtmf="5" next="#z" /> Cheers, Dustin |
|
mtatum111
|
|
| I have a question. Can you explain the difference between the dtmf attribute for <menu> and the dtmf attribute for <choice>. I am a little confused on that principal.
Thanks Melissa |
|
voxeoblehn
|
|
| Hi Melissa,
The dtmf attribute used in the <menu> element is a Boolean value of either true or false. By default, it will be specified to false, but if set to true it will assign the first 9 menu choices implied dtmf grammar values (unless the choices already have them explicitly assigned). Meaning, if you do not specifically set the dtmf attribute in your choices, the menu will assign them implied value from 1 to 9 on it own. Having said that, the dtmf attribute used in the <choice> element would be used to specifically assign a dtmf value to a choice, in example, the following: [code] <choice event="Event_1" dtmf="1" message="'you selected one'"> </choice> <choice event="Event_2" dtmf="12" message="'you selected twelve'"> </choice> [/code] In the instance of <choice>, we set purposely assign the dtmf values instead of the menu applying a value based on their order. Hope you find this helpful and if you have any further questions, please do not hesitate to contact us. Regards, Brian L. Voxeo Support |
|
mtatum111
|
|
| Brian, thanks so much. That makes perfect sense :) | |
mtatum111
|
|
| On this example from the vxml spec 2.0 - If the speaker says Astrology, then I understand that we are playing the msg "I did not understand what you said." which is a platform specific default msg for catch event nomatch. However, I don't understand why the system is then playing the msg "Welcome home. Say one of:xxx" Wouldn't this msg only be played if the <catch event="nomatch"> contained a <reprompt/>. Is this being assumed here. Thanks for any clarification. If the <reprompt/> is not part of the system defined <catch event="nomatch> then, I would think that the system would not play anything and the user would just say something like Sports to go to the next processing.
<?xml version="1.0" encoding="UTF-8"?> <vxml version="2.0" xmlns="http://www.w3.org/2001/vxml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2001/vxml http://www.w3.org/TR/voicexml20/vxml.xsd"> <menu> <prompt> Welcome home. Say one of: <enumerate/> </prompt> <choice next="http://www.sports.example.com/vxml/start.vxml"> Sports </choice> <choice next="http://www.weather.example.com/intro.vxml"> Weather </choice> <choice next="http://www.stargazer.example.com/voice/astronews.vxml"> Stargazer astrophysics news </choice> <noinput>Please say one of <enumerate/></noinput> </menu> </vxml> This dialog might proceed as follows: C: Welcome home. Say one of: sports; weather; Stargazer astrophysics news. H: Astrology. C: I did not understand what you said. (a platform-specific default message.) C: Welcome home. Say one of: sports; weather; Stargazer astrophysics news. H: sports. C: (proceeds to http://www.sports.example.com/vxml/start.vxml) |
|
jdyer
|
|
| Hi,
Looks like what is confusing you is the differences between he shorthand expressions [b]<nomatch>[/b] & [b]<noinput>[/b], so I am going to address both of them to hopefully clear things up a bit! [li]What you are seeing is a[b]<nomatch>[/b] which unless specified otherwise does play the platform specific wav file "I did not understand what you said" and then reprompts[/li] [li]The second question of why didn't is play the <noinput> message, this is only reserved for events such as when the application expects DTMF or voice input but receives none. [/li] Here are a few links on these elements that may clear this up a bit further -[url=http://docs.voxeo.com/voicexml/2.0/shorthandexceptions.htm?search=nomatch#anchor]Shorthand events[/url] -[url=http://docs.voxeo.com/voicexml/2.0/noinput.htm]NoInput[/url] -[url=http://docs.voxeo.com/voicexml/2.0/nomatch.htm]NoMatch[/url] Sure hope that helps, if there is anything else that we can do to assist please let us know! We are always more then happy to offer any assistance our developers may need! Regards, John Customer Engineer |
|
mtatum111
|
|
| John, thanks for the information. I understand the difference between the <nomatch> and <noinput>. I think my confusion come in because I didn't see a </reprompt>. Thanks for the links though. It looks like for the events that <reprompt/> is automatically builtin. Do you agree.
Nomatch The 'nomatch' exception will get thrown when the caller says something or presses a DTMF key for which the application cannot match to a grammar utterance in the application. Unless specifically handled, it will play the default error wave file, and reprompt the user. I was just confused because I though the conversation should sound like the following - see this example and it will hopefully explain what I am trying to ask. Thanks for any clarification. C: Welcome home. Say one of: sports; weather; Stargazer astrophysics news. H: Astrology. C: I did not understand what you said. (a platform-specific default message.) C: Since I didn't see a </reprompt> I thought that Caller would hear silence instead of - Welcome home. Say one of: sports; weather; Stargazer astrophysics news. H: Astrology. C: I did not understand what you said. (a platform-specific default message.) C: Welcome home. Say one of: sports; weather; Stargazer astrophysics news. H: sports. C: (proceeds to http://www.sports.example.com/vxml/start.vxml) H: sports. C: (proceeds to http://www.sports.example.com/vxml/start.vxml) |
|
mtatum111
|
|
| Just to clarify I guess my main question is the following
Is <reprompt/> automatically a part of <nomatch> or does it have to be specified. It seems that it has to be specified. For instance <nomatch> <prompt>I could not find a match </prompt> </nomatch> vs <nomatch> <prompt> I could not find a match </prompt> <reprompt/> </nomatch> Hope that this explains my question. |
|
jdyer
|
|
| You are correct, the default behavior if a [code][b]<nomatch>[/b][/code] has [b]not[/b] been specified is going to be as if it where specified with a <reprompt/>. If a [code][b]<nomatch>[/b][/code] is specified it will not reprompt unless specifically told to do so with use of the [code][b]<reprompt/>[/b][/code] element.
If you make use of the following: [code] <?xml version="1.0" encoding="UTF-8"?> <vxml version="2.0"> <menu> <prompt> Welcome home. Say one of: <enumerate/> </prompt> <choice next="http://www.sports.example.com/vxml/start.vxml"> Sports </choice> <choice next="http://www.weather.example.com/intro.vxml"> Weather </choice> <choice next="http://www.stargazer.example.com/voice/astronews.vxml"> Stargazer astrophysics news </choice> <noinput>Please say one of <enumerate/></noinput> </menu> <nomatch> <prompt> I could not find a match </prompt> </nomatch> </vxml> [/code] The result will be: C: Welcome home. Say one of: sports; weather; Stargazer astrophysics news. H: Astrology. C: I could not find a match (from the user defined [b]nomatch[/b]) H: <silence> C: Please say one of: sports; weather; Stargazer astrophysics news. (from the [b]noinput[/b]) H: sports. C: (proceeds to http://www.sports.example.com/vxml/start.vxml) Hope that clears things up a bit for you, please let us know if there are any other questions. We are certainly always more then happy to be off assistance! Regards, John Customer Engineer |
|
punkin
|
|
| <menu id="activities" accept="approximate" dtmf="true">
<prompt> <enumerate> For information about <value expr="_prompt"/> press <value expr="_dtmf"/> </enumerate> </prompt> <choice next="#apple">apple</choice> <choice next="#greengrapes" accept="exact">green seedless grapes</choice> <choice next="#redgrapes" accept="exact">red seedless grapes</choice> <nomatch> Sorry, you must choose one: <enumerate/> </nomatch> </menu> Voxeo TTS usually interprets and speaks very fast for option choices. It doesn't happen to Nuance, which will give a slightly pause before the choice and spell out clearly and slowly about which key to press. Is <break> the only choice to slow down the speak? Is there any better way to handle this? |
|
punkin
|
|
| I thought I had to give each <choice> with <break>. Instead, I could put <break> inside the <enumerate>. It is much easier.
<menu id="activities" accept="approximate" dtmf="true"> <prompt> <enumerate> For information about <value expr="_prompt"/> <break time="medium"/> press <value expr="_dtmf"/> <break time="large"/> </enumerate> </prompt> <choice next="#apple"> apple </choice> <choice next="#greengrapes" accept="exact"> green seedless grapes </choice> <choice next="#redgrapes" accept="exact"> red seedless grapes </choice> <nomatch> Sorry, you must choose one: <enumerate/> </nomatch> </menu> |
|
VoxeoDante
|
|
| Hello Punkin,
You are right on the Money! Putting the break in side of the enumerate will certainly accomplish what you are looking to doo with less additional code. You could also utilize the <prosody> tag to slow down the speech. Like so; <menu id="activities" accept="approximate" dtmf="true"> <prompt> <enumerate> <prosody rate="slow"> For information about <value expr="_prompt"/> press <value expr="_dtmf"/> </prosody> </enumerate> </prompt> <choice next="#apple">apple</choice> <choice next="#greengrapes" accept="exact">green seedless grapes</choice> <choice next="#redgrapes" accept="exact">red seedless grapes</choice> <nomatch> Sorry, you must choose one: <enumerate/> </nomatch> </menu> For more information on <prosody> you can take a look here in the elements table; http://www.vxml.org/prosody.htm I hope this helps. Cheers, Dante Vitulano |
|
punkin
|
|
| <prosody> with "slow" rate doesn't sound right in <choice>. <break> sounds better, especially the way it mimics a human pause. Using "x-slow" rate in <choice> is even horrible. Using <break> in <choice> sounds more natural in this case.
I can see <prosody> is handy for another purpose. Thanks. |
|
ciscox83
|
|
| Hi everyone.
I'm trying to move from a menu to a form field. The idea is something like this: <vxml> <menu id="menu"> <prompt>Choose where do you wanna go:</prompt> <choice next="#form_01/field_02">field</choice> </menu> <form id="form_01"> <field name="field_01"> <prompt>Hello, I'm field one</prompt> </field> <field name="field_02"> <prompt>Hello, I'm field two</prompt> </field> </form> </vxml> There is a way to navigate from a dialogue to directly another form field? Thanks, Christian |
|
VoxeoDustin
|
|
| Hey Christian,
There is not a way to move to a specific field within a form from outside that form. However, once in the form, you can use <goto nextitem="fieldname"/> to move to the field you wish. Regards, Dustin Hayre Solutions Engineer Voxeo Corporation |
|
splash
|
|
| Could anyone explain me how to the "menu" element to ask for a credit card number through dtmf. I can use the (field & filled) but would like to do it using menu | |
voxeoJason
|
|
| Hi,
To capture a string of numbers, <menu> really isn't the best choice. Would it be possible to let us know what your end goal is so we can better direct you on a solution that's applicable for your desired project? Regards, Jason Voxeo Support |
|
splash
|
|
| I am supposed to authenticate the customer with his 10 digit account number and i have built it using the "field"..
I am new to VXML so was wondering if i can do this using the "menu" |
|
voxeoJason
|
|
| If you're looking to capture those digits, a grammar is definitely the way to go. Menu is really only good to use if you're looking for a variety of different options. There's a much easier way to do a yes/ no type set up.
The best way to accomplish your project would be to use the digits [url=http://www.vxml.org/grxmlbuiltins.htm]builtin grammar[/url] to capture the numbers, and then a boolean builtin grammar with [url=http://www.vxml.org/if.htm]conditional statements[/url] for the confirmation option. Regards, Jason Voxeo Support |
|
SSA_PCS
|
|
| Hello,
I've probably missed something simple, but I would like my menu to only respond to defined choices and nothing else. Currently it plays "I did not understand what you said" when an undefined DTMF is sent, and a choice would, as far as I can tell, have to restart the message or play an empty prompt or something else. Can I have the menu completely ignore these and continue playing the message? I was considering trying something like <nomatch><prompt></prompt></nomatch>. Would this just play nothing when the key was pressed and continue playing the rest of the menu? |
|
VoxeoDustin
|
|
| Hello,
Yes. Adding a no match handler with an empty prompt should override the default nomatch prompt. Regards, Dustin Hayre Technical Account Lead Voxeo Corporation |
| login |