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
- supported version for cvp 3.1
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
104
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 10:51 AM
This document was generated from CDN thread
Created by: Janine Graves on 14-12-2006 10:33:00 PM
Hi,
What is the official version of Studio that is supported under CVP 3.1? I have customers wanting to use Studio 5.x with CVP 3.1, is this officially supported?
If not, do you foresee that it will be?
Also, does any version of Studio support any of the features of VXML 2.1 that weren't in VXML 2.0?
Using <mark> to Detect Barge-in During Prompt Playback
Using <data> to Fetch XML Without Requiring a Dialog Transition
Concatenating Prompts Dynamically Using <foreach>
Recording User Utterances While Attempting Recognition
Specifying the Media Format of Utterance Recordings
Adding namelist to <disconnect>
Adding type to <transfer>
Subject: RE: supported version for cvp 3.1
Replied by: Michael Bochynski on 14-12-2006 10:49:51 PM
Janine,
We have recently introduced support for CVP 3.1 gateways in Audium Studio 5.1. However, Call Services 3.6.X is required to run the applications created with Studio.
Please refer to the Software download section for details on the available Gateway Adapters:
http://www.audiumcentral.com/supportcenter/viewtopic.php?t=2752
Moreover, VoiceXML 2.1 support was entered into our feature tracking system.
Regards,
Michael
Subject: RE: supported version for cvp 3.1
Replied by: Janine Graves on 14-12-2006 10:55:52 PM
Thanks, but I don't understand the response.
Is call services 3.6 supported with CVP 3.1? If not, what good is having Studio available for CVP 3.1? If so, then is there a gateway adapter download for Server as well as Studio?
Thanks, Janine
Subject: RE: supported version for cvp 3.1
Replied by: Janine Graves on 14-12-2006 10:59:24 PM
Also, if the customer has CVP 3.1 and has been using CVP Studio 3.4 and if they want to upgrade to Studio 5.1.3 with the new adapters, what is the upgrade path they should take? As, they'll need to go from the old licensing scheme to the new Activation scheme.
All the customers want to move off CVP Studio 3.4, as there are so many nice features that have been added to Studio 5.1.3. So this question comes up all the time in training classes.
Thanks, Janine
Subject: Cisco CVP and Audium
Replied by: Cory Wright on 14-12-2006 11:21:55 PM
Janine,
Good question. Let me try and explain what we have currently and, generally, what we're looking at.
If a customer has CVP, they generally use the CVP development products -- which include CVP Studio and CVP VXML Server. Audium had referred to this set of products as our Cisco OEM version.
If a customer has Audium, they use the Audium products -- Audium Studio and Audium Call Services. Audium had referred to this as our "flagship" set of products.
The two product sets are not interchangeable today. So, you can't use an Audium product to build or deploy to a Cisco OEM product, and vice versa -- regardless of version.
The Audium flagship products have supported some flavors of CVP 3.0 in a past release, where the designation was that the target VXML output was for the v3.0 set of products called CVP inclusive of the Access Gateway doing the VXML interpretation. This is not true in the current Audium flagship release.
Rather, in the current release of the Audium flagship products -- Studio 5.1.3 and Call Services 3.6.4 -- we just released Gateway Adapters Pack Release 3, which includes support for CVP 3.1 targets with DTMF and OSR only. This enables Audium customers to use CVP 3.1 as a target. CVP 3.1 customers using the Cisco OEM versions (CVP Studio and CVP VXML Server) already have that capability; albeit, on a older version base.
The next release of CVP will have updated versions of CVP Studio and CVP VXML Server.
From an upgrade point of view, we think it's intuitive for the 2 products to converge; however, we want to be deliberate and thoughtful -- especially because of the size of the installed base and support process changes coming soon. Until then, we recommend that customers stick with one set of products or another.
Regards,
Cory
(Other OEM versions aren't discussed here, but generally, any OEM product is only supported with the other OEM products it is compatible with -- not Audium flagship products.)
Subject: Upgrade path
Replied by: Cory Wright on 14-12-2006 11:38:32 PM
Janine,
Regarding your question about customers with CVP 3.1 using CVP Studio 3.4 wanting to upgrade to Studio 5.1.3 with the new CVP 3.1 adapters, let me try and break it down.
Customers with CVP 3.1 using CVP Studio 3.4 are more than likely Cisco customers, not Audium customers, unless there was a change in midstream for some reason.
In this case, if they are considering moving from Cisco CVP Studio 3.4 to the Audium flagship products, it's really a wholesale change. They have to purchase and swap out to Audium Call Services 3.6.4 from CVP VXML Server as well as to the Audium Studio 5.1.3 product and then retest using the CVP 3.1 adapters for the Audium flagship products. Audium flagship products and Cisco OEM products cannot be mixed and matched.
Cisco is not currently offering the purchase of an upgrade conversion like this.
That makes sense, because it's a lot of extra work, unnecessarily, when the upcoming new CVP release will equalize the playing field between the two product sets; although it will not converge the two products.
Once that release comes out, then the stage is set for aligning the product sets so they make more sense. Until then, customers should keep them separate.
I'll also disclaim this post by saying that I'm talking to our entire installed base of both sets of products here, not any one particular customer situation. There could be situations on a customer by customer basis where the advice above wouldn't apply. In those cases, they'd work directly with their account team and Product Support Specialist to identify a solution that's appropriate for their situation.
Regards,
Cory
Subject: RE: Upgrade path
Replied by: Janine Graves on 15-12-2006 02:27:51 AM
Thanks for that clarification. Please tell me if this is correct:
For the Cisco customers, who have CVP 3.1 and are using the CVP Studio, they will not be able to upgrade to a newer vesion of Studio without upgrading their entire CVP suite (ICM, Combo Box, CVP VXML Server, etc.) to CVP 4.0, is that correct?
Subject: RE: Upgrade path
Replied by: null on 15-12-2006 05:25:56 AM
Janine, I bet this is so.
TAC support for these complex systems is very intensive. Coming from an ICM/IPCC background, I can tell you that TAC are very careful to check with you up front that you are running the correct "suite" of components on the correct hardware. It's too complex to allow it to be otherwise.
Furthermore, having played with CVP 4.0 (I was on the TOI in Brussels last week) there are certainly new elements in CVP Studio (like the ReqICMLabel element) that won't work without the support of the modified CVP 4.0 subsystems.
That said, I really wanted to see the "Documenter" work in Studio, but it would not draw the diagrams!
Regards,
Geoff
Subject: RE: Upgrade path
Replied by: Janine Graves on 15-12-2006 01:27:39 PM
Thanks Geoff,
I'm attaching a sample Documenter printout from a simple application. it's in RTF format. If you open it in WORD, you'll see the pictures. If you open in in WordPad then you won't see the pictures.
Subject: CVP 3.1 to 4.0
Replied by: Cory Wright on 15-12-2006 04:48:38 PM
Janine,
I don't think your statement is accurate in the breakout of the "entire CVP suite".
The way Cisco offers CVP is in a bundle that includes several products, and 4.0 does require upgrades across some of them, but not necessarily every one you mentioned. However, CVP Studio 3.1 is in CVP 3.1 and CVP Studio 4.0 is in CVP 4.0, so you'd necessarily upgrade to get the new features in CVP Studio 4.0.
In general, Cisco coordinates tremendous amounts of testing across it's whole voice product line to ensure compatibility.
But, anything related to a CVP 4 upgrade, the details of what has to be upgraded, and any customer situation specifics are beyond the scope of this forum. There should be lots of info on the Cisco.com and partner websites.
I'd direct anyone with questions of this nature to contact their Contact Center or Voice PSS and their Cisco Account Manager.
Regards,
Cory
Subject: RE: CVP 3.1 to 4.0
Replied by: null on 21-12-2006 04:29:22 AM
Janine,
No need to attach anything ... your answer was sufficient to point me in the right direction.
I was using CVP 4.0 on a Virtual Machine (VMWare) Windows 2003 Server at the Cisco TOI course, and it certainly did not have MS Word onboard - I was more than certainly looking at the RTF file with Wordpad.
Now that I open the same file in MS Word, I do see the diagrams and the more serious formatting.
Thanks for the tip.
Regards,
Geoff
Created by: Janine Graves on 14-12-2006 10:33:00 PM
Hi,
What is the official version of Studio that is supported under CVP 3.1? I have customers wanting to use Studio 5.x with CVP 3.1, is this officially supported?
If not, do you foresee that it will be?
Also, does any version of Studio support any of the features of VXML 2.1 that weren't in VXML 2.0?
Using <mark> to Detect Barge-in During Prompt Playback
Using <data> to Fetch XML Without Requiring a Dialog Transition
Concatenating Prompts Dynamically Using <foreach>
Recording User Utterances While Attempting Recognition
Specifying the Media Format of Utterance Recordings
Adding namelist to <disconnect>
Adding type to <transfer>
Subject: RE: supported version for cvp 3.1
Replied by: Michael Bochynski on 14-12-2006 10:49:51 PM
Janine,
We have recently introduced support for CVP 3.1 gateways in Audium Studio 5.1. However, Call Services 3.6.X is required to run the applications created with Studio.
Please refer to the Software download section for details on the available Gateway Adapters:
http://www.audiumcentral.com/supportcenter/viewtopic.php?t=2752
Moreover, VoiceXML 2.1 support was entered into our feature tracking system.
Regards,
Michael
Subject: RE: supported version for cvp 3.1
Replied by: Janine Graves on 14-12-2006 10:55:52 PM
Thanks, but I don't understand the response.
Is call services 3.6 supported with CVP 3.1? If not, what good is having Studio available for CVP 3.1? If so, then is there a gateway adapter download for Server as well as Studio?
Thanks, Janine
Subject: RE: supported version for cvp 3.1
Replied by: Janine Graves on 14-12-2006 10:59:24 PM
Also, if the customer has CVP 3.1 and has been using CVP Studio 3.4 and if they want to upgrade to Studio 5.1.3 with the new adapters, what is the upgrade path they should take? As, they'll need to go from the old licensing scheme to the new Activation scheme.
All the customers want to move off CVP Studio 3.4, as there are so many nice features that have been added to Studio 5.1.3. So this question comes up all the time in training classes.
Thanks, Janine
Subject: Cisco CVP and Audium
Replied by: Cory Wright on 14-12-2006 11:21:55 PM
Janine,
Good question. Let me try and explain what we have currently and, generally, what we're looking at.
If a customer has CVP, they generally use the CVP development products -- which include CVP Studio and CVP VXML Server. Audium had referred to this set of products as our Cisco OEM version.
If a customer has Audium, they use the Audium products -- Audium Studio and Audium Call Services. Audium had referred to this as our "flagship" set of products.
The two product sets are not interchangeable today. So, you can't use an Audium product to build or deploy to a Cisco OEM product, and vice versa -- regardless of version.
The Audium flagship products have supported some flavors of CVP 3.0 in a past release, where the designation was that the target VXML output was for the v3.0 set of products called CVP inclusive of the Access Gateway doing the VXML interpretation. This is not true in the current Audium flagship release.
Rather, in the current release of the Audium flagship products -- Studio 5.1.3 and Call Services 3.6.4 -- we just released Gateway Adapters Pack Release 3, which includes support for CVP 3.1 targets with DTMF and OSR only. This enables Audium customers to use CVP 3.1 as a target. CVP 3.1 customers using the Cisco OEM versions (CVP Studio and CVP VXML Server) already have that capability; albeit, on a older version base.
The next release of CVP will have updated versions of CVP Studio and CVP VXML Server.
From an upgrade point of view, we think it's intuitive for the 2 products to converge; however, we want to be deliberate and thoughtful -- especially because of the size of the installed base and support process changes coming soon. Until then, we recommend that customers stick with one set of products or another.
Regards,
Cory
(Other OEM versions aren't discussed here, but generally, any OEM product is only supported with the other OEM products it is compatible with -- not Audium flagship products.)
Subject: Upgrade path
Replied by: Cory Wright on 14-12-2006 11:38:32 PM
Janine,
Regarding your question about customers with CVP 3.1 using CVP Studio 3.4 wanting to upgrade to Studio 5.1.3 with the new CVP 3.1 adapters, let me try and break it down.
Customers with CVP 3.1 using CVP Studio 3.4 are more than likely Cisco customers, not Audium customers, unless there was a change in midstream for some reason.
In this case, if they are considering moving from Cisco CVP Studio 3.4 to the Audium flagship products, it's really a wholesale change. They have to purchase and swap out to Audium Call Services 3.6.4 from CVP VXML Server as well as to the Audium Studio 5.1.3 product and then retest using the CVP 3.1 adapters for the Audium flagship products. Audium flagship products and Cisco OEM products cannot be mixed and matched.
Cisco is not currently offering the purchase of an upgrade conversion like this.
That makes sense, because it's a lot of extra work, unnecessarily, when the upcoming new CVP release will equalize the playing field between the two product sets; although it will not converge the two products.
Once that release comes out, then the stage is set for aligning the product sets so they make more sense. Until then, customers should keep them separate.
I'll also disclaim this post by saying that I'm talking to our entire installed base of both sets of products here, not any one particular customer situation. There could be situations on a customer by customer basis where the advice above wouldn't apply. In those cases, they'd work directly with their account team and Product Support Specialist to identify a solution that's appropriate for their situation.
Regards,
Cory
Subject: RE: Upgrade path
Replied by: Janine Graves on 15-12-2006 02:27:51 AM
Thanks for that clarification. Please tell me if this is correct:
For the Cisco customers, who have CVP 3.1 and are using the CVP Studio, they will not be able to upgrade to a newer vesion of Studio without upgrading their entire CVP suite (ICM, Combo Box, CVP VXML Server, etc.) to CVP 4.0, is that correct?
Subject: RE: Upgrade path
Replied by: null on 15-12-2006 05:25:56 AM
Janine, I bet this is so.
TAC support for these complex systems is very intensive. Coming from an ICM/IPCC background, I can tell you that TAC are very careful to check with you up front that you are running the correct "suite" of components on the correct hardware. It's too complex to allow it to be otherwise.
Furthermore, having played with CVP 4.0 (I was on the TOI in Brussels last week) there are certainly new elements in CVP Studio (like the ReqICMLabel element) that won't work without the support of the modified CVP 4.0 subsystems.
That said, I really wanted to see the "Documenter" work in Studio, but it would not draw the diagrams!
Regards,
Geoff
Subject: RE: Upgrade path
Replied by: Janine Graves on 15-12-2006 01:27:39 PM
Thanks Geoff,
I'm attaching a sample Documenter printout from a simple application. it's in RTF format. If you open it in WORD, you'll see the pictures. If you open in in WordPad then you won't see the pictures.
Subject: CVP 3.1 to 4.0
Replied by: Cory Wright on 15-12-2006 04:48:38 PM
Janine,
I don't think your statement is accurate in the breakout of the "entire CVP suite".
The way Cisco offers CVP is in a bundle that includes several products, and 4.0 does require upgrades across some of them, but not necessarily every one you mentioned. However, CVP Studio 3.1 is in CVP 3.1 and CVP Studio 4.0 is in CVP 4.0, so you'd necessarily upgrade to get the new features in CVP Studio 4.0.
In general, Cisco coordinates tremendous amounts of testing across it's whole voice product line to ensure compatibility.
But, anything related to a CVP 4 upgrade, the details of what has to be upgraded, and any customer situation specifics are beyond the scope of this forum. There should be lots of info on the Cisco.com and partner websites.
I'd direct anyone with questions of this nature to contact their Contact Center or Voice PSS and their Cisco Account Manager.
Regards,
Cory
Subject: RE: CVP 3.1 to 4.0
Replied by: null on 21-12-2006 04:29:22 AM
Janine,
No need to attach anything ... your answer was sufficient to point me in the right direction.
I was using CVP 4.0 on a Virtual Machine (VMWare) Windows 2003 Server at the Cisco TOI course, and it certainly did not have MS Word onboard - I was more than certainly looking at the RTF file with Wordpad.
Now that I open the same file in MS Word, I do see the diagrams and the more serious formatting.
Thanks for the tip.
Regards,
Geoff
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