« Back to General Discussion - All Versions

CVP 3.x to 4.x question

Combination View Flat View Tree View
Threads [ Previous | Next ]
CVP 3.x to 4.x question
Answer
7/29/08 11:37 PM
After reviewing a customer scripts who we are looking at upgrading from CVP 3.x to 7.x, here are my findings:

=============================================
Data Passed from CVP to ICM:

Application="app name" (call.user.microapp.ToVXML[0]) RCK= (Call.user.microapp.ToExtVXML[0],";RCK=",Call.RouterCallKey)
ANI= (Call.user.microapp.ToExtVXML[0],";ANI=",Call.CallingLineID)
DNIS= (Call.user.microapp.ToExtVXML[0],";DNIS=",Call.DialedNumberString)

Here is the final list of values from CVP to ICM:

<setting name="caller_input">{Data.Session.Calltype}</setting>= PV2

<setting name="FromExtVXML0">{Data.Element.please_input_4digit_pin.value}</setting> =PV1

<setting name="FromExtVXML1">{Data.Element.amc_input_serial.value}</setting> =PV3

<setting name="FromExtVXML2">{Data.Element.amc_input_close_code.value}</setting> =PV4

<setting name="FromExtVXML3">{Data.Session.strReturnCode,Data.Session.strReturnDesc}</setting> =PV5

=============================================

Call.user.microapp.ToExtVXML[0] does this need to be an array variable to support migration to CVP 7.x?
Flag

Re: CVP 3.x to 4.x question
Answer
7/31/08 9:43 PM as a reply to ANDREW DIGNAN.
Towards CVP VXML:
Looks like you pass all your name value pairs in one ToExtVXML[] array element, namely element zero. Concatenated together using semi-colons. Something like:

application=MYAPP;RCK=wwww-xxxx-yyyy-zzzz;ANI=9995551212;DNIS=8005558888

Fine. Not the way I do it, but perfectly fine.

You can do the same in CVP 4 (7). (It already is an array variable so your question is odd).

Towards ICM.
You are filling in the mandatory caller_input and have a 4 element array of FromExtVXML[] data.

Fine. You can do the same in CVP 4(7).

When I migrated apps from CVP 3.0 to CVP 4.0, the only serious problem I can remember is that Cisco (Audium) dropped the ability to specify (create) session variables in the SubDialog Start. A huge change that required me to move all that initialization to the next node in the script. Most annoying. If they had told us why they did that, I would have been happy, but it seemed so arbitrary.

Regards,
Geoff
Flag