Cisco Cisco Customer Voice Portal 8.0(1)
2-59
Cisco Customer Voice Portal (CVP) Release 3.1(0) Configuration and Administration Guide
Chapter 2 Using NAM/ICM with the Customer Voice Portal IVR Solution
CVP Micro-Applications
Notes
•
The variables declared in the customer VXML must be named exactly as specified above. VXML is
case-sensitive.
case-sensitive.
•
The “caller-input” variable must be declared and used in the VXML. The only way that it is
acceptable to not populate this variable is if the external VXML is returning an error event.
Examples of error events include <badfetch>, <noinput>, and <nomatch>. If the “caller_input”
variable is not set to a value and an error event isn’t generated, the CVP assumes that a “No Entry”
error occurred.
acceptable to not populate this variable is if the external VXML is returning an error event.
Examples of error events include <badfetch>, <noinput>, and <nomatch>. If the “caller_input”
variable is not set to a value and an error event isn’t generated, the CVP assumes that a “No Entry”
error occurred.
•
The FromExtVXML variables are optional. You can use these variables if the “caller_input” variable
is not sufficient. If you are not using this additional data then the ECC Variable array does not need
to be defined.
is not sufficient. If you are not using this additional data then the ECC Variable array does not need
to be defined.
•
If the User.microapp.FromExtVXML ECC Variable array is undefined or partially defined, a
warning message appears when the App Server starts up on the VRU PIM console window.
warning message appears when the App Server starts up on the VRU PIM console window.
•
If you set an “FromExtVXML” variable in the external VXML, the User.microapp.FromExtVXML
must be defined on the ICM. If it isn’t, the CVP does not attempt to set the value and an error appears
on the VRU PIM console window. However, no error appears in the CVP log files.
must be defined on the ICM. If it isn’t, the CVP does not attempt to set the value and an error appears
on the VRU PIM console window. However, no error appears in the CVP log files.
•
If you need more than 210 characters but less than the full 1050 characters, you can declare the
User.microapp.FromExtVXML array to be less than four elements long. If you do this, you only use
the corresponding number of External VXML Variables. For example, if you configure a 2 element
“FromExtVXML” ECC Variable array, you can utilize the “caller_input”, “FromExtVXML0” and
“FromExtVXML1” VXML variables.
User.microapp.FromExtVXML array to be less than four elements long. If you do this, you only use
the corresponding number of External VXML Variables. For example, if you configure a 2 element
“FromExtVXML” ECC Variable array, you can utilize the “caller_input”, “FromExtVXML0” and
“FromExtVXML1” VXML variables.
•
If the external VXML sets a FromExtVXML variable to a value that is longer than the maximum
ECC Variable length, an error message appears in the VRU PIM console window and the value is
not set. No error appears in the CVP log files.
ECC Variable length, an error message appears in the VRU PIM console window and the value is
not set. No error appears in the CVP log files.
Sample External VXML Code
<?xml version=”1.0”>
<vxml version=”2.0”>
<var name="caller_input"/>
<form id=”getcredit”>
<field name=”input”>
<prompt>
What is your credit card type?
</prompt>
<help>
I am trying to collect your credit card type.
<reprompt/>
</help>
<nomatch>
<return event=”nomatch”/>
</nomatch>
<grammar src=”cctype.grxml” type=”application/srgs+xml”/>