Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet
- DevNet Collaboration
- Collaboration Knowledge Base
- Export Audio From CVP
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
475
Views
1
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-25-2014 10:30 AM
This document was generated from CDN thread
Created by: Jeff Russell on 12-02-2013 03:07:17 PM
After a user gives responses within an IVR (e.g. name, address, prescribers, etc.), I need to have their responses exported to an audio file(s) (.wav or .mp3) on a server in a pre-determined naming convention. Each "bundle" of audio responses (associated with an individual call) would then be FTP'd to a third party to be transcribed.
How do I export the audio responses captured by the elements within CVP (e.g. Form_With_Confirm, Record_With_Confirm, etc.)?
I cannot see any documentation mentioning how to do this.
Thanks!
Subject: RE: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training
Replied by: Hemal Mehta on 12-02-2013 03:38:43 PM
The best way to have the response stored as a wav file would be to use record element. However record is not subject to recognition and will not match against a grammar. So you have can have the user record their responses using the record element and then store it and ftp it.
You can look up the record element documentation, it is quite straightforward. You can specify the path etc in the settings. You can create your own filename for each audio and also have it ftpe’d.
For record you will need to make sure of your settings on the vxml gateway and make sure you allow for ample recording time etc.
Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, February 12, 2013 3:07 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training Forum: Export Audio From CVP
Jeff Russell has created a new message in the forum "Training Forum": -------------------------------------------------------------- After a user gives responses within an IVR (e.g. name, address, prescribers, etc.), I need to have their responses exported to an audio file(s) (.wav or .mp3) on a server in a pre-determined naming convention. Each "bundle" of audio responses (associated with an individual call) would then be FTP'd to a third party to be transcribed.
How do I export the audio responses captured by the elements within CVP (e.g. Form_With_Confirm, Record_With_Confirm, etc.)?
I cannot see any documentation mentioning how to do this.
Thanks!
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/11861519 or simply reply to this email.
Subject: RE: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training
Replied by: Janine Graves on 12-02-2013 03:47:41 PM
Hemal, Do you know if Cisco supports this feature of VXML 2.1:
Recording User Utterances While Attempting Recognition
Several elements defined in [VXML2] can instruct the interpreter to accept user input during execution. These elements include <field>, <initial>, <link>, <menu>, <record>, and <transfer>. VoiceXML 2.1 extends these elements to allow the interpreter to conditionally enable recording while simultaneously gathering input from the user.
To enable recording during recognition, set the value of the recordutterance property to true. If the recordutterance property is set to true in the current scope, the following three shadow variables are set on the application.lastresult$ object whenever the application.lastresult$ object is assigned (e.g. when a <link> is matched):
Table 8: recordutterance-related shadow variables
recording
The variable that stores a reference to the recording, or undefined if no audio is collected. Like the input item variable associated with a <record> element as described in section 2.3.6 of [VXML2], the implementation of this variable may vary between platforms.
recordingsize
The size of the recording in bytes, or undefined if no audio is collected.
recordingduration
The duration of the recording in milliseconds, or undefined if no audio is collected.
When these properties are set on the application.lastresult$ object, if an input item (as defined in section 2.3 of [VXML2]) has also been filled and has its shadow variables assigned, the interpreter must also assign recording, recordingsize, and recordingduration shadow variables for these input items, the values of which equal the corresponding properties of the application.lastresult$ object. For example, in the case of <link> and <menu>, since no input item has its shadow variables set, the interpreter only sets the application.lastresult$ properties.
Support for this feature is optional on <record>, and <transfer>. Platforms that support it set the aforementioned shadow variables on the associated form item variable and the corresponding properties on the application.lastresult$ object when the recordutterance property is set to true in an encompassing scope.
Like recordings created using the <record> tag, utterance recordings can be played back using the expr attribute on <audio>.
Like recordings created using the <record> tag, utterance recordings can be submitted to a document server via HTTP POST using the namelist attribute of the <submit>, <data>, and <subdialog> elements. The enctype attribute must be set to "multipart/form-data" [RFC2388], and the method attribute must be set to "post". To provide flexibility in the naming of the variable that is submitted to the document server, the interpreter must allow the utterance recording to be assigned to and posted via any valid ECMAScript variable.
In the following example, the dialog requests a city and state from the user. On the third recognition failure, the recording of the user's utterance is submitted to a document server.
<?xml version="1.0" encoding="UTF-8"?>
<vxml xmlns="http://www.w3.org/2001/vxml"
version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2001/vxml
http://www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.xsd">
<form>
<property name="recordutterance" value="true"/>
<field name="city_state">
<prompt>
Say a city and state.
</prompt>
<grammar type="application/srgs+xml" src="citystate.grxml"/>
<nomatch>
I'm sorry. I didn't get that.
<reprompt/>
</nomatch>
<nomatch count="3">
<var name="the_recording"
expr="application.lastresult$.recording"/>
<submit method="post"
enctype="multipart/form-data"
next="upload.cgi"
namelist="the_recording"/>
</nomatch>
</field>
</form>
</vxml>
7.1 Specifying the Media Format of Utterance Recordings
To specify the media format of the resulting recording, set the recordutterancetype property. Platforms must support the audio file formats specified in Appendix E of [VXML2]. Other formats may also be supported. The recordutterancetype property defaults to a platform-specific format which should be one of the required formats. If an unsupported media format is encountered during recognition, the platform throws an error.unsupported.format event which specifies the unsupported media format in its message variable. Note that the recordutterancetype property does not affect the <record> element.
8 Adding namelist to <disconnect>
As described in section 5.3.11 of [VXML2], the <disconnect> element causes the interpreter context to disconnect from the user. VoiceXML 2.1 extends the <disconnect> element to support the following attribute:
Table 9: <disconnect> Attributes
namelist
Variable names to be returned to the interpreter context. The default is to return no variables; this means the interpreter context will receive an empty ECMAScript object. If an undeclared variable is referenced in the namelist, then an error.semantic is thrown (5.1.1 of [VXML2]).
The <disconnect> namelist and the <exit> namelist are processed independently. If the interpreter executes both a <disconnect> namelist and an <exit> namelist, both sets of variables are available to the interpreter context. The precise mechanism by which these variables are made available to the interpreter context is platform specific.
Subject: RE: New Message from Janine Graves in Customer Voice Portal (CVP) - Trainin
Replied by: Hemal Mehta on 12-02-2013 04:16:43 PM
Janine,
Yes, that will work too and it is a better option if it works well . I believe I was able to test recordutterance in the past. However there are some issues with the path and there were some performance overheads associated with that on Cisco. I will need to go back and test it with new version.
I have used it on genesys platform and did not have any issue using recordutterance in the past.
Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, February 12, 2013 3:48 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Janine Graves in Customer Voice Portal (CVP) - Training Forum: RE: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training
Janine Graves has created a new message in the forum "Training Forum": -------------------------------------------------------------- Hemal, Do you know if Cisco supports this feature of VXML 2.1:
Recording User Utterances While Attempting Recognition
Several elements defined in [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2> can instruct the interpreter to accept user input during execution. These elements include <field>, <initial>, <link>, <menu>, <record>, and <transfer>. VoiceXML 2.1 extends these elements to allow the interpreter to conditionally enable recording while simultaneously gathering input from the user.
To enable recording during recognition, set the value of the recordutterance property to true. If the recordutterance property is set to true in the current scope, the following three shadow variables are set on the application.lastresult$ object whenever the application.lastresult$ object is assigned (e.g. when a <link> is matched):
Table 8: recordutterance-related shadow variables
recording
The variable that stores a reference to the recording, or undefined if no audio is collected. Like the input item variable associated with a <record> element as described in section 2.3.6<http://www.w3.org/TR/voicexml20/#dml2.3.6> of [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2>, the implementation of this variable may vary between platforms.
recordingsize
The size of the recording in bytes, or undefined if no audio is collected.
recordingduration
The duration of the recording in milliseconds, or undefined if no audio is collected.
When these properties are set on the application.lastresult$ object, if an input item (as defined in section 2.3<http://www.w3.org/TR/voicexml20/#dml2.3> of [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2>) has also been filled and has its shadow variables assigned, the interpreter must also assign recording, recordingsize, and recordingduration shadow variables for these input items, the values of which equal the corresponding properties of the application.lastresult$ object. For example, in the case of <link> and <menu>, since no input item has its shadow variables set, the interpreter only sets the application.lastresult$ properties.
Support for this feature is optional on <record>, and <transfer>. Platforms that support it set the aforementioned shadow variables on the associated form item variable and the corresponding properties on the application.lastresult$ object when the recordutterance property is set to true in an encompassing scope.
Like recordings created using the <record> tag, utterance recordings can be played back using the expr attribute on <audio>.
Like recordings created using the <record> tag, utterance recordings can be submitted to a document server via HTTP POST using the namelist attribute of the <submit>, <data>, and <subdialog> elements. The enctype attribute must be set to "multipart/form-data" [RFC2388<http://www.w3.org/TR/voicexml21/#ref_RFC2388>], and the method attribute must be set to "post". To provide flexibility in the naming of the variable that is submitted to the document server, the interpreter must allow the utterance recording to be assigned to and posted via any valid ECMAScript variable.
In the following example, the dialog requests a city and state from the user. On the third recognition failure, the recording of the user's utterance is submitted to a document server.
<?xml version="1.0" encoding="UTF-8"?>
<vxml xmlns="http://www.w3.org/2001/vxml"
version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2001/vxml
http://www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.xsd<http://www.w3.org/2001/vxml%20%0bhttp:/www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.xsd>">
<form>
<property name="recordutterance" value="true"/>
<field name="city_state">
<prompt>
Say a city and state.
</prompt>
<grammar type="application/srgs+xml" src="citystate.grxml"/>
<nomatch>
I'm sorry. I didn't get that.
<reprompt/>
</nomatch>
<nomatch count="3">
<var name="the_recording"
expr="application.lastresult$.recording"/>
<submit method="post"
enctype="multipart/form-data"
next="upload.cgi"
namelist="the_recording"/>
</nomatch>
</field>
</form>
</vxml>
7.1 Specifying the Media Format of Utterance Recordings
To specify the media format of the resulting recording, set the recordutterancetype property. Platforms must support the audio file formats specified in Appendix E of [VXML2<http://www.w3.org/TR/voicexml21/#ref_VXML2>]. Other formats may also be supported. The recordutterancetype property defaults to a platform-specific format which should be one of the required formats. If an unsupported media format is encountered during recognition, the platform throws an error.unsupported.format event which specifies the unsupported media format in its message variable. Note that the recordutterancetype property does not affect the <record> element.
8 Adding namelist to <disconnect>
As described in section 5.3.11<http://www.w3.org/TR/2004/REC-voicexml20-20040316/#dml5.3.11> of [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2>, the <disconnect> element causes the interpreter context to disconnect from the user. VoiceXML 2.1 extends the <disconnect> element to support the following attribute:
Table 9: <disconnect> Attributes
namelist
Variable names to be returned to the interpreter context. The default is to return no variables; this means the interpreter context will receive an empty ECMAScript object. If an undeclared variable is referenced in the namelist, then an error.semantic is thrown (5.1.1<http://www.w3.org/TR/2004/REC-voicexml20-20040316/#dml5.1.1> of [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2>).
The <disconnect> namelist and the <exit> namelist are processed independently. If the interpreter executes both a <disconnect> namelist and an <exit> namelist, both sets of variables are available to the interpreter context. The precise mechanism by which these variables are made available to the interpreter context is platform specific.
Hemal Mehta:
The best way to have the response stored as a wav file would be to use record element. However record is not subject to recognition and will not match against a grammar. So you have can have the user record their responses using the record element and then store it and ftp it.
You can look up the record element documentation, it is quite straightforward. You can specify the path etc in the settings. You can create your own filename for each audio and also have it ftpe’d.
For record you will need to make sure of your settings on the vxml gateway and make sure you allow for ample recording time etc.
Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, February 12, 2013 3:07 PM
To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>
Subject: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training Forum: Export Audio From CVP
Jeff Russell has created a new message in the forum "Training Forum": -------------------------------------------------------------- After a user gives responses within an IVR (e.g. name, address, prescribers, etc.), I need to have their responses exported to an audio file(s) (.wav or .mp3) on a server in a pre-determined naming convention. Each "bundle" of audio responses (associated with an individual call) would then be FTP'd to a third party to be transcribed.
How do I export the audio responses captured by the elements within CVP (e.g. Form_With_Confirm, Record_With_Confirm, etc.)?
I cannot see any documentation mentioning how to do this.
Thanks!
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/11861519 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/11863865 or simply reply to this email.
Created by: Jeff Russell on 12-02-2013 03:07:17 PM
After a user gives responses within an IVR (e.g. name, address, prescribers, etc.), I need to have their responses exported to an audio file(s) (.wav or .mp3) on a server in a pre-determined naming convention. Each "bundle" of audio responses (associated with an individual call) would then be FTP'd to a third party to be transcribed.
How do I export the audio responses captured by the elements within CVP (e.g. Form_With_Confirm, Record_With_Confirm, etc.)?
I cannot see any documentation mentioning how to do this.
Thanks!
Subject: RE: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training
Replied by: Hemal Mehta on 12-02-2013 03:38:43 PM
The best way to have the response stored as a wav file would be to use record element. However record is not subject to recognition and will not match against a grammar. So you have can have the user record their responses using the record element and then store it and ftp it.
You can look up the record element documentation, it is quite straightforward. You can specify the path etc in the settings. You can create your own filename for each audio and also have it ftpe’d.
For record you will need to make sure of your settings on the vxml gateway and make sure you allow for ample recording time etc.
Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, February 12, 2013 3:07 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training Forum: Export Audio From CVP
Jeff Russell has created a new message in the forum "Training Forum": -------------------------------------------------------------- After a user gives responses within an IVR (e.g. name, address, prescribers, etc.), I need to have their responses exported to an audio file(s) (.wav or .mp3) on a server in a pre-determined naming convention. Each "bundle" of audio responses (associated with an individual call) would then be FTP'd to a third party to be transcribed.
How do I export the audio responses captured by the elements within CVP (e.g. Form_With_Confirm, Record_With_Confirm, etc.)?
I cannot see any documentation mentioning how to do this.
Thanks!
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/11861519 or simply reply to this email.
Subject: RE: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training
Replied by: Janine Graves on 12-02-2013 03:47:41 PM
Hemal, Do you know if Cisco supports this feature of VXML 2.1:
Recording User Utterances While Attempting Recognition
Several elements defined in [VXML2] can instruct the interpreter to accept user input during execution. These elements include <field>, <initial>, <link>, <menu>, <record>, and <transfer>. VoiceXML 2.1 extends these elements to allow the interpreter to conditionally enable recording while simultaneously gathering input from the user.
To enable recording during recognition, set the value of the recordutterance property to true. If the recordutterance property is set to true in the current scope, the following three shadow variables are set on the application.lastresult$ object whenever the application.lastresult$ object is assigned (e.g. when a <link> is matched):
Table 8: recordutterance-related shadow variables
recording
The variable that stores a reference to the recording, or undefined if no audio is collected. Like the input item variable associated with a <record> element as described in section 2.3.6 of [VXML2], the implementation of this variable may vary between platforms.
recordingsize
The size of the recording in bytes, or undefined if no audio is collected.
recordingduration
The duration of the recording in milliseconds, or undefined if no audio is collected.
When these properties are set on the application.lastresult$ object, if an input item (as defined in section 2.3 of [VXML2]) has also been filled and has its shadow variables assigned, the interpreter must also assign recording, recordingsize, and recordingduration shadow variables for these input items, the values of which equal the corresponding properties of the application.lastresult$ object. For example, in the case of <link> and <menu>, since no input item has its shadow variables set, the interpreter only sets the application.lastresult$ properties.
Support for this feature is optional on <record>, and <transfer>. Platforms that support it set the aforementioned shadow variables on the associated form item variable and the corresponding properties on the application.lastresult$ object when the recordutterance property is set to true in an encompassing scope.
Like recordings created using the <record> tag, utterance recordings can be played back using the expr attribute on <audio>.
Like recordings created using the <record> tag, utterance recordings can be submitted to a document server via HTTP POST using the namelist attribute of the <submit>, <data>, and <subdialog> elements. The enctype attribute must be set to "multipart/form-data" [RFC2388], and the method attribute must be set to "post". To provide flexibility in the naming of the variable that is submitted to the document server, the interpreter must allow the utterance recording to be assigned to and posted via any valid ECMAScript variable.
In the following example, the dialog requests a city and state from the user. On the third recognition failure, the recording of the user's utterance is submitted to a document server.
<?xml version="1.0" encoding="UTF-8"?>
<vxml xmlns="http://www.w3.org/2001/vxml"
version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2001/vxml
http://www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.xsd">
<form>
<property name="recordutterance" value="true"/>
<field name="city_state">
<prompt>
Say a city and state.
</prompt>
<grammar type="application/srgs+xml" src="citystate.grxml"/>
<nomatch>
I'm sorry. I didn't get that.
<reprompt/>
</nomatch>
<nomatch count="3">
<var name="the_recording"
expr="application.lastresult$.recording"/>
<submit method="post"
enctype="multipart/form-data"
next="upload.cgi"
namelist="the_recording"/>
</nomatch>
</field>
</form>
</vxml>
7.1 Specifying the Media Format of Utterance Recordings
To specify the media format of the resulting recording, set the recordutterancetype property. Platforms must support the audio file formats specified in Appendix E of [VXML2]. Other formats may also be supported. The recordutterancetype property defaults to a platform-specific format which should be one of the required formats. If an unsupported media format is encountered during recognition, the platform throws an error.unsupported.format event which specifies the unsupported media format in its message variable. Note that the recordutterancetype property does not affect the <record> element.
8 Adding namelist to <disconnect>
As described in section 5.3.11 of [VXML2], the <disconnect> element causes the interpreter context to disconnect from the user. VoiceXML 2.1 extends the <disconnect> element to support the following attribute:
Table 9: <disconnect> Attributes
namelist
Variable names to be returned to the interpreter context. The default is to return no variables; this means the interpreter context will receive an empty ECMAScript object. If an undeclared variable is referenced in the namelist, then an error.semantic is thrown (5.1.1 of [VXML2]).
The <disconnect> namelist and the <exit> namelist are processed independently. If the interpreter executes both a <disconnect> namelist and an <exit> namelist, both sets of variables are available to the interpreter context. The precise mechanism by which these variables are made available to the interpreter context is platform specific.
Hemal Mehta:The best way to have the response stored as a wav file would be to use record element. However record is not subject to recognition and will not match against a grammar. So you have can have the user record their responses using the record element and then store it and ftp it.
You can look up the record element documentation, it is quite straightforward. You can specify the path etc in the settings. You can create your own filename for each audio and also have it ftpe’d.
For record you will need to make sure of your settings on the vxml gateway and make sure you allow for ample recording time etc.
Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, February 12, 2013 3:07 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training Forum: Export Audio From CVP
Jeff Russell has created a new message in the forum "Training Forum": -------------------------------------------------------------- After a user gives responses within an IVR (e.g. name, address, prescribers, etc.), I need to have their responses exported to an audio file(s) (.wav or .mp3) on a server in a pre-determined naming convention. Each "bundle" of audio responses (associated with an individual call) would then be FTP'd to a third party to be transcribed.
How do I export the audio responses captured by the elements within CVP (e.g. Form_With_Confirm, Record_With_Confirm, etc.)?
I cannot see any documentation mentioning how to do this.
Thanks!
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/11861519 or simply reply to this email.
Subject: RE: New Message from Janine Graves in Customer Voice Portal (CVP) - Trainin
Replied by: Hemal Mehta on 12-02-2013 04:16:43 PM
Janine,
Yes, that will work too and it is a better option if it works well . I believe I was able to test recordutterance in the past. However there are some issues with the path and there were some performance overheads associated with that on Cisco. I will need to go back and test it with new version.
I have used it on genesys platform and did not have any issue using recordutterance in the past.
Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, February 12, 2013 3:48 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Janine Graves in Customer Voice Portal (CVP) - Training Forum: RE: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training
Janine Graves has created a new message in the forum "Training Forum": -------------------------------------------------------------- Hemal, Do you know if Cisco supports this feature of VXML 2.1:
Recording User Utterances While Attempting Recognition
Several elements defined in [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2> can instruct the interpreter to accept user input during execution. These elements include <field>, <initial>, <link>, <menu>, <record>, and <transfer>. VoiceXML 2.1 extends these elements to allow the interpreter to conditionally enable recording while simultaneously gathering input from the user.
To enable recording during recognition, set the value of the recordutterance property to true. If the recordutterance property is set to true in the current scope, the following three shadow variables are set on the application.lastresult$ object whenever the application.lastresult$ object is assigned (e.g. when a <link> is matched):
Table 8: recordutterance-related shadow variables
recording
The variable that stores a reference to the recording, or undefined if no audio is collected. Like the input item variable associated with a <record> element as described in section 2.3.6<http://www.w3.org/TR/voicexml20/#dml2.3.6> of [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2>, the implementation of this variable may vary between platforms.
recordingsize
The size of the recording in bytes, or undefined if no audio is collected.
recordingduration
The duration of the recording in milliseconds, or undefined if no audio is collected.
When these properties are set on the application.lastresult$ object, if an input item (as defined in section 2.3<http://www.w3.org/TR/voicexml20/#dml2.3> of [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2>) has also been filled and has its shadow variables assigned, the interpreter must also assign recording, recordingsize, and recordingduration shadow variables for these input items, the values of which equal the corresponding properties of the application.lastresult$ object. For example, in the case of <link> and <menu>, since no input item has its shadow variables set, the interpreter only sets the application.lastresult$ properties.
Support for this feature is optional on <record>, and <transfer>. Platforms that support it set the aforementioned shadow variables on the associated form item variable and the corresponding properties on the application.lastresult$ object when the recordutterance property is set to true in an encompassing scope.
Like recordings created using the <record> tag, utterance recordings can be played back using the expr attribute on <audio>.
Like recordings created using the <record> tag, utterance recordings can be submitted to a document server via HTTP POST using the namelist attribute of the <submit>, <data>, and <subdialog> elements. The enctype attribute must be set to "multipart/form-data" [RFC2388<http://www.w3.org/TR/voicexml21/#ref_RFC2388>], and the method attribute must be set to "post". To provide flexibility in the naming of the variable that is submitted to the document server, the interpreter must allow the utterance recording to be assigned to and posted via any valid ECMAScript variable.
In the following example, the dialog requests a city and state from the user. On the third recognition failure, the recording of the user's utterance is submitted to a document server.
<?xml version="1.0" encoding="UTF-8"?>
<vxml xmlns="http://www.w3.org/2001/vxml"
version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2001/vxml
http://www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.xsd<http://www.w3.org/2001/vxml%20%0bhttp:/www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.xsd>">
<form>
<property name="recordutterance" value="true"/>
<field name="city_state">
<prompt>
Say a city and state.
</prompt>
<grammar type="application/srgs+xml" src="citystate.grxml"/>
<nomatch>
I'm sorry. I didn't get that.
<reprompt/>
</nomatch>
<nomatch count="3">
<var name="the_recording"
expr="application.lastresult$.recording"/>
<submit method="post"
enctype="multipart/form-data"
next="upload.cgi"
namelist="the_recording"/>
</nomatch>
</field>
</form>
</vxml>
7.1 Specifying the Media Format of Utterance Recordings
To specify the media format of the resulting recording, set the recordutterancetype property. Platforms must support the audio file formats specified in Appendix E of [VXML2<http://www.w3.org/TR/voicexml21/#ref_VXML2>]. Other formats may also be supported. The recordutterancetype property defaults to a platform-specific format which should be one of the required formats. If an unsupported media format is encountered during recognition, the platform throws an error.unsupported.format event which specifies the unsupported media format in its message variable. Note that the recordutterancetype property does not affect the <record> element.
8 Adding namelist to <disconnect>
As described in section 5.3.11<http://www.w3.org/TR/2004/REC-voicexml20-20040316/#dml5.3.11> of [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2>, the <disconnect> element causes the interpreter context to disconnect from the user. VoiceXML 2.1 extends the <disconnect> element to support the following attribute:
Table 9: <disconnect> Attributes
namelist
Variable names to be returned to the interpreter context. The default is to return no variables; this means the interpreter context will receive an empty ECMAScript object. If an undeclared variable is referenced in the namelist, then an error.semantic is thrown (5.1.1<http://www.w3.org/TR/2004/REC-voicexml20-20040316/#dml5.1.1> of [VXML2]<http://www.w3.org/TR/voicexml21/#ref_VXML2>).
The <disconnect> namelist and the <exit> namelist are processed independently. If the interpreter executes both a <disconnect> namelist and an <exit> namelist, both sets of variables are available to the interpreter context. The precise mechanism by which these variables are made available to the interpreter context is platform specific.
Hemal Mehta:
The best way to have the response stored as a wav file would be to use record element. However record is not subject to recognition and will not match against a grammar. So you have can have the user record their responses using the record element and then store it and ftp it.
You can look up the record element documentation, it is quite straightforward. You can specify the path etc in the settings. You can create your own filename for each audio and also have it ftpe’d.
For record you will need to make sure of your settings on the vxml gateway and make sure you allow for ample recording time etc.
Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, February 12, 2013 3:07 PM
To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>
Subject: New Message from Jeff Russell in Customer Voice Portal (CVP) - Training Forum: Export Audio From CVP
Jeff Russell has created a new message in the forum "Training Forum": -------------------------------------------------------------- After a user gives responses within an IVR (e.g. name, address, prescribers, etc.), I need to have their responses exported to an audio file(s) (.wav or .mp3) on a server in a pre-determined naming convention. Each "bundle" of audio responses (associated with an individual call) would then be FTP'd to a third party to be transcribed.
How do I export the audio responses captured by the elements within CVP (e.g. Form_With_Confirm, Record_With_Confirm, etc.)?
I cannot see any documentation mentioning how to do this.
Thanks!
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/11861519 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/11863865 or simply reply to this email.
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents