Cory Wright | 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.) |
| Please sign in to flag this as inappropriate. |